Database Info

Quick Qestion About Relocking The Bootloader

Couple quick question regarding locking the re-locking the bootloader.
First off I have the ATT One X rooted with TWRP Recovery. To go back to stock if I so choose, would I have to reflash the stock recovery then do fastboot oem lock before running the ruu or can i just fastboot oem lock the bootloader without flashing the stock recovery, then run the ruu?
I think I have to reflash the stock recovery first before relocking the bootloader. If that's the case, can someone link to the stock recovery img file?
I also read that if you're currently rooted and has your CID, you can update to 2.20 and root again...is that still the case?
Thanks

plmiller0905 said:
Couple quick question regarding locking the re-locking the bootloader.
First off I have the ATT One X rooted with TWRP Recovery. To go back to stock if I so choose, would I have to reflash the stock recovery then do fastboot oem lock before running the ruu or can i just fastboot oem lock the bootloader without flashing the stock recovery, then run the ruu?
I think I have to reflash the stock recovery first before relocking the bootloader. If that's the case, can someone link to the stock recovery img file?
I also read that if you're currently rooted and has your CID, you can update to 2.20 and root again...is that still the case?
Thanks
Click to expand...
Click to collapse
You can just fastboot oem lock, the RUU will take care of restoring the original ROM.
EDIT: This is my 123 post

plmiller0905 said:
Couple quick question regarding locking the re-locking the bootloader.
First off I have the ATT One X rooted with TWRP Recovery. To go back to stock if I so choose, would I have to reflash the stock recovery then do fastboot oem lock before running the ruu or can i just fastboot oem lock the bootloader without flashing the stock recovery, then run the ruu?
I think I have to reflash the stock recovery first before relocking the bootloader. If that's the case, can someone link to the stock recovery img file?
I also read that if you're currently rooted and has your CID, you can update to 2.20 and root again...is that still the case?
Thanks
Click to expand...
Click to collapse
If you want to go back to stock just fastboot oem lock then run the RUU. This is what I did. You can then re-unlock the bootloader and install SuperSU to reestablish root. It's pretty easy. Keep in mind, once you go to 2.20 you can not flash boot.img or radios from TWRP. You have to use adb to flash the boot.img, then boot into recovery and flash the ROM.
If you go into the Dev section, one of the first threads covers this and actually has a guide so you wouldn't have had to ask a question.

danny39 said:
You can just fastboot oem lock, the RUU will take care of restoring the original ROM.
EDIT: This is my 123 post
Click to expand...
Click to collapse
So even though I have a custom recovery (TWRP) I don't have to flash the stock recovery before I relock the bootloader?

plmiller0905 said:
So even though I have a custom recovery (TWRP) I don't have to flash the stock recovery before I relock the bootloader?
Click to expand...
Click to collapse
Here. You don't need the 1.85 RUU though. Just use 2.20 and skip the manual update from AT&T.
http://forum.xda-developers.com/showthread.php?t=1812039&highlight=2+20+unlock

Butters619 said:
If you want to go back to stock just fastboot oem lock then run the RUU. This is what I did. You can then re-unlock the bootloader and install SuperSU to reestablish root. It's pretty easy. Keep in mind, once you go to 2.20 you can not flash boot.img or radios from TWRP. You have to use adb to flash the boot.img, then boot into recovery and flash the ROM.
If you go into the Dev section, one of the first threads covers this and actually has a guide so you wouldn't have had to ask a question.
Click to expand...
Click to collapse
Butters619 said:
Here. You don't need the 1.85 RUU though. Just use 2.20 and skip the manual update from AT&T.
http://forum.xda-developers.com/showthread.php?t=1812039&highlight=2+20+unlock
Click to expand...
Click to collapse
Thanks...I really appreciate it

plmiller0905 said:
So even though I have a custom recovery (TWRP) I don't have to flash the stock recovery before I relock the bootloader?
Click to expand...
Click to collapse
No, it's the opposite: You can't RUU until you relock. It will fail if you try.

iElvis said:
No, it's the opposite: You can't RUU until you relock. It will fail if you try.
Click to expand...
Click to collapse
Oh ok...gotcha...so fastboot lock bootloader then run the ruu...great.
Like I mentioned before...I just got a little confused because people on YouTube is also flashing a stock recovery IMG before running the ruu.
Sent from my HTC One X using Tapatalk 2

plmiller0905 said:
So even though I have a custom recovery (TWRP) I don't have to flash the stock recovery before I relock the bootloader?
Click to expand...
Click to collapse
RUU will restore your recovery to the stock recovery.

Just keep in mind that once you lock your bootloader you won't be able to boot your phone until you run the RUU. So make sure you're ready to go with the RUU before you fastboot oem lock.

need help to back to stock

ok i need help,i install PA over stock rom on 2.2 firmare,before flashing i maked a nandroid backup,i wanted to sell the phone and wanted to back to stock rom,BUT im stuck at boot loop htc screen because while i flash Pa i flash a PA boot img so i cant boot now stock rom,what is to best advice to back to any rom,can i flash somehow flash boot image of stock rom and where can find that boot img,or something else i can do,when i get into twrp recovery i cant do factory reset its failed and i dont have gapps and PA rom on my sd card that files are no more on my sd card i dont know why,so i cant flash PA anymore,need any help asap

