Hi there. I unlocked the bootloader using HTCDev, flashed recovery to 4Ext recovery, rooted, took backup and installed Endymion.
So now I have,
HBOOT 2.00.002
S-On
Endymion 3.4
I want to restore my stock ROM. I tried going to recovery (vol down + power button), wipe clean, restore the ROM. Restoring is success but I am unable to boot. I get stuck in HTC with white background screen and then it reboots to 4Ext recovery. I tried flashing boot.img from the back up but it made no difference. Please help me out.
Since you want Stock you can flash partition images from a rom.zip taken from RUU with the suitable version (system and boot)
amidabuddha said:
On your SDcard there is a folder named "clockworkmod". Find your backup there, copy the boot.img to your PC and flash it via fastboot.
Click to expand...
Click to collapse
Yes. I tried the same. But it did not make any difference. Actually, I want to generalize it. In case, I back up some other ROM and want to restore, I will face same issue. Am I missing anything ?
prince87 said:
Yes. I tried the same. But it did not make any difference. Actually, I want to generalize it. In case, I back up some other ROM and want to restore, I will face same issue. Am I missing anything ?
Click to expand...
Click to collapse
I was not reading your post carefully. My post is edited.
But my recommendation is to use one of the guides from the Index thread to downgrade your version and S-OFF. The you will solve all the inconveniences, caused by the htcdev.com unlock method...
amidabuddha said:
I was not reading your post carefully. My post is edited.
But my recommendation is to use one of the guides from the Index thread to downgrade your version and S-OFF. The you will solve all the inconveniences, caused by the htcdev.com unlock method...
Click to expand...
Click to collapse
If I do any of this, will I updates from HTC ? I mean, if restore to stock and tommorrow HTC releases updates. Will I be getting it ?
prince87 said:
If I do any of this, will I updates from HTC ? I mean, if restore to stock and tommorrow HTC releases updates. Will I be getting it ?
Click to expand...
Click to collapse
yes when you restore stock you will have the update. But for his you need to be completely Stock - so your hboot should be locked, your recovery should be stock, etc....
@poster
have you tried flashing the boot.img of the RUU u want to use tru fastboot usb?
lynxnoon said:
@poster
have you tried flashing the boot.img of the RUU u want to use tru fastboot usb?
Click to expand...
Click to collapse
I flashed the boot.img from my ROM back up. My baseband version is 20.4801.30.0822U_3822.10.08.04_M. Build number is 1.05.401.4. I found 4 RUUs with same baseband version but not build number. So I am not sure it will completely restore back to my custom ROM. Will it ?
prince87 said:
I flashed the boot.img from my ROM back up. My baseband version is 20.4801.30.0822U_3822.10.08.04_M. Build number is 1.05.401.4. I found 4 RUUs with same baseband version but not build number. So I am not sure it will completely restore back to my custom ROM. Will it ?
Click to expand...
Click to collapse
With this build number you can flash any European RUU (1.28.401.1 or 1.47.401.4 or 2.10.401.9). Just lock your bootloader first
amidabuddha said:
With this build number you can flash any European RUU (1.28.401.1 or 1.47.401.4 or 2.10.401.9). Just lock your bootloader first
Click to expand...
Click to collapse
So there is no way I revert back to my old build number? With European RUU, I can get updates only when HTC releases updates in Europe. Am I correct ?
prince87 said:
So there is no way I revert back to my old build number? With European RUU, I can get updates only when HTC releases updates in Europe. Am I correct ?
Click to expand...
Click to collapse
There is no release with version 1.05.401.4 for saga (Desire S) To check your original build number reboot the phone to bootloader, connect to PC (setup fastboot - link in my signature) and type in cmd:
Code:
fastboot getvar version-main
the output of this command should be your original build number. Find the correct RUU and use it t restore to Stock as it was before. (do not forget to lock the bootloader first - fastboot oem lock)
amidabuddha said:
There is no release with version 1.05.401.4 for saga (Desire S) To check your original build number reboot the phone to bootloader, connect to PC (setup fastboot - link in my signature) and type in cmd:
Code:
fastboot getvar version-main
the output of this command should be your original build number. Find the correct RUU and use it t restore to Stock as it was before. (do not forget to lock the bootloader first - fastboot oem lock)
Click to expand...
Click to collapse
Thanks. You are right. My version is actually 2.15.720.3. I am having difficulty locating for that particular version. However, I found an RUU for 2.15.832.5. Not sure whether I can use that.
prince87 said:
Thanks. You are right. My version is actually 2.15.720.3. I am having difficulty locating for that particular version. However, I found an RUU for 2.15.832.5. Not sure whether I can use that.
Click to expand...
Click to collapse
You have to use misc_version (you can use this guide without the rooting part) to change your build number to 1.47.720.1 and flash the RUU_Saga_hTC_Asia_India_1.47.720.1 from the Shipped Desire S ROM thread. The check for updates and update to the latest Stock version Over the Air (OTA)
Edit: just saw your post - 2.15.832.5 is not for your region - you will brick the phone with it...go with the above
amidabuddha said:
You have to use misc_version (you can use this guide without the rooting part) to change your build number to 1.47.720.1 and flash the RUU_Saga_hTC_Asia_India_1.47.720.1 from the Shipped Desire S ROM thread. The check for updates and update to the latest Stock version Over the Air (OTA)
Edit: just saw your post - 2.15.832.5 is not for your region - you will brick the phone with it...go with the above
Click to expand...
Click to collapse
I tried this. I could go till step 6. Then when I ran the RUU, I got incorrect version error on PC and Desire S screen went black.
prince87 said:
I tried this. I could go till step 6. Then when I ran the RUU, I got incorrect version error on PC and Desire S screen went black.
Click to expand...
Click to collapse
Are you using RUU_Saga_hTC_Asia_India_1.47.720.1 ?
amidabuddha said:
Are you using RUU_Saga_hTC_Asia_India_1.47.720.1 ?
Click to expand...
Click to collapse
Yes. But baseband version does not match. My device is still S-ON. Will the above procedure work ?
prince87 said:
Yes. But baseband version does not match. My device is still S-ON. Will the above procedure work ?
Click to expand...
Click to collapse
The baseband is different, because this version is older. You will not find a 2.15.720.3 RUU at this point so you need to downgrade.
Are you sure that you have successfully changed your misc_version to 1.47.720.1 ?
amidabuddha said:
The baseband is different, because this version is older. You will not find a 2.15.720.3 RUU at this point so you need to downgrade.
Are you sure that you have successfully changed your misc_version to 1.47.720.1 ?
Click to expand...
Click to collapse
Well. I don't know how to be sure. I followed step-by-step and I got no errors. However, the RUU version detected was same as my current one. If possible, it would be great if I could avoid this whole RUU thing. I have a back up and I am able to restore. If there was any way, I could boot to it, it would be great.
prince87 said:
Well. I don't know how to be sure. I followed step-by-step and I got no errors. However, the RUU version detected was same as my current one. If possible, it would be great if I could avoid this whole RUU thing. I have a back up and I am able to restore. If there was any way, I could boot to it, it would be great.
Click to expand...
Click to collapse
Ok you can try to flash the backup images from the clockworkmod folder one by one with fastboot:
Code:
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash data data.img
fastboot flash hboot boot.img
Edit: also see the "info" option in 4EXT for errors. If any - wipe the cache and try to boot again
amidabuddha said:
Ok you can try to flash the backup images from the clockworkmod folder one by one with fastboot:
Code:
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash data data.img
fastboot flash hboot boot.img
Edit: also see the "info" option in 4EXT for errors. If any - wipe the cache and try to boot again
Click to expand...
Click to collapse
Is it fastboot flash hboot boot.img? I thought it was fastboot flash boot boot.img ? Also, my backups are stored as ext4.tar files. So I img for boot and recovery only.
Related
I updated to ICS via OTA while already S-OFF. I thought I would able to update recovery again via hboot and nandroid back, but I seem to be stuck.
Any ideas? I double checked and the script shows model id pg5813000.
Help?
Phateless said:
I updated to ICS via OTA while already S-OFF. I thought I would able to update recovery again via hboot and nandroid back, but I seem to be stuck.
Any ideas? I double checked and the script shows model id pg5813000.
Help?
Click to expand...
Click to collapse
nandroid backup wont have recovery (it just has the backup of ROM)..so it wont work
as far as flashing recovery via Pg58IMG.zip file from bootloader
you need to make sure that android-info.txt inside the zip has your cid and mid
if it doesn't match..just edit and replace with yours
to get your cid and mid---fastboot commands
fastboot getvar cid
fastboot getvar mid
Phateless said:
I updated to ICS via OTA while already S-OFF. I thought I would able to update recovery again via hboot and nandroid back, but I seem to be stuck.
Any ideas? I double checked and the script shows model id pg5813000.
Help?
Click to expand...
Click to collapse
I hope you are still on an ENG Hboot, if not, please get user friendly firmware corresponding to your CID and flash it.
Now, I've attached a recovery.img, this is your stock recovery.
Connect fastboot usb
fastboot flash recovery recovery.img
fastboot reboot
Then apply OTA.
PS: Being a senior member I assume you don't need more help than that, if you do, please post back
ganeshp said:
nandroid backup wont have recovery (it just has the backup of ROM)..so it wont work
as far as flashing recovery via Pg58IMG.zip file from bootloader
you need to make sure that android-info.txt inside the zip has your cid and mid
if it doesn't match..just edit and replace with yours
to get your cid and mid---fastboot commands
fastboot getvar cid
fastboot getvar mid
Click to expand...
Click to collapse
kgs1992 said:
I hope you are still on an ENG Hboot, if not, please get user friendly firmware corresponding to your CID and flash it.
Now, I've attached a recovery.img, this is your stock recovery.
Connect fastboot usb
fastboot flash recovery recovery.img
fastboot reboot
Then apply OTA.
PS: Being a senior member I assume you don't need more help than that, if you do, please post back
Click to expand...
Click to collapse
Thanks for your help guys.
I'm not trying to apply ota, I've already done that. I'm already at bone stock ics, and trying to flash clockwork recovery so I can restore a nandroid of cm7, but the new Hboot doesn't like any of the files that used to work fine.
Unfortunately I am not on an engineering Hboot, but I am still S-off. Will fastboot still work?
The phone boots and runs fine, but I might be stuck with no way back to root.
This thread is about the sensation, but I'm using the glacier because it still has cm7 on it.
Sent from my HTC Glacier using xda premium
Phateless said:
Thanks for your help guys.
I'm not trying to apply ota, I've already done that. I'm already at bone stock ics, and trying to flash clockwork recovery so I can restore a nandroid of cm7, but the new Hboot doesn't like any of the files that used to work fine.
Unfortunately I am not on an engineering Hboot, but I am still S-off. Will fastboot still work?
The phone boots and runs fine, but I might be stuck with no way back to root.
This thread is about the sensation, but I'm using the glacier because it still has cm7 on it.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Mate, just go my tool (link in description), there is a recovery.img for 4EXT in the attachments.
Flash it like I told you. If it fails , you will need to get an ENG boot by flashing appropriate fw.
Hope this helps.
kgs1992 said:
Mate, just go my tool (link in description), there is a recovery.img for 4EXT in the attachments.
Flash it like I told you. If it fails , you will need to get an ENG boot by flashing appropriate fw.
Hope this helps.
Click to expand...
Click to collapse
I think you misunderstand. I am not trying to apply the OTA because I have already done that. I am currently stuck at stock rom, with stock recovery, but s-off, and I'm trying to get my custom recovery back so I can restore a cm7 build, or maybe flash cm9.
Right now I'm installing drivers so I can try your fastboot commands.
It worked! I just had the wrong mid/cid in the script. Thanks guys, I'm back in business!
Phateless said:
I think you misunderstand. I am not trying to apply the OTA because I have already done that. I am currently stuck at stock rom, with stock recovery, but s-off, and I'm trying to get my custom recovery back so I can restore a cm7 build, or maybe flash cm9.
Right now I'm installing drivers so I can try your fastboot commands.
Click to expand...
Click to collapse
4EXT is a custom recovery. You will be able to restore your NANDROID backup through that recovery.
I don't know how to make this any clearer mate.
kgs1992 said:
4EXT is a custom recovery. You will be able to restore your NANDROID backup through that recovery.
I don't know how to make this any clearer mate.
Click to expand...
Click to collapse
The problem was that the hboot wasn't accepting my pg58img.zip. I was using that to try to flash cwm5. I think you were misunderstanding the problem I was having.
Phateless said:
The problem was that the hboot wasn't accepting my pg58img.zip. I was using that to try to flash cwm5. I think you were misunderstanding the problem I was having.
Click to expand...
Click to collapse
Yes, because you need an unlocked Hboot for pg58img to be flashed.. so instead of solving the problem, I gave you a workaround of installing 4ext instead of cwm mate..
Sent from my HTC Sensation XE with beats audio
kgs1992 said:
Yes, because you need an unlocked Hboot for pg58img to be flashed.. so instead of solving the problem, I gave you a workaround of installing 4ext instead of cwm mate..
Sent from my HTC Sensation XE with beats audio
Click to expand...
Click to collapse
I have a locked hboot, but S-OFF prevailed because I had done that before applying the ICS ota update.
The issue wasn't which recovery I was installing, the issue was that my hboot wouldn't accept my pg58img.zip file because I didn't have the correct cid and mid in there. Once I corrected that I was able to flash cwm recovery 5.
Your solution of using fastboot to confirm my mid and cid did help, I just chose to use a different recovery. Does that make more sense?
Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!
LSGio said:
Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!
Click to expand...
Click to collapse
1. No, if you have S-ON you can't create a NAND backup as you don't have a custom recovery.
2. ***TAMPERED*** means that an app or apps have gone into your /system/ partition, thereby triggering the tampered flag. You can remove this message by running a HTC RUU.
3. No, you first flash the zip file with the boot.img inside, then flash the boot.img in the bootloader. fastboot flash boot boot.img
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
Then yes you can make a backup and restore later. Just always full wipe, cache and dalvik cache wipe.
As far as flashing kernels/boot.img, if you are < hboot 1.13 then just flash via recovery. If your hboot is > or = to hboot 1.13tjen flash via fastboot or flash img GUI (available in the play store and in various threads).
And as of right now there is no s-off for the one s.
Sent from a baked One S
If I've helped hit the thanks button
LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.
KACE321 said:
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.
Click to expand...
Click to collapse
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?
LSGio said:
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?
Click to expand...
Click to collapse
fastboot oem writecid 11111111
usaff22 said:
fastboot oem writecid 11111111
i have 2 questions:
1.how many 1's do i have to write
2.can i get back to my cid and how?
Click to expand...
Click to collapse
Yes, you can make nand backups and restore them if you have a custom recovery. You don't need to have s-off for that but you do need to have your bootloader unlocked. Depending on your hboot version, restoring a nand backup will not restore your boot image. (1.09 and below will, 1.13 and up won't.) We do now have the means to downgrade hboot tho.
You get the *tampered* line if your recovery is unsigned. When you use a custom rom, you will most likely also get a red warning text over your boot splash. It's normal.
You have to extract the boot image from the rom zip and flash it in fastboot before you boot the new rom. This may even be before you flash the new rom. You can leave the rom zip unchanged and flash it in recovery.
-Jobo
if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Sent from my HTC One S using xda app-developers app
LSGio said:
if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Click to expand...
Click to collapse
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
LSGio said:
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Click to expand...
Click to collapse
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.
touch of jobo said:
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.
Click to expand...
Click to collapse
can you please tell me how can i download an ruu that matches my stock rom. cause when i get to the filefactory server it tells me that i need to buy premium because the file is larger than 500MB.
and the link to the ruu downloads is from this thread:
http://forum.xda-developers.com/showthread.php?t=1543588
if youll go to the first page and click the (ville S4) link you will see a list of ruu's but i can't download them because the size of them is larger han 500mb and i need premium.
I've got an HTC One S [s3]. CID is HTC__622 Asia HK
I have unlocked bootloader, TWRP recovery and superSU loaded as well as Rom Manger
Tonight there is an OTA update available. So I want to use it. I downloaded it and
ran command: fastboot oem lock
and tried to run the update. It just keeps booting into my fastboot menu.
I heard that I need to install stock recovery tfor this to work but I don't know where I can find it.
I do have a reovery_signed.img file that I saved from somewhere that is 5,957 kb. Not sure if I flash that if it would give me stock recovery.
Can someone give me a direction to go. I have spent last 12 hours just reading stuff and still don't know what to do.
Htc_asia_hk Stock Recovery File
Does anyone know where I can find the stock recovery file for my One S [S3]
Its Htc_asia_hk the CID is HTC__622 ???
The beginning of the file name should look like this:
RUU_VILLEC2_U_ICS_40_HTC_ASIA_HK_
Flash stock recovery
Lock bootloader
Then run the ota update.
Sent from a HTC
Try This RUU in fastboot
http://forum.xda-developers.com/showthread.php?t=2011598
Quills88 said:
Does anyone know where I can find the stock recovery file for my One S [S3]
Its Htc_asia_hk the CID is HTC__622 ???
The beginning of the file name should look like this:
RUU_VILLEC2_U_ICS_40_HTC_ASIA_HK_
Click to expand...
Click to collapse
you dont need to flash stock recovery because RUU does ...
luxandroid said:
you dont need to flash stock recovery because RUU does ...
Click to expand...
Click to collapse
The problem is I didn't take a backup before I unlocked my bootloader and flashed twrp recovery so I don't have a stock recovery to go back to.
The RUU for HTC__044 has a different CID and won't work on my device unless I can extract just the stock recovery from the RUU without having to install it. Is that possible?
same
Quills88 said:
The problem is I didn't take a backup before I unlocked my bootloader and flashed twrp recovery so I don't have a stock recovery to go back to.
The RUU for HTC__044 has a different CID and won't work on my device unless I can extract just the stock recovery from the RUU without having to install it. Is that possible?
Click to expand...
Click to collapse
i also have htc__622 CID and i didn't make backup before fiddling with the innards.
What you have to do is
1. Flash stock recovery
2. Lock your bootloader
3. Enter fastboot and run the RUU for your phone
Your phone will then be just as it was when you bought it and then you can run the OTA. Make sure you find the right RUU for your phone. I have been searchiing for one for days and couldnt find it. Hope this helped
nez762 said:
What you have to do is
1. Flash stock recovery
2. Lock your bootloader
3. Enter fastboot and run the RUU for your phone
Your phone will then be just as it was when you bought it and then you can run the OTA. Make sure you find the right RUU for your phone. I have been searchiing for one for days and couldnt find it. Hope this helped
Click to expand...
Click to collapse
I have the same problem, so I have few questions....
Where can I find stock recovery for HTC One S c2?
How to lock bootloader?
THANK YOU!
I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
sorry, for my bad english.
Privremeni said:
I have the same problem, so I have few questions....
Where can I find stock recovery for HTC One S c2?
How to lock bootloader?
THANK YOU!
Click to expand...
Click to collapse
Hi,
You can lock your bootloader with next command in fastboot:
fastboot oem lock
But question remains
Where can I find stock recovery for HTC One S c2?
Somebody cab help us?
Thanks!
Impo5sible said:
I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
sorry, for my bad english.
Click to expand...
Click to collapse
You cant flash OTA trough TWRP, thats my problem also. My CID is 032 as yours. If you find RUU JB, send me the link please!
Privremeni said:
You cant flash OTA trough TWRP, thats my problem also. My CID is 032 as yours. If you find RUU JB, send me the link please!
Click to expand...
Click to collapse
Maybe a stock recovery of JB would be enough.
Hello guys,
Try this:
Step 1: relock the bootloader (start your phone in fastboot, open cmd, got to folder where are fastboot files, type "fastboot oem lock" )
Step 2: find your desired stock jb or ics online. http://filesdownload.net/showthread.php?70-HTC-One-S-(-RUU_VILLE-)-(-RUU_VILLEC2-)
Step 3: connect your phone to the pc in fastboot (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
Step 5: Now you are in stock ROM
It should work after this!
On my HTC One S [S3] , CID HTC_032 works
splanet.info has something interesting
At least ota is there for htc__622
Nez is right
nez762 said:
What you have to do is
1. Flash stock recovery
2. Lock your bootloader
3. Enter fastboot and run the RUU for your phone
Your phone will then be just as it was when you bought it and then you can run the OTA. Make sure you find the right RUU for your phone. I have been searchiing for one for days and couldnt find it. Hope this helped
Click to expand...
Click to collapse
After I locked my bootloader and tried running the OTA update I tried a few things that didn't work.
But what did work for me was when I unlocked bootloader again
And used Hasoon's Toolkit for One S
and reflashed the recovery file. I used the recovery_signed.img file (5,957 kb) that I had saved from when I was rooting it the first time and renamed it to a one word name per Hasoon's instructions, then flashed it.
Then I relocked bootloader and did a factory reset and ran the OTA update and it worked.
I was lucky that I had that recovery file saved. Still not sure where I got it from. But one thing for sure is that it was hard to find a RUU file for my CID. Hasoon's toolkit does have links to a website with a list of RUUs on it but mine wasn't on the list.
If you want me to email you my signed_recovery.img file send me a pm with your email address and I'll send it.
Privremeni said:
I have the same problem, so I have few questions....
Where can I find stock recovery for HTC One S c2?
How to lock bootloader?
THANK YOU!
Click to expand...
Click to collapse
I have attached the stock recovery just use fastboot to flash it
Hi! First of all I would like to thank everyone that helped me to get that update via OTA successfully. Now I'm running debranded Android 4.2.2 Sense 5 and I would like to share with you this clear TWRP Backup of freshly installed ROM. All I did to this I made a factory reset before making a backup. I made a backup with TWRP 2.6.3.0 (openrecovery-twrp-2.6.3.0-k2_ul.img). The backed up partitions are: Boot, Data and System.
>> CLICK HERE TO DOWNLOAD << (dev-host mirror) (Android File Host mirror)
>> Firmware.zip <<
Further details:
Android 4.2.2
HTC Sense 5.0
Software version: 3.11.401.1
HTC SDK API: 5.41
Kernel version:
3.4.10-gae62ace
[email protected] #1
SMP PREEMPT
Radio:
1.18.40a.00.05_10.81a.40.23L
Build version:
3.11.401.1 CL260192 release-keys
Browser version:
WebKit/534.30
CIDs which were attached to update from 4.1.2 to 4.2.2:
HTC__001
HTC__016
HTC__032
HTC__203
HTC__A07
HTC__E11
HTC__J15
HTC__Y13
These CIDs should run this build without any scratch. I'm not sure about the others!
Instructions to the firmware.zip
loCe45 said:
Things I've done to flash firmware (I have S-off):
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Now everything should be in working order (network, speaker)
afterwards dont forget to flash back twrp recovery:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
You can also flash the firmware.zip by changing it name to PL80IMG.zip and placing it on your sd card. Then avoiding the adb and fastboot this time just reboot to bootloader (just reboot the device by pressing power and selecting Restart and just after screen turns off hold the VOL- button until the bootloader appears), then it would search for the file you placed on sd card. When it'll find it it will ask you for flash - confirm by pressing VOL+, then after it completes - POWER to reboot.
If you want, i can put it on my dev-host or androidfilehost account.
old.splatterhand said:
If you want, i can put it on my dev-host or androidfilehost account.
Click to expand...
Click to collapse
Good idea. But now - post it to the attachment system?
EDIT: nvm, uploading to MediaFire
DOWNLOAD LINK IS UP! Look in OP.
Hello ! I am with JB 4.1.2 stock ,rooted ... i want to ask do i need to change the radio or something before i flash the rom ? Thanks you for the work !
my radio is 1.15.40a.00.04
After third try, my upload at dev-host was successful: http://d-h.st/fT7
@[mention]Bazdir[/mention]
You can put the link into your first post.
I'll come back, when upload to androidfilehost is finished.
Would be nice if you attached the firmware files too, because network doesnt work with old radio/baseband
Temporary link to firmware: https://dl.dropboxusercontent.com/u/905514/firmware.zip
Please reupload it somewhere else.
Things I've done to flash firmware (I have S-off):
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Now everything should be in working order (network, speaker)
afterwards dont forget to flash back twrp recovery:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
btw. imho this is the fastest way to get new update if you're not fully stock
@Bazdir
Some links for first post:
Your backup at androidfilehost:
http://www.androidfilehost.com/?fid=23212708291675772
Firmware.zip for k2ul at Dev-host: http://d-h.st/uwh
Missing language
Yesterday I tried to install this backup. The update process was without any problems but I had the noisy voice. So I went back to Saturn III.
I have seen there is a firmware.zip. Can I use TWRP to install? Or how must this be done???
Another problem was/ is that I couldn't select the right language: I have found "Deutsch (Belgien)" etc but there was no "Deutsch (Deutschland)".
@ old.splatterhand
I believe you have tried this ROM. Which one did you used?
Yes, i tried it. When i remember right, i used Deutschland (United Kingdom).
There popped up various variants to flash the firmware files, but as i didn't i can't give any guide or helping hand at this point.
I will wait, 'til the OTA for my phone is coming, so i will be sure, that i have the correct file (with correct language) for flashing.
Sylvia said:
Yesterday I tried to install this backup. The update process was without any problems but I had the noisy voice. So I went back to Saturn III.
I have seen there is a firmware.zip. Can I use TWRP to install? Or how must this be done???
Another problem was/ is that I couldn't select the right language: I have found "Deutsch (Belgien)" etc but there was no "Deutsch (Deutschland)".
@ old.splatterhand
I believe you have tried this ROM. Which one did you used?
Click to expand...
Click to collapse
I've just explained how to flash the firmware two posts above.
loCe45 said:
I've just explained how to flash the firmware two posts above.
Click to expand...
Click to collapse
Ups, sorry!
I made a restore with your file and flashed the given firmware with bootloader. It did Not fix my sound problem. Do I need to be s-off to make it work?
-My radio is still 1.15.40a...
-K2ul, s-on, unlocked, rooted
-I installed the 32mb firmware.zip from the first post by changing the name and following instructions
Sent from my HTC One SV using xda app-developers app
If somebody try use this backup with CID not listed here? I have some problem with this. MD5 is correct but twrp shows loading failure. I have stock odexed 4.1.2 with s-off. My Cid is T-Mobile Poland.
HTC One SV + Tapatalk
djmietekk said:
I made a restore with your file and flashed the given firmware with bootloader. It did Not fix my sound problem. Do I need to be s-off to make it work?
-My radio is still 1.15.40a...
-K2ul, s-on, unlocked, rooted
-I installed the 32mb firmware.zip from the first post by changing the name and following instructions
Sent from my HTC One SV using xda app-developers app
Click to expand...
Click to collapse
Radio haven't changed...? Weird. Maybe this is because of S-ON and you have different CID than listed in android-info.txt, which prevents the flash. I was doing it being S-OFF. I have no idea.
marceli-szpak said:
If somebody try use this backup with CID not listed here? I have some problem with this. MD5 is correct but twrp shows loading failure. I have stock odexed 4.1.2 with s-off. My Cid is T-Mobile Poland.
HTC One SV + Tapatalk
Click to expand...
Click to collapse
Loading failure...? Interesting. Did you tried restoring it with TWRP that I have? ( http://techerrata.com/file/twrp2/k2_ul/openrecovery-twrp-2.6.3.0-k2_ul.img ) -- you don't have to flash it, if you don't want to - just place it where you have fastboot on your PC and do fastboot boot [file name here]
Ok. I change recovery and restore work's but I can't load firmware it shows bad Cid in bootloader. I try both via fastboot and PL80... file. So I must change Cid becouse without this I have noise problem while calling. Is it correct route ?
HTC One SV + Tapatalk
marceli-szpak said:
Ok. I change recovery and restore work's but I can't load firmware it shows bad Cid in bootloader. I try both via fastboot and PL80... file. So I must change Cid becouse without this I have noise problem while calling. Is it correct route ?
HTC One SV + Tapatalk
Click to expand...
Click to collapse
To be honest... @old.splatterhand said somewhere that it's not a firmware.zip related bug, but it's somewhere inside system files. So propably, when you'll restore from my backup, you should have everything working. Propably. I'm not sure about it, because I haven't tested it myself. And I'm S-OFF so it makes another difference.
Bluetooth was not firmware, noisy problem i think it is.
@marceli-szpak
Yes, change your cid otherwise it will fail.
old.splatterhand said:
Bluetooth was not firmware, noisy problem i think it is.
Click to expand...
Click to collapse
To be honest - Before ICS downgrade and making updates via OTA on different CID, I've updated bootloader with firmware.zip (the radio version has changed and stuff) and then flashed the odexed 4.2.2 ROM via TWRP and the noisy calls were still there.
Hello,
I am trying to flash CleanRom 7.0 or any JB rom on my HTC One X (AT&T) but always gets stuck in bootloop (phone does not go past boot screen after flashing). This is what i have done.
The phone is on AT&T 1.82 stock room (rooted, SuperCID, S-Off). The phone was on some older HBoot version so I upgraded it to 2.15. Radio is 0.17.32.09.12. And I have TWRP recovery.
So I made a nadroid backup in recovery and than tried to install AT&T 3.82 rooted (downloaded from XDA, may be without radio and all). After successful flashing when I tried to reboot the system it got stuck on AT&T boot screen. So I rebooted in recovery and wiped everything. After that I tried to install CleanROM 7.0 R2 and same thing happened and even I tried latest elemental kernel but same thing is keep happening.
Can you please help me with this?
Thanks
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
timmaaa said:
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
Click to expand...
Click to collapse
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
alex8525 said:
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
Click to expand...
Click to collapse
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.omg after flashing.
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
Yes I am S-Off. I will let you know the version of TWRP when I get back home since I don't have phone with me right now. By the way I used goomanager to update TWRP, if that helps.
Thanks,
phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
K so if you are s-off then you can just flash it. If you wernt then you would need to flash boot.img. now you can try to flash the boot.img. it might not fix it but start small and work up.
Sent from my HTC Butterfly s using Tapatalk
alex8525 said:
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
Click to expand...
Click to collapse
TWRP is the correct way to install ROMs, but I have a feeling that your current version of TWRP is your problem. Some (2.4.x, 2.5.x) are buggy and have major problems. If your TWRP version is either of those that I've just mentioned you can update it to a known bug-free version like this:
Download the modified version of TWRP*2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
That's the reason I asked what twrp version he had
Sent from my HTC Butterfly s using Tapatalk