Database Info

Firmware Update Q&A [extra noob friendly]

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:

[Q] Installing RUU, which one to choose

Hi,
My battery has been acting up for almost half a year now and my usage time is half of what it was when i got it. I have been installing several different ROMs and kernels so I am at a lost on what's wrong. So I have decided to install a RUU to see if a total reset can fix my phone.
I found this page: http://www.androidfiles.org/ruu/?developer=Ville
Does anybody know which RUU from the link is the newest/best? Will I get updates from HTC when I do this?
Currently running trickdroid 10.3.2, bricked kernel, twrp 2.3.3, S-OFF and superCID - is there anything in particular I should know before doing this?
I have never installed a RUU before, hope somebody can help

anyone? Or perhaps just a part answer

teamet said:
anyone? Or perhaps just a part answer
Click to expand...
Click to collapse
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman

G.Rabbani said:
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman
Click to expand...
Click to collapse
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that)
2. CID & MID (CID getter from play store will tell you that)
3. Last Stock firmware you had/installed?
4. HBOOT version?
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that) -----> S4
2. CID & MID (CID getter from play store will tell you that) -----> 11111111
3. Last Stock firmware you had/installed? -----> JB 4.1.1
4. HBOOT version? -----> 2.15.0000
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the response I've responded to your queries inline.

G.Rabbani said:
Thanks for the response I've responded to your queries inline.
Click to expand...
Click to collapse
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386

G.Rabbani said:
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386
Click to expand...
Click to collapse
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
Edit 2: The CID in all cases comprises of 8 characters. i.e HTC__001 (8 chars), BM___001 (8 chars, my CID) etc. So when changing the CID, be sure to have an 8 character CID.
regards

khan.orak said:
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
regards
Click to expand...
Click to collapse
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.

G.Rabbani said:
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.
Click to expand...
Click to collapse
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
- Just need to Unlock bootloader to Root/Flash custom recovery/custom ROM

khan.orak said:
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
Click to expand...
Click to collapse
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...

G.Rabbani said:
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...
Click to expand...
Click to collapse
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.

khan.orak said:
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.
Click to expand...
Click to collapse
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:

G.Rabbani said:
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:
Click to expand...
Click to collapse
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?

G.Rabbani said:
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?
Click to expand...
Click to collapse
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?

G.Rabbani said:
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?
Click to expand...
Click to collapse
- Okay before anything, i would advise to flash TWRP 2.3.3.0 recovery and you will avoid many issues currently being faced with 2.5.0.0.
You can find 2.3.3.0 Here.
If you need help on flashing, ask away.
- now your questions:
1. No and No
2. You have to boot into bootloader and then go into FASTBOOT and write the command
fastboot oem writecid HTC__001
BTW, I assume you have adb+fastboot files on your PC?
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
fastboot oem writecid HTC__001
Click to expand...
Click to collapse
This only works if you are S-OFF
hTConeS | SoFF | ChaRmAnDrOiD | BuLLetprOOf
Inverted Sense 5 Theme Updates+Tweaks
Inverted Sense 4+

[Q] My HTC One X AT&T has signal issues and random reboots

