Database Info

Restoring with 4Ext recovery

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.

[Q] S3 Villec2 OTA update

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

(GUIDE) RESTORE JB HBOOT 3.06 TO STOCK AFTER CUSTOM ROM ONE S C2 (villec2) !!

i find it hard to restore my one s because there is no official RUU for my one s c2,i failed to s-off aswel to use older RUU that i have so i found out that you can still restore your rom to stock after using custom roms..this method is tested and working (but me reminded to always have nandroid back up and use it at your own risk)
1st step: download a OTA update,in my case i download ASIA WWE 3.17.707.102 (it is in a zip form): you can find yours here http://splanet.info
or you can obtain it form any other source
2nd step: once you have the zip file open it and extract the firmware.zip (put it beside the fastboot.exe or inside the folder where adb and fastboot is)
now before proceeding to next step you need to verify first your CID
To Get the CID of your phone: reboot the phone in bootloader/fastboot mode (adb reboot bootloader), and use fastboot getvar cid. Match this in the android-info.txt file found inside the firmware.zip file. If it doesn’t match, don’t go any further.
**************If you’re still here, I guess your CID matched.*******************
now we will need tools like notepadc++ and 7zip
3rd step: Now, in the OTA zip file, find the file updater-script in the directory META-INF/com/google/android. In this we’ll need to remove some code that doesn’t work with recoveries other than the default HTC ones. (extract the updater-script)
then Open the file with any decent text editor that preserves newlines (for windows, Notepad++ springs to mind, on Linux/Mac just use vi), and look for a textblock like this:
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__044") == "t");
);
delete that line.. then save it. after that delete the update-script inside the OTA (located in META-INF/com/google/android.) after deleting copy the new updater-script that we have just edited to the same directory where you delete the old updater-script..
4th step: Next, reboot your phone into Clockworkdmod Recovery (or whatever recovery you have installed), make a nandroid backup of your phone, and copy the OTA zip file on the phone. As a safety measure, it’s recommended to make a backup of everything on the SD storage to your computer.
5th step: When the backups are completed, reboot your phone into bootloader/fastboot mode. It’s time to lock the bootloader again, so we can flash the firmware update. This can be done using the command fastboot oem lock. Your phone will reboot.
6th step: Reboot it once again, this time to OEM update mode: adb reboot oem-78
7th step: Flash the firmware update: fastboot flash zip firmware.zip. If this complains without getting you a green progressbar on the screen, try it again – the second time it usually sticks.(even if it fails the the 4th time around just try and try it)
Once this process completes, reboot the phone again in the new bootloader: fastboot reboot-bootloader.
Now you can unlock your bootloader again, using the Unlock_Code.bin file you got from htcdev.com: fastboot flash unlocktoken Unlock_Code.bin.
At this point, you’d sure as hell wish you’d made a backup, if you didn’t. Because now your phone is wiped, reset to factory default. Don’t say I didn’t warn you upfront.
8th step: After the reboot finishes, you can once again boot in booloader/fastboot mode, and flash your recovery anew. For Clockworkdmod Recovery, the command is fastboot flash recovery <filename.img> Now you can boot the phone in the recovery (select the option from the bootloader menu).
9th step: Once in the recovery, it’s time to restore your nandroid backup. You did make one, did you?
If you finished restoring the backup, or you can now flash the OTA zip on the phone, updating the ROM to the new version or stock version.
After this, you just need to reboot one more time, this time to the ROM itself. Let it finish upgrading all applications, and tadaa, your freshly upgraded phone.
This worked for me, might not work for you. No promises.
this tut i found is for the one x but i made a one s version (villec2) which works.. so have fun and restore your device to stock....
Hope This Helps...
if you like this feel free to like and thanks me
ps: sorry for really bad english
-- xander

Would it work as an update for phone which doesn't "see" the OTA update and cheating recovery by placing the OTA as update.zip on phone's memory doesn't work either?

