Here's the Rom.zip I pulled from the AT&T 4.18.502.7 RUU
Encrypted version is Removed until i find another source (file was damaged, sorry for any inconvenience )
This will work if your s-off and your modelid: PN0712000 and CID: CWS__001
or you can EDIT the Android-info.txt to match your MID and CID
Decrypted version is here >> http://www.androidfilehost.com/?fid=23329332407580500
Huge thanks to @nkk71 for decrypting the files
And another Big thanks to @AndroidFileHost for the source RUU
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip
Instructions for flashing
If your s-on be sure the bootloader is locked
fastboot oem lock
Copy your downloaded file to your fastboot / adb folder
Rename the file Rom.zip
open a command prompt in the same folder (shift + right click - command prompt here )
adb reboot-bootloader
fastboot commands:
fastboot oem rebootRUU
wait for the Silver HTC logo
fastboot flash zip Rom.zip
the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip Rom.zip
most times the green status bar does not reach the 100% mark. So when the output in the command window is complete, you can reboot:
fastboot reboot
I find these files much easier to use than the RUU.exe and these can be flashed with a MAC or Linux ....Have Fun !!
:good: :good:
clsA said:
Here's the Rom.zip I pulled from the AT&T 4.18.502.7 RUU
This will work if your s-on and your modelid: PN0712000 and CID: CWS__001
Encrypted version is here >> http://www.androidfilehost.com/?fid=23329332407580207
This will work if you s-off and your modelid: PN0712000 and CID: CWS__001
or you can EDIT the Android-info.txt to match your MID and CID
Decrypted version is here >> http://www.androidfilehost.com/?fid=23329332407580500
Huge thanks to @nkk71 for decrypting the files
And another Big thanks to @AndroidFileHost for the source RUU
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip
Instructions for flashing
Copy your downloaded file to your fastboot / adb folder
Rename the file Rom.zip
open a command prompt in the same folder (shift + right click - command prompt here )
adb reboot-bootloader
fastboot commands:
fastboot oem rebootRUU
wait for the Silver HTC logo
fastboot flash zip Rom.zip
the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip Rom.zip
most times the green status bar does not reach the 100% mark. So when the output in the command window is complete, you can reboot:
fastboot reboot
I find these files much easier to use than the RUU.exe and these can be flashed with a MAC or Linux ....Have Fun !!
Click to expand...
Click to collapse
thanks again, much appreciated! I will give it a few more minutes but I work at 6am!
a little help please
I just put my One back to stock. S-on, relocked, tamper gone, etc When I try to update using the above method i get
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (1519630 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.002s
any ideas? thank you!
gsxrfl1k6 said:
I just put my One back to stock. S-on, relocked, tamper gone, etc When I try to update using the above method i get
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (1519630 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.002s
any ideas? thank you!
Click to expand...
Click to collapse
I just tested it and had the same problem ...I'll update when I get the new file uploaded
clsA said:
I just tested it and had the same problem ...I'll update when I get the new file uploaded
Click to expand...
Click to collapse
I'm also having the same issue. Have you been able to figure out what is wrong?
TaDoey said:
I'm also having the same issue. Have you been able to figure out what is wrong?
Click to expand...
Click to collapse
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
HEllo, friend now i feel very dissapointed thus i was not able to update my phone is a htc one M7 7120 from AT$T running this useless firmware 1.26.502.12, im in Colombia myabe thats why the AT&T system update is not working and i tried to run that RUU 3.X.502... but it still giving me the ERROR 158, any idea how can i update this phone? Thank man hope u can answer me.
Sli2cooL said:
HEllo, friend now i feel very dissapointed thus i was not able to update my phone is a htc one M7 7120 from AT$T running this useless firmware 1.26.502.12, im in Colombia myabe thats why the AT&T system update is not working and i tried to run that RUU 3.X.502... but it still giving me the ERROR 158, any idea how can i update this phone? Thank man hope u can answer me.
Click to expand...
Click to collapse
Is your bootloader locked/relocked?
Are you S-OFF or S-ON?
What is the CID?
Is this the RUU 3.17.502.3 that you are trying to run?
You will not get any AT&T updates if you are not on the AT&T network!
If you are not S-OFF, I would recommend obtaining S-OFF then rebrand your phone to the International (.401) variant. Then you could get the OTA updates and not worry about the AT&T network.
majmoz said:
Is your bootloader locked/relocked?
Are you S-OFF or S-ON?
What is the CID?
Is this the RUU 3.17.502.3 that you are trying to run?
You will not get any AT&T updates if you are not on the AT&T network!
If you are not S-OFF, I would recommend obtaining S-OFF then rebrand your phone to the International (.401) variant. Then you could get the OTA updates and not worry about the AT&T network.
Click to expand...
Click to collapse
Hello mate, thanks for the reply, now that you mention it sounds pretty interesting to rebrand to phone to int. variant, but... How do i ado that? Right now im running 4.18.502.7 Stock for AT&T, i would not liek to bother you so much but is there any way to do that i wouls appreciate the help.
Yes im S-OFF and yes im unlocked, TWRP tho, CWS__001, hboot 1.44.000000 and rooted.
Once again thanks for the help.
Sli2cooL said:
Hello mate, thanks for the reply, now that you mention it sounds pretty interesting to rebrand to phone to int. variant, but... How do i ado that? Right now im running 4.18.502.7 Stock for AT&T, i would not liek to bother you so much but is there any way to do that i wouls appreciate the help.
Yes im S-OFF and yes im unlocked.
Once againm thans for the help.
Click to expand...
Click to collapse
Here is a outline of what you will need to do.
Here are the steps to re-branding your phone to Int'l:
Unlock bootloader if not unlocked already!
Install Custom recovery
Download TWRP 2.6.3.3 from here: http://techerrata.com/browse/twrp2/m7
Achieve S-OFF, if not already!
With your hboot 1.5x use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Try all options!
Change CID to the new code:
Code:
[B][I]adb reboot bootloader
fastboot oem writecid HTC__001[/I][/B] <- (CID is exactly 8 characters)
[B][I]fastboot reboot-bootloader[/I][/B]
Change MID to the new code: PN0710000 using: [TOOL] MID change without ENG HBOOT | Aroma GUI
Remove "Tampered" with the Guru Bootloader Reset Tool
Download and flash 4.19.401.9 firmware; place firmware in your fastboot/adb folder and rename to firmware.zip. Ensure you have moved all of your personal items off of your phone this firmware will wipe your phone. Open a command window in your fastboot/adb folder and type:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Execute http://www.htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe/ which now matches your CID & MID
There is no need to lock/relock bootloader with S-OFF, and do not even THINK about going back to S-ON!!!
Now you can receive the OTAs or flash them manually.
OTA_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.11-4.19.401.9_R_release_355954met8o678uio0omu3.zip
OTA_M7_UL_K44_SENSE60_MR_HTC_Europe_5.11.401.10-4.19.401.11_release_372404wj19h95c0x6oa19n.zip
OTA_M7_UL_K443_SENSE60_MR_HTC_Europe_6.09.401.5-5.11.401.10_release_386803.zip
OTA_M7_UL_K443_SENSE60_MR_HTC_Europe_6.09.401.10-6.09.401.5_release_397712mm1f6dd6rksg0p3s.zip
Click to expand...
Click to collapse
majmoz said:
Here is a outline of what you will need to do.
Click to expand...
Click to collapse
Thansk for the reply mate is it neccesary to change the MID of the phone?
Also the hboot is it good at 1.44?
Sli2cooL said:
Thansk for the reply mate is it neccesary to change the MID of the phone?
Also the hboot is it good at 1.44?
Click to expand...
Click to collapse
Only if it is different. I don't know your MID but if it is different from the Int'l MID then you will not be able to flash the firmware, RUU or OTAs.
Yes, it will change when you flash the firmware & RUU. I would keep a copy of it for future use.
majmoz said:
Only if it is different. I don't know your MID but if it is different from the Int'l MID then you will not be able to flash the firmware, RUU or OTAs.
Click to expand...
Click to collapse
I think it is 712000 from AT&T, quite different right?
Sli2cooL said:
I think it is 712000 from AT&T, quite different right?
Click to expand...
Click to collapse
Yes, just think you should only have to change it once!
majmoz said:
Yes, just think you should only have to change it once!
Click to expand...
Click to collapse
Ho danm , then i cannot get back to 7120? Anyways Int goes better i guess, no malfunction on LTE/4G?
Sli2cooL said:
Ho danm , then i cannot get back to 7120? Anyways Int goes better i guess, no malfunction on LTE/4G?
Click to expand...
Click to collapse
You can go back; just do the same steps for AT&T. If you have LTE/4G now you will still have LTE/4G after this process does not change the bands that are hard coded into the phone. The radio in the software merely enhances the bands that are in the phone but can not replace them.
majmoz said:
You can go back; just do the same steps for AT&T. If you have LTE/4G now you will still have LTE/4G after this process does not change the bands that are hard coded into the phone. The radio in the software merely enhances the bands that are in the phone but can not replace them.
Click to expand...
Click to collapse
Okey buddy thansk again for the help ill be trying it tomorrow and ill be updating the process. :good:
I missed this one, well it went well, now i can recieve the OTAs in auto mode, THX for the help @majmoz.
Sorry but when I type "fastboot flash zip Rom.zip" fastboot stops, Someone, can help me? :crying:
I'm S-ON
hboot 1.57
CID: CWS__001
Related
I successfully got S-OFF on my Evo V. Now I'm trying to downgrade my hboot to 1.04 ENG. My current hboot is the one JBear puts on after getting S-OFF.
When trying to flash the PG86IMG.zip through fastboot, it gives me the "CID Incorrect!" error and have to power off. My CID is "SPCS_002"
Any help is greatly appreciated.
*EDIT*
Lol. It seems like I find the answer right after I made the thread everytime. I had to edit the PG86IMG.zip to use my CID.
FussyQBert said:
*EDIT*
Lol. It seems like I find the answer right after I made the thread everytime. I had to edit the PG86IMG.zip to use my CID.
Click to expand...
Click to collapse
You could also use the hboot downloads from this post which have been modified to work with both the Sprint (SPCS_001) and Virgin Mobile (SPCS_002) CID's.
ramjet73
ramjet73 said:
You could also use the hboot downloads from this post which have been modified to work with both the Sprint (SPCS_001) and Virgin Mobile (SPCS_002) CID's.
ramjet73
Click to expand...
Click to collapse
Well, I did use an hboot from that post. I tried editing the text file inside to remove the SPCS_001 but this still didn't work. Now when trying to flash through the bootloader, it parses the zip but then doesn't install.
Not sure what's going on :crying:
*EDIT*
Ok now I might have screwed something up. I was able to flash through the command line fastboot, rather than the bootloader. I flashed through the command line using these commands:
fastboot oem rebootRUU
fastboot flash zip PG86IMG_ENG_1.04-hboot.zip
Now my phone is stuck on the RUU HTC screen (the black with silver letters). The progress bar is about 3/4 full
FussyQBert said:
*EDIT*
Ok now I might have screwed something up. I was able to flash through the command line fastboot, rather than the bootloader. I flashed through the command line using these commands:
fastboot oem rebootRUU
fastboot flash zip PG86IMG_ENG_1.04-hboot.zip
Now my phone is stuck on the RUU HTC screen (the black with silver letters)
Click to expand...
Click to collapse
Did you issue the "fastboot reboot" or "fastboot reboot-bootloader" command after the flash finished? Or you can just remove/replace the battery then power on.
ramjet73
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
First of all, sorry my bad english.
I've unlocked the Bootloader and the phone is S-Off but before i did that, the phone couldn't receive any update from AT&T, android version is 4.3
I installed a custom recovery but i want to know what ROM do you guys recommend me, i'm looking for something with kit kat 4.4.3 or 4.4.2, idk what version is available to the cell.
Somebody can help me with it? or returning back to stock , i tried looking for a RUU for my phone but no results.
m7_ul_pvt ship s-off rh
hboot 1.55
cid- CWS__001
radio-4T.20.3218.13
OS-3.17.502.3
hope you can help me, please :b, i want to feel sense 6.0 :v (i'm on sense 5.0)
I'm not living in the US, i live in the frontier with usa (baja california) but i can't go to USA xD
Since s-off change cid to BS_US001 and run the 6.07.1540.3 youll probably have to do in increments to get to that build but its doable...search for the brighstar ruu and the ota's for it here.
Tsukymaiden said:
First of all, sorry my bad english.
I've unlocked the Bootloader and the phone is S-Off but before i did that, the phone couldn't receive any update from AT&T, android version is 4.3
I installed a custom recovery but i want to know what ROM do you guys recommend me, i'm looking for something with kit kat 4.4.3 or 4.4.2, idk what version is available to the cell.
Somebody can help me with it? or returning back to stock , i tried looking for a RUU for my phone but no results.
m7_ul_pvt ship s-off rh
hboot 1.55
cid- CWS__001
radio-4T.20.3218.13
OS-3.17.502.3
hope you can help me, please :b, i want to feel sense 6.0 :v (i'm on sense 5.0)
I'm not living in the US, i live in the frontier with usa (baja california) but i can't go to USA xD
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Since s-off change cid to BS_US001 and run the 6.07.1540.3 youll probably have to do in increments to get to that build but its doable...search for the brighstar ruu and the ota's for it here.
Click to expand...
Click to collapse
Brighstar, okay i'll do it but by some reason, the cell can lose is free company? i'm not in AT&T, it's unlocked to all companies of my country (telcel mexico), it will lose the unlock?
and if i change the CID, the cell will no longer boot in the version of it? (4.3) or it does not affect? and i don't understand the part of "Do in increments to get that build" x)
Tsukymaiden said:
Brighstar, okay i'll do it but by some reason, the cell can lose is free company? i'm not in AT&T, it's unlocked to all companies of my country (telcel mexico), it will lose the unlock? I believe the phone will still remain carrier unlocked
and if i change the CID, the cell will no longer boot in the version of it? (4.3) or it does not affect? When you change the CID the phone will look for that version
and i don't understand the part of "Do in increments to get that build" x)You have to install the earlier OTAs first and in order or you might make your phone inoperable.
Click to expand...
Click to collapse
Here is a guide to help to you:
Here are the steps to re-branding your phone to DevEd:
Unlock bootloader if not unlocked already!
Install Custom recovery
Download TWRP 2.6.3.3 from here: http://techerrata.com/browse/twrp2/m7
Achieve S-OFF
With your hboot 1.5x use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Try all options!
Change CID to the new code:
Code:
[B][I]adb reboot bootloader
fastboot oem writecid BS_US001[/I][/B] <- (CID is exactly 8 characters)
[B][I]fastboot reboot-bootloader[/I][/B]
Download and flash 4.19.1540.9 firmware; place firmware in your fastboot/adb folder and rename to firmware.zip. Ensure you have moved all of your personal items off of your phone this firmware will wipe your phone. Open a command window in your fastboot/adb folder and type:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Execute RUU_4.19.1540.9.exe which now matches your CID & MID
There is no need to lock/relock bootloader with S-OFF, and do not even THINK about going back to S-ON!!!
Now you can receive the OTAs or flash them manually.
OTA 5.11.1540.9 - 4.19.1540.9
OTA 6.07.1540.1 - 5.11.1540.9
Click to expand...
Click to collapse
Helloo I changed the Cid into google play edition and installed lollipop 5.0.1. If i want to go to developer edition i just need to flash the ruu of 4.4dev edition?
Sent from my HTC One using XDA Free mobile app
Tsukymaiden said:
Helloo I changed the Cid into google play edition and installed lollipop 5.0.1. If i want to go to developer edition i just need to flash the ruu of 4.4dev edition?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Yes, that is how it suppose to happen. However, it may not be that simple. The GPe hboot may be higher and the lower RUU may not run. There has been issues in the past with locking and relocking the bootloader with the GPe variant. You might want to read about it in the Forum or Google it. Another option is to wait until Lollipop gets released to the DevEd then try the change.
I seem to have confirmation, from HTC and from THIS site: http://www.androidpit.com/what-is-my-firmware-number
... that the software number IS the firmware number on this phone.
BUT ...*if* that's true, then - why is the viper page so concerned with the firmware (mainver) number NOT being available through "fastboot getvar all" with TWRP on the phone?
Wombat Pete said:
I seem to have confirmation, from HTC and from THIS site: http://www.androidpit.com/what-is-my-firmware-number
... that the software number IS the firmware number on this phone.
BUT ...*if* that's true, then - why is the viper page so concerned with the firmware (mainver) number NOT being available through "fastboot getvar all" with TWRP on the phone?
Click to expand...
Click to collapse
Software number is the number of base your ROM is set off. If you update firmware but don't update ROM your software number will not change an match your firmware numbers in bootloader....when wanting to verify firmware numbers I only do it in bootloader. Just what I do.
Tigerstown said:
Software number is the number of base your ROM is set off. If you update firmware but don't update ROM your software number will not change an match your firmware numbers in bootloader....when wanting to verify firmware numbers I only do it in bootloader. Just what I do.
Click to expand...
Click to collapse
Thanks ...I am, however, in the situation described: I've used TWRP and fastboot doesn't show a mainver.
What can I do - what would you do? - to determine firmware number in that case?
Wombat Pete said:
Thanks ...I am, however, in the situation described: I've used TWRP and fastboot doesn't show a mainver.
What can I do - what would you do? - to determine firmware number in that case?
Click to expand...
Click to collapse
You must have been on a old twrp that had a bug that remove os number. So flash the latest twrp an then flash the latest firmware zip an it will show....or you can go to about phone an find your radios an find out what firmware had those radios. Myself I would upgrade twrp flash latest firmware an be good.
Tigerstown said:
You must have been on a old twrp that had a bug that remove os number. So flash the latest twrp an then flash the latest firmware zip an it will show....or you can go to about phone an find your radios an find out what firmware had those radios. Myself I would upgrade twrp flash latest firmware an be good.
Click to expand...
Click to collapse
So... when I do that, it'll replace the older TWRP, yes? I think the latest is 2.8 (here: http://teamw.in/project/twrp2/225)
...BUT then the newbie question: how to determine the latest firmware? What info do I need to provide to figure that out? And thanks once again, it is greatly, greatly appreciated.
Wombat Pete said:
So... when I do that, it'll replace the older TWRP, yes? I think the latest is 2.8 (here: http://teamw.in/project/twrp2/225)
...BUT then the newbie question: how to determine the latest firmware? What info do I need to provide to figure that out? And thanks once again, it is greatly, greatly appreciated.
Click to expand...
Click to collapse
Yea its 2.8.5.0 an just place in fastboot folder an reboot phone to bootloader then in terminal type
Fastboot flash recovery nameoffile.img
That will flash twrp.
Tigerstown said:
Yea its 2.8.5.0 an just place in fastboot folder an reboot phone to bootloader then in terminal type
Fastboot flash recovery nameoffile.img
That will flash twrp.
Click to expand...
Click to collapse
Got that, I've been doing that successfully enough. But you wrote: "flash the latest twrp and then flash the latest firmware zip"
It's the second part of that I'm not entirely sure of - the latest firmware zip ...for 4.4.4? For this phone? You didn't just mean updating TWRP, right? That's the newbie question I'm asking - after I flash the latest TWRP, how do I determine the right (best) firmware zip to flash thereafter?
Wombat Pete said:
Got that, I've been doing that successfully enough. But you wrote: "flash the latest twrp and then flash the latest firmware zip"
It's the second part of that I'm not entirely sure of - the latest firmware zip ...for 4.4.4? For this phone? You didn't just mean updating TWRP, right? That's the newbie question I'm asking - after I flash the latest TWRP, how do I determine the right (best) firmware zip to flash thereafter?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95916177934529541
Latest Att firmware zip. Needs to be flash via fastboot have you ever flash firmware before?
Tigerstown said:
https://www.androidfilehost.com/?fid=95916177934529541
Latest Att firmware zip. Needs to be flash via fastboot have you ever flash firmware before?
Click to expand...
Click to collapse
I just rooted the phone, in the process of which i flashed the (older, obviously, with the bug) version of twrp onto the phone. Established SU, etc.. I'm planning to get the latest viper rom on the phone - that's why i need to know the firmware number, because the instructions for getting viper on the phone begin with getting and flashing a Stock Backup and a stock recovery that
(i) corresponding with my current firmware version (newest, but definitely not newer), and
(ii) have the same SKU (x.xx.401.x) as this phone.
So ...I've flashed things,but - no, haven't flashed firmware before.
And any advice will be appreciated!
Wombat Pete said:
I just rooted the phone, in the process of which i flashed the (older, obviously, with the bug) version of twrp onto the phone. Established SU, etc.. I'm planning to get the latest viper rom on the phone - that's why i need to know the firmware number, because the instructions for getting viper on the phone begin with getting and flashing a Stock Backup and a stock recovery that
(i) corresponding with my current firmware version (newest, but definitely not newer), and
(ii) have the same SKU (x.xx.401.x) as this phone.
So ...I've flashed things,but - no, haven't flashed firmware before.
And any advice will be appreciated!
Click to expand...
Click to collapse
That'd how you flash firmware. Via fastboot
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader
Tigerstown said:
That'd how you flash firmware. Via fastboot
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader
Click to expand...
Click to collapse
I'm pretty sure that all makes sense to me - I'll do it tomorrow and report what happens here!
Tigerstown said:
That'd how you flash firmware. Via fastboot
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Part 1 was successful, part 2 - not.
I put the firmware file in root storage for the phone and in the fastboot directory of the computer, rebooted to fastboot and did what you said, but it failed:
target reported max download size of 1826414592 bytes
sending 'zip' (32221 KB)...
OKAY [ 2.031s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.054sI note that the firmware zip file to which you directed me ends in "S-off".
This phone is S-on still. Do I need S-off?
Or is there a firmware zip for S-on?
Or is that not the problem - was I supposed to have booted into TWRP?
Thanks, as ever
Wombat Pete said:
Part 1 was successful, part 2 - not.
I put the firmware file in root storage for the phone and in the fastboot directory of the computer, rebooted to fastboot and did what you said, but it failed:
target reported max download size of 1826414592 bytes
sending 'zip' (32221 KB)...
OKAY [ 2.031s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.054sI note that the firmware zip file to which you directed me ends in "S-off".
This phone is S-on still. Do I need S-off?
Or is there a firmware zip for S-on?
Or is that not the problem - was I supposed to have booted into TWRP?
Thanks, as ever
Click to expand...
Click to collapse
Yea s-off is needed..pretty sure I said that in a early post.
Additional info: redid it, tried with TWRP running, terminal didn't respond. So, as I presumed, we meant - have the phone in fastboot.
So I did that again, here's the terminal result:
C:\...FASTBOOTDIRECTORY>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.014s]
finished. total time: 0.017s
C:\...FASTBOOTDIRECTORY>fastboot flash zip ATT444fi
rmwareS_OFF.zip
target reported max download size of 1826418688 bytes
sending 'zip' (32221 KB)...
OKAY [ 2.027s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 4.273s
Tigerstown said:
Yea s-off is needed..pretty sure I said that in a early post.
Click to expand...
Click to collapse
Ah, ok. I'll do that, then.
I'm planning on following these instructions: http://htc-one.wonderhowto.com/how-...-one-m8-install-custom-firmware-mods-0154461/
Wombat Pete said:
Ah, ok. I'll do that, then.
I'm planning on following these instructions: http://htc-one.wonderhowto.com/how-...-one-m8-install-custom-firmware-mods-0154461/
Click to expand...
Click to collapse
Pretty sure that exploit is dead. I would try sunshine here.
http://theroot.ninja/
Tigerstown said:
Pretty sure that exploit is dead. I would try sunshine here.
http://theroot.ninja/
Click to expand...
Click to collapse
Sunshine says: incompatible with the device - this is a known issue, we're working on it.
Any ideas?
Tigerstown said:
Pretty sure that exploit is dead. I would try sunshine here.
http://theroot.ninja/
Click to expand...
Click to collapse
Yes, it's dead, and it doesn't look like Sunshine is going to work on this phone... yet. Unless I change something on it, and I'm having trouble figuring out what. So I can either figure out how to change my phone's contents so that Sunshine likes it better OR wait until Sunshine figures this out, which i think it will, eventually.
BUT...hmmm...is FASTBOOT the only way to get the new firmware onto the device? Can it be done by putting it in the right directory and using the recovery to flash it?
(I'm sure there's a way to get this done! I need a better understanding of what the various things that can be flashed are, of what needs to be flashed how, in what order, and why...)
Wombat Pete said:
Yes, it's dead, and it doesn't look like Sunshine is going to work on this phone... yet. Unless I change something on it, and I'm having trouble figuring out what. So I can either figure out how to change my phone's contents so that Sunshine likes it better OR wait until Sunshine figures this out, which i think it will, eventually.
Click to expand...
Click to collapse
If you are on hboot 3.19, sunshine won't work. If that is your case, there is nothing you can do to change that. You can't downgrade hboot with s-on.
Wombat Pete said:
BUT...hmmm...is FASTBOOT the only way to get the new firmware onto the device? Can it be done by putting it in the right directory and using the recovery to flash it?
(I'm sure there's a way to get this done! I need a better understanding of what the various things that can be flashed are, of what needs to be flashed how, in what order, and why...)
Click to expand...
Click to collapse
What you describe is not possible. The partitions needed to flash (radio, hboot, etc.) are protected unless you s-off. The means of flashing (fastboot, etc) doesnt' change that fact. Only a signed, encrypted firmware will work.
So if you have hboot 3.19, you are stuck with the current firmware until AT&T releases the LP update.
---------- Post added at 10:39 AM ---------- Previous post was at 10:20 AM ----------
Wombat Pete said:
... that the software number IS the firmware number on this phone.
Click to expand...
Click to collapse
Yes and no.
Folks here most commonly refer to the firmware number as being the same as the software number since the "firmware" in fact does not have a "number". "Firmware" (and that term is potentially confusing in itself) is simply a collection of critical modules (partitions?) that get updated with an OTA or RUU, but are not on the system (ROM or software) partition. We essentially refer to firmware numbers by the software it deployed with, simply for lack of anything better to refer to them by.
In fact, the main version (that is missing for you) is a bit irrelevant. On stock device, it will tell you what "firmware number" you are on. But if you start flashing ROMs, that isn't the case anymore. Main version will just then just be changed to read whatever software version (ROM) is on the phone, which will not necessarily correspond to the firmware. For instance, you might have KitKat firmware (say "number" 3.42) on the phone. But flash a Lollipop based ROM, say 4.16 software, and your "main version" will read 4.16, even though your firmware has not changed.
Its more reliable to look at hboot and radio numbers, and then decipher what firmware you are currently on. But even that can be a little misleading. As some folks will then (as I've witnesses) get the mistaken impression that all they need to do is update the hboot. Which is just one of the several "critical" components contained in the firmware zip.
The following post come from another thread the OP had opened. No need for 2 threads on the same subject:good:
Wombat Pete said:
Successfully rooted, busybox installed, all good so far. Now I'd like to move to the latest Viper.
The first real problem: I can't figure out my firmware version. When I run “fastboot getvar all”, the info starts with:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: [email protected]
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
...
THAT IS, no main version information.
I'm new at this, though learning. TWO THINGS I don't quite understand: (i) I saw a recommendation for reverting to the previous recovery... that means just going to the Fastboot menu and hitting recovery? And then would I have to go through the reboot process again to get where I am now? AND (ii) The VIPER page describes the process, which involves flashing a stock backup and a stock recovery and THEN TWRP - I'd love to understand what that's for, why it's necessary before flashing the new ROM.
Not sure how to proceed with without knowing the firmware number. I *DID* determine that hboot 1.55 means 3.xx.xxx.x, which seems to be the case here (the "version-bootloader" line).
I *could* go for S-off, but I'm not sure I need to or even want to.
Soooo.... not sure. IN the phone's OS it says:
Android version: 4.4.4
HTC Sense version: 6.0
Software number: 3.42.502.1
HTC SDK API level: 6.25
Kernel bversion: 3.4.0-g931e842
[email protected] #1
SMT PREEMPT
Build number: 3.42.502.1 CL 441323 release-keys
I thought those numbers (3.42.502.1) were supposed to be clear to the firmware number. Which is consistent with "hboot 1.55 means 3.xx.xxx.x". BUT ...Viper's presumption of "1.54" is throwing me off.
Not ready to proceed, I think, until I figure it out. Any and all help will be appreciated!
Click to expand...
Click to collapse