if you are selling it reboot into bootloader and run "fastboot oem lock" then run the 2.20 ruu

DvineLord said:
if you are selling it reboot into bootloader and run "fastboot oem lock" then run the 2.20 ruu
Click to expand...
Click to collapse
i will try thanks

vigorito said:
i will try thanks
Click to expand...
Click to collapse
i dont have in bootloader oem lock?

vigorito said:
i dont have in bootloader oem lock?
Click to expand...
Click to collapse
i run the ruu 2.2 (i didnt find the fastboot oem lock) and the ruu start updating the rom and sending about 5 mins and i get error 155 unknown error the rom update utillity cannot cupdate your anddorid phone please get the correct rom update utillity and try again,can i just go to recovery again and do a restore again of stock rom ( nandroid stock) and then just flash boot image from stock rom but i dont know where can find boot image from stock rom?

vigorito said:
i run the ruu 2.2 (i didnt find the fastboot oem lock) and the ruu start updating the rom and sending about 5 mins and i get error 155 unknown error the rom update utillity cannot cupdate your anddorid phone please get the correct rom update utillity and try again,can i just go to recovery again and do a restore again of stock rom ( nandroid stock) and then just flash boot image from stock rom but i dont know where can find boot image from stock rom?
Click to expand...
Click to collapse
Fastboot oem lock
Type into the fastboot cmd prompt while phone is in fastboot. Then run the ruu
Sent from my One X using xda app-developers app

Myrder said:
Fastboot oem lock
Type into the fastboot cmd prompt while phone is in fastboot. Then run the ruu
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
i did it in command promt i get bootloader lock succesfully
then bootloader tz htc svc disable ret and some numbers
and then failed (status read failed) too many links and in bootloader i see its relocked and some security warning
im running ruu now will se whats gonna happen

bro...i hit thanks!

I was actually wondering about the issue of having to flash the boot.img if restoring a TWRP backup. I assumed that it would have to be flashed via fastboot, since boot.img is obviously needed but can't be accessed by recovery on the 1.14 hboot. But haven't seen that discussed or confirmed here. Doesn't actually apply to my One X, since I'm on the old hboot. More just wondering academically.
Seems like the OP has taken the route of running the RUU. But if you ever need the boot.img for a stock ROM, many of the stock ROMs are posted in Development. So you can download the right one, and pull boot.img from it.

Yes you need to flash boot.img when restoring a backup on hboot 1.14.
Sent from my HTC One XL using xda app-developers app

Thanks for the tips guys, I also used this just now to unroot my phone and return it to bone-stock. I used the All-in-one tool to relock the bootloader and got the same error message that OP got, but after rebooting into the bootloader it said Re-Locked. Then downloaded HTC Sync and the 2.20 RUU and ran it. Took 15 minutes total and my phone looks stock, unless of course some busybody at AT&T decides to check the bootloader.
I am returning my One X and buying a One X + tomorrow morning.
EDIT: Oh and in case anyone is confused, you DO NOT need to flash boot.img in order to flash the 2.20 RUU.

i heard people say that they flashed the twrp boot backup in fastboot and it worked the same as flashing the boot from rom.zip in the ruu. i prefer the ruu method for going back to stock, just seems more official imo.

[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] RUU question

Going to RUU to 3.18 but I need to make sure of some things.
From what i've gathered since I'm S-Off I do not have to relock the bootloader. But since I'm running Vanilla Root-Box do I RUN the RUU while in fastboot or do I just run it while fully booted up or do I wipe everything in recovery then do it through fastboot?

c0d_fish said:
Going to RUU to 3.18 but I need to make sure of some things.
From what i've gathered since I'm S-Off I do not have to relock the bootloader. But since I'm running Vanilla Root-Box do I RUN the RUU while in fastboot or do I just run it while fully booted up or do I wipe everything in recovery then do it through fastboot?
Click to expand...
Click to collapse
run while in fastboot. nothing else is required.

exad said:
run while in fastboot. nothing else is required.
Click to expand...
Click to collapse
Thanks exactly what I needed to know

You will need to downgrade the TP firmware and reflash recovery afterwards.

GaBuzz said:
You will need to downgrade the TP firmware and reflash recovery afterwards.
Click to expand...
Click to collapse
Yeah I'm all set thanks, I just needed to know about the fastboot thing. Already finished doing everything.

You don't have to be in fastboot to run the RUU. As long as the screen of the phone is on, it doesn't matter what mode (bootloader, flastboot, fully booted), the RUU will run. This is by design, as the RUU is intended as a recovery tool.

Ruu never works for me unless I'm in fastboot.
I always get a random generic error.
Sent from my HTC One X using xda app-developers app

That's odd. I don't think I've ever had to go into fastboot to run the RUU.

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