xQrzy said:
Would it work as an update for phone which doesn't "see" the OTA update and cheating recovery by placing the OTA as update.zip on phone's memory doesn't work either?
Click to expand...
Click to collapse
hello mate,
ive tried before but it didnt work,you really have to do the stuff,but incase your one s is in different status it will be different..for mine im still s-on
and the ota rom will only work for the firmware .zip that is inside the ota which you will have to manually flash..

Hi xander1993,
I am sorry to bother you but your answer is not clear to me
You say you tried it but didn't work and just after that you write I have to do the stuff
So let's clarify my situation and then I will wait for your answer:
I am currently using TD6 because I could not update to JB using OTA. My HBOOT now is 2.11.
I did go back to stock 4.0.4 (by RUU, my CID is HTC__032) several times, tried OTA, but no result.
Then I tried (also several times) to download the OTA zip file from splanet, place it on phone and reboot to stock recovery - every time it was showing me first a pgone with green arrows shaping to a circle and one arrow inside the circle and after several seconds it was a phone with red triangle with an exclamation mark - at this stage I had to wait few minutes for reboot every time. No effect.
So my question is:
Will your guide help me to get just update from 4.0.4 to JB?

xQrzy said:
Hi xander1993,
I am sorry to bother you but your answer is not clear to me
You say you tried it but didn't work and just after that you write I have to do the stuff
So let's clarify my situation and then I will wait for your answer:
I am currently using TD6 because I could not update to JB using OTA. My HBOOT now is 2.11.
I did go back to stock 4.0.4 (by RUU, my CID is HTC__032) several times, tried OTA, but no result.
Then I tried (also several times) to download the OTA zip file from splanet, place it on phone and reboot to stock recovery - every time it was showing me first a pgone with green arrows shaping to a circle and one arrow inside the circle and after several seconds it was a phone with red triangle with an exclamation mark - at this stage I had to wait few minutes for reboot every time. No effect.
So my question is:
Will your guide help me to get just update from 4.0.4 to JB?
Click to expand...
Click to collapse
okay now i got your question my guide is about s-on devices restoring to jelly bean stockbecause s3 version havent got any RUU,all the RUU i found is ICS so i made this to restore back to stock,so in your situation you are still in ics? are you s-off? or s-on? and do you have the bootloader unlocked?
i can help you to update to jb with the OTA just find your OTA that matches your phones CID and MID,
after that you will need to have custom recovery like twrprecovery
then just follow my post above start 2nd step... i will wait for your reply...

As I mentioned above I am on TD6 now (TrickDroid 6), HOS S3, ICS base, S-ON (there is no S-OFF for S3 ), bootloader unlocked.
Hmm, what is MID? I haven't heard of it before..
I will follow your guide once I get an answer for this simple question

AW: (GUIDE) RESTORE JB HBOOT 3.06 TO STOCK AFTER CUSTOM ROM ONE S C2 (villec2) !!
I have a One s with cid vodap102 and Android 4.0.3 can i Flash on this way Android 4.1 Euro stock rom on my One s ?
Sent from my HTC One S using xda app-developers app

xantan said:
I have a One s with cid vodap102 and Android 4.0.3 can i Flash on this way Android 4.1 Euro stock rom on my One s ?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
u can try but most probably u cant
Make a backup before doing

AW: (GUIDE) RESTORE JB HBOOT 3.06 TO STOCK AFTER CUSTOM ROM ONE S C2 (villec2) !!
Im testing this
Sent from my HTC One S using xda app-developers app

Yes it will work because this method is also tricking the custom recovery so that ota can be installed
Sent from my HTC One S using xda app-developers app

Mid is the model of device so if yours is one s s3 don't worry about mid,
Sent from my HTC One S using xda app-developers app

Yes you can it update you to 4.1.1 just download the right ota for your device specifically the right ota for your cid
Sent from my HTC One S using xda app-developers app

