OK so I'm trying to downgrade my phone from Honeycomb to gingerbread. Thus far I've unlocked the bootloader, installed super user, well anyway I'm at the point of installing the RUU. According to globaltrons guide, my flyer which is a 16 gig wifi US only model, should use one of the brightstar firmwares. Well I tried both and I get an UNKNOWN ERROR 1555 telling me I have the wrong RUU. Now my flyer is sitting here draining the battery and I can't get it to turn off. And can someone just tell me what RUU I need? I'm sure all 16 gig us flyers are the same anyway. Its the refirb from buy.com. Anyone else who bought one probably has the same RUU
Alright help just isn't coming fast enough so I finally got it to shut off. I just remembered the 3 button trick from my captivate and waddayaknow it worked on the flyer. Now I'm going to try again and see what RUU i'm supposed to run.
Alright now that I'm out of that mess I checked the CID again and its BS_US001, and according to the guide, I should use a brightstar RUU. Well there are 2 and I tried both and both told me I'm using the wrong one. So what the hell?
i would try following this guide
http://forum.xda-developers.com/showthread.php?t=1358758
If you need to get to fast boot you should be able to do that by holding power and volume down for around 20 seconds
Do you have the Fastboot drivers installed?
I should have fastboot drivers installed. I mean I've connected it fastboot and ran many adb commands...doesn't that mean fastboot drivers are installed? Also the RUU gets to "signature verification" and fails every time!! I actually went back through and changed the version number to the version number of the other brightside ruu and same issue! Globaltron's guide must be wrong.
Anyway my tab is running right now on stock honeycomb, just no progress is being made here and its frustrating the hell out of me! I've been stuck on the same damn step for 2 days now!
the link for the BASE RUU you need is http://hyuh.net/files/flyer/RUU_US_WIFI_B10.zip
This will get the device charging again, howver you will then have to flash a custom ROM,
Globatrons Guide will show you how to use the light version i have linked to.
Any questions just as as i have done the process lots of times
Give me the details of where you started from and what you did. I think you missed a couple steps
Alright cool, but does it turn off security? I still got S-on as I need that RUU installed so I can disable it.
Cor-master said:
I should have fastboot drivers installed. I mean I've connected it fastboot and ran many adb commands...doesn't that mean fastboot drivers are installed? Also the RUU gets to "signature verification" and fails every time!! I actually went back through and changed the version number to the version number of the other brightside ruu and same issue! Globaltron's guide must be wrong.
Click to expand...
Click to collapse
Ok well boot the device into fastboot then put the file i have linked tointo the same folder as your fastboot normall C:/android/Android-skd-windows/Tools
Then run the following commands
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <downloaded file name>
Flashing will fail with Error 90 first time due to hboot change (this is normal)
fastboot flash zip <downloaded file name>
The on screen indicator on the phone will not reach fully to the right end of the progress bar, this is ok
fastboot reboot
---------- Post added at 12:42 AM ---------- Previous post was at 12:38 AM ----------
Cor-master said:
Alright cool, but does it turn off security? I still got S-on as I need that RUU installed so I can disable it.
Click to expand...
Click to collapse
Ahhh, with it being S-ON Nots ure this will work. :/ Sorry Dude
MCNord Any ideas ?
mcord11758 said:
Give me the details of where you started from and what you did. I think you missed a couple steps
Click to expand...
Click to collapse
I first unlocked the tablet through HTC developers. Then I followed step by step and installed revolutionary, and then used revolutionary to install super user permissions. I then ran this command:
fastboot getvar cid
To get the CID. The CID came back as BS_US001. So I looked at Globaltrons guide and according to it, the ones that say "Brightstar" are the ones I need. 2 came up, but the numbers that were supposed to match, matched on both, so I just picked one. the download was capped so bad from that file sharing site that I just let it download overnight and went to bed.
So today I resumed my work. I next ran these commands
adb push misc_version /data/local/misc_version
adb shell
$ su
# chmod 777 /data/local/misc_version
# /data/local/misc_version -s (whatever the version number was)
and then I rebooted into fastboot, ran the first RUU and UNKNOWN ERROR
So I repeated the last steps with the other RUU and UNKNOWN ERROR...
Cor-master said:
I first unlocked the tablet through HTC developers. Then I followed step by step and installed revolutionary, and then used revolutionary to install super user permissions. I then ran this command:
fastboot getvar cid
To get the CID. The CID came back as BS_US001. So I looked at Globaltrons guide and according to it, the ones that say "Brightstar" are the ones I need. 2 came up, but the numbers that were supposed to match, matched on both, so I just picked one. the download was capped so bad from that file sharing site that I just let it download overnight and went to bed.
So today I resumed my work. I next ran these commands
adb push misc_version /data/local/misc_version
adb shell
$ su
# chmod 777 /data/local/misc_version
# /data/local/misc_version -s (whatever the version number was)
and then I rebooted into fastboot, ran the first RUU and UNKNOWN ERROR
So I repeated the last steps with the other RUU and UNKNOWN ERROR...
Click to expand...
Click to collapse
Are you S-Off Yet ?
If yes try the file i suggested, its quick and easy and then allow you to flash custom roms
p.s. i will be able to stop up until you get this sorted. So we will try it now
I'm not because if I read correctly I have to be on gingerbread to turn it off. And thats where I'm at now. The tablet has stock Honeycomb 3.2 installed. I'm basically just trying to get from stock honeycomb, to honeycomb with S-off if that helps.
Were you on hc or gb, does your bootloader say soff, what is your end game here
I got my tablet on February 29th and did the ota update to honeycomb as soon as I had it. I've kept it stock till now. My end point is honeycomb with S-off basically. If I can get to honeycomb S-off without going back to gingerbread first than I'm all for it, but if I read correctly, you have to be on gingerbread with s-off to go to honeycomb with s-off.
After all that I figured I might install leedroid.
Cor-master said:
I'm not because if I read correctly I have to be on gingerbread to turn it off. And thats where I'm at now. The tablet has stock Honeycomb 3.2 installed. I'm basically just trying to get from stock honeycomb, to honeycomb with S-off if that helps.
Click to expand...
Click to collapse
Ok i understand where you are now , firstly are you still getting the problem where your device isn't charging ?
And the RUU you have downloaded is definitely correct ?
Man do I miss my captivate. It was as simple as #1. Plug in computer. #2. Install super one click, and you could install any rom you wanted... but it didn't have a security lock, nor did it ever have a locked bootloader either.
ioiwillioi said:
Ok i understand where you are now , firstly are you still getting the problem where your device isn't charging ?
And the RUU you have downloaded is definitely correct ?
Click to expand...
Click to collapse
Oh sorry, no I got my tablet to reboot. Its sitting on my desk idling in stock honeycomb right now. And it charges fine. I just can't get an RUU to run. There are 2 brightstars so I downloaded both, and neither work. Maybe there's a third one , but according the CID the brightstar one SHOULD work, it just doesn't. According the readme with the RUU the error I"m getting means incorrect RUU.
Ex captivate user here as well, yea this is a bit more
Did you relock bootloader prior to attempting ruu
Cor-master said:
Oh sorry, no I got my tablet to reboot. Its sitting on my desk idling in stock honeycomb right now. And it charges fine. I just can't get an RUU to run. There are 2 brightstars so I downloaded both, and neither work. Maybe there's a third one , but according the CID the brightstar one SHOULD work, it just doesn't. According the readme with the RUU the error I"m getting means incorrect RUU.
Click to expand...
Click to collapse
Just tried downloading them to check the RUU and the link seems to be broken, did your deffinately download ok ?
Whats the filesize, GLobatrons guide has been spot on for hundreds of users
no its still unlocked. I just had a thought here. 2 ideas actually. #1. I don't have an sd card currently in, as I never bought one for my flyer. On the steps that required an sd card I just pulled the one from my phone. I dunno maybe the RUU wants to copy itsself to the SD-card but can't because its not there. Also #2. I did reinstall my apps last night so I could use my tablet today, which are all in the internal storage. If I wipe my tablet and put an SD-card in, might that fix the problem?
Related
Evening!!
I'm hoping you all might be able to help me out here. I have been running the OTA GB ROM for months now. Tonight I rebooted my phone by just holding the power button and hitting reboot. Its now however stuck on the HTC screen and won't boot past it.
I can get into the FASTBOOT menu and such, however when I try to go into the RECOVERY the phone just shuts off, or it will just reboot back into the HTC screen. I've tried download the Rezound_All-In-One_Kit_v2.0 and was able to flash the recovery again however I'm getting the same results, phone just shuts off.
Any idea on how to get my phone back? I really don't care about the data on the phone, just want to get it backup and working. lol I'm really confused as to why all the sudden its getting stuck on the HTC screen.
Did you try removing the battery and putting it back in?
are you rooted? which recovery?
I'm using Amon Ra style vigor and I am unlocked/rooted.
I'm trying to get ADB to detect my phone, but not having luck in that realm either. Was just going to try to push a ROM over to the phone. However it does not appear that it will detect my phone when in the FASTBOOT USB mode. I do a adb devices and it just comes back as none being found...
Kabish said:
I'm using Amon Ra style vigor and I am unlocked/rooted.
Click to expand...
Click to collapse
Download the RUU. Relock your phone ("fastboot oem lock" from command prompt), and run the ruu from your PC while connected to USB. After that you can unlock your phone again and start from scratch.
link to the RUU:
http://forum.xda-developers.com/showpost.php?p=22045045&postcount=58
Will do downloading now, and thank you for the link. I so want to bang my head on the table.
Kabish said:
I'm trying to get ADB to detect my phone, but not having luck in that realm either. Was just going to try to push a ROM over to the phone. However it does not appear that it will detect my phone when in the FASTBOOT USB mode. I do a adb devices and it just comes back as none being found...
Click to expand...
Click to collapse
disconnect your phone
close command prompt
ctrl+alt+del and kill any adb process
take out your battery, then put your battery back and connect your phone to your PC and boot to fastboot.
open up CMD again and you should be able to detect your phone.
Ugh...
"ERROR [140]: BOOTLOADER VERSION ERROR"
"The ROM Update Utility cannot update your Android Phone.
Please get the correct ROM Update Utility and try again"
Kabish said:
Ugh...
"ERROR [140]: BOOTLOADER VERSION ERROR"
"The ROM Update Utility cannot update your Android Phone.
Please get the correct ROM Update Utility and try again"
Click to expand...
Click to collapse
you're on the latest gb update?
Yes I should be on the latest OTA. I had my phone rooted when I first got it, then Verizion did an OTA update which was messing with my phone. So I did an RUU and then re-rooted with the OTA Pre Root ROM.
Trying to follow this thread now.. Corsses Fingers...
http://forum.xda-developers.com/showthread.php?t=1338916&page=6
Kabish said:
Yes I should be on the latest OTA. I had my phone rooted when I first got it, then Verizion did an OTA update which was messing with my phone. So I did an RUU and then re-rooted with the OTA Pre Root ROM.
Trying to follow this thread now.. Corsses Fingers...
http://forum.xda-developers.com/showthread.php?t=1338916&page=6
Click to expand...
Click to collapse
gl. let me know how it goes.
Looks like that is not going to work.. I pulled the "firmware" file from that post and renamed it to the PH98IMG.ZIP.
It goes to "Loading...PH98IMG.ZIP
Then
Parsing...PH98IMG.ZIP
Then it just goes back to the main HBOOT menu.
I did unlock my phone again since I had locked it to run the RUU. Any suggestions on how to get the RUU to run?
Ran the RUU again from the link that you sent me. Getting this info when running it:
FROM IMAGE VERSION: 3.10.605.7
TO IMAGE VERSION: 2.01.605.11
Guessing it going from 3.10 to 2.01 is the issue???
Kabish said:
Ran the RUU again from the link that you sent me. Getting this info when running it:
FROM IMAGE VERSION: 3.10.605.7
TO IMAGE VERSION: 2.01.605.11
Guessing it going from 3.10 to 2.01 is the issue???
Click to expand...
Click to collapse
so you are on the leaked ruu?
Apparently so...
I was sure I was on the OTA Stock one though, but apparently not, or I jacked things up trying to fix everything and flashed the wrong one.
I'm trying to go through post to downgrade my Mainver file. Thing is since I can't get into Recovery for whatever reason, and stupid ADB won't list my phone its making this difficult. I can run commands, example locking/unlocking but it won't let me shell in.
Kabish said:
Apparently so...
I was sure I was on the OTA Stock one though, but apparently not, or I jacked things up trying to fix everything and flashed the wrong one.
I'm trying to go through post to downgrade my Mainver file. Thing is since I can't get into Recovery for whatever reason, and stupid ADB won't list my phone its making this difficult. I can run commands, example locking/unlocking but it won't let me shell in.
Click to expand...
Click to collapse
try to run the leak again.relock, put the ph file on the root of your sd card, then run the file in hboot once. after that finishes, run it again.
http://androidcommunity.com/htc-rezound-android-4-0-ics-leaked-with-sense-3-6-get-it-now-20120316/
download the stock version. you need to be relocked to do this.
after that, unlock, flash a recovery, then proceed to install an ics rom, like clean rom or the many others out there.
after you flash the leak twice, and boot to the OS for the first time, it can take up to 10 minutes to boot up in some cases. be patient.
Ok, i'll give that a go...
If I'm reading that post right though it saying that is ICS?? I was not running ICS, I had tried ICS but it was too buggy for my taste so I flashed back my restore and kernel. I'm wondering if I accidently flashed the ICS PH98IMG file.
I'm willing to give it a go though... Its going to take for EVER to download that file though as its on Rapidshare and I'm getting an eta of 6hrs lol.
What really just gets me is that I've not touched my phone as far as rooting/updating since February. And out of the blue it decides to take a dump on me...
Kabish said:
Ok, i'll give that a go...
If I'm reading that post right though it saying that is ICS?? I was not running ICS, I had tried ICS but it was too buggy for my taste so I flashed back my restore and kernel.
I'm willing to give it a go though... Its going to take for EVER to download that file though as its on Rapidshare and I'm getting an eta of 6hrs lol.
Click to expand...
Click to collapse
ICS isn't that buggy especially after flashing a good rom. I actually have no bugs at all. Clean ROM is as stable as they come.
When you flashed the leak before, you lost the ability to fully revert back to pre leak status. you can however install a gb rom, but your radios ad such stay upgraded to the leak versions.
---------- Post added at 01:51 AM ---------- Previous post was at 01:48 AM ----------
Kabish said:
What really just gets me is that I've not touched my phone as far as rooting/updating since February. And out of the blue it decides to take a dump on me...
Click to expand...
Click to collapse
If its February, then you aren't on the leak. you just need to reset your main version I believe.
If I remember correctly my phone kept crashing on me. Granted this is when ICS first came out. I don't remember running an RUU though for ICS, however I did run one to get the OTA update.
I have a A500 tablet as well, which it is running ICS so I kind of get the two all mixed up when I think what I've done lol I've changed ROMS on my A500 so many times that my volume rocker is almost warn out
Found another host for the ICS Stock, it will be done in about 10 minutes.
Kabish said:
If I remember correctly my phone kept crashing on me. Granted this is when ICS first came out. I don't remember running an RUU though for ICS, however I did run one to get the OTA update.
I have a A500 tablet as well, which it is running ICS so I kind of get the two all mixed up when I think what I've done lol I've changed ROMS on my A500 so many times that my volume rocker is almost warn out
Found another host for the ICS Stock, it will be done in about 10 minutes.
Click to expand...
Click to collapse
ICS leak isnt in ruu format. perhaps thats why you dont remember it.
INSTALL:
- rename the downloaded leak file to “PH98IMG.zip” (no quotes)
– Place the renamed file onto the root of the SD Card
- relock your device
– Power down your device
– Reboot into the bootloader by holding VOL DOWN + Power
– The flashing process should begin automatically
- once complete, go back to bootloader and flash a second time.
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 tried a while ago to unlock my bootloader using HTCDev when it first came out, would get to the part where the confirmation screen should pop up on your phone screen to unlock the bootloader but the screen never showed after multiple attempts, so frustrated, I gave up and told my self I'd come back later. Well later came around a few days ago and I attempted to unlock the bootloader again with the same results as the first time, get to the point where I'm supposed to confirm on my phone screen but it never shows. Did some research to find out the OTA version of the update to ICS could have possibly been the problem, but before I went any further I did a full backup of my phone using Carbon, then did a factory reset from the fastboot menu. Now the problem is, after I did the factory reset my computer no longer recognizes my phone when I plug it in. It can't find HTC sync on my computer even though it is, adb devices shows nothing, same with fastboot devices in fastboot mode. My computer recognized the phone just fine up until the factory reset. So I guess my question is, what caused this to happen and how can I fix it? Also, maybe some help unlocking my bootloader? I think I have to flash the RUU but my phone is 2.95.651 and I don't think it lets you go backwards unless you are S-OFF?
Edit: I guess I should mention that I've tried uninstalling and reinstalling the HTC drivers, usb debugging is enabled and Fast Boot in the power options is disabled, I'm also using the USB cord supplied with my phone, tried different USB ports, performed a second factory reset, made sure all my SDK stuff was up to date, and scoured these forums for 2 days now trying to figure it out (apologies if I missed the one thread with all the answers I need, I did try though). Additionally, in fastboot when I plug in my USB cord it switches to fastboot usb, but nothing shows up on devices, which I find really odd.
Anybody have any ideas/solutions for this?
Yep,
http://androidforums.com/showthread.php?p=5810229
I used srs root to gain a root shell followed scotty85's instructions to set mainver low via adb shell then used the brick downgrade hboot method and followed it up with 1.13 ruu and finished with revolutionary
Post #50 is my instructions and scotty85 are a few posts back
Ok, so I got it... kind of. What I did was try the above method with no luck but I ended up using wraith's temproot and scotty's mainver workaround from above then while it was still in it's temproot state I was able to flash a 2.89 RUU, and after that I was unable to unlock the bootloader through HTCdev. Now on to actually root/s-offing it ^ ^
embersanenders said:
Ok, so I got it... kind of. What I did was try the above method with no luck but I ended up using wraith's temproot and scotty's mainver workaround from above then while it was still in it's temproot state I was able to flash a 2.89 RUU, and after that I was unable to unlock the bootloader through HTCdev. Now on to actually root/s-offing it ^ ^
Click to expand...
Click to collapse
Do 2.89 and 2.95 both use the same hboot?
Sent from my Evo V 4G using Tapatalk 2
thewraith420 said:
Do 2.89 and 2.95 both use the same hboot?
Sent from my Evo V 4G using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure if they use the same hboot or not. I was able to flash 2.89 RUU in the temproot state on hboot 1.58.0000. After the flash I retried unlocking the bootloader through HTCdev and it worked flawlessly. Then I was able to root it and juopnutbear s-off, which applied juopnutbear hboot 1.58.5858. It seems like temprooting the phone using your method and flashing a 2.89 RUU might be the workaround for people who have trouble using HTCdev due to the OTA update.
I should also mention someone suggested this method on phandroid forums (scott actually, I believe) on a different thread and so I tried it. I was going to link his post here but I haven't met the link post requirement yet. So as a disclaimer, this isn't my idea, it just worked so I posted here.
Now that I'm home from work I figured I could give a more detailed list of what I did to root my Evo 3D, I feel the information above gets a little confusing with so many different places to go. As previously stated I had trouble unlocking my bootloader using HTCdev, it would get to the step where you confirm on your phone the unlock but never show up, I found this was usually caused by updating your phone to ICS using the OTA as compared to an RUU. Somehow something gets messed up and your phone never wants to confirm, hopefully this will help people who don't want to brick/downgrade hboot in order to be able to root their phones but can't unlock from HTCdev do to this error. Anyway, on to it.
1. Download SRSRoot
A 2.89 RUU
The files from [Guide] Quick And Dirty Evo 3D/V Root & S-OFF (Sprint and Virgin Mobile Only)
2. Run SRSRoot
3. SmartRoot
4. Follow the steps until your phone restarts and you just have a status bar at the top (this is your 'temproot')
5. Close SRSRoot (you may have to kill in the task manager, or at least I did to get it to completely quit mid-steps)
6. Navigate to the folder where the files from the 'QnD' guide and open the cmd link in the Root folder.
7. Type, or copy & paste the following in order (not the stuff in brackets like this, these are notes);
adb devices (should return your phones serial number, indicating drivers are working, and you're connected)
adb push misc_version /data/local/tmp/misc_version
adb shell (should change your prompt to a #, if not, have your phone awake and watch the screen to grant superuser permissions when you enter su (not likely applicable here))
chmod 777 /data/local/tmp/misc_version (have your phone awake and be watching it, in case superuser needs you to grant permission (again, not likely applicable))
/data/local/tmp/misc_version -s 1.00.000.0
exit (exit again if your prompt changes to a $)
8. Run your 2.89 RUU exe (it should run and reinstall 2.89 to stock, you may lose information, unsure about that though, so back ups are always recommended)
9. Restart your phone after the install if it doesn't happen automatically
10. Retry unlocking using HTCdev method
Hopefully at this point the bootloader actually unlocks for you and you can start at Step 2 of the 'QnD' guide to get root access and S-Off.
Big thanks to thewraith420 for the temproot method and scotty85 over at phandroid for the mainver change directions.
The reason I asked if 2.89 used the 1.58 hboot is just to further understand why it worked I think that setting the mainver is what let you run the ruu. And it didn't complain about the hboot because they use the same one. Nicely done getting the info together.
Sent from my PG86100 using Tapatalk 2
misc_version location
embersanenders said:
adb push misc_version /data/local/tmp/misc_version
Click to expand...
Click to collapse
I was encountering the same issue as you for the HTC bootloader unlock, so thanks so much for this info, it worked like a charm. It might be helpful for others to know that you can find the misc_version referenced by downloading the file scotty85 mentions in his post on guide-how-manually-downgrade-firmware-build-6-01-605-05 (Sorry, I'm unable to post the link)
I tried to s-off my phone today with plenty of methods so I could put my phone back to stock. My hboot is 1.44 but I believe it is a patched version as the date is July 5 2013. Revone gives me error code 6 and firewater gives the chaser error. On a mac so can't use rum runner, and can't use ruu.exe files. Anything I could try? I would think either find a way to update or maybe flash a custom kernel would work?
ADarkKnight said:
I tried to s-off my phone today with plenty of methods so I could put my phone back to stock. My hboot is 1.44 but I believe it is a patched version as the date is July 5 2013. Revone gives me error code 6 and firewater gives the chaser error. On a mac so can't use rum runner, and can't use ruu.exe files. Anything I could try? I would think either find a way to update or maybe flash a custom kernel would work?
Click to expand...
Click to collapse
Post a fastboot getvar all (except for imei and serialno).
majmoz said:
Post a fastboot getvar all (except for imei and serialno).
Click to expand...
Click to collapse
Thanks for the reply. Not home right now but have an update. When running firewater, the last command /data/local/tmp/firewater does nothing except delete the file. Know what to do?
ADarkKnight said:
Thanks for the reply. Not home right now but have an update. When running firewater, the last command /data/local/tmp/firewater does nothing except delete the file. Know what to do?
Click to expand...
Click to collapse
I didn't use firewater so I'm not sure about that. However, you could update to the RUU 3.17.502.3.rom.zip then try firewater again. I don't think firewater really works well with that low of a hboot. Here are the commands for running the rom.zip:
Code:
[B][I]./adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]./fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]./fastboot flash zip 3.17.502.3.rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]./fastboot flash zip 3.17.502.3.rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]./fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Good luck I got to get some sleep!
majmoz said:
I didn't use firewater so I'm not sure about that. However, you could update to the RUU 3.17.502.3.rom.zip then try firewater again. I don't think firewater really works well with that low of a hboot. Here are the commands for running the rom.zip:
Good luck I got to get some sleep!
Click to expand...
Click to collapse
Thanks for the instructions, actually ended up flashing stock recovery and took ota's up to that version. Still no dice for s-off. Oh well, doesn't really matter, was just going to do it because i'm replacing my phone with att, but what are the odds they know how to get into the bootloader Getting the replacement today, and funny beaups replied to me saying he'll update a fix today. Hopefully I can s-off the replacement.
Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
skylirizm said:
Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
Click to expand...
Click to collapse
Hello my friend, the reason you can't load the pg86img is because you have unlocked bootloader. The fastboot commands could help us a lot, did you follow the controlbear instructions in the correct order? I think there is a way through windows with exe files I don't remember well because I did S-OFF 3years+ before. If you want we can try together some time. If you want for start we can flash 4ext recovery and a custom rom so your phone can boot.
mhnx said:
Hello my friend, the reason you can't load the pg86img is because you have unlocked bootloader. The fastboot commands could help us a lot, did you follow the controlbear instructions in the correct order? I think there is a way through windows with exe files I don't remember well because I did S-OFF 3years+ before. If you want we can try together some time. If you want for start we can flash 4ext recovery and a custom rom so your phone can boot.
Click to expand...
Click to collapse
Hi there, I didn't know with having the bootloader unlocked that it would cause any issues, but there you go!
Yeah, if there's a guide to flashing the 4EXT Recovery and a custom rom that would be great!
I have a fair idea of how to do it, but don't want to try anything without having someone of greater knowledge point me in the right direction
Thanks!
Just an update, I did come across a thread to flash 4EXT Recovery onto my Evo 3D.
Put Recovery.img into my platform-tools folder, used the fastboot command, it said sending and OK.
Selected recovery and still boot loops. No idea where to go from here now
skylirizm said:
Just an update, I did come across a thread to flash 4EXT Recovery onto my Evo 3D.
Put Recovery.img into my platform-tools folder, used the fastboot command, it said sending and OK.
Selected recovery and still boot loops. No idea where to go from here now
Click to expand...
Click to collapse
Sorry for being late, I had some problems with my internet connection. Can you boot into recovery? Power button + Vol- and choose recovery, if you can boot tell me first which version you have and second what type of rom you want to have.
mhnx said:
Sorry for being late, I had some problems with my internet connection. Can you boot into recovery? Power button + Vol- and choose recovery, if you can boot tell me first which version you have and second what type of rom you want to have.
Click to expand...
Click to collapse
Hey there,
That's OK, I don't mind the wait, it's all good!
I can boot into Fastboot, but when I choose recovery/factory reset etc, it shows the HTC Logo and then goes into a bootloop.
As for the ROM, I want to get the original GB ROM for it because when I updated it to the latest ICS that's when the camera and touch started to get weird, whereas beforehand it was fine.
So thinking, if I go back down to GB Stock, that it should be all fine again, but I am not too sure on that one.
Thanks!
skylirizm said:
Hey there,
That's OK, I don't mind the wait, it's all good!
I can boot into Fastboot, but when I choose recovery/factory reset etc, it shows the HTC Logo and then goes into a bootloop.
As for the ROM, I want to get the original GB ROM for it because when I updated it to the latest ICS that's when the camera and touch started to get weird, whereas beforehand it was fine.
So thinking, if I go back down to GB Stock, that it should be all fine again, but I am not too sure on that one.
Thanks!
Click to expand...
Click to collapse
Well, we have to downgrade the hboot version first. Did you do the wire trick procedure right? You can download a pg86img and flash it first to fix the bootloops. First lock the bootloader. When you finish this report here. I have to sleep it's late here and I work early. I'll send you tomorrow. See you.
mhnx said:
Well, we have to downgrade the hboot version first. Did you do the wire trick procedure right? You can download a pg86img and flash it first to fix the bootloops. First lock the bootloader. When you finish this report here. I have to sleep it's late here and I work early. I'll send you tomorrow. See you.
Click to expand...
Click to collapse
Ok, the technician I took the phone to supposedly did the wire trick for S-OFF, but, it's still S-ON.
I have downloaded a lot of stock PG86IMG files before posting on here and none work, they scan when in bootloader and then nothing after that.
But that would be because I haven't locked the bootloader. So in saying this, I lock the bootloader following steps on many forum posts on here, then flash a .zip file that's correct and then it should all work?
I'll wait for your response, thanks!
skylirizm said:
Ok, the technician I took the phone to supposedly did the wire trick for S-OFF, but, it's still S-ON.
I have downloaded a lot of stock PG86IMG files before posting on here and none work, they scan when in bootloader and then nothing after that.
But that would be because I haven't locked the bootloader. So in saying this, I lock the bootloader following steps on many forum posts on here, then flash a .zip file that's correct and then it should all work?
I'll wait for your response, thanks!
Click to expand...
Click to collapse
I do not think that the wire trick procedure was correct because you are still s on. Lock the bootloader and try to load the zip.
mhnx said:
I do not think that the wire trick procedure was correct because you are still s on. Lock the bootloader and try to load the zip.
Click to expand...
Click to collapse
Hey, so I tried a P86IMG.zip from this thread here - http://forum.xda-developers.com/showthread.php?t=2274635
I couldn't find another one and with that I get an error "Main Version Fail" or "Main Version Check Fail".
I then tried RUU and RUU in zip format.
RUU comes back with wrong bootloader error. (I couldn't find an RUU that matched my radio version so I went with the nearest one)
RUU Zip comes back through fastboot with "remote 43 main version check fail"
Also I tried to do the Wire Trick and got stuck at the "ADB and Fastboot not found" even though the files are there and the phone is connected.
So still a little bit...stuck :\
Also relocked bootloader it just says relocked now.
If you need any other additional info I can send screenshots of what it's at.
Thanks!
skylirizm said:
Hey, so I tried a P86IMG.zip from this thread here - http://forum.xda-developers.com/showthread.php?t=2274635
I couldn't find another one and with that I get an error "Main Version Fail" or "Main Version Check Fail".
I then tried RUU and RUU in zip format.
RUU comes back with wrong bootloader error. (I couldn't find an RUU that matched my radio version so I went with the nearest one)
RUU Zip comes back through fastboot with "remote 43 main version check fail"
Also I tried to do the Wire Trick and got stuck at the "ADB and Fastboot not found" even though the files are there and the phone is connected.
So still a little bit...stuck :\
Also relocked bootloader it just says relocked now.
If you need any other additional info I can send screenshots of what it's at.
Thanks!
Click to expand...
Click to collapse
Did you try flashing the zip after the locking? You are doing the wire trick procedure on live linux cd?
mhnx said:
Did you try flashing the zip after the locking? You are doing the wire trick procedure on live linux cd?
Click to expand...
Click to collapse
Yes, tried flashing the zip after locking. Live CD is being used also. I will try again later. Thanks!
skylirizm said:
Yes, tried flashing the zip after locking. Live CD is being used also. I will try again later. Thanks!
Click to expand...
Click to collapse
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
mhnx said:
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
Click to expand...
Click to collapse
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
donkeykong1 said:
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
Click to expand...
Click to collapse
Oh that would be extremely helpful, I can use Linux, but prefer my Windows PC as it has all the files and it's just easier.
Thanks so much!
mhnx said:
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
Click to expand...
Click to collapse
donkeykong1 said:
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
Click to expand...
Click to collapse
So update -
DK sent me the windows version of ControlBear via PM - thank you.
Have an unlocked bootloader.
I tried ControlBear, and because I can not boot into the OS, I start it at Fastboot USB, it reboots, then says "Connecting to Device", then "Testing ADB connection" then "Press Enter To Exit" and that's it, can't do anything else from there, and it gets stuck in the boot loop that it still has.
Tried again to google for methods for HBOOT 1.53, and am trying some of those methods, but it's not looking good at all.
I haven't even got to the stage where it asks me to do any sort of wire trick.
Also my battery in the EVO 3D has died so am using a battery out of a HTC MyTouch 4G with help from electrical tape :\
So now, any suggestions? I am trying to flash another RUU that's stock for my Radio (Well, it's close enough - RUUs are both 11.25.3504.06, mine is 11.25.3504.16)
EDIT: Tried all RUUs with relocked bootloader and comes back with bootloader error (ERROR 140). So, no idea.
Also it's scanning for PG86DIAG.img files on the SD Card - that's not normal is it.
Do you think we should give up on it, it's probably hard bricked and dead now
I think it's literally hard bricked and no way to bring it back from the dead.
As per my original post, all the details for the phone are there. And it sucks that I can't find a correct RUU for my phone (As it was Telstra AU - latest update of ICS)
AHH I don't know.
skylirizm said:
So update -
DK sent me the windows version of ControlBear via PM - thank you.
Have an unlocked bootloader.
I tried ControlBear, and because I can not boot into the OS, I start it at Fastboot USB, it reboots, then says "Connecting to Device", then "Testing ADB connection" then "Press Enter To Exit" and that's it, can't do anything else from there, and it gets stuck in the boot loop that it still has.
Tried again to google for methods for HBOOT 1.53, and am trying some of those methods, but it's not looking good at all.
I haven't even got to the stage where it asks me to do any sort of wire trick.
Also my battery in the EVO 3D has died so am using a battery out of a HTC MyTouch 4G with help from electrical tape :\
So now, any suggestions? I am trying to flash another RUU that's stock for my Radio (Well, it's close enough - RUUs are both 11.25.3504.06, mine is 11.25.3504.16)
EDIT: Tried all RUUs with relocked bootloader and comes back with bootloader error (ERROR 140). So, no idea.
Also it's scanning for PG86DIAG.img files on the SD Card - that's not normal is it.
Do you think we should give up on it, it's probably hard bricked and dead now
I think it's literally hard bricked and no way to bring it back from the dead.
As per my original post, all the details for the phone are there. And it sucks that I can't find a correct RUU for my phone (As it was Telstra AU - latest update of ICS)
AHH I don't know.
Click to expand...
Click to collapse
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
mhnx said:
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
Click to expand...
Click to collapse
Hey there, thanks for the help again, unfortunately, still didn't work.
I unlocked the bootloader again. Then tried to flash what you said, it said "writing" then "successful". I pulled the battery and tried to boot into recovery and just loops
skylirizm said:
Hey there, thanks for the help again, unfortunately, still didn't work.
I unlocked the bootloader again. Then tried to flash what you said, it said "writing" then "successful". I pulled the battery and tried to boot into recovery and just loops
Click to expand...
Click to collapse
Try doing:
fastboot erase recovery
fastboot flash recovery "recovery".img
fastboot format system
fastboot format boot
And if it still doesn't let me send you a boot.img in some minutes to try flashing it.
EDIT: And something last, you can still do the controlbear trick while not in OS, its easy if you wanna try let me know.
skylirizm said:
Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
Click to expand...
Click to collapse
i have same problem plz give me GB rom link and flash method
---------- Post added at 07:56 AM ---------- Previous post was at 07:42 AM ----------
mhnx said:
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
Click to expand...
Click to collapse
plz help my htc evo 3d is bootloop no go to any recovery mode i flash all recovery
BOOTLOADER-UNLOCK
HBOOT-1.53.0007
RADIO-11.25.3504.06.M
i flash many ruu.exe but this
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Radio_11.77.3504.00U_11.25.3
flash seccussfully without any error but no booting only htc logo plz help