Hi everybody i flash my htc one x at&t with android 4.2.2 (sense5), i used urdroid version --------->(http://forum.xda-developers.com/showthread.php?t=2331373) and now my phone lost the signal and random reboots, i heard that the problem is the kernel but i don't know what kernel i should install. hope you can help me.
Thanks.
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as 32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot

Please search properly before posting next time, the answer has been discussed dozens of times in every single Sense 5 ROM thread.
1. Search before posting.
Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.
Click to expand...
Click to collapse
You can flash the Beastmode kernel to fix the problem but the real solution is to flash the 2.15 firmware package. You'll find it (along with detailed instructions) in Turge's stock Sense 5 ROM thread in our Android Development section.
Sent from my Evita

Thanks for the answer
Could you send me the link please
Sent from my HTC One XL using xda app-developers app

I told you exactly where to find it, I'm not going to go and find it for you, that's something you can do for yourself. In the time it took you to write that post your could have already found it and downloaded it.
Sent from my Evita

Thanks dude, i downloaded the beastmode kernel and flash it but now when my phone is starting stuck on at&t logo and then reboot. Do you know why my phone do that?
I'm not super cid and i'm S-ON
Thanks for your answers.

There are a certain group of phones that have a slow SoC, basically they can't handle the Beastmode kernel. You'll need to get s-off and flash the firmware instead. If you need links just look in the Everything Evita thread in my signature. You should bookmark that thread, it contains links to pretty much everything you'll ever need.
Sent from my Evita

Thanks, i'm thinking return to stock rom. Do i have relock my bootloader right? And then run RUU or what do you recomend me to do?

Whatever you do don't run any RUU yet. If you want to return to stock you need to get s-off first. I know you think you don't have SuperCID but if your phone is an at&t model then there's no way you could have unlocked your bootloader without SuperCID. Basically, s-on + SuperCID + jb RUU = brick. So lets check your CID. I'm assuming you have adb/fastboot installed on your PC? If not you need to do that first. Once you have it installed you can connect your phone in fastboot mode (reboot to bootloader and connect), then you need to open a command prompt from within your fastboot folder on your PC (open folder where fastboot.exe is located, shift + right click, select open command prompt here), then issue this command:
Code:
fastboot oem readcid
Tell me what it says.
Sent from my Evita

I was reading about s-off and super cid but I'm new doing this and sounds a little hard to do so don't you think it's better if I install a stock backup
That will solve my problem?

You were right I'm super-cid my cid is: 11111111

S-off is very easy if you already have SuperCID. The biggest obstacle is installing adb/fastboot, if you haven't already. Otherwise, don't worry about being new. We all were at one time. Just read up and understand the process, and follow the instructions carefully, and you will be fine.
---------- Post added at 12:52 PM ---------- Previous post was at 12:50 PM ----------
arthur2820 said:
don't you think it's better if I install a stock backup
Click to expand...
Click to collapse
I don't see how that is in any way "better". If you s-off, all you then need to do is install the 2.15 firmware package, and the signal drop and random reboot issues will disappear.
If you went through the trouble to be able to flash custom ROMs, let's keep it that way.

arthur2820 said:
I was reading about s-off and super cid but I'm new doing this and sounds a little hard to do so don't you think it's better if I install a stock backup
That will solve my problem?
Click to expand...
Click to collapse
arthur2820 said:
You were right I'm super-cid my cid is: 11111111
Click to expand...
Click to collapse
I thought so. Getting s-off is pretty easy, all you need to do is follow some instructions and enter some fastboot and adb commands. Basically, if you can read and type you can do it. As Redpoint said you do need adb/fastboot installed, if you don't already have those you can Google search 'minimal adb and fastboot' and the first result should be a thread that explains how to install it very easily.
We all started somewhere, it might seem a bit daunting at first but I guarantee you it isn't as hard as it seems. Once you get learning it becomes really easy to understand. If you have any questions and can't find answers after some thorough searching just ask, you've got some good people here to assist you.
Sent from my Evita

Thanks I'll try it, could you send me the link of adb/fastboot installer? I guess that the only thing I have to do to install 2.15 formaware it's get s-off
Sent from my HTC One XL using xda app-developers app

See my post right above yours, I've told you what to search for.
Sent from my Evita

i found this thread http://forum.xda-developers.com/showthread.php?t=2155071 i've downloaded the zips bit in the step number 1 i don't know whats means "working directory" the thread it's the correct to get s-off?
how can i flush the image? (step 5)

That's one of the two s-off methods, yes. Your working directory is the folder on your PC where you have adb.exe and fastboot.exe located. You have those installed now right? In order to open the command prompt from that location just shift + right click anywhere in the folder then select open command prompt here.
Sent from my Evita

yes i've installed minimal adb and fastboot. the other method it's easier?

The method you're already using is fine, I used that method and it took me about ten minutes.
Sent from my Evita

ok. mmm but what means flush image again immediately?
Do i have to put the 2 zips in the working directory?

Did you read the instructions? It details exactly what you need to do, follow those directions to the letter. It tells you which zip needs to stay in zip format and which zip needs to be extracted. It tells you what commands to type when the command prompt returns text.
Sent from my Evita

[Q]~[HELP] SuperCID, Unlocked, Rooted, and S-OFF, how to restore to stock AT&T ROM?

[Q]~[HELP] SuperCID, Unlocked, Rooted, and S-OFF, how to restore to stock AT&T ROM?
Hi, geeks,
For my AT&T HTC One X, I have followed you guys all the way to here now: with SuperCID, Bootloader Unlocked (via HTC Dev), Rooted of course, and S-OFF (with touchscreen firmware down-graded).
Now I want to go back to AT&T stock ROM to use the ISIS wallet. Could you please tell me how? I am worried that my phone get bricked!
Thank you so much!

You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita

Thank you, timmaaa. Do I need to lock the bootloader and so on? I saw it somewhere but can't find the link now.
timmaaa said:
You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita
Click to expand...
Click to collapse

To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita

timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.

One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse

Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita

Hi, timmaaa, I got a RUU error 155 when flashing RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe.
Seems I need to re-lock the bootloader, which I am reluctant to do. Do I miss anything?
timmaaa said:
Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita
Click to expand...
Click to collapse

You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita

Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
timmaaa said:
You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita
Click to expand...
Click to collapse

aaronDroid80 said:
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.
Click to expand...
Click to collapse
You need to make sure the person you are trading with understands the phone is s-off and bootloader unlocked, and what that means.
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
BBS678 said:
One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
Click to expand...
Click to collapse
If you think you might still want to flash custom ROMs, you need to ask yourself why you want to return to stock in the first place.
Going back to stock if you are s-off, custom recovery, etc. is a step backward, not forward. Aside from getting on the correct hboot, firmware, etc. (or selling/trading your phone like the guy above), there is no benefit to going through all the hassle to running the RUU to get back to stock. Just flash a stock rooted ROM as timmaaa originally mentioned.
EDIT: Missed the part in the OP where it mentioned ISIS. See my response below (#13).

An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
BBS678 said:
Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
Click to expand...
Click to collapse

BBS678 said:
An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
Click to expand...
Click to collapse
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? Its possible. Changing from SuperCID is very easy with fastboot. Just search for the command.
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4

Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
redpoint73 said:
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? I suppose its possible, but my gut says no. Especially in light of the following:
I'm thinking it more the issue that the AT&T One X is not a "ISIS ready phone": http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
Click to expand...
Click to collapse

BBS678 said:
Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
Click to expand...
Click to collapse
Yes, I later realized that One X is not available at all anymore from AT&T (and that it is supposed to be ISIS ready), and revised my above response accordingly.
BBS678 said:
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
Click to expand...
Click to collapse
It could also be that they are looking at the phone model number. So SuperCID is a possibility, but not certain.
Its easy to change from SuperCID with a simple fastboot command. Just search this forum for the proper syntax.
---------- Post added at 02:43 PM ---------- Previous post was at 02:32 PM ----------
Here is the command to change from CID:
fastboot oem writecid CWS__001
(note that CWS__001 has two underscores)

Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.

BBS678 said:
Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.
Click to expand...
Click to collapse
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.

Hi, timmaaa, could you please shed some lights on this (change back to stock CID) please? Thanks!

here is my other post about ISIS: http://forum.xda-developers.com/showthread.php?p=49822333
redpoint73 said:
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.
Click to expand...
Click to collapse

Everything that @redpoint73 has said is correct. There's pretty much no risk involved in changing your CID back to stock, having s-off does not rely on SuperCID. You can try changing your CID using the command that redpoint gave before.
There's pretty much no risk involved with going from s-off to s-on either. I don't know where you read that but I believe you're misunderstanding the information. Personally I wouldn't go back to s-on though because I don't believe that is affecting your ability to run ISIS. Plus getting s-off again can be tricky sometimes.
Sent from my Evita

Upgrading my hboot???

Hello all, here is my situation.
I recently purchased two used HTC One X phones. After a bit of research, I found out that they are actually the international version, the XL or Evita as they also go by. This is not a problem to me. I struggled getting them to take custom ROMs and I was finally able to get Cyanogenmod 10.0 installed. They are working great as is, however I would like to be able to update further, as there are a couple very minor bugs. Whenever I try to install an update through clockwordmod recovery, I always get a bootloader error. The number is spits out is 2.14, which I know is a never version of hboot. So, my question is, should I update my hboot (currently in 1.14.0002) to 2.14 in order to install newer versions of Cyanogenmod? If so, can you please provide detailed step by step instructions, or link me to a forum that does? Thank you.
Other potentially relevant information:
-EVITA PVT SHIP S-ON RL
bootloader unlocked via HTCdev

Ok, firstly it isn't the hboot you need to update, it's the firmware. It just happens that the firmware contains the hboot, and the hboot version is what's used by the ROM installer to tell whether you've updated or not. First thing you'll need to do is get s-off, that's required for flashing the firmware.
Facepalm S-off
Rumrunner S-off Thread
Once you've done that just head to the How-To Guide For Beginners thread in my signature and follow the directions there to update your firmware.
It might be a good idea to bookmark that thread, and also the Evita FAQ thread. The answer to your question is contained within the FAQ thread, which is actually stickied at the top of the section you've just posted in.
Sent from my Evita

timmaaa said:
Ok, firstly it isn't the hboot you need to update, it's the firmware. It just happens that the firmware contains the hboot, and the hboot version is what's used by the ROM installer to tell whether you've updated or not. First thing you'll need to do is get s-off, that's required for flashing the firmware.
Facepalm S-off
Rumrunner S-off Thread
Once you've done that just head to the How-To Guide For Beginners thread in my signature and follow the directions there to update your firmware.
It might be a good idea to bookmark that thread, and also the Evita FAQ thread. The answer to your question is contained within the FAQ thread, which is actually stickied at the top of the section you've just posted in.
Sent from my Evita
Click to expand...
Click to collapse
Okay, thanks. Yeah I'm aware you can't get boot without a firmware update. Will 2.14 allow me to update to cyanogenmod 11?

Yes it will but getting that firmware requires you to run an RUU, which also requires s-off, and is a lot harder than just flashing the firmware package.
Sent from my Evita

timmaaa said:
Yes it will but getting that firmware requires you to run an RUU, which also requires s-off, and is a lot harder than just flashing the firmware package.
Sent from my Evita
Click to expand...
Click to collapse
Major problems. I now have s-off but my phone refuses to boot. It was in a boot loop, tried flashing boot.img again and now it tries to start then fails, black screen until I how the volume and power button to get back into bootloader. Any suggestions on that?

asilaydyingdl said:
Major problems. I now have s-off but my phone refuses to boot. It was in a boot loop, tried flashing boot.img again and now it tries to start then fails, black screen until I how the volume and power button to get back into bootloader. Any suggestions on that?
Click to expand...
Click to collapse
Flash a ROM, not really a major problem.
Sent from my Evita

timmaaa said:
Flash a ROM, not really a major problem.
Sent from my Evita
Click to expand...
Click to collapse
Tried it, still fails. Installed the ROM, gapps, and flashboot flash boot boot.img

timmaaa said:
Flash a ROM, not really a major problem.
Sent from my Evita
Click to expand...
Click to collapse
Flashed the right boot.img (somehow had the wrong one) now back in boot loop again. Any ideas? I did have to change my CID because I did not turn on debugging for ADB. Would that have something to do with it?

What are your bootloader details now? What did you change your CID to? And what did that have to do with debugging? What ROM did you flash?
Sent from my Evita

timmaaa said:
What are your bootloader details now? What did you change your CID to? And what did that have to do with debugging? What ROM did you flash?
Sent from my Evita
Click to expand...
Click to collapse
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT 1.14.0002
Flashed Cyanogenmod 10.0.0. I was unable to use the last command successfully on facepalm's tutorial without allow ADB in android debugging.

Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita

timmaaa said:
Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Ummm... how do I transfer the new files to my phone if I can't get it to boot in the first place? I will need to transfer the files for the new ROM.

timmaaa said:
Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
IM BACK IN!!! Updating the firmware did it! THANKS FOR YOUR HELP!!! KITKAT HERE I COME!