I read the guide and I barely understood how it works, but my question would be this:
Im on CID BSTAR301 (yeah, Latinamerican fked up CID stuck on 4.0.3) and if I change some of the code of a RUU.zip file (with other updated CID), would it work on my device? Is there any way to cheat the RUU to make it work on others CID? I think this could be possible, it's just some editable files, I hope this could work because I don't wanna be stuck on 4.0.3 while others Villec2 are with official JB

krlwarrior said:
I read the guide and I barely understood how it works, but my question would be this:
Im on CID BSTAR301 (yeah, Latinamerican fked up CID stuck on 4.0.3) and if I change some of the code of a RUU.zip file (with other updated CID), would it work on my device? Is there any way to cheat the RUU to make it work on others CID? I think this could be possible, it's just some editable files, I hope this could work because I don't wanna be stuck on 4.0.3 while others Villec2 are with official JB
Click to expand...
Click to collapse
sorry i am bad in english...but the method up is working...ill help you..first download your OTA for your CID..then tell me when you got it
you can find yours here http://splanet.info/

The problem is that my CID is not in the list, BSTAR301... I want to use other RUU because there is no RUU for my CID Can we cheat on other RUU file?

krlwarrior said:
The problem is that my CID is not in the list, BSTAR301... I want to use other RUU because there is no RUU for my CID Can we cheat on other RUU file?
Click to expand...
Click to collapse
no you cant cheat the RUU but can cheat the OTA update,even if you dont have the the correct OTA it will install but first you need to be unlock via HTCDEV and you got to have twrp custom recovery

When trying to flash the firmware, mine says "remote: 44 hboot version check fail" I have hboot 3.01.0000 :| Any ideea why?

bubert said:
When trying to flash the firmware, mine says "remote: 44 hboot version check fail" I have hboot 3.01.0000 :| Any ideea why?
Click to expand...
Click to collapse
you are not htc dev unlocked?

HTC One S Arabic JB update
Hi,
I bought an HTC One S from Dubai(Arabic Region) and I am using it in India right now. I have not yet received the JB update for the phone.
I was able to find the OTA files for the JB Update to the One S for the Arabic Region here -
splanet.info/
My CID is HTC_J15 as given by the CID Getter app.
I booted into the bootloader and got the following information -
***Locked***
VilleC2 PVT SHIP S-ON RL
HBOOT-2.09.0001
RADIO-16.05.20.24_M
OpenDSP-v05.6.0.2226.00.0418
eMMC-boot
May 10 2012, 17:19:49
This was followed by the HBoot, FastBoot, Recovery. Factory Rset, SIMLock, Image CRC and Show BarCode options.
Can you guide me as to how I can install the JB update?
Please bear with me as I am a noob.
Thanks.

sshray said:
Hi,
I bought an HTC One S from Dubai(Arabic Region) and I am using it in India right now. I have not yet received the JB update for the phone.
I was able to find the OTA files for the JB Update to the One S for the Arabic Region here -
splanet.info/
My CID is HTC_J15 as given by the CID Getter app.
I booted into the bootloader and got the following information -
***Locked***
VilleC2 PVT SHIP S-ON RL
HBOOT-2.09.0001
RADIO-16.05.20.24_M
OpenDSP-v05.6.0.2226.00.0418
eMMC-boot
May 10 2012, 17:19:49
This was followed by the HBoot, FastBoot, Recovery. Factory Rset, SIMLock, Image CRC and Show BarCode options.
Can you guide me as to how I can install the JB update?
Please bear with me as I am a noob.
Thanks.
Click to expand...
Click to collapse
first thing first you need to have htc dev unlock boot loader http://www.htcdev.com/bootloader select "all other supported models" then follow the on screen instruction then after that go back here....

[HOW TO] Unlock bootloader, root, flash custom recovery, rom ..

