Related
Hey guys, i have my rezound running cleanrom icse 3.1 and want to revert back to stock - no root ect. so much has changed since i did this last so im confused, How do i go back to stock, i did the factory reset but that just puts me back to no data on cleanrom icse 3.1.
Any help would be appreciated.
i have clockwork recovery installed
*unlocked*
s-on
hboot 2.10.000
thabnks
real stock
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
michaelbsheldon said:
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
Click to expand...
Click to collapse
Thanks, ill try this and get back to you.
Again thank you.
michaelbsheldon said:
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
Click to expand...
Click to collapse
im getting an error:
C:\mini-adb_vigor>fastboot oem writesecureflag 3
... INFOvreg_set: request is duplicated id 14
INFO vigor_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
INFOwritesecureflag: Permission denied, value 1
OKAY [ 1.578s]
finished. total time: 1.578s
C:\mini-adb_vigor>
any ideads?
next
Android Police posted a zip file 3.14.605.12PH98IMG.zip.
Its the same info in that RUU.
Download it, rename to just PH98IMG.zip and place in root of sdcard.
Run that, and it'll do the factory restore you want, maybe without those
unrequested comments it made in fastboot.
michaelbsheldon said:
Android Police posted a zip file 3.14.605.12PH98IMG.zip.
Its the same info in that RUU.
Download it, rename to just PH98IMG.zip and place in root of sdcard.
Run that, and it'll do the factory restore you want, maybe without those
unrequested comments it made in fastboot.
Click to expand...
Click to collapse
Tried that, didnt work, hboot/cwm recovery said invalid,
I finally got s-off with the JuopunutBear / wire trick and now it seems to be working.
Thank you for the guidance.:good:
Firstly, the problem why the RUU wasn't working, was that your bootloader was unlocked (fastboot oem lock to relock the bootloader)
This usually gives an "Unknown Error 99" message.
The reason it worked after S-OFF is because JuopunutBear erases the unlock token.
Secondly, when you're trying to do something like this, it's better to search for a reliable source for instructions & not jump at any answers that you can find.
michaelbsheldon said:
Do a Google search for:
RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe
Relock your phone with these fastboot commands:
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Then put your phone back into fastboot with power/volume down, then run this exe as Administrator.
You'l unroot it and turn it into 100% stock. If S-0ff, it wont change that.
Click to expand...
Click to collapse
This answer is so so wrong. How can you provide advice on something that you have no idea about?
This instructions are for S-ON & if your device has JuopunutBear hboot, then this will brick the phone.
Would you ever be willing to try something like this on your own phone?
*
If you'd been bothered to read OP comments, he was S-0n, so JBear Hboot couldn't have been there.
Save your crabby comments.
michaelbsheldon said:
If you'd been bothered to read OP comments, he was S-0n, so JBear Hboot couldn't have been there.
Save your crabby comments.
Click to expand...
Click to collapse
Sure, in which case writesecureflag isn't required at all.
Although these wrong S ON bricks are unbrickable, never in any case tell anyone to do that command unless you fully understand the implications of what you are saying.
If you notice, he later did S-OFF with JuopunutBear:
wohn said:
I finally got s-off with the JuopunutBear / wire trick and now it seems to be working.
Click to expand...
Click to collapse
in which case, his phone would have bricked if he had JB hboot had tried your commands.
The android police RUU you linked to is not an Official RUU, it's made from an OTA. Which is why he was unable to flash it without S-OFF.
The instructions you gave were wrong & I simply called you out on that.
I honestly don't want to argue on this, I just want you to be careful of what you advice people to do.
Although this is a public forum & everyone's input is welcome & I'm nobody to enforce any rules; I'm simply giving you my opinion.
The rest is upto you. Good day.
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
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Here is a picture of hboot:
Sent from my ADR6400L using xda app-developers app
cyberkeeper1 said:
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Click to expand...
Click to collapse
Something I don't understand here: how were you able to run fastboot oem writecid while S-ON? Have you since gone S-ON after writing the incorrect CID?
Furthermore, why in the world would you venture from my explicit instructions on how to fix the radio? I can't imagine any reason you would want to re-lock the bootloader or go S-ON. As I keep saying: if you are already unlocked or S-OFF, I almost never see a legitimate reason to run the RUU!
I assume you still can boot into CyanogenMod? If so, follow these instructions (Windows):
Set this in CM: Settings > Developer options > Root access > Apps and ADB
Download the latest unlock script package (we will not run the script, but we do need the files there)
Extract the unlock script package and open a command window in that directory
Type these commands:
Code:
adb root
adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
adb pull /sdcard/cid
hexalter cid 0x214=0x56,0x5A,0x57,0x5F,0x5F,0x30,0x30,0x31
adb push cid /sdcard/
adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
This should revert your CID back to VZW__001.
deleted
cyberkeeper1 said:
See I wish I could boot. I didn't understand why it accepted an oem command while s-on either. But alas, it did. I wrote that command after relocking. I am not s-off. Never was, hence my entire problem. I was afraid to try s-off because of the higher possibility of bricking my phone. It's not like the thunderbolt where it always works. If I was s-off I would know what to do and could flash hotdogs as my Cid if I wanted. My first problem is being stuck in hboot and can't restore. I wiped everything. Boot, data, system, recovery all in prep for stock since I am s-on
Click to expand...
Click to collapse
From the bootloader, what is the output this?
Code:
fastboot getvar cid
deleted
cyberkeeper1 said:
The output is:
VZW_0001
Click to expand...
Click to collapse
I can't even explain the number of ways you shot yourself in the foot. You really wiped recovery and boot too? How did you come to believe this would be a good idea? Or is necessary at all?
I believe the only option you have is to try and flash the stock signed recovery through fastboot (not even sure if it'll work), and then use ruu mode to TRY and fix things up:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ruu.zip
I suspect even that will complain about the incorrect CID though. Perhaps jose has some other ideas.
deleted
deleted
deleted
deleted
deleted
YESSSSSSSSSSSSSS! I GOT IT! I GOT IT! I GOT IT!
When i want something done, i try the impossible...
so... here is the thing... and COMPLETELY unexpected it is. Apparently, you can submit the following cid as an unlock token to HTCdev and get returned a valid unlock code BIN file. with VZW_0001 (obviously incorrect) i STILL received the file and it said token submitted successfully. downloaded, flashed and now unlocked. still s-on, but WAY more room for fixing now. i flashed the CID back to the proper VZW__001 using adb root shell in recovery. worked great! thanks MDMOWER for the codes to revert. now i can flash my custom ROM backup back to the device after flashing just the stock rom (NO RELOCKING THIS TIME FOR ME!) to fix the radios the way i was supposed to. ( being tired = not reading + not using glasses) i don't understand it myself, but i bet this one is going to through you for a loop. the only conclusion i can come up with is the fact that another device actually DOES use the CID of VZW_0001 and is not an officially supported device. that would explain why i was even able to be successful. but its speculation at best until confirmed.
cyberkeeper1 said:
YESSSSSSSSSSSSSS! I GOT IT! I GOT IT! I GOT IT!
When i want something done, i try the impossible...
so... here is the thing... and COMPLETELY unexpected it is. Apparently, you can submit the following cid as an unlock token to HTCdev and get returned a valid unlock code BIN file. with VZW_0001 (obviously incorrect) i STILL received the file and it said token submitted successfully. downloaded, flashed and now unlocked. still s-on, but WAY more room for fixing now. i flashed the CID back to the proper VZW__001 using adb root shell in recovery. worked great! thanks MDMOWER for the codes to revert. now i can flash my custom ROM backup back to the device after flashing just the stock rom (NO RELOCKING THIS TIME FOR ME!) to fix the radios the way i was supposed to. ( being tired = not reading + not using glasses) i don't understand it myself, but i bet this one is going to through you for a loop. the only conclusion i can come up with is the fact that another device actually DOES use the CID of VZW_0001 and is not an officially supported device. that would explain why i was even able to be successful. but its speculation at best until confirmed.
Click to expand...
Click to collapse
moderators, after a few replies from the users, i don't mind if you close my thread because my problem is solved.
EDIT: maybe not yet... bootlooping after fix and restore of last backup before the incident. do i have to have the Super CID written to boot from any custom rom?
cyberkeeper1 said:
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Here is a picture of hboot:
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
are you rooted?
EDIT: got confused and was thinking this was a new thread sorry
jose51197 said:
you rooted?
Click to expand...
Click to collapse
i am now that i fixed everything. well the recovery partition is rooted. i cant get my phone to boot now though. i tried using the backup i made right before returning to stock and it no longer works. i get a boot loop from the first boot screen. loads HTC logo, then legal warning in red. screen turns black and back again. it never loads into the CM10.1. i manually flashed the kernel from my backup since i am still s-on. i am going to try fresh installing a rom.
cyberkeeper1 said:
i am now that i fixed everything. well the recovery partition is rooted. i cant get my phone to boot now though. i tried using the backup i made right before returning to stock and it no longer works. i get a boot loop from the first boot screen. loads HTC logo, then legal warning in red. screen turns black and back again. it never loads into the CM10.1. i manually flashed the kernel from my backup since i am still s-on. i am going to try fresh installing a rom.
Click to expand...
Click to collapse
You messed a lot with you phone man, better install stock rom throught ruu or mdmowers way then s off revert cid and flash cm10
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
You messed a lot with you phone man, better install stock rom throught ruu or mdmowers way then s off revert cid and flash cm10
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
i am inclined to agree based on what its doing, but wanted to be sure. i just didnt want to have to re-re unlock again. lol. i'll see what happens.
I was able to successfully flash cyanogenmod, but my phone only works for data, not for calls or texts. I assume this is because I'm still on Super CID (11111111). When I try to revert to the VZW cid, i receive an error executing the adb shell. It tells me that it's a read only file system. I'm rooted, s off, and bootloader unlocked. Any help would be greatly appreciated as my phone is only half usable right now
Don't use adb shell once you're s-off. Use these commands:
Code:
adb reboot bootloader
Once in fastboot, issue this command to revert to the VZW CID:
Code:
fastboot oem writecid VZW__001
that's it.
Sent from my Incredible 4G LTE using xda app-developers app
Thanks so much for the quick response. I knew I was overthinking it. Just applied the change, rebooting now. I'll follow up with my findings.
---------- Post added at 06:27 PM ---------- Previous post was at 06:16 PM ----------
Well, it changed the CID, but the issue still persists. If I look in about phone > status, it says my mobile phone number is 000-000-0000. I'm definitely preplexed to say the least.
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
Hi There! How can I get access to all commands in FastBoot? I need command fastboot oem writeimei.
Device info(S-OFF):
HBOOT:1.25.0003
RADIO: 1.15.40.04
Do you have a patched bootloader on a Desire X? ENG instead of SHIP?
Normally fastboot is a DOS-command (phone should be in FASTBOOT mode).
RuudM said:
Do you have a patched bootloader on a Desire X? ENG instead of SHIP?
Normally fastboot is a DOS-command (phone should be in FASTBOOT mode).
Click to expand...
Click to collapse
I enter command(on my screenshot): fastboot oem ?. I use modificated HBoot. How can I patch my bootloader?
Actually it was a question about the patched HBoot, it seems to be an engineering HBoot (Google) which is rarely seen. Most phones (Desire X) are S-On so you can use the fastboot.exe command. The 'engineering HBoot' is different. I don't know how that command is executed. It looks like you don't need the fastboot command itself on that Hboot.
I assume you tried already al sorts of writeimei commands inside the box, with or without bootloader. Sorry, can't help you any further!
Iinformation of somebody else:
eng= engineering. In the bootloader screen,it will say "eng" where it currently says "ship"
Eng bootloaders were initially prepaired for testers of pre-release and developmental devices to make specific changes. they were never really intended to be in the public's hands as i mentioned,i dont think ive ever seen one for the one s. im sure one exists,but no one has leaked it,or accidentally found a device with it,if it does.
once,i completely randomly stumbled upon an eng hboot for the htc merge,while helping a user in puerto rico(his friends device had one)
patched= modified stock
it is simply a stock hboot that is "patched" or modified to provide some(but not all) of the extra fastboot commands,and elimiate the restrictions of the stock version(example,being able to "fastboot flash" ALL partitions)
patched hboots are not signed with an official htc signiture,and therefore,can ONLY be installed on s off phones. sneeking one onto an s on device(or turning a device s on with one present) will result in a potentially unrecoverable hard brick.
an example of a patched hboot is the hboots installed when one runs the "revolutionary" tool on older phones that that particular tool works on.
come to think of it,ive not seen any patched hboots for the one s,either,but then,im not in the xda one s forums daily
OK. What affects the commands of FastBoot? Version of HBoot? How can I get ENG Hboot?