Hey guys, i have my rezound running cleanrom icse 3.1 and want to revert back to stock - no root ect. so much has changed since i did this last so im confused, How do i go back to stock, i did the factory reset but that just puts me back to no data on cleanrom icse 3.1.
Any help would be appreciated.
i have clockwork recovery installed
*unlocked*
s-on
hboot 2.10.000
thabnks
real stock
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
michaelbsheldon said:
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
Click to expand...
Click to collapse
Thanks, ill try this and get back to you.
Again thank you.
michaelbsheldon said:
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
Click to expand...
Click to collapse
im getting an error:
C:\mini-adb_vigor>fastboot oem writesecureflag 3
... INFOvreg_set: request is duplicated id 14
INFO vigor_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
INFOwritesecureflag: Permission denied, value 1
OKAY [ 1.578s]
finished. total time: 1.578s
C:\mini-adb_vigor>
any ideads?
next
Android Police posted a zip file 3.14.605.12PH98IMG.zip.
Its the same info in that RUU.
Download it, rename to just PH98IMG.zip and place in root of sdcard.
Run that, and it'll do the factory restore you want, maybe without those
unrequested comments it made in fastboot.
michaelbsheldon said:
Android Police posted a zip file 3.14.605.12PH98IMG.zip.
Its the same info in that RUU.
Download it, rename to just PH98IMG.zip and place in root of sdcard.
Run that, and it'll do the factory restore you want, maybe without those
unrequested comments it made in fastboot.
Click to expand...
Click to collapse
Tried that, didnt work, hboot/cwm recovery said invalid,
I finally got s-off with the JuopunutBear / wire trick and now it seems to be working.
Thank you for the guidance.:good:
Firstly, the problem why the RUU wasn't working, was that your bootloader was unlocked (fastboot oem lock to relock the bootloader)
This usually gives an "Unknown Error 99" message.
The reason it worked after S-OFF is because JuopunutBear erases the unlock token.
Secondly, when you're trying to do something like this, it's better to search for a reliable source for instructions & not jump at any answers that you can find.
michaelbsheldon said:
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
Click to expand...
Click to collapse
This answer is so so wrong. How can you provide advice on something that you have no idea about?
This instructions are for S-ON & if your device has JuopunutBear hboot, then this will brick the phone.
Would you ever be willing to try something like this on your own phone?
*
If you'd been bothered to read OP comments, he was S-0n, so JBear Hboot couldn't have been there.
Save your crabby comments.
michaelbsheldon said:
If you'd been bothered to read OP comments, he was S-0n, so JBear Hboot couldn't have been there.
Save your crabby comments.
Click to expand...
Click to collapse
Sure, in which case writesecureflag isn't required at all.
Although these wrong S ON bricks are unbrickable, never in any case tell anyone to do that command unless you fully understand the implications of what you are saying.
If you notice, he later did S-OFF with JuopunutBear:
wohn said:
I finally got s-off with the JuopunutBear / wire trick and now it seems to be working.
Click to expand...
Click to collapse
in which case, his phone would have bricked if he had JB hboot had tried your commands.
The android police RUU you linked to is not an Official RUU, it's made from an OTA. Which is why he was unable to flash it without S-OFF.
The instructions you gave were wrong & I simply called you out on that.
I honestly don't want to argue on this, I just want you to be careful of what you advice people to do.
Although this is a public forum & everyone's input is welcome & I'm nobody to enforce any rules; I'm simply giving you my opinion.
The rest is upto you. Good day.
Related
Is there a way to get this phone back to stock? I have been searching everywhere with no luck so far.
Download either the 2.08 or 2.17 RUU .exe file, reboot bootloader, fastboot oem lock, run RUU file.
Thanks for the response. I just thought I only had to download a RUU and change the name to PG86IMG and flash it. What do you mean by oem lock?
Before running the ruu, put the phone in fastboot mode and in a command prompt type "fastboot oem lock" no quotes
squiggs95 said:
Before running the ruu, put the phone in fastboot mode and in a command prompt type "fastboot oem lock" no quotes
Click to expand...
Click to collapse
C:\Users\[email protected]#[email protected]>fastboot oem lock
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Is what I got
i dont think there is a way to do this when you are s-on
sorry!!!
Do u have drivers and fastboot installed?
Drivers yes, fastboot apparently not.
Nvm, I had to go to the Fastboot folder, hold shift then right click. Open command window here.
Although it still had all the applications I had installed. Is that normal?
Usually not. When i unrooted mine all my apps were gone. If u go into your bootloader does it say you are relocked?
squiggs95 said:
Usually not. When i unrooted mine all my apps were gone. If u go into your bootloader does it say you are relocked?
Click to expand...
Click to collapse
Yeah it says "relocked" and clockwork recovery was gone... I assume it worked?
! twitty said:
Yeah it says "relocked" and clockwork recovery was gone... I assume it worked?
Click to expand...
Click to collapse
youll know if it worked when you have that pg86img.zip on the root of your sdcard and then relock your phone and then boot into hboot by holding volume down and the power button and watch for the blue bar on the upper right to load the new file...
Fastboot folder???
! twitty said:
Drivers yes, fastboot apparently not.
Nvm, I had to go to the Fastboot folder, hold shift then right click. Open command window here.
Although it still had all the applications I had installed. Is that normal?
Click to expand...
Click to collapse
So where do I find this Fastboot folder? I need to unroot my wifes phone due to the bottom buttons aren't working properly and it is on Hboot 1.5 s-on... t/u for your help.
kaw900r said:
So where do I find this Fastboot folder? I need to unroot my wifes phone due to the bottom buttons aren't working properly and it is on Hboot 1.5 s-on... t/u for your help.
Click to expand...
Click to collapse
Once you lock your bootloader its still gonna show "relocked" anyway. They will know that you had it rooted. Just find a stock unrooted Rom. Save your self the hastle. I could be wrong though but I am pretty sure that you will get a watermarked bootloader once you relock. They might not even check the bootloader and if they do they might not care.
Sent from my PG86100 using xda premium
kaw900r said:
So where do I find this Fastboot folder? I need to unroot my wifes phone due to the bottom buttons aren't working properly and it is on Hboot 1.5 s-on... t/u for your help.
Click to expand...
Click to collapse
You wipe first in recovery then go back to hboot
fastboot oem lock with adb
Relocks you
Now just find and download the 2.17 RUU EXE run it and your set man.
When you rooted your phone you had a folder at the root of your C drive in which you probably downloaded and extracted a zip file in with the root files you used. After you put your phone in fast goot, Go to command prompt type cd /"name of file you extracted that in", hit enter, then type adb, hit enter again, then type fastboot oem lock. You will then have S-ON and be able to run the RUU to un-root
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
Alright people, I need help. I have an HTC Rezound (obviously) for verizon. I want to go back to Complete Stock, (as if it were brand new).
It was unlocked using HTC devs method
Its rooted
It is s-on
The recovery file i used is : recovery-ra-vigor-3.16-gnm
I installed a custom rom: Business_ICS4.0.3_Sense3.6-v6.3
Android version 4.03.605.2
HTC Sense 3.6
How do i get my phone to be:
Completely stock
Stock rom
no root
Locked title in Hboot
fix the tampered title in hboot
Any help is much apreciated
Are you doing this to warranty it? It will say "relocked" when you are done. It hasn't been a problem for anyone in the past though, you should still be able to return it to Verizon.
Instructions on how to return to stock are here:
http://forum.xda-developers.com/showpost.php?p=38244272&postcount=10
You probably should use the latest official RUU (prior to the OTA they just rolled out a couple days ago) which is 3.14.605.12. The link I have is to an .exe file. You just connect your phone to your pc and then double click. It will take you through the steps.
Get it here:
http://androidfiles.org/ruu/?dir=Vigor
That will get you back to stock, unrooted and it will say "relocked".
There was a global leak that wasn't official. If you want to use that, get it here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
This is a zip file you put on your external sd card. Follow instructions in the first link I gave you.
THANK YOU
feralicious said:
Are you doing this to warranty it? It will say "relocked" when you are done. It hasn't been a problem for anyone in the past though, you should still be able to return it to Verizon.
Instructions on how to return to stock are here:
http://forum.xda-developers.com/showpost.php?p=38244272&postcount=10
You probably should use the latest OTA, prior to the one they just rolled out a couple days ago which is 3.14.605.12. The link I have is to an .exe file. You just connect your phone to your pc and then double click. It will take you through the steps.
Get it here:
http://androidfiles.org/ruu/?dir=Vigor
That will get you back to stock, unrooted and it will say "relocked".
There was a global leak that wasn't official. If you want to use that, get it here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
This is a zip file you put on your external sd card. Follow instructions in the first link I gave you.
Click to expand...
Click to collapse
Thank you so much it worked like a charm!!! You just saved me from a weeks worth of searching i did and a couple of headaches.. Thank you very much
You're welcome, glad it worked for you!
I noticed I typed the wrong thing when I said "latest OTA", I should have said "latest official RUU" (don't know what was going on in my head) so I'm going to edit that post to fix it for any future readers.
okay, im having the same problem, except im s-off. i need to send my rez back for warranty reasons, i have a custom rom, my h-boot says locked, s-off, 2.27.000. any help would be awsome! thanks!
motodanr1 said:
okay, im having the same problem, except im s-off. i need to send my rez back for warranty reasons, i have a custom rom, my h-boot says locked, s-off, 2.27.000. any help would be awsome! thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=
Sweet, thanks! When I click on the link I get "no thread specified" though ..?
Sent from my ADR6300 using xda app-developers app
Go into dev, sticky, roll up thread. Click on back to s-on link
Phaded said:
http://forum.xda-developers.com/showthread.php?t=
Click to expand...
Click to collapse
I was Tampered/Locked and s-off. I ran the 4.03.605.2 RUU twice then its said locked the tampered was removed. I used the mini-adb_vigor program to achieve S-ON. Open a Command prompt wtih admin privileges and enter these commands pressing enter after each one. Now I am completely back to Locked S-ON. Hope this helps.
cd c:\mini-adb_vigor
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
netookska05 said:
I was Tampered/Locked and s-off. I ran the 4.03.605.2 RUU twice then its said locked the tampered was removed. I used the mini-adb_vigor program to achieve S-ON. Open a Command prompt wtih admin privileges and enter these commands pressing enter after each one. Now I am completely back to Locked S-ON. Hope this helps.
cd c:\mini-adb_vigor
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Click to expand...
Click to collapse
Make sure to run this on a stock hboot or it will brick.
I am having a similar issue. I am rooted, I never relocked my bootloader, stock minus a few mods, but the ota update keeps failing. What do I need to do to be able to accept the update so it stops rebooting my phone?
Hey guys, I need to return my phone to verizon because of a simcard/PUK lock error. I'm on the current OTA update (2.06) but still unlocked, rooted and S-off. I need to go back to bone stock if possible. Can I still follow the guide in this thread to go back to stock??
http://forum.xda-developers.com/showthread.php?t=2017525
Anyone?
scheirere said:
Anyone?
Click to expand...
Click to collapse
You don't have to relock your phone all you have to do is flash the ENG Bootloader then you can run the RUU. Make sure you have all the drivers you need installed first or it WILL fail.
ENG Bootloader:
http://forum.xda-developers.com/showthread.php?t=2156713
Also this won't take away your S-Off the only way to get to S-On is by running a special command. Once S-Off always S-Off.
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
scheirere said:
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
Click to expand...
Click to collapse
Yes try here:
http://forum.xda-developers.com/showpost.php?p=37277937&postcount=66
Oh and don't forget to hit thanks on that post.
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
scheirere said:
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
Click to expand...
Click to collapse
This first:
1. adb reboot bootloader
2. fastboot oem rebootRUU
3. fastboot flash zip ModdedPL832IMG.zip
4. Profit
making sure that the .zip is in the same folder as fastboot
then run the RUU after you reboot the phone.
Yes it should be the same drivers you used when rooting.
Looks like I spoke too soon on those downloaded files. The download of the RUU file bombed out on me and I didn't realize it. When I go back to the site in the link, and try to download the file now, it just sits waiting. I guess the site is down? Any other links or locations?
Downloads working now maybe keep trying they say they are under a DDOS attack. Here it is from hotfile but I can't confirm this as real.
HERE
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
scheirere said:
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
Click to expand...
Click to collapse
After step 1, but before step 2, do this:
fastboot devices
If you don't get a device id, then you don't have the proper drivers installed.
If you get a device id, then try step 2 again ...
If that doesn't work, then I don't know
Maybe try a different USB port on your computer also use the OEM cable if you can.
Thanks guys for the suggestions. Unfortunately, still no luck. Same results when flashing the Modded file. I did try adb devices as suggested and got the device ID. So I think the drivers are OK. I also tried another USB port just to see if it helped. No go.
Just because I'm pretty new to this stuff, here's a detailed list of what I'm doing.....
1.) ADB reboot bootloader (from a command prompt)
Phone reboots to bootloader screen with Fastboot USB in red, hightlighted.
The screen no longer displays the "TAMPERED" heading at the top. So it looks like I'm making some progress.
2.) fastboot oem rebootRUU (from a command prompt again)
Phone screen goes from white to black with nothing but a large HTC logo in white.
Nothing else happens at this point. I've let the phone sit for 30 minutes with no apparent change and nothing on the host PC.
I then went thru my computer to the directory were the RUU_DLX.... file resides and executed (double clicked) it. I get an RUU - InstallShield screen and then I go thru the HTC rom update utility steps. After a few steps the utility does it's thing and the phone then reboots.
3.) ADB reboot bootloader again
Phone reboots into bootloader screen
4.) fastboot flash zip ModdedPL832IMG.zip (from a command prompt)
Phone does nothing but the command screen returns:
sending 'zip' (485 KB)...OKAY [ 0.266s]
writing 'zip'...FAILED (remote: not allowed)"
pretty much immediately
Am I doing this correctly?
At this point the bootloader screen no longer says tampered. Can I just relock the bootloader so it's s-on again?
BTW, here's what the bootloader screen shows:
*** UNLOCKED ***
MONARUDO PVT SHP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
Or can I just send the phone back as it is?
Bootloader uses a different driver than ADB. My advise is to boot into the bootloader then verify in device manager that the driver is loaded. See attached. Flashing the RUU will not get you S-On you need a command to do that and I don't know what it is off the top of my head I have never used it.
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