Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
demayod said:
Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
Click to expand...
Click to collapse
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Thanks so much for the response! I appreciate the help. Very informative. I'll read through & hopefully I report back with good news tomorrow morning. :cyclops:
Yay! All done!
Thanks so much for the guide! and the help!
-Dan
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
demayod said:
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
Click to expand...
Click to collapse
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
clsA said:
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
Click to expand...
Click to collapse
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
demayod said:
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
Click to expand...
Click to collapse
This is the instructions posted by Scotty85
I'm just re-posting it for you
http://androidforums.com/t-one-all-things-root/723061-t-ruu-1-26-502-12-a.html#post5864243
Click to expand...
Click to collapse
here is how you extract rom.zip:
Quote:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
here are some directions to flash "rom.zip"
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse
clsA said:
This is the instructions posted by Scotty85
I'm just re-posting it for you
Click to expand...
Click to collapse
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
demayod said:
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
Click to expand...
Click to collapse
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
My mid is PN0712000. I think that was always my mid. Don't recall changing it.
My cid is currently CW__001
I've tried: RUU_M7_UL_JB_50_Cingular_1.26.502.12.exe
also tried: RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2.exe
I'm currently S-On (could that be an issue?)
I'm unlocked.
clsA said:
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
Click to expand...
Click to collapse
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Yep that should do it
Sent from my HTC One using Tapatalk 4
It did! I'm completely back to stock. I decided to update to the latest RUU that AT&T has released. Just to avoid AT&T wanting me to update to see if it fixes the problem. I know for a fact that it wouldn't fix the problem anyway.
Oddly, my phone told me I was up to date while on the .12 RUU even though I knew the .15 RUU exists. I downloaded the RUU for .15 and it ran fine once I went back to stock after running the .12 rom.zip.
In summary, you saved me from a huge headache! Thanks so much for all the help & kindness.
demayod said:
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Click to expand...
Click to collapse
How did you change our CID if you were S-On?
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
larrydadz said:
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
Click to expand...
Click to collapse
Comments: Sprint
modelid:
cid: SPCS_001
Related
I AM PLAYING WITH MY REZOUND FROM LAST 1 MONTH YESTERDAY I THOUGHT I HAVE TO UPDATE IT TO ICS(RUU FROM ANDROIDPOLICE) AND FLASHED RUU FROM HEREhttp://www.androidpolice.com/2012/08/02/exclusive-download-htc-rezound-ice-cream-sandwich-ruu-for-final-ota-3-14-605-12/
AFTER FLASHING RUU PHONE STARTS REBOOTING ,NO APPS DOWNLOAD FROM PLAY STORE ,
NOW I WANTS TO GO BACK TO GINGERBREAD OFFICIAL ROM
PLZ SOMEONE HELP ME SO I CAN FLASH GB OFFICIAL RUU ON MY REZOUND
DETAILS OF MY REZOUND-
TAMPERED
****RELOCKED***
VIGOR PVT SHIP S-ON RL
HBOOT -2.25.0000
RADIO-1.22.10.0421R/1.22.10.0424R
OPENDSP-V13.6.0.7611.00.0104
EMMC-BOOT
APR 12 2012,16:47:46
PLZ SUGGEST ME TO GO BACK TO GB OR ANY FIX TO STOP ALL RANDOM REBOOTS.
In order to downgrade you need to S-OFF, then flash one of the old RUU's.
Did you factory reset after installing the ICS?
I would also try installing the new 4.3.605.2 RUU from Android Police... factory default, flash twice (if you flash an RUU, ALWAYS do it twice), then factory default again.
acejavelin said:
In order to downgrade you need to S-OFF, then flash one of the old RUU's.
Did you factory reset after installing the ICS?
I would also try installing the new 4.3.605.2 RUU from Android Police... factory default, flash twice (if you flash an RUU, ALWAYS do it twice), then factory default again.
Click to expand...
Click to collapse
+1 I would try the factory reset before anything. then follow the steps above.
if you are 100% sure you want to go back to GB then you would need s-off
you need s-off to go back to gingerbread. try flashing the new 4.3.605.2
Thnx for all replies can someone confirm Ruu 4.3.605.2 is stable and working fine ?
Sent from my SGH-T999 using xda app-developers app
I have searched google but not able to found any valid link for latest ruu can someone plz post latest ruu link for download ?
Sent from my SGH-T999 using xda app-developers app
sanchitgrover said:
I have searched google but not able to found any valid link for latest ruu can someone plz post latest ruu link for download ?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It is completely stable, and fixes way more issues than the changelog mentions...
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
And select AP Mirror #1 which is hosted on beta.androidfilehost.com, a very reliable and (usually) speedy server, it takes about 3 minutes for me to download it ( I have done it lots of times, people keep saying doesn't work), just click the link, then the green circle with a down arrow to download it (to the left of the filename), MD5 matches every time. If that one give you trouble, go to the same link and on the right hand side there are mirrors of that server, they work equally well.
And like every ROM, VERIFY the MD5 before flashing... if it don't match, don't flash!
It looks like your RUU didn't install completely. Flash it *several* times, until you get the screen where all items are listen as "OK" and it says to reboot.
If that still doesn't work, try flashing it through fastboot:
install HTC Sync (this will install drivers for adb and bootloader debug). Somehow obtain fastboot.exe (pretty sure it comes with HTC Sync. If not, download the Rezound All In One Toolkit. Open a command prompt and change the directory to the same one that fastboot.exe is in (use the command "cd" then the full folder location, ex "cd c:\users\yourname\desktop\fastboot folder").
Next, you'll want to take out your phone's SD card. Power on the phone, holding power and volume down to boot into the bootloader. Then, choose fastboot. Connect your phone to your PC at this time. Now use the command "fastboot oem rebootRUU". Your phone will reboot to a black screen with a silver HTC logo. Next, drag the RUU file you downloaded (doesn't matter what it's named) to the same folder as fastboot.exe. Use the command "fastboot flash zip <ruu name>", replacing "<ruu name>" with the name of the file, obviously. Once the command prompt says it's done, you can safely turn off your phone, or do a battery pull if necessary.
I highly recommend you do not revert to Gingerbread, because it requires a firmware downgrade and the S-Off procedure is necessary. Things can go horribly wrong with S-off especially if you don't know what you're doing.
scy1192 said:
It looks like your RUU didn't install completely. Flash it *several* times, until you get the screen where all items are listen as "OK" and it says to reboot.
If that still doesn't work, try flashing it through fastboot:
install HTC Sync (this will install drivers for adb and bootloader debug). Somehow obtain fastboot.exe (pretty sure it comes with HTC Sync. If not, download the Rezound All In One Toolkit. Open a command prompt and change the directory to the same one that fastboot.exe is in (use the command "cd" then the full folder location, ex "cd c:\users\yourname\desktop\fastboot folder").
Next, you'll want to take out your phone's SD card. Power on the phone, holding power and volume down to boot into the bootloader. Then, choose fastboot. Connect your phone to your PC at this time. Now use the command "fastboot oem rebootRUU". Your phone will reboot to a black screen with a silver HTC logo. Next, drag the RUU file you downloaded (doesn't matter what it's named) to the same folder as fastboot.exe. Use the command "fastboot flash zip <ruu name>", replacing "<ruu name>" with the name of the file, obviously. Once the command prompt says it's done, you can safely turn off your phone, or do a battery pull if necessary.
I highly recommend you do not revert to Gingerbread, because it requires a firmware downgrade and the S-Off procedure is necessary. Things can go horribly wrong with S-off especially if you don't know what you're doing.
Click to expand...
Click to collapse
So this will work with out S-off? I am on Venom Rom on ICS. Great Rom but when I plug my headphones in the phone reboots. I want to get back to Stock ICS.
Thanks
duvious said:
So this will work with out S-off? I am on Venom Rom on ICS. Great Rom but when I plug my headphones in the phone reboots. I want to get back to Stock ICS.
Thanks
Click to expand...
Click to collapse
Without S-OFF you can only go same version or newer, not backwards, but you will have to relock your bootloader... You should then be able to flash the 4.3.605.2 RUU with no problem.
scy1192 said:
It looks like your RUU didn't install completely. Flash it *several* times, until you get the screen where all items are listen as "OK" and it says to reboot.
If that still doesn't work, try flashing it through fastboot:
install HTC Sync (this will install drivers for adb and bootloader debug). Somehow obtain fastboot.exe (pretty sure it comes with HTC Sync. If not, download the Rezound All In One Toolkit. Open a command prompt and change the directory to the same one that fastboot.exe is in (use the command "cd" then the full folder location, ex "cd c:\users\yourname\desktop\fastboot folder").
Next, you'll want to take out your phone's SD card. Power on the phone, holding power and volume down to boot into the bootloader. Then, choose fastboot. Connect your phone to your PC at this time. Now use the command "fastboot oem rebootRUU". Your phone will reboot to a black screen with a silver HTC logo. Next, drag the RUU file you downloaded (doesn't matter what it's named) to the same folder as fastboot.exe. Use the command "fastboot flash zip <ruu name>", replacing "<ruu name>" with the name of the file, obviously. Once the command prompt says it's done, you can safely turn off your phone, or do a battery pull if necessary.
I highly recommend you do not revert to Gingerbread, because it requires a firmware downgrade and the S-Off procedure is necessary. Things can go horribly wrong with S-off especially if you don't know what you're doing.
Click to expand...
Click to collapse
acejavelin said:
Without S-OFF you can only go same version or newer, not backwards, but you will have to relock your bootloader... You should then be able to flash the 4.3.605.2 RUU with no problem.
Click to expand...
Click to collapse
That is great news. I will relock and flash!
htc rezound hboot 2.25.0000 can flash global verizon rom?
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
u can flash gb rom with patch to fix sdcard mounting problem
unlock ur device
install recovery
flash the rom & patch
flash the kernel via fastboot or hboot
then power it on normally
or
flash stock gb only the rom.zip and boot.img via hboot
root
patch ur device manually
basheerbr said:
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
Click to expand...
Click to collapse
just download it from android police and flash, flash twice followed with a factory reset. should b in good shape after.
basheerbr said:
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
Click to expand...
Click to collapse
For the global RUU - http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Feel free to open a new thread vs using an 8 month old one that isn't related to your problem if you can't find what you're looking for also.
basheerbr said:
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
Click to expand...
Click to collapse
mike7728 said:
just download it from android police and flash, flash twice followed with a factory reset. should b in good shape after.
Click to expand...
Click to collapse
Also, make sure you allow it to fully do its thing, don't pull battery or anything in the middle of it. The screen will go black for a second or two, just wait it out. It will leave you in bootloader when it's done iirc.
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
Ok, I have been away from the site and havent messed with my phone for over a year so I am really rusty but I want to flash to ICS. However after many hours today without success I have restored the GB. Hoping someone can give me some insight to my mistake as things have changed a far bit in a year.
I currently have Nils Business Sense Gingerbread and want to go flash Nils Business ICS 4.0.3 Sense. http://forum.xda-developers.com/showthread.php?t=1508118
I believe I followed direction as described on the above page but I could never get the recent RUU to install. Looking at the directions on the above thread post #3 "Latest RUU Leak and Installation Instructions" I can get it to step #6 but things fall apart there. It finds the PH98IMG.zip and scans it like the directions say but never prompts me to say "yes" as describes. It does have the progress bar on the right side that will complete and then returns to the bootloader screen but at no point does it actually go to the white HTC load screen. Is there something missing from the directions or could I have missed something?
The phone was unlocked thru HTC website over a year ago. I believe its s-off but dont remember and unable to figure out how to tell.
Thanks in advance. Mark
Okay, first of all, to check if you are s-off boot into bootloader and look up top. Around the 2nd or 3rd line I believe, it will say Vigor and either s-off or s-on in there.
If you are s-on you need to relock the bootloader in fastboot.
fastboot oem lock
If you didn't do that and you are s-on that's probably the issue.
I ran the RUU a week or so ago so I'm trying to remember exactly what happened.
I don't recall if it just automatically ran or if it asked me if I wanted to "update".
When you say you see a progress bar, do you see a list of items and does it say "updating" next to each item as it gets to it? Can you say exactly what is on the screen after it starts? Also you are using the latest global, 4.03.605.2?
After it makes a first pass it will go to a black screen for a couple minutes then back to bootloader to run again. Then you'll see the same screen with the list and "updating" next to each item.
Then it will boot back into bootloader and ask you if you want to reboot iirc. Or else it reboots itself but I think it asked me. Then you'll see a normal boot but it will take a while so just be patient.
Thanks for the quick reply.
No it never gets to the point of updating anything. I finds then scans the img, it has a blue completion bar on the right side of the screen when it is scanning. That will complete but it never updates anything and returns to the recovery screen. I even tried just loading the ROM without installing the RUU and it sat on the white HTC screen for an hour so clearly I have to update the RUU before I can flash Nils ROM.
Ok apparently I am S-on so need to relock bootloader.
Can you give me a little more details on how to do it. Guessing I'm not grasping fastboot oem lock.
Are you s-off or s-on? If s-on, did you relock first?
You might try running the 3.14.xxxxxx from here:
http://androidfiles.org/ruu/?dir=Vigor
It's an exe file so just double click it on the desktop and it will run.
Or you can give these commands in fastboot:
fastboot oem rebootRUU
fastboot flash zip NameOfZip.zip
Then if that works you can try the global again. Double the work, but unless someone else comes along with a solution it's something you can try while waiting.
mbrudolph said:
Ok apparently I am S-on so need to relock bootloader.
Can you give me a little more details on how to do it. Guessing I'm not grasping fastboot oem lock.
Click to expand...
Click to collapse
Okay, that's probably it then. Was writing my last post when you posted.
So power down the phone, pull the battery then put it back in and boot into bootloader. Switch to fastboot and connect to your pc.
Open up your command window and navigate to where you have your fastboot/adb folder (I attached what you need in case you no longer have it, just place the folder on the root of your pc so you would navigate to c:\android).
Then type
fastboot oem lock
That will lock you so you can run the RUU.
Afterwards you will need to unlock again. If you no longer have your unlock code you can get it again from HTCDev. If you go to their site it explains how.
http://www.htcdev.com/bootloader/
Once you receive your token put it in the "android" folder (or whatever the name of your folder you use for fastboot is).
Then type
fastboot flash unlocktoken Unlock_code.bin
I keep my android folder with the unlock token and latest Amon Ra recovery in there so I always know they're there if I need them.
Then you'll need to flash the newest AmonRa, it's up to 3.16 now.
Root ( didn't have to do anything, was already set to flash ROM)
Flash Nils' ROM.
Also, since you are s-on you will need to flash the kernel from the ROM after you flash the ROM. I don't know if he has it set to make a PH98IMG file or not - some ROMs create one on your sd card. If not, you need to pull it from the ROM, put it in the "android" folder and flash in fastboot. I would pull it out ahead of time in case so you're ready.
fastboot flash boot boot.img (or whatever the name of his kernel is)
Then you should be able to boot up and enjoy.
feralicious said:
Okay, that's probably it then. Was writing my last post when you posted.
So power down the phone, pull the battery then put it back in and boot into bootloader. Switch to fastboot and connect to your pc.
Open up your command window and navigate to where you have your fastboot/adb folder (I attached what you need in case you no longer have it, just place the folder on the root of your pc so you would navigate to c:\android).
Then type
fastboot oem lock
That will lock you so you can run the RUU.
Afterwards you will need to unlock again. If you no longer have your unlock code you can get it again from HTCDev. If you go to their site it explains how.
http://www.htcdev.com/bootloader/
Once you receive your token put it in the "android" folder (or whatever the name of your folder you use for fastboot is).
Then type
fastboot flash unlocktoken Unlock_code.bin
I keep my android folder with the unlock token and latest Amon Ra recovery in there so I always know they're there if I need them.
Then you'll need to flash the newest AmonRa, it's up to 3.16 now.
Root ( didn't have to do anything, was already set to flash ROM)
Flash Nils' ROM.
Also, since you are s-on you will need to flash the kernel from the ROM after you flash the ROM. I don't know if he has it set to make a PH98IMG file or not - some ROMs create one on your sd card. If not, you need to pull it from the ROM, put it in the "android" folder and flash in fastboot. I would pull it out ahead of time in case so you're ready.
fastboot flash boot boot.img (or whatever the name of his kernel is)
Then you should be able to boot up and enjoy.
Click to expand...
Click to collapse
Hey feralicious,
Been reading this and with my white screen issue, I have two questions.....first is like you I have an android folder where I keep the unlock token and amonRa recovery but mine is 3.15. Where can I get 3.16 from? I saw a thread with zip files but it said you had to be S-off and I am not.
My second question is what is file you attached here?
318sugarhill said:
Hey feralicious,
Been reading this and with my white screen issue, I have two questions.....first is like you I have an android folder where I keep the unlock token and amonRa recovery but mine is 3.15. Where can I get 3.16 from? I saw a thread with zip files but it said you had to be S-off and I am not.
My second question is what is file you attached here?
Click to expand...
Click to collapse
There's a link for 3.16 at the bottom of the Amon Ra thread in development. Not the attachments, the link right above those.
I attached the folder with the files needed to use fastboot/adb.
feralicious said:
There's a link for 3.16 at the bottom of the Amon Ra thread in development. Not the attachments, the link right above those.
I attached the folder with the files needed to use fastboot/adb.
Click to expand...
Click to collapse
Ok. I don't need those. I have adb all set. I will check that thread again. Any real difference in 3.16 vs 3.15?
318sugarhill said:
Ok. I don't need those. I have adb all set. I will check that thread again. Any real difference in 3.16 vs 3.15?
Click to expand...
Click to collapse
The only difference I know of is that 3.16 has a working root option.
Feralicious,
Just wanted to thank you again. Today, I finally got everything updated and working well. Couldn't have done it without your help.
THANKS!!! :highfive:
Mark
mbrudolph said:
Feralicious,
Just wanted to thank you again. Today, I finally got everything updated and working well. Couldn't have done it without your help.
THANKS!!! :highfive:
Mark
Click to expand...
Click to collapse
You're welcome! Glad I could help. :good:
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Here is a picture of hboot:
Sent from my ADR6400L using xda app-developers app
cyberkeeper1 said:
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Click to expand...
Click to collapse
Something I don't understand here: how were you able to run fastboot oem writecid while S-ON? Have you since gone S-ON after writing the incorrect CID?
Furthermore, why in the world would you venture from my explicit instructions on how to fix the radio? I can't imagine any reason you would want to re-lock the bootloader or go S-ON. As I keep saying: if you are already unlocked or S-OFF, I almost never see a legitimate reason to run the RUU!
I assume you still can boot into CyanogenMod? If so, follow these instructions (Windows):
Set this in CM: Settings > Developer options > Root access > Apps and ADB
Download the latest unlock script package (we will not run the script, but we do need the files there)
Extract the unlock script package and open a command window in that directory
Type these commands:
Code:
adb root
adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
adb pull /sdcard/cid
hexalter cid 0x214=0x56,0x5A,0x57,0x5F,0x5F,0x30,0x30,0x31
adb push cid /sdcard/
adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
This should revert your CID back to VZW__001.
deleted
cyberkeeper1 said:
See I wish I could boot. I didn't understand why it accepted an oem command while s-on either. But alas, it did. I wrote that command after relocking. I am not s-off. Never was, hence my entire problem. I was afraid to try s-off because of the higher possibility of bricking my phone. It's not like the thunderbolt where it always works. If I was s-off I would know what to do and could flash hotdogs as my Cid if I wanted. My first problem is being stuck in hboot and can't restore. I wiped everything. Boot, data, system, recovery all in prep for stock since I am s-on
Click to expand...
Click to collapse
From the bootloader, what is the output this?
Code:
fastboot getvar cid
deleted
cyberkeeper1 said:
The output is:
VZW_0001
Click to expand...
Click to collapse
I can't even explain the number of ways you shot yourself in the foot. You really wiped recovery and boot too? How did you come to believe this would be a good idea? Or is necessary at all?
I believe the only option you have is to try and flash the stock signed recovery through fastboot (not even sure if it'll work), and then use ruu mode to TRY and fix things up:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ruu.zip
I suspect even that will complain about the incorrect CID though. Perhaps jose has some other ideas.
deleted
deleted
deleted
deleted
deleted
YESSSSSSSSSSSSSS! I GOT IT! I GOT IT! I GOT IT!
When i want something done, i try the impossible...
so... here is the thing... and COMPLETELY unexpected it is. Apparently, you can submit the following cid as an unlock token to HTCdev and get returned a valid unlock code BIN file. with VZW_0001 (obviously incorrect) i STILL received the file and it said token submitted successfully. downloaded, flashed and now unlocked. still s-on, but WAY more room for fixing now. i flashed the CID back to the proper VZW__001 using adb root shell in recovery. worked great! thanks MDMOWER for the codes to revert. now i can flash my custom ROM backup back to the device after flashing just the stock rom (NO RELOCKING THIS TIME FOR ME!) to fix the radios the way i was supposed to. ( being tired = not reading + not using glasses) i don't understand it myself, but i bet this one is going to through you for a loop. the only conclusion i can come up with is the fact that another device actually DOES use the CID of VZW_0001 and is not an officially supported device. that would explain why i was even able to be successful. but its speculation at best until confirmed.
cyberkeeper1 said:
YESSSSSSSSSSSSSS! I GOT IT! I GOT IT! I GOT IT!
When i want something done, i try the impossible...
so... here is the thing... and COMPLETELY unexpected it is. Apparently, you can submit the following cid as an unlock token to HTCdev and get returned a valid unlock code BIN file. with VZW_0001 (obviously incorrect) i STILL received the file and it said token submitted successfully. downloaded, flashed and now unlocked. still s-on, but WAY more room for fixing now. i flashed the CID back to the proper VZW__001 using adb root shell in recovery. worked great! thanks MDMOWER for the codes to revert. now i can flash my custom ROM backup back to the device after flashing just the stock rom (NO RELOCKING THIS TIME FOR ME!) to fix the radios the way i was supposed to. ( being tired = not reading + not using glasses) i don't understand it myself, but i bet this one is going to through you for a loop. the only conclusion i can come up with is the fact that another device actually DOES use the CID of VZW_0001 and is not an officially supported device. that would explain why i was even able to be successful. but its speculation at best until confirmed.
Click to expand...
Click to collapse
moderators, after a few replies from the users, i don't mind if you close my thread because my problem is solved.
EDIT: maybe not yet... bootlooping after fix and restore of last backup before the incident. do i have to have the Super CID written to boot from any custom rom?
cyberkeeper1 said:
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Here is a picture of hboot:
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
are you rooted?
EDIT: got confused and was thinking this was a new thread sorry
jose51197 said:
you rooted?
Click to expand...
Click to collapse
i am now that i fixed everything. well the recovery partition is rooted. i cant get my phone to boot now though. i tried using the backup i made right before returning to stock and it no longer works. i get a boot loop from the first boot screen. loads HTC logo, then legal warning in red. screen turns black and back again. it never loads into the CM10.1. i manually flashed the kernel from my backup since i am still s-on. i am going to try fresh installing a rom.
cyberkeeper1 said:
i am now that i fixed everything. well the recovery partition is rooted. i cant get my phone to boot now though. i tried using the backup i made right before returning to stock and it no longer works. i get a boot loop from the first boot screen. loads HTC logo, then legal warning in red. screen turns black and back again. it never loads into the CM10.1. i manually flashed the kernel from my backup since i am still s-on. i am going to try fresh installing a rom.
Click to expand...
Click to collapse
You messed a lot with you phone man, better install stock rom throught ruu or mdmowers way then s off revert cid and flash cm10
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
You messed a lot with you phone man, better install stock rom throught ruu or mdmowers way then s off revert cid and flash cm10
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
i am inclined to agree based on what its doing, but wanted to be sure. i just didnt want to have to re-re unlock again. lol. i'll see what happens.
I was able to successfully flash cyanogenmod, but my phone only works for data, not for calls or texts. I assume this is because I'm still on Super CID (11111111). When I try to revert to the VZW cid, i receive an error executing the adb shell. It tells me that it's a read only file system. I'm rooted, s off, and bootloader unlocked. Any help would be greatly appreciated as my phone is only half usable right now
Don't use adb shell once you're s-off. Use these commands:
Code:
adb reboot bootloader
Once in fastboot, issue this command to revert to the VZW CID:
Code:
fastboot oem writecid VZW__001
that's it.
Sent from my Incredible 4G LTE using xda app-developers app
Thanks so much for the quick response. I knew I was overthinking it. Just applied the change, rebooting now. I'll follow up with my findings.
---------- Post added at 06:27 PM ---------- Previous post was at 06:16 PM ----------
Well, it changed the CID, but the issue still persists. If I look in about phone > status, it says my mobile phone number is 000-000-0000. I'm definitely preplexed to say the least.
Ok, so I tired to dabble in custom roms and I got burnt!!!
First things first,
HTC One X+ (International)
Version Main: 1.17.708.1
CID: HTC_622
S-On
HBOOT: 1.35.0000
Radio: 3.1204.168.32
I'm trying to RUU the device back to the stock and then never tinker again!
Can someone please step me through this, all the links I'm finding are dead or the RUU doesn't run.
Many thanks =)
Get hasoons20000 one x+ toolkit it has a link for ruu
Gave this a shot, I cannot find the appropriate RUU for my device.
****...
CJMilsey said:
Gave this a shot, I cannot find the appropriate RUU for my device.
****...
Click to expand...
Click to collapse
What country did you buy it from and what is your CID?
I bought it online (from Asia) The CID is 622 as above.
Addicted2xda said:
What country did you buy it from and what is your CID?
Click to expand...
Click to collapse
Bump
CJMilsey said:
Bump
Click to expand...
Click to collapse
Refer to the posting rules. You should not bump a thread within 24 hours...
You can download the RUU (ENRC2B) from this :
http://forum.xda-developers.com/showthread.php?t=2094118
you need to relock your bootloader before running the RUU
http://www.androidfiles.org/ruu/get...Radio_3.1204.168.32_release_299722_signed.exe
I'm sorry, I must have missed that one :/
I Tried this before but the RUU used didn't work, but I'll try to re-download and go from there.
(RUU_ENRC2B_U_JB_45_hTC_Asia_WWE_1.17.707.1_Radio_3.1204.168.32_release_299722_signed.exe)
Will it be a problem that my phone is 1.17.708.1 and that this is 1.17.707.1 (0.0.001 lower)?
Also, do I need to flash the stock recovery. And If so where would I go about getting it?
You will only have to relock the bootloader again and then (while in fastboot) run the RUU. Remember that you will lose everything on the device.
To relock the bootloader use Hansoon's toolkit. It has all the commands build in for easy use.
"Wrong CID" I'm not sure why this is wrong. 662 came back from fastboot getvar cid, and does indeed correspond to Hong Kong.
What would you advise from here dear sir?
CJMilsey said:
"Wrong CID" I'm not why this is wrong. 662 came back from fastboot getvar cid, and does indeed correspond to Hong Kong.
What would you advise from here dear sir?
Click to expand...
Click to collapse
Are you sure it's a generic HK CID? And not an operator locked one? Maybe you need the RUU from a particular operator.....
Sent from my HTC One X+ using Tapatalk 4 Beta
AndroHero said:
Are you sure it's a generic HK CID? And not an operator locked one? Maybe you need the RUU from a particular operator.....
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
I looked up the CID and it's just for HK, the phone came unlock so I doubt it needs a locked RUU. But hey, I've been wrong before.
Is there any reason the phone would not accept the correct RUU?
Okk,
This might seem a bit weird but I had the same issue with my Intl HOX+ and I have given it to hTC and they asked me to shell out aroun 18K to change the motherboard! (Which of course we all know is not required since this is a software issue).
So here is what I did:
1. I relocked the boot loader (I hope you have the unlock_code.bin with you, else get it from hTCDev)
2. Of course it started giving relocked security warning.
3. Again unlocked the boot loader and voila - it booted straight in to Elegancia!
This essentiially happens because unlocking the bootloader formats all the partitions except system and boot (I guess, because my media files were gone...).
See if this gets you through.
But DO IT AT YOUR OWN RISK!
I am talking about International HOX+, I do not know if ATT works in a different way.
Unfortunately that hasn't worked and I'm still stuck with the stall during boot :/
I think my best bet will the RUU, but I just can't get one that will work.
Do you know a ROM that I could side-load onto my device and just use it with that?
Thanks
Addicted2xda said:
Okk,
This might seem a bit weird but I had the same issue with my Intl HOX+ and I have given it to hTC and they asked me to shell out aroun 18K to change the motherboard! (Which of course we all know is not required since this is a software issue).
So here is what I did:
1. I relocked the boot loader (I hope you have the unlock_code.bin with you, else get it from hTCDev)
2. Of course it started giving relocked security warning.
3. Again unlocked the boot loader and voila - it booted straight in to Elegancia!
This essentiially happens because unlocking the bootloader formats all the partitions except system and boot (I guess, because my media files were gone...).
See if this gets you through.
But DO IT AT YOUR OWN RISK!
I am talking about International HOX+, I do not know if ATT works in a different way.
Click to expand...
Click to collapse
I had a small bootloader problem and was just surfing this section.I used your method of relocking and again unlocking and my problem was solved.I found it obligatery for me to thank you.
---------- Post added at 10:30 AM ---------- Previous post was at 10:21 AM ----------
CJMilsey said:
Unfortunately that hasn't worked and I'm still stuck with the stall during boot :/
I think my best bet will the RUU, but I just can't get one that will work.
Do you know a ROM that I could side-load onto my device and just use it with that?
Click to expand...
Click to collapse
I have unbricked mine by efforts of two long days and nights from about same problem. Provide the details and I will try to help you out,
1. can you boot to recovery.
2. If yes.which recovery you use.
3. what were you doing when this happened.
faandrabi said:
I have unbricked mine by efforts of two long days and nights from about same problem. Provide the details and I will try to help you out,
1. can you boot to recovery.
2. If yes.which recovery you use.
3. what were you doing when this happened.
Click to expand...
Click to collapse
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
CJMilsey said:
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
Click to expand...
Click to collapse
flash twrp through fasboot as only twrp provides side load option.
when twrp is flashed ,boot to recovery.side load incertcoin rom through hasoons toolkit.
don't worry about 707 or 708 etc.Mine was 707.1 but i am using incertcoin which is 401.3
after falshing incertcoin if it is again in boot loop then
use this command from adb
adb shell
wipe data
and reboot
you will be done.
CJMilsey said:
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
Click to expand...
Click to collapse
I hope you are on TWRP 2.5? If not update it...
And then use adb sideload
Hi,
I have the exact same problem.. I can get to TWRP recovery and HBOOT and my PC only detects the phone if its in recovery.
my CID is HTC__001.
I am trying to find a working RUU to run..
I tried this one: RUU_ENRC2B_U_JB_45_hTC_Asia_TW_1.14.709.17_Radio_3.1204.167.31_release_291089_signed.exe
(But that didn't work)
Any suggestions?
Thanks in advance.
rmuruga said:
Hi,
I have the exact same problem.. I can get to TWRP recovery and HBOOT and my PC only detects the phone if its in recovery.
my CID is HTC__001.
I am trying to find a working RUU to run..
I tried this one: RUU_ENRC2B_U_JB_45_hTC_Asia_TW_1.14.709.17_Radio_3.1204.167.31_release_291089_signed.exe
(But that didn't work)
Any suggestions?
Thanks in advance.
Click to expand...
Click to collapse
download incertcoin rom from hox+ android development & hasoon toolkit v2.4
boot in recovery
connect to pc
run onex+.exe and side load the rom
after it is done flash boot.img inside rom through fasboot command
and you will be done