Related
I got a 3d from a friend who says he was trying to root it. He did the htc unlock I think. The bootloader said unlocked, I relocked it with the relock oem command on cmd. I have tried a few different IMG and exe files and none will work. does anyone have any ideas as to what else I could try? Ive googled and all I keep getting is more downloads for ruu.
Any help will be greatly appreciated.
gamy2121 said:
I got a 3d from a friend who says he was trying to root it. He did the htc unlock I think. The bootloader said unlocked, I relocked it with the relock oem command on cmd. I have tried a few different IMG and exe files and none will work. does anyone have any ideas as to what else I could try? Ive googled and all I keep getting is more downloads for ruu.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
This article tells you how to read and set the CID. It's written for the GSM version, but the "readcid" command seems to work on my CDMA version and has a value of "SPCS_001". If that's not what your phone shows it may be why the RUU's aren't working.
I didn't try the "writecid" command since I don't need to change mine.
ramjet73
ramjet73 said:
This article tells you how to read and set the CID. It's written for the GSM version, but the "readcid" command seems to work on my CDMA version and has a value of "SPCS_001". If that's not what your phone shows it may be why the RUU's aren't working.
I didn't try the "writecid" command since I don't need to change mine.
ramjet73
Click to expand...
Click to collapse
I just did the readcid and it says I have SPCS_001
gamy2121 said:
I just did the readcid and it says I have SPCS_001
Click to expand...
Click to collapse
Are you putting your phone into "fastboot USB" mode in the bootloader before running the RUU.exe from Windows? It's supposed to work if you're booted into Android and just reboot into the bootloader on its own, but sometimes that doesn't work.
Also, try the "fastboot devices" command from the PC directory with ADB before running the RUU.exe and make sure you get a serial number that starts with "HT" as a response.
ramjet73
ramjet73 said:
Are you putting your phone into "fastboot USB" mode in the bootloader before running the RUU.exe from Windows? It's supposed to work if you're booted into Android and just reboot into the bootloader on its own, but sometimes that doesn't work.
Also, try the "fastboot devices" command from the PC directory with ADB before running the RUU.exe and make sure you get a serial number that starts with "HT" as a response.
ramjet73
Click to expand...
Click to collapse
Yes to the fastboot usb - Thats all I can do if I try to boot up it just gets stuck at the white htc screen.
edit: this is what Im getting on the fastboot devices --- SH19THX01975 fastboot
gamy2121 said:
Yes to the fastboot usb - Thats all I can do if I try to boot up it just gets stuck at the white htc screen.
edit: this is what Im getting on the fastboot devices --- SH19THX01975 fastboot
Click to expand...
Click to collapse
I don't recognize that serial number as an Evo 3D. I have two and their serials both start with "HT".
Maybe someone else can help with that.
ramjet73
ramjet73 said:
I don't recognize that serial number as an Evo 3D. I have two and their serials both start with "HT".
Maybe someone else can help with that.
ramjet73
Click to expand...
Click to collapse
Thanks for your help, I did notice on the phone one of the errors was something about hoot being older.
SOLVED*****
Heres what I had to do incase some else ever has this problem.
IDK what the previous owner did but I had to start the RUU on the PC then go into the temp folder and go into the ROM folder with 7zip and take the stock recovery.img and fastboot flash it through cmd. Then I ran the RUU and the phone finally took it.
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
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
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