Unlocking Bootloader
What you need:
PC
Phone
Installed HTC sync (phone drivers)
Unlocking "tool" (batch file and fastboot / adb files)
With unlocked bootloader you will be able to flash custom recovery needed for flashing ROM, rooting etc.
Guide:
Download unlock.rar from attachment
Extract contest of rar to your desktop
Restart your phone
When powering up, press and hold “Volume Down” to enter Bootloader
With volume up / down select “Fastboot” and select it with power button
You should see “Fastboot USB” on your phone screen
Run “Unlock bootloader.bat” from your desktop
Press “t” and confirm with enter to get token
Go to HTC Dev registration and register
Go to HTC Dev unlock bootloader
Select “all other supported models” on right
Skip all steps till step 9
Paste your token like shown in step 9
After some time you will receive E-Mail with Unlock_code.bin in attachment
Save Unlock_code.bin to your desktop
In “Unlock bootloader.bat ” press “u” and confirm with enter
On your phone you should see unlock menu, move with Volume Up and select with Power
That’s it, your phone bootloader should now be unlocked and ready to flash custom recovery.
Flashing Recovery
After you are done with unlocking bootloader you can flash custom recovery.
Recommended recovery for HTC One S Ville C2 is TWRP, because it is most stable one that works with device.
You can use Superboot to root your phone and than install Goomanager from play store and flash TWRP from it
or you can try this:
download latest TWRP recovery from HERE (one with villec2 in name is the one you need)
download attached recovery flashing utility and extract content to your desktop
rename recovery image to twrp.img and place it on desktop (or location where you extracted flashing utility)
reboot your phone into fastboot (restart it and while starting press and hold volume down, when in bootloader press power to enter fastboot mode)
run flash-recovery.bat
press f and confirm with enter
your recovery should now be flashed and you can enter it by selecting recovery from your bootloader screen (volume up / down to navigate, power to select)
Flashing custom ROM
After you have unlocked bootloader / installed custom recovery you can flash custom ROM
After you have found ROM that you would like to flash and saved it on your phone this are the steps you need to take:
reboot into recovery
wipe data (factory reset) and cache
go back chose "install"
locate ROM you have downloaded to your phone
after rom has been installed reboot into fastboot
now you need to flash boot.img
Boot.img is usually included inside ROM .zip file, but since ONE S has S-ON it cannot be flashed from recovery but you need to flash it from fastboot.
Click to expand...
Click to collapse
download fastboot files from attachment and extract them to c:/fastboot
Start cmd (win+r -> cmd)
in cmd:
cd\
cd fastboot
fastboot flash boot boot.img
fastboot erase cache
reboot phone
HBOOT versions and ROM compatibility
Not all ROMs are compatible with all HBOOT versions.
Minimum required HBOOT version for flashing SENSE based, android 4.04 or 4.1.1 (JellyBean) ROM is 2.11 (you will get it with official 4.0.4 OTA update).
You can run older versions of Sense based ROMs (4.0.3) on newer hboot versions.
This does not comply to AOSP ROMs

Thank you, great how-to.
As i made my phone ready for New Roms i stucked at TWRP. If anyone else has problems there. Try this after unlocking bootloader
http://forum.xda-developers.com/showthread.php?t=1788974
And install goomanager from play store and install open recovery

AW: [HOW TO] Unlock bootloader, root, flash custom recovery, rom ..
Good job.
This should answer a lot of questions for new users
Sent from my HTC One S

Elias96 said:
Thank you, great how-to.
As i made my phone ready for New Roms i stucked at TWRP. If anyone else has problems there. Try this after unlocking bootloader
http://forum.xda-developers.com/showthread.php?t=1788974
And install goomanager from play store and install open recovery
Click to expand...
Click to collapse
i'm not sure will superboot work with devices upgraded to 4.1 (or if any one even ships with 4.1) but i will add it as option in OP

Great one! Just to get ti to stick
Any requirements/restrictions for all this due to branding, android version, cid?

should work with all devices

Nice job:good: Sticky

I'm on VIP Serbia 4.0.3 stock rom, and I don't have any updates through software update on phone. Bipe wrote me in mail that it should be at least 4.0.4 software to be sure that this would work. Any workaround? Like debranding or flashing internatioal stock rom?

