Related
How would I go about doing this sso I can sell it? I'm currently on a 3.5 rom.
Same problem here (warranty exchange). I've done everything recommended here http://forum.xda-developers.com/showthread.php?t=1192300 but when I rune the .exe, I get an error [155] (incorrect ruu). I have searched everywhere for an up-to-date RUU, but have not had any luck.
You need to change your cid number to correspond with your carrier if you search the forums there is a list of them I presume you know how to go about this as you would have to have the super cid 11111111 or Eu HTC__001 to flash another Ruu other than your carriers
Sent from my HTC Sensation Z710e using XDA App
Change Cid number? Why would I have to do this? I've never messed with that before.
My apologies I presumed you had installed a unbranded firmware prior to rooting
Normally you have to change the cid to do this as the gold card method won't work
Sent from my HTC Sensation Z710e using XDA App
I followed a thread here to return to S-ON and then flashed the newest RUU from the post that lists all of the RUU's for the Sensation.
alright I've been reading and I'm still a little confused.
Basically, I have an s-off sensation with root and a rom. It's a T-Mobile sensation. I never debranded or anything like that.
What exactly do I need to do to return to stock as if I just bough it? I also noticed there are two TMOUS ruu files....which one do I use?
OK, lets begin
When you S-OFF'd the HBOOT changed to a newer one than your stock, TMOUS ROM. Because of this, you NEED Super CID to be able to go to a lower HBOOT. So that's why you need to change to it.
Once done, you can flash the stock 1.29.531.2 RUU. Once this has completed, you can change the CID back to the TMOUS one and then go back to S-ON and voila - one stock, ready to sell Sensation
Has any one got the Vodafone UK ROM please?
Cancel that. The download hasn't got that long left, so I'll just wait for it to finish.
EddyOS said:
OK, lets begin
When you S-OFF'd the HBOOT changed to a newer one than your stock, TMOUS ROM. Because of this, you NEED Super CID to be able to go to a lower HBOOT. So that's why you need to change to it.
Once done, you can flash the stock 1.29.531.2 RUU. Once this has completed, you can change the CID back to the TMOUS one and then go back to S-ON and voila - one stock, ready to sell Sensation
Click to expand...
Click to collapse
Thanks....so how exactly would I do this super CID thing? lol
So basically...do super cid thing, flash stock RUU, then super cid again? Sorry, I've never really done much other than flash roms, so I don't know what this cid stuff is.
You should've really learnt all this before jumping in as you should always know how to get out of something before you go ahead with it.
The guide you followed to S-OFF has the Super CID procedure:
http://forum.xda-developers.com/showthread.php?t=1192300
However, before changing it you need to make a note of your current one. To do so, you need to run the following fastboot command:
fastboot getvar cid
Once done, use the guide above to write the Super CID. This will allow you to flash the 1.29.531.2 RUU.
Then, using the same procedure as writing Super CID, write your old one back. Then follow the guide to get S-ON
Having said all that, you could just try flashing the 1.29.531.2 RUU and if it works then follow the guide to go back to S-ON - it may work
I have tried to change it to 111111... but the exe gives me the error nontheless. What do i change the CID TO?
akbisw said:
I have tried to change it to 111111... but the exe gives me the error nontheless. What do i change the CID TO?
Click to expand...
Click to collapse
I'm sure you've already figured it out since the thread hasn't been updated since a couple of months back, but here's the link to the thread with the answer if anyone gets here while searching for the right T-MOUS Stock CID for sensation:
http://forum.xda-developers.com/showthread.php?p=23046170
be careful
if u updated firmware to ics be careful before flashing an ruu this messed up my phone
Sorry for bumping an old topic, this topic was helpful with what I needed. I need to return my phone to stock for a replacement. I completed all the steps but what can I double check to make sure I did it correct. I have stock rom and s on. My CID still shows "11111111". I was trying to get the OTA update to ICS but it won't let me download it so it worries me that I still am not completely stock.
My phone is unbranded , unrooted & stock using ROM 1.47.401.4.
I have downloaded the latest ota 2.10.401.4 and in that zip there was a firmware zip in it.
i renamed the firmware zip to pg88img.zip and put it in my phone's sd root.
After the reboot of the phone has updated the firmware BUT thats all.
If i reboot the phone stucks on the HTC logo but also i can go to the bootloader options if on the reboot i hold down the volume button.
Is there any way to restore the phone?
I try to flash the stock rom but nothing.
Can anybody help please??
Resolution:
If anyone has the same problem and has hboot-2.00.0002 & S-ON you have to unlock the bootloader via htcdev.com site following all the steps and flash the EXT4 Recovery via FASTBOOT and NOT ADB.!!
Then go to recovery and flash any custom rom.
avensakias said:
My phone is unbranded , unrooted & stock using ROM 1.47.401.4.
I have downloaded the latest ota 2.10.401.4 and in that zip there was a firmware zip in it.
i renamed the firmware zip to pg88img.zip and put it in my phone's sd root.
After the reboot of the phone has updated the firmware BUT thats all.
If i reboot the phone stucks on the HTC logo but also i can go to the bootloader options if on the reboot i hold down the volume button.
Is there any way to restore the phone?
I try to flash the stock rom but nothing.
Can anybody help please??
Click to expand...
Click to collapse
You can't boot because of new hboot. Have u s-off device ?
Sent from my HTC Desire S using xda premium
No the phone is s-on and up on the screen it says LOCKED.
Never saw LOCKED before.
Is there any way to S-OFF now with the new hboot ??
avensakias said:
No the phone is s-on and up on the screen it says LOCKED.
Never saw LOCKED before.
Is there any way to S-OFF now with the new hboot ??
Click to expand...
Click to collapse
It says locked but nothin is locked. Try to flash 4ext recovery over adb. Should work I think. Instructions in general forum .
Sent from my HTC Desire S using xda premium
Thanks.
i'll try and see whats going to happen.
Which update did you download? There are a couple available - odexed & deodexed.
Maybe worth trying which ever one you didn't download the first time?
Also are you giving it plenty of time to load? First boot from a fresh install always takes a long time.
Don't worry, you don't have a brick
Peace
Sent from my HTC Desire S
Unlock bootloader but still S-ON
Using the http://www.htcdev.com/bootloader/unlock-instructions i managed to get my bootloader UNLOCKED but it still says S-ON.
Tryed to flash the 4EXTvia adb but it says ERROR no device found.
Any other instruction on how to get my DS working again?
Going on bootloader i see:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.09.08.20_M
eMMC-boot
Aug 22 2011,15:22:13
Any other suggestion pls??
You need to get your phone s-off using one of the methods in this part of the forum. Then you can install ext4 & new rom
Peace
Sent from my phone
HOW???
My hboot is HBOOT-2.00.0002 and the revolution to s-off is only for hboots 0.98.0000 & 0.98.0002.
Can you be more specific?
The only way that i can communicate to my DS is only via fastboot.
Can anybody help or the phone goes to the trash?? What should i do??
Waiting for stock RUU 2.10.401.4
I believe that the only way to restore the phone is to wait till the stock RUU 2.10.401.4 leak someday..
If anybody else can help me please do.
Thanks.
avensakias said:
I believe that the only way to restore the phone is to wait till the stock RUU 2.10.401.4 leak someday..
If anybody else can help me please do.
Thanks.
Click to expand...
Click to collapse
That would be a choice, but I would say you'll be better of to use xtc-clip to gain s-off, after this everything is possible or just give it back for warranty and let them repair it,
because it's still s-on, but just to know, what else where in the zip?
Could it be that you forgot something, have you tried a factory reset?
Sent from my HTC Desire S using XDA App
Tectas said:
That would be a choice, but I would say you'll be better of to use xtc-clip to gain s-off, after this everything is possible or just give it back for warranty and let them repair it,
because it's still s-on, but just to know, what else where in the zip?
Could it be that you forgot something, have you tried a factory reset?
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Do you know if I can get it from Greece.?
Does xtc clip works on hboot-2.00.0002.?
avensakias said:
Do you know if I can get it from Greece.?
Does xtc clip works on hboot-2.00.0002.?
Click to expand...
Click to collapse
Xtc-clip works with every version on every HTC device.
Go to a second hand handy shop that also does repairs and stuff like this maybe they get one, I s-offed mine this way for €20^^
Swyped from my HTC Desire S
What did you download originally?
Was it an official ota update, or from this forum?
If you tried to flash the odexed version, many users have problems with this. Can you try the deodexed version?
Sent from my HTC Desire S
I was with the original shipped rom 1.47.401.4 S-ON & UNROOTED.
I downloaded via my computer http://liveimage.htc.com/OTA_Saga_S...1.47.401.4_release_217301kjfuq12qqm0wuhg7.zip
In that zip file there was another zip file called Firmware.zip.
I renamed the firmware.zip to pg88img.zip and i put it in the root of my sd card.
I rebooted holding the volume down button and the phone went to bootloader mode found the pg88img.zip and flashed it.
After that the phone goes only to bootloader showing
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.09.08.20_M
eMMC-boot
Aug 22 2011,15:22:13
Is there any way to flash the OTA via fastboot since over adb i get the message device not found..???
Do you have a "recovery" option in the fastboot menu? If so try to go to this menu and see if adb recognises it then. But you have probably tried this already, right.
With adb, when you type 'adb devices', your phone is not shown, correct?
I'm not sure about getting S-off with the new hboot, I did mine with the old hboot.
You could try to download the deodexed rom on this page and flash that, but you need to get into recovery first.
Sorry, not much help I'm afraid.
Did you try to install these fastboot drivers?
Unfortunately i have tried everything so far but didn't work.
The xtc clip maybe is the only way.. Or if the s-off solution of revolution will support in future my hboot and do it that way.
I also noticed that when i tried to flash the stock rom i had 1.47.401.4 and was stuck on the HTC logo the update software said that i had rom 11.10.401.4.!!!!!
Since i flashed the original fota why the version said 11.10.401.4 and not 2.10.401.4??
WTF IS GOING ON.??
Well, I still don't think you have a brick - you can get into the bootloader, you just need your pc to recognise it via USB.
Have you tried flashing the previous hboot version you had? To enable revolutionary s-off?
Also have a look around the general Android forums, there are some very experienced peeps there who may be able to help.
Peace
Sent from my HTC Desire S
avensakias said:
Do you know if I can get it from Greece.?
Does xtc clip works on hboot-2.00.0002.?
Click to expand...
Click to collapse
You should ask this question on the XTC phone tools forum to raskal to be 100% sure that this new version is covered (see link on the XTC in my sig)
and as @tectas has said, there is still a possibility that you are still able to return under warranty and allow them to resolve it for you..
sorry unable to assist with confidence.
EDIT: see this thread that I created a while back that contains another link within it to lots of XTC owners around the world within it, but I'd confirm that the new HBOOT is covered before you run XTC http://forum.xda-developers.com/showthread.php?t=1076937&highlight=xtc
I ask them. Thanks anyway.
The 3 things left.
1. to ask xtc forum if my hboot-2.00.0002 is supported.
2. to wait till revolution s-off supports in the future my hboot.
3. to wait till someone leakes the stock signed ruu 2.10.401.4
That's all unfortunately..
hey there,
bought my gf a desire s to christmas. i, as a sensation user at the moment am very comfortable with development. flashing, adb, fastboot and things like that are working flawless.
as i don't have so much time to read atm, i have some questions concerning the way to set the desire s up. it was shipped with 1.47 rom, t-mobile branded, sense 2.1, android 2.3.1 and hboot 0.98.0002
i want to flash this rom: endymion sense v3.1 (android 2.3.5, sense 3.5)
i already achieved s-off with revolutionary, hboot is now 6.98.1002 with radio 3805.06.02.03_M. 4ext recovery 2.2.7RC5 is installed as well.
now i saw, that there is RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe availble. i also read in the forum, that this ota brings some parts for firmware, which are not flashed with a custom rom.
so would you recommend to flash this ruu first? wouldn't i lose s-off then? would i be abled to achieve s-off again after flashing this? also, for my sensation i would have to supercid first - i didn't read about this here in the forums.
what i would want to do:
1. flash RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe
2. run revolutionary again
3. flash custom recovery
4. flash endymion v3.1
would it be possible this way? or would you recommend any other way to me? i want to have all firmware parts as up to date as possible before i flash the custom rom.
smint86 said:
hey there,
bought my gf a desire s to christmas. i, as a sensation user at the moment am very comfortable with development. flashing, adb, fastboot and things like that are working flawless.
as i don't have so much time to read atm, i have some questions concerning the way to set the desire s up. it was shipped with 1.47 rom, t-mobile branded, sense 2.1, android 2.3.1 and hboot 0.98.0002
i want to flash this rom: endymion sense v3.1 (android 2.3.5, sense 3.5)
i already achieved s-off with revolutionary, hboot is now 6.98.1002 with radio 3805.06.02.03_M. 4ext recovery 2.2.7RC5 is installed as well.
now i saw, that there is RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe availble. i also read in the forum, that this ota brings some parts for firmware, which are not flashed with a custom rom.
so would you recommend to flash this ruu first? wouldn't i lose s-off then? would i be abled to achieve s-off again after flashing this? also, for my sensation i would have to supercid first - i didn't read about this here in the forums.
what i would want to do:
1. flash RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe
2. run revolutionary again
3. flash custom recovery
4. flash endymion v3.1
would it be possible this way? or would you recommend any other way to me? i want to have all firmware parts as up to date as possible before i flash the custom rom.
Click to expand...
Click to collapse
Cause you are already s-off I would say it's senseless to use the ruu first, because it would put you back to s-on like you suggested, but only if the revolutionary bootloader doesn't make problems.
There are many reports of problems with it and I would say you should replace it with the 2.00.2002 engineer bootloader.
before just flash a custom recovery (I would recommend 4ext touch) and if your done with the bootloader flash the ROM of your choice.
To get bootloader, recovery,... just look at the index thread at the development section, it's all in there.
The last step to achieve a full upgraded phone would be to update the radio to the latest version, this you will also find at the index thread.
Happy modding
Oh and welcome, sry^^
Swyped from my desire s running damn sweet ice cream
Tectas said:
There are many reports of problems with it and I would say you should replace it with the 2.00.2002 engineer bootloader.
Click to expand...
Click to collapse
is there a guide you are referring to? i already got 4ext recovery installed, but i don't find any post concerning 2.00.2002 bootloader. if i flash this one i would stay s-off? and it would bring me all parts which i would be missing without 2.10.401.8 RUU?
/edit:
now i found this one, you are referring to that?
Tectas said:
The last step to achieve a full upgraded phone would be to update the radio to the latest version, this you will also find at the index thread.
Click to expand...
Click to collapse
i guess you are referring to this? 20.4801.30.0822U_3822.10.08.04 with my sensation i would also have to flash a matching ril, isn't it recommended with desire s?
smint86 said:
is there a guide you are referring to? i already got 4ext recovery installed, but i don't find any post concerning 2.00.2002 bootloader. if i flash this one i would stay s-off? and it would bring me all parts which i would be missing without 2.10.401.8 RUU?
/edit:
now i found this one, you are referring to that?
Click to expand...
Click to collapse
Yes this guide is to "downgrade" (in fact it's an upgrade, even if the version number is lower).
Yes you would stay s-off.
No it not brings you all what is missing, just a part of it, the rest you get with flashing the radio and the rom.
smint86 said:
i guess you are referring to this? 20.4801.30.0822U_3822.10.08.04 with my sensation i would also have to flash a matching ril, isn't it recommended with desire s?
Click to expand...
Click to collapse
It's not really needed, you can do it if it's in the zip (or better said if it's there it's done at the flashing procedure), but you're also good to go without it.
Hello, I'm new to the Android scene having come from the iPhone so have a few questions before updating my HTC Desire S.
I would like to install the basic non-branded version of Android 2.3.5 with Scenes 3.0.
What I have is a HTC Desire S on Orange UK, Android 2.3.3, Sense 2.1, software 1.47.61.1
Now before the update came out I rooted my phone with Revolutionary and am S-OFF
with HBOOT-6.98.1002 and RADIO-3805.06.02.03_M I also installed superuser and I was about to install a custom ROM to get rid of the Orange bloatware.
But would I be able to achieve this by just installing a RUU .exe, ie this one ?
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe
or do I need to find the latest Europe ROM and flash with ROM Manager?
apologies for my ignorance I've been reading the forum but I'm still a newbie to Android, I would like to get some advise so I don't brick my phone
Ctrlloki said:
Hello, I'm new to the Android scene having come from the iPhone so have a few questions before updating my HTC Desire S.
I would like to install the basic non-branded version of Android 2.3.5 with Scenes 3.0.
What I have is a HTC Desire S on Orange UK, Android 2.3.3, Sense 2.1, software 1.47.61.1
Now before the update came out I rooted my phone with Revolutionary and am S-OFF
with HBOOT-6.98.1002 and RADIO-3805.06.02.03_M I also installed superuser and I was about to install a custom ROM to get rid of the Orange bloatware.
But would I be able to achieve this by just installing a RUU .exe, ie this one ?
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe
or do I need to find the latest Europe ROM and flash with ROM Manager?
apologies for my ignorance I've been reading the forum but I'm still a newbie to Android, I would like to get some advise so I don't brick my phone
Click to expand...
Click to collapse
First if you run this RUU or any non brand specific over your branded phone you will brick it.
Second: using RUU /a proper one/ will bring you back to Stock, and you will lose your root and S-OFF. But in your case running RUU will brick the phone because you have a Revolutionary bootloader /6.98.1002/ which has a protection and cannot be overwritten with RUU.
Third - custom ROM is a modified software (which is always rooted) that can be flashed via custom recovery (look at the sticky guide for beginners) The RUU is a Stock software (used in the past by HTC for updates)
Anyway if you want to debrand you can do this with a Goldcard and the RUU, mentioned by you but an earlier version like 1.28.401.1 or 1.47.401.4 (they can be unlocked with Revolutionary, the latest - 2.10.401.8 cannot), then S-OFF and root again/flash a custom ROM.
You can use the latest with a Goldcard, but then to gain root you will have to use htcdev.com to unlock the bootloader (which will send info about this to HTC and probably void your warranty - during the process you have to confirm your agreement with that)
Thanks for the quick reply and heads up on the Goldcard.
So after some reading on the Goldcard I take it that all I have to do is make myself a SD Goldcard and have it in the phone, then run the 2.10.401.8 RUU this will install Android 2.3.5 + Sense 3 unbranded but automatically S-OFF & un-root the phone.
(I'm not worried about losing these at this time)
but do I need to change anything about my Revolutionary bootloader "6.98.1002" before doing the above ?
Cheers
Ctrlloki said:
but do I need to change anything about my Revolutionary bootloader "6.98.1002" before doing the above ?
Click to expand...
Click to collapse
Yes you should replace your bootloader with an Engineering one like 0.98.2000 (link in my signature) or 2.00.2002
you can use Android flasher for that (link in the Index thread)
Then I suggest you to use an older European version to debrand (1.28 or 1.47) instead of RUU and use custom ROMs in order to keep the S-OFF and root
There are plenty of custom ROMs based on the latest official Sense 3.0 that you can flash instead the original (and you will have no bloatware on it)
Thanks for the info amidabuddha. I will give it a try tonight.
Just a small clarification if there is a term confusion:
You should follow this procedure ONLY IF you want to debrand the phone completely (i.e. change the version to an unbranded of all system components: hboot, misc, etc.) on low level
In case that under debrand you mean clean OS, without carrier specific software you need just to flash any Sense 3.0 based custom ROM, flash with ROM Manager and you are done. Then if you don't like the Orange splash screen you can replace it with Android flasher to another. Basically there is no difference whether you are branded or not to use custom ROMs. Branded means that your system version will stay Orange with any ROM running on it.
So you will stay branded and you want to return to Stock someday you will have to use the Orange RUU (but this is healthier in order to keep your warranty)
WARNING*WARNING*WARNING
do this at your own risk! This is for s4 only!!
It has been brought to my attention that there might be a mid (model id) conflict
With flashing this and me along with others are trying to narrow down the issue. Thanks to @real187 for bring this to my attention.
I'm
S-off
Cid 11111111
MID PJ4011000
And had no problems flashing this firmware but others with same setup have reported soft brick.
OK I think @mkinney88 may have pin pointed where the soft brick may be coming from. If you s-off using facepalm, flash the firmware.zip and get soft bricked try this.
1. Get back to s-on (warning read directions several times before doing you CAN hard brick your phone) ~ http://forum.xda-developers.com/showthread.php?p=38267667
2. Get s-off with moonshine ~ http://forum.xda-developers.com/showthread.php?p=42613403
First off this is mostly ment for the T-Mobile branded phones but ill try and help all please let me know when asking questions if you have a T-Mobile or HTC branded phone (it has it right on the front of phone ).
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111 (I had no problem flashing firmware with s-off and Cid 11111111 but others have reported problems so if you don't want to chance it write your Cid to T-MOB010)
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Downloads
FIRMWARE ZIP DOWNLOAD
https://drive.google.com/folderview?id=0B-BYnLh2sosKamRwaUJJS05oU3M&usp=sharing or http://db.tt/Wua8mDS2
Credit go's to mkinney88 for the firmware
Bricks
First off if you can get into bootloader then you don't have a hard brick.
If your phone is in the black screen of death there may be hope but we're still trying to figure that one out.
If your phone doesn't respond to any input from you (power, power+volume down) then congratulations you have a hard brick but don't through it in the junk drawer just yet, you can have it jtag repaired (they open phone plug into main board and flash everything)
Here's the link (you do have to pay for this)
http://forum.xda-developers.com/showthread.php?p=37136553
One more just in case
rc420head said:
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Click to expand...
Click to collapse
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
vatsaman said:
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
Click to expand...
Click to collapse
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
I put a note of this in op just now, thanks for the warning, I'm trying to figure out why some can do this Cid 11111111 and some can't.
-----------------------------------------
Friends don't let friends post without searching first!
rc420head said:
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
Click to expand...
Click to collapse
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
Something else is going on. I used facepalm, and Cid 11111111 to flash firmware twice now with no issues and started same as you hboot 1.14
-----------------------------------------
Friends don't let friends post without searching first!
thank you!
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
khan.orak said:
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
Click to expand...
Click to collapse
I'm not sure if I understand your question. So let me ask a few questions.
What hboot are you on?
What carrier are you using?
Are you wanting to try cm 10.1 and afraid for losing stock?
What is stock just HTC sense 4+ or is there carrier added stuff?
rc420head said:
I'm not sure if I understand your question. So let me ask a few questions.
Click to expand...
Click to collapse
ok I'll try to make it clearer.
What hboot are you on?
Click to expand...
Click to collapse
I'm on hboot 2.15.0000
What carrier are you using?
Click to expand...
Click to collapse
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Are you wanting to try cm 10.1 and afraid for losing stock?
Click to expand...
Click to collapse
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
What is stock just HTC sense 4+ or is there carrier added stuff?
Click to expand...
Click to collapse
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
khan.orak said:
ok I'll try to make it clearer.
I'm on hboot 2.15.0000
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
Click to expand...
Click to collapse
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
rc420head said:
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
Click to expand...
Click to collapse
Thanks for the reply, really much appreciated.
I already have rooted the device and custom recovery TWRP 2.5. Though I am considering to downgrade it to 2.3.30. Now I made a backup of stock ROM. (System + Boot Partition)
So is this the only way I can get to stock?
I read somewhere that the following method could be used too(?)
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
khan.orak said:
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
Click to expand...
Click to collapse
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Big thanks! :good:
vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes this will also work (I was under the impression no ruu's were available)
khan.orak said:
Big thanks! :good:
Click to expand...
Click to collapse
forgiven90 said:
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah disabling the fast dormancy solved all my problems. :good: