Database Info

Install a custom ROM with HTC official unlock

Can anyone please tell me how to install a custom ROM onto my Desire S with the bootloader unlocked via HTC Dev and S-ON?
My guess is that you install CWMR and flash it via that. But you need root access to do that, I thought unlocking the bootloader was meant to eliminate this.
Also, I've been reading that people are having issues installing ROMs this way, they are experiencing a hang at the HTC logo on boot.
Any information will be greatly appreciated, thank you.

spagmuff said:
Can anyone please tell me how to install a custom ROM onto my Desire S with the bootloader unlocked via HTC Dev and S-ON?
My guess is that you install CWMR and flash it via that. But you need root access to do that, I thought unlocking the bootloader was meant to eliminate this.
Also, I've been reading that people are having issues installing ROMs this way, they are experiencing a hang at the HTC logo on boot.
Any information will be greatly appreciated, thank you.
Click to expand...
Click to collapse
After you flash the custom ROM using CWM, you then have to extract the boot.img file from the ROM.zip file and manually flash it in FASTBOOT mode. That is the nature of the unlocked bootloader. The boot partition is not mounted R/W in recovery mode, it is only mounted R/W when you are in bootloader FASTBOOT mode.

Ok, from reading yours and various other posts in the forum, I need to do the following to install a custom ROM with an unlocked bootloader and S-ON:
1. Unlock bootloader via HTC's website
2. Root phone (with gingerbreak apk?)
3. Install CWM via ROM manager
4. Backup existing ROM with CWM and backup files with titanium
5. Install ROM via CWM (wipe data, wipe cache, install ROM)
6. Flash boot.img (HBOOT, fastboot, and flash image)
7.Reboot into cyanogenmod
If I have anything wrong, please let me know. Thanks.

spagmuff said:
Ok, from reading yours and various other posts in the forum, I need to do the following to install a custom ROM with an unlocked bootloader and S-ON:
1. Unlock bootloader via HTC's website
2. Root phone (with gingerbreak apk?)
3. Install CWM via ROM manager
4. Backup existing ROM with CWM and backup files with titanium
5. Install ROM via CWM (wipe data, wipe cache, install ROM)
6. Flash boot.img (HBOOT, fastboot, and flash image)
7.Reboot into cyanogenmod
If I have anything wrong, please let me know. Thanks.
Click to expand...
Click to collapse
Step 2 and 3 are not necessary. After you Unlock the bootloader, you could then simply flash ClockworkMod in FASTBOOT mode.
1. Unlock bootloader.
2. Flash CWM image in FASTBOOT mode.
3. Backup existing ROM with CWM.
etc.

Successfully installed latest nightly r2 yesterday night :O
All is fine, 3D performance is smoothly and fine...
Thanks for yours posts

I would also like to thank you tpbklake, haven't tried it yet, but I'm sure it'll work!

I will be getting a new unbranded Desire S in a couple of days,
In case it will be running HBOOT 2.00.0002 with S-ON will I be still able to flash a custom rom on the device? AKAIK S-ON only protects the radio from being modified.
sorry, I'm new to this
edit: okay i read its not possible to flash a custom rom, but then what can i do when I rooted and flashed a custom recovery?

kjdfkvdjjndvldmv; awesome

xStreame said:
I will be getting a new unbranded Desire S in a couple of days,
In case it will be running HBOOT 2.00.0002 with S-ON will I be still able to flash a custom rom on the device? AKAIK S-ON only protects the radio from being modified.
sorry, I'm new to this
edit: okay i read its not possible to flash a custom rom, but then what can i do when I rooted and flashed a custom recovery?
Click to expand...
Click to collapse
Either isn't possible without s-off, look at the index thread, it's all there.
Swyped from my desire s running damn sweet ice cream

I'm on an Inc2 but since it's basically the same I hope this applies...
I'm in the same position as the OP with the newly unlocked bootloader via HTC.
I flashed cwm through fastboot but now I can't reflash through ROM Manager. I installed both SuperUser and BusyBox but both point the finger at eachother saying the other needs to be installed. What am I missing??

Kayak83 said:
I'm on an Inc2 but since it's basically the same I hope this applies...
I'm in the same position as the OP with the newly unlocked bootloader via HTC.
I flashed cwm through fastboot but now I can't reflash through ROM Manager. I installed both SuperUser and BusyBox but both point the finger at eachother saying the other needs to be installed. What am I missing??
Click to expand...
Click to collapse
Download the latest su-3.0.x.zip file. Then boot into CWM recovery and install this zip file. This will root the current ROM you have installed and then ROM Manager and BusyBox will both be happy.

@korenisko
So you unlocked via HTC dev, flashed custom recovery, wiped all partitions, flashed cyanogenmod, rebooted into fastboot, flashed boot.img via fastboot (fastboot flash boot /pathtobootimg/boot.img, if i recall correctly) and then you were able to boot into cyanogen?
I did exactly these steps (only with 4ext instead of cwm, which shouldn't affect the result) and was stuck with the white bootscreen and no adb logcat output whatsoever.
Currently I am back on a prerooted official RUU (2.3.3), but it still performs really bad and I would like to have cyanogenmod.
Btw: I have a Desire S, hboot 2.00.0002, S-ON, no carrier branding.
Thanks,
wenzlern

The currect way
I Have HTC Desire S with original Rom 2.10.401.8 and HBOOT 2.00.0002 S-On
My goal is to install the Endymon
I read many thread and i understood that the curret way to do this is:
Downgrade My ROM from 2.3.5 ( 2.10.401.8 with HBOOT 2.00.0002) to a ROM 2.3.3 with HBOOT 0.98.00000 (Ex: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.exe)
To do this i need to follow the steps from 1 to 7 of this
http://forum.xda-developers.com/showpost.php?p=20535265&postcount=26
Now i need to change HBOOT, Change Recovery and Root the phone. To do this i need to use Revolutionary tool for Windows from http://revolutionary.io/ and follow the istruction.
Now i can download the custom Rom and install using this way:
http://forum.xda-developers.com/showthread.php?t=1257731
Is It right?
Thanks

Hello, I just want to share my experience on how i managed to S-OFF my phone. My main problem was that I had the latest ruu on 2.10.401.8 and couldnt downgrade. Even though i unlocked the bootloader using the htcdev .bin file I couldnt install the proper recovery (clockwork mod) nor a previous ruu. So here is what I did.
I first unlocked the phone using the htcdev.
Then I followed those pretty 7 steps mentioned on prev post.
and changed my version to a prev one.
I r e l o c k e d my phone using htc supertool and
clicked my 1.47 ruu exe file. That worked and it downgraded my phone.
After that it was a piece of cake to use the revolutionary tool to S-OFF.
Thanks all the xda community for the infos i got and managed to do it....
cheers

mannkan said:
Hello, I just want to share my experience on how i managed to S-OFF my phone. My main problem was that I had the latest ruu on 2.10.401.8 and couldnt downgrade. Even though i unlocked the bootloader using the htcdev .bin file I couldnt install the proper recovery (clockwork mod) nor a previous ruu. So here is what I did.
I first unlocked the phone using the htcdev.
Then I followed those pretty 7 steps mentioned on prev post.
and changed my version to a prev one.
I r e l o c k e d my phone using htc supertool and
clicked my 1.47 ruu exe file. That worked and it downgraded my phone.
After that it was a piece of cake to use the revolutionary tool to S-OFF.
Thanks all the xda community for the infos i got and managed to do it....
cheers
Click to expand...
Click to collapse
Congrats. XDA is really helpful.

Sarina,
No need to wipe dalvik cache?
bcoz few ROM's developers days it a must!!!!
I trying to flash CM7.1 stable version.

mannkan said:
Hello, I just want to share my experience on how i managed to S-OFF my phone. My main problem was that I had the latest ruu on 2.10.401.8 and couldnt downgrade. Even though i unlocked the bootloader using the htcdev .bin file I couldnt install the proper recovery (clockwork mod) nor a previous ruu. So here is what I did.
I first unlocked the phone using the htcdev.
Then I followed those pretty 7 steps mentioned on prev post.
and changed my version to a prev one.
I r e l o c k e d my phone using htc supertool and
clicked my 1.47 ruu exe file. That worked and it downgraded my phone.
After that it was a piece of cake to use the revolutionary tool to S-OFF.
Thanks all the xda community for the infos i got and managed to do it....
cheers
Click to expand...
Click to collapse
Many thanks for this it has helped me get S-off again after a very frustrating weekend.

Procedure getting rooted ans current

So to get current I would just flash to the newest ruu, then root it (can you root 1.85?), then open the downloader, then flash cwm?
Just trying to cover my bases.
Sent from my HTC One X using XDA

Is your objective to update to 1.85 and remain rooted?

joho5 said:
So to get current I would just flash to the newest ruu, then root it (can you root 1.85?), then open the downloader, then flash cwm?
Just trying to cover my bases.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
If you are currently bootloader unlocked, then go into fastboot etc and "fastboot oem unlock" (http://forum.xda-developers.com/showthread.php?t=1675312).
If not, then flash new RUU.
Afterwards bootloader unlock.
Then flash CWM.
Finally flash Superuser through CWM.
Then you can flash custom ROMs (hopefully more are coming!!!).

ce12373 said:
If you are currently bootloader unlocked, then go into fastboot etc and "fastboot oem unlock" (http://forum.xda-developers.com/showthread.php?t=1675312).
If not, then flash new RUU.
Afterwards bootloader unlock.
Then flash CWM.
Finally flash Superuser through CWM.
Then you can flash custom ROMs (hopefully more are coming!!!).
Click to expand...
Click to collapse
I am not unlocked. I'm still on 1.72 just debloated and rooted. To unlock my bootloader, I just use htcdev right?
So I will flash current ruu, then unlock with htcdev, then flash cwm, and then flash the root and ill be ready?
I got a question, in the future will you always have to be on that certain ruu to flash that particular Rom? I come from the infuse where once you were rooted and had cwm, you could skip around rims by cwm every time, didn't have to do anything prior to each custom rom.
Sent from my HTC One X using XDA

[Q] S3 Villec2 OTA update

I've got an HTC One S [s3]. CID is HTC__622 Asia HK
I have unlocked bootloader, TWRP recovery and superSU loaded as well as Rom Manger
Tonight there is an OTA update available. So I want to use it. I downloaded it and
ran command: fastboot oem lock
and tried to run the update. It just keeps booting into my fastboot menu.
I heard that I need to install stock recovery tfor this to work but I don't know where I can find it.
I do have a reovery_signed.img file that I saved from somewhere that is 5,957 kb. Not sure if I flash that if it would give me stock recovery.
Can someone give me a direction to go. I have spent last 12 hours just reading stuff and still don't know what to do.

Htc_asia_hk Stock Recovery File
Does anyone know where I can find the stock recovery file for my One S [S3]
Its Htc_asia_hk the CID is HTC__622 ???
The beginning of the file name should look like this:
RUU_VILLEC2_U_ICS_40_HTC_ASIA_HK_

Flash stock recovery
Lock bootloader
Then run the ota update.
Sent from a HTC

Try This RUU in fastboot
http://forum.xda-developers.com/showthread.php?t=2011598

Quills88 said:
Does anyone know where I can find the stock recovery file for my One S [S3]
Its Htc_asia_hk the CID is HTC__622 ???
The beginning of the file name should look like this:
RUU_VILLEC2_U_ICS_40_HTC_ASIA_HK_
Click to expand...
Click to collapse
you dont need to flash stock recovery because RUU does ...

luxandroid said:
you dont need to flash stock recovery because RUU does ...
Click to expand...
Click to collapse
The problem is I didn't take a backup before I unlocked my bootloader and flashed twrp recovery so I don't have a stock recovery to go back to.
The RUU for HTC__044 has a different CID and won't work on my device unless I can extract just the stock recovery from the RUU without having to install it. Is that possible?

same
Quills88 said:
The problem is I didn't take a backup before I unlocked my bootloader and flashed twrp recovery so I don't have a stock recovery to go back to.
The RUU for HTC__044 has a different CID and won't work on my device unless I can extract just the stock recovery from the RUU without having to install it. Is that possible?
Click to expand...
Click to collapse
i also have htc__622 CID and i didn't make backup before fiddling with the innards.

What you have to do is
1. Flash stock recovery
2. Lock your bootloader
3. Enter fastboot and run the RUU for your phone
Your phone will then be just as it was when you bought it and then you can run the OTA. Make sure you find the right RUU for your phone. I have been searchiing for one for days and couldnt find it. Hope this helped

nez762 said:
What you have to do is
1. Flash stock recovery
2. Lock your bootloader
3. Enter fastboot and run the RUU for your phone
Your phone will then be just as it was when you bought it and then you can run the OTA. Make sure you find the right RUU for your phone. I have been searchiing for one for days and couldnt find it. Hope this helped
Click to expand...
Click to collapse
I have the same problem, so I have few questions....
Where can I find stock recovery for HTC One S c2?
How to lock bootloader?
THANK YOU!

I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
sorry, for my bad english.

Privremeni said:
I have the same problem, so I have few questions....
Where can I find stock recovery for HTC One S c2?
How to lock bootloader?
THANK YOU!
Click to expand...
Click to collapse
Hi,
You can lock your bootloader with next command in fastboot:
fastboot oem lock
But question remains
Where can I find stock recovery for HTC One S c2?
Somebody cab help us?
Thanks!

Impo5sible said:
I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
sorry, for my bad english.
Click to expand...
Click to collapse
You cant flash OTA trough TWRP, thats my problem also. My CID is 032 as yours. If you find RUU JB, send me the link please!

Privremeni said:
You cant flash OTA trough TWRP, thats my problem also. My CID is 032 as yours. If you find RUU JB, send me the link please!
Click to expand...
Click to collapse
Maybe a stock recovery of JB would be enough.

Hello guys,
Try this:
Step 1: relock the bootloader (start your phone in fastboot, open cmd, got to folder where are fastboot files, type "fastboot oem lock" )
Step 2: find your desired stock jb or ics online. http://filesdownload.net/showthread.php?70-HTC-One-S-(-RUU_VILLE-)-(-RUU_VILLEC2-)
Step 3: connect your phone to the pc in fastboot (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
Step 5: Now you are in stock ROM
It should work after this!
On my HTC One S [S3] , CID HTC_032 works

splanet.info has something interesting
At least ota is there for htc__622

Nez is right
nez762 said:
What you have to do is
1. Flash stock recovery
2. Lock your bootloader
3. Enter fastboot and run the RUU for your phone
Your phone will then be just as it was when you bought it and then you can run the OTA. Make sure you find the right RUU for your phone. I have been searchiing for one for days and couldnt find it. Hope this helped
Click to expand...
Click to collapse
After I locked my bootloader and tried running the OTA update I tried a few things that didn't work.
But what did work for me was when I unlocked bootloader again
And used Hasoon's Toolkit for One S
and reflashed the recovery file. I used the recovery_signed.img file (5,957 kb) that I had saved from when I was rooting it the first time and renamed it to a one word name per Hasoon's instructions, then flashed it.
Then I relocked bootloader and did a factory reset and ran the OTA update and it worked.
I was lucky that I had that recovery file saved. Still not sure where I got it from. But one thing for sure is that it was hard to find a RUU file for my CID. Hasoon's toolkit does have links to a website with a list of RUUs on it but mine wasn't on the list.
If you want me to email you my signed_recovery.img file send me a pm with your email address and I'll send it.

Privremeni said:
I have the same problem, so I have few questions....
Where can I find stock recovery for HTC One S c2?
How to lock bootloader?
THANK YOU!
Click to expand...
Click to collapse
I have attached the stock recovery just use fastboot to flash it

[Q] ROm Flashing issue

Hello,
I am trying to flash CleanRom 7.0 or any JB rom on my HTC One X (AT&T) but always gets stuck in bootloop (phone does not go past boot screen after flashing). This is what i have done.
The phone is on AT&T 1.82 stock room (rooted, SuperCID, S-Off). The phone was on some older HBoot version so I upgraded it to 2.15. Radio is 0.17.32.09.12. And I have TWRP recovery.
So I made a nadroid backup in recovery and than tried to install AT&T 3.82 rooted (downloaded from XDA, may be without radio and all). After successful flashing when I tried to reboot the system it got stuck on AT&T boot screen. So I rebooted in recovery and wiped everything. After that I tried to install CleanROM 7.0 R2 and same thing happened and even I tried latest elemental kernel but same thing is keep happening.
Can you please help me with this?
Thanks

At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita

timmaaa said:
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
Click to expand...
Click to collapse
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks

alex8525 said:
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
Click to expand...
Click to collapse
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk

phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.omg after flashing.
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
Yes I am S-Off. I will let you know the version of TWRP when I get back home since I don't have phone with me right now. By the way I used goomanager to update TWRP, if that helps.
Thanks,

phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks

K so if you are s-off then you can just flash it. If you wernt then you would need to flash boot.img. now you can try to flash the boot.img. it might not fix it but start small and work up.
Sent from my HTC Butterfly s using Tapatalk

alex8525 said:
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
Click to expand...
Click to collapse
TWRP is the correct way to install ROMs, but I have a feeling that your current version of TWRP is your problem. Some (2.4.x, 2.5.x) are buggy and have major problems. If your TWRP version is either of those that I've just mentioned you can update it to a known bug-free version like this:
Download the modified version of TWRP*2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita

That's the reason I asked what twrp version he had
Sent from my HTC Butterfly s using Tapatalk

At&t Htc One X 4.2.2 Root

Help im new!
Soo i recently got my htc one x on android jelly bean 4.2.2 from at&t and is there a method or easy root method for this version? 4.2.2, with 5.18? I really want to try and root my phone but i know nothing about messing with all these types of files, and i dont want to risk destroying my phone.
Im not sure if there is already a post or something about this and if it is im sorry, these forums are a bit overwhelming and i am new.
I would very much appeircate any help or info on being able to easily root my htc one x 4.2.2, 5.18 at&t white.

The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita

timmaaa said:
The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita
Click to expand...
Click to collapse
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.

There is a perfectly easy way to unlock your bootloader on the 3.18 software, it isn't a stupid phone, nor is the exploit hard to achieve, hundreds if not thousands of people have done it. It's as simple as entering a few adb/fastboot commands.
You can't root on 5.18 because the update patched the weakness that was exploited in the 3.18 software/firmware. It takes time for devs to crack these things and the update has only just been released. It's not even sure whether the devs will want to spend any time finding a crack for a phone that's relatively old now. This is why you never take an update without first unlocking/rooting, unless you're comfortable with the fact that you won't be able to (it is a well established fact that updates patch exploits).
Sent from my Evita

5.18!to 3.18 ruu
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?

brenntard said:
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?
Click to expand...
Click to collapse
Bootloader details please.
Sent from my Evita

timmaaa said:
Bootloader details please.
Sent from my Evita
Click to expand...
Click to collapse
Tampered
Relocked
Evita put ship s-on rl
Hboot-2.18.0000
Radio-1.35a.32.45.27
Opendsp-v33.1.0.45.1128
Emmc-boot
It's weird, I tried using the all in one toolkit and was able to unlock the boot loader, get twrp recovery working and flash supersu. The only problem I ran into was when I opened supersu it said the binaries need to update. The first time I updated them and it was fine then the phone shut off and supersu would always need updated when opened...I downloaded titanium backup and was able to get root access before my phone restarted and I had to update supersu again... It is now relocked, obviously, but easy enough to unlock again using the toolkit

You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita

timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Yes it says me CID is 11111111. Why would supersu be acting so funny and constantly telling me to update the binaries...supersu seems relatively useless at this point. do i need supersu to flash a custom ROM?

Forever95 said:
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.
Click to expand...
Click to collapse
Lack of research. A working root method exists for 3.18, both a "manual" method and two "Toolkits" for those that can't handle the manual method.
Also, you should never never never install an OTA update unless you know what has been patched, changed, etc. Updates frequently will patch existing root exploits, and therefore leaving you in the spot you find yourself in.
Other devices (such as the One) can be rooted with later firmware, simply because that device has more developer interest. It requires the right talented developer(s) putting in the time and effort to find the exploit method. Its still possible on this device with 5.18. All it takes is the right guy and the proper amount of motivation. But as the device is getting older, and devs are moving to other phones, those chances do get more unlikely.

UPDATE!
timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for the help. i know officially have an s-off device that is unlocked and rooted ready to run custom ROMS.
My next question would be how do i flash a kernel and why would i flash a kernel?

cant flash ROM
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?

brenntard said:
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?
Click to expand...
Click to collapse
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.

timmaaa said:
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.
Click to expand...
Click to collapse
That sounds easy enough.. I was able to gain s-off through the face palm method earlier today so now i just need to flash the 2.15 firmware. in the thread it says to "make sure you flash your current ROM's boot.img after" is this necessary if i am using the stock 4.2.2 sense 5 ROM already, does the download include the radio? do i need a different radio?

The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita

timmaaa said:
The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita
Click to expand...
Click to collapse
awesome! im gonna try that tonight.

Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita

timmaaa said:
Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for your help! i succesfully flashed the firmware and amnow running CM10.2.1. If i want to flash a 4.4 ROM do i need a different recovery? im currently using 2.5.0.0

Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita

timmaaa said:
Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
Click to expand...
Click to collapse
I guess the all in one toolkit hasn't had an update in a while...
thanks again for all the help, really appreciated
i have been working to get a custom rom on my device for roughly a month now and today was the day it finally happened
glad to say i learned a lot thanks to help from people like you in this great forum