4.0.4 is needed for JB based custom ROMs to work
If you don't have OTA update you can try flashing 4.0.4 RUU

Forgive my noobness,
ruu is an offline pc update tool? Folowed the links and got to site hosting files:
PJ4020000_OTA_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100-1.11.401.110_release_2865916.zip
And
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed.exe
I suppose one is an update (zip) and the other is full rom, and that both are 4.0.4.
Should I try to install just update or full? And is the update flashable zip to be installed through stock recovety?
Sent from my HTC One S using Tapatalk 2

Cayman.n2o said:
Forgive my noobness,
ruu is an offline pc update tool? Folowed the links and got to site hosting files:
PJ4020000_OTA_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100-1.11.401.110_release_2865916.zip
And
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed.exe
I suppose one is an update (zip) and the other is full rom, and that both are 4.0.4.
Should I try to install just update or full? And is the update flashable zip to be installed through stock recovety?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
its best to use ruu, but ensure make a full backup of data through twrp because ruu will erase all user data, secondly for ruu you will need to relock your bootloader. After your phone is updated, unlock your bootloader again.

I haven't done anything to my phone yet. Its stock as it can be So no twrp, unlocked bootloader or so.
When you mention backing up data, you mean rom and such?So if (hope it won't) anything goes wrong with ruu, I can restore phone to a present state? I have all I need synced and copied to my pc that would be called "user data".

Cayman.n2o said:
I haven't done anything to my phone yet. Its stock as it can be So no twrp, unlocked bootloader or so.
When you mention backing up data, you mean rom and such?So if (hope it won't) anything goes wrong with ruu, I can restore phone to a present state? I have all I need synced and copied to my pc that would be called "user data".
Click to expand...
Click to collapse
ok so go with ruu and just be sure that the CID of ur device is supported with RUU that u r going to flash and if there will be some error it will give prior to flash so most probably nothing should go wrong

How to know which one should I use? On villec2.info folowed the link to this: http://www.androidfiles.org/ruu/?dir=VilleC2
There are few europe ruu files, just want to be sure... The Europe_2.15.401.100 seams to latest. Also how to check the CID compatibility? My CID is HTC_032 (got it by CID Getter app from store)

Hope this will clear things out for you:
x.xx.401.x - World Wide English (WWE):
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
x.xx.709.x - Asia TW (Taiwan)
cidnum: HTC__621
x.xx.720.x - Asia (India)
cidnum: HTC__038
(x.xx.707.x - Asia WWE (World Wide English)
cidnum: HTC__044
(x.xx.708.x - Asia HK (Hong Kong)
cidnum: HTC__622
Click to expand...
Click to collapse
what you need is the one with "x.xx.401.x" in name, latest version

Hello everyone!
I have updated my phone to 4.0.4 using ruu. Now I'm going to try to flash recovery and root it.
Anyone tried and sucsseded in flashing stock 4.0.4 after using some custom 4.1.1 roms? I would love to try out some custom roms but it would be nice if I could get back 4.0.4.

Cayman.n2o said:
Hello everyone!
I have updated my phone to 4.0.4 using ruu. Now I'm going to try to flash recovery and root it.
Anyone tried and sucsseded in flashing stock 4.0.4 after using some custom 4.1.1 roms? I would love to try out some custom roms but it would be nice if I could get back 4.0.4.
Click to expand...
Click to collapse
You can go back to stock just don't forget to make nadrod backup first... Or if you don't you can always use RUU
Sent from my HTC One S using Tapatalk 2

I have the one-s with (Serbian Telenor) Android 4.0.3 (soft. 1.11.401.110) , Do I have to install this first (EXE file) RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed
or this one first (zip file) : PJ4020000_OTA_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100-1.11.401.110_release_2865916
and then do with the update zip file OTA_VILLEC2_U_JB_45_S_HTC_Europe_3.17.401.102_16.22.20.03U_16.11.20.24_M_release_305849f16hjx6h6neosbyn

most probably ruu will give error

bilal_liberty said:
most probably ruu will give error
Click to expand...
Click to collapse
Why do you think that ?

[GUIDE][TOOL]FUU/Firmware HTC One Mini

General Information
This Has Been Made To Help Those How Have No Clue What There Doing When Upgrading There Firmware Note And Want A One Click That Mimiks HTC RUU
FUU Definition
Firmware Update Utility
There are a few Firmware flashing threads and lots of zips and good and bad instructions. However, i noticed that many users asked about what they get when they flash what they download and also about how to flash it with S-OFF on various threads. This confusion has occasionally lead to people losing their custom kernels and custom recoveries and/or their SDcard partitions being unintentionally wiped.
I am writing this because i believe in "responsible" sharing. Since the full RUU's aren’t shared but only components (modified as well as unmodified) with often insufficient documentation, which in turn leads to a lot of confusion among the lesser informed users, i will try to catch some of that. I believe that sharing full RUU's would be a lot safer, as only those who actually know enough about it can disassemble them. RUU’s do always reassure users that there is a guaranteed and safe way to go back.
Prerequisites:​All you need is a Windows System with current drivers and maybe HTC Sync Manager installed, it is better to have HTC Sync uninstalled and only the drivers left. Just try if the FUU runs without HTC Sync. On my system, i am always greeted with an “Error 170" if i try to run the FUU on a booted Android - it doesn’t recognize the phone with ADB. This is a typical driver and/or ADB error. Solution here: make sure you have the latest driver suite. FailSafe way to get them is to install HTC Sync Manager (remove it if you don’t like it afterwards but leave the drivers in the sytem!).​
FUU How To​
[*]Download the firmware you want
[*]then run the installer
[*]install it to folder you want to any folder will do
[*]then run the tool and upgrade or downgrade your firmware
ZIP Flash HowTo​
Step-By-Step:​1. If device is booted into Android, reboot into bootloader by running:
Code:
adb reboot bootloader
1.a Or else, if your device is in a different state or you just prefer the button method:
Press Power for 15 seconds and hold Vol Down at the same time, when the screen and charging LED go dark immediately release Power but keep holding Vol Down until you see the bootloader screen. Notice: If the device refuses to reboot, you might need to hold it to a bright light with its light sensor. This is a very specific bug in the HTC ONE. The light trick always works.
2. Now place the Firmware_named_something.zip into your adb/fastboot folder
3. Now run:
Code:
fastboot oem rebootRUU
4. Followed by:
Code:
fastboot flash zip Firmware_named_something.zip
(replace "Firmware_named_something.zip" with the name of your zip)
5. Now check the console output. It should approximately look like this:
“flush" certainly means “Flash" so press the arrow up key on your keyboard and enter to run the flash command again without reboot...
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution! The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot! The bar will only fill up to 100% once you type the following command:
6.
Code:
fastboot reboot-bootloader
Error handling strategies:​IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL it could not boot up anymore! It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (dont use hubs! Always straight-to-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot... there are many possible sources for flash fails.
The least dangerous FAILED messages are listed below and are safe to reboot:
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 you did not lock your bootloader (Needs a relock for S-ON phones that want to update the firmware.)​
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn’t help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
fastboot oem writecid 11111111
You can change back to any desired CID after a successfull firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn’t brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- Tell me if you find out what’s causing an unknown error here!
For “Error 155 relock bootloader" do:
- run the fastboot command “fastboot oem lock" - only applies to S-ON phones that want to update the firmware. There a relocked bootloader is required. This error won’t show on S-OFF phones.
- Error 155 can also mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of wrong region lock.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers or ADB/Fastboot binaries. One way to solve is to run the exe with the phone already in Fastboot mode. Else you will have to dig into your windows driver system and try to fix there. Best option: re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn’t work with ADB and Fastboot.​
I always test all of these zips on my own device. But as always, flash at own risk. You're writing to critical parts of your phone. If anything goes wrong along the way, you might be bricked.
FUU Downloads (Windows only)​
Update: added Firmware For Sense 5.5 4.3 FUU
Download
MD5: 4cc050c25d2006600dfdbcc186789ef0
This FUU is Stock. Contents: Firmware from vrvr And So You should be good to Go. This package does wipes SDcard.​
Update: added Modifyed Hbbot No Red Text FUU
Download
MD5: 3918b9ca578f6f117a96e39f14873cd2
This FUU is modified. Contents: Firmware from vrvr And And Then Modifyed With No Red Text, So You should be good to Go. This package does wipes SDcard.​
Update: added Firmware For 4.4 KitKat FUU
Download
MD5: 701f1b7c07356e3fd7aaacf2e777d666
This FUU is stock. Contents: Firmware from The HTC OTA So You should be good to Go. This package does wipes SDcard.***NOTE*** The Boot Has Been Removed Because It May Cause You Some Problems And Result In Having To Reflash Your Rom​
Fastboot ZIP Downloads​
Update: added Firmware For 4.4 KitKat
Download
MD5: a0a05707fdbbdc7b7b162a7f6d76c4c8
This package is stock. Contents: Firmware from The HTC OTA So You should be good to Go. This package does Not wipes SDcard.***NOTE*** The Boot Has Been Removed Because It May Cause You Some Problems And Result In Having To Reflash Your Rom
Update: added Firmware For Sense 5.5 4.3
Download
MD5: 1f9f200cf468dc40ddd3c5415c639823
This package is stock. Contents: Firmware from vrvr And So You should be good to Go. This package does Not wipes SDcard.
Update: added Modifyed Hbbot No Red Text
Download
MD5: 2f5467f6fdcc854198a95d6ed7146c7f
This package is modified. Contents: Firmware from vrvr And And Then Modifyed With No Red Text, So You should be good to Go. This package does Not wipes SDcard.​Credits​Thank You Sneakyghost For The Tool And The Op
ramjet73 My mentor for HBOOT Modding
tr1gg3r84 - For Testing
vrvr For The OTA Witch I Modify Of off
Disclaimer​You are aware that writing to the security protected partitions increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested on various phones at time of posting, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any responsibility. The method itself is developed by Google and HTC, i only provide access and information to it and you execute it.
You understand that you should not do it if you are not willing to accept this risk.​
XDA:DevDB Information
[GUIDE][TOOL]FUU/Firmware HTC One Mini, a Tool/Utility for the HTC One Mini
Contributors
Flashalot
Version Information
Status: Stable
Stable Release Date: 2014-02-23
Created 2014-02-23
Last Updated 2014-02-23

For me

Update for 4.4 Firmware has been released enjoy

Thanks for this I'll have a look

coming from stock 4.3 ... tried both methods to update to 4.4.2 ... Both create endless bootloop.
S-OFF, SuperCID ... tried both unlocked and locked bootloader

leungalv said:
coming from stock 4.3 ... tried both methods to update to 4.4.2 ... Both create endless bootloop.
S-OFF, SuperCID ... tried both unlocked and locked bootloader
Click to expand...
Click to collapse
Have you tried wiping cache and davik cache
Sent from a potato running Android

Flashalot said:
Have you tried wiping cache and davik cache
Sent from a potato running Android
Click to expand...
Click to collapse
Yup tried wiping cache & davik. Fixing the permissions. Nothing works. Just goes HTC -> black screen -> off -> HTC -> black screen -> off.
Re-flashing the 4.3 boot.img will get it to boot back into 4.3.

i have stock htc firmware - android 4.3, phone is rooted. unlocked and s-off.
what do i do to get back to 100% stock firmware, without root and stock recovery :/

kabalah89 said:
i have stock htc firmware - android 4.3, phone is rooted. unlocked and s-off.
what do i do to get back to 100% stock firmware, without root and stock recovery :/
Click to expand...
Click to collapse
Flash stock firmware and stock ROM
After if you want to go back to s-on run this command
fastboot oem writesecureflag 3
Please make sure you are in stock hboot if not you will be in a permanent brick
Sent from my SPH-L710 using Tapatalk

Hello,
I;ve tried this and got into a bootloop. i don't know what to do now?
The phone is ocked en not S-off
I know i must flash the RUU, but i cannot find a european RUU.
Please help?

A little confused
What are the requirements in order to perform a firmware update? Does the device need to be S-off or have super CID?
If I'm only wanting to update my hboot, do I just follow the FUU instruction and ignore the Zip Flash instructions? or do I need both?
Sorry, it's just a little unclear to me.
Thanks!
Nevermind - the answer is yes, you do need to be S-Off and THANK YOU! It worked perfectly!

PuffDaddy_d said:
What are the requirements in order to perform a firmware update? Does the device need to be S-off or have super CID?
If I'm only wanting to update my hboot, do I just follow the FUU instruction and ignore the Zip Flash instructions? or do I need both?
Sorry, it's just a little unclear to me.
Thanks!
Nevermind - the answer is yes, you do need to be S-Off and THANK YOU! It worked perfectly!
Click to expand...
Click to collapse
@PuffDaddy_d, can you help me:
1. what method did you use?
2. what firmware did you use to get hboot 2.21 to flash stock 4.4?
3. if you used the 1st method that wipe sdcard, how can you flash the Rom?
pls help, I really want to have stock KitKat on mine. thx.

S-off your device, flash hboot with fastboot command and then you can flash 4.4.2 with adb sideload from twrp recovery
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk

gramateas said:
S-off your device, flash hboot with fastboot command and then you can flash 4.4.2 with adb sideload from twrp recovery
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
thx @gramateas. you helped me with sideload method, but I really need a clear answers (as help) of my other 2 questions.

You can flash modded hboot 2.21
But first you must s-off your device
http://forum.xda-developers.com/showthread.php?t=2584810
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk

Hello, after using this FUU i got into a bootloop. Using fastboot i could install custom recovery, after unlocking the phone via HTCDEV. Now i am running 4.4.2 with S-on and working fine.
Sent from my HTC One mini using xda app-developers app

Zoeriva said:
Hello, after using this FUU i got into a bootloop. Using fastboot i could install custom recovery, after unlocking the phone via HTCDEV. Now i am running 4.4.2 with S-on and working fine.
Sent from my HTC One mini using xda app-developers app
Click to expand...
Click to collapse
whay hboot are you on?

I am on 2.21 hboot
Sent from my HTC One mini using xda app-developers app

gramateas said:
You can flash modded hboot 2.21
But first you must s-off your device
http://forum.xda-developers.com/showthread.php?t=2584810
Στάλθηκε από το HTC One mini μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I tried to upgrade my hboot last night and this was what happened.
first I come with :
1. hboot 2.19
2. unlocked bootloader
3. twrp recovery
4. rooted stock 4.3
5. super cid 11111111
6. S-On
so, I tried to make S-off first. I used revone method. when I successfully S-off mine, I entered a bootloop (but when reverted to s-on, the bootloop was gone).
is it safe to continue flash the hboot when I got s-off and bootloop?
thx

edimonoarfa said:
I tried to upgrade my hboot last night and this was what happened.
first I come with :
1. hboot 2.19
2. unlocked bootloader
3. twrp recovery
4. rooted stock 4.3
5. super cid 11111111
6. S-On
so, I tried to make S-off first. I used revone method. when I successfully S-off mine, I entered a bootloop (but when reverted to s-on, the bootloop was gone).
is it safe to continue flash the hboot when I got s-off and bootloop?
thx
Click to expand...
Click to collapse
Well you could have as long as your on stock hboot then your OK but if not and your on a modded hboot you could brick
Also I'm looking in to see why every one is getting bootloops on firmware and I will be makeing no red text soon for Kitkat hboot
Sent from my SPH-L710 using Tapatalk