I want to install "[ROM][AROMA] KickDroidXL v5.2.0" but my htc one x (at&t) is completely stock.
So: step 1: unlocked with htcdev.com
step 2: Custom recovery
step 3: Firmware
Based on the "you need" info
Step 4: flash rom.
(I think i will s-off as well my mobile)
My questions are:
1) Is there any problem if i keep stock recovery?
2) On firmware instructions that is given here: "http://forum.xda-developers.com/showthread.php?t=2485865" 4th post
how should i do this throught commands (i use windows) or through my phone's screen when it is powered up by volume down and power buttons??
thanks a lot!
ps.christos said:
I want to install "[ROM][AROMA] KickDroidXL v5.2.0" but my htc one x (at&t) is completely stock.
So: step 1: unlocked with htcdev.com
step 2: Custom recovery
step 3: Firmware
Based on the "you need" info
Step 4: flash rom.
(I think i will s-off as well my mobile)
My questions are:
1) Is there any problem if i keep stock recovery?
2) On firmware instructions that is given here: "http://forum.xda-developers.com/showthread.php?t=2485865" 4th post
how should i do this throught commands (i use windows) or through my phone's screen when it is powered up by volume down and power buttons??
thanks a lot!
Click to expand...
Click to collapse
Here are your steps:
Before I can give any advice on the steps you need to take I need to see your bootloader details, the first five lines will do. I can answer your questions though.
1. You can't keep the stock recovery, a custom recovery is required on a modified phone.
2. The commands are issued through a command prompt on a Windows PC (you need to have adb/fastboot installed on the PC).
Sent from my Evita
timmaaa said:
Here are your steps:
Before I can give any advice on the steps you need to take I need to see your bootloader details, the first five lines will do. I can answer your questions though.
1. You can't keep the stock recovery, a custom recovery is required on a modified phone.
2. The commands are issued through a command prompt on a Windows PC (you need to have adb/fastboot installed on the PC).
Sent from my Evita
Click to expand...
Click to collapse
There are some changes of the planes and because of lack "playing" with my mobile i haven't reply you. So i desided to go for CyanogenMod 11.0 so instractions are:
" 1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU or later.
3.Flash a custom recovery (TWRP/CWM with SELinux capabilities).
4.Download latest nightly from http://download.cyanogenmod.org/?device=evita.
5.Locate 4.4 Gapps via a quick Google search.
6.Wipe factory/data reset in recovery before installing CM11.0 (unless you are already on a CM11.0 build).
7.Reboot into recovery and install nightly and gapps."
Before the instraction i think i should root and unlock the bootloader, so i used "[TOOL] HTC One X (Evita) All-In-One Toolkit V3.0.1 [7-7-2013] [PERM ROOT][Noob-Proof]" to unlock bootloader and root the phone. I have done this. I will (haven't do it yet) s-off and then flash custom recovery. Then it is the easy part i thing, (same as in every device, i have done it to htc desire).
So my question is am i rooted? Some apps like titanium backup and adfree gives me error, that is why i am thinging or i am not rooted or i have to "gain" su access through terminal. For flashing custome recovery i will use "[TOOL] HTC One X (Evita) All-In-One Toolkit V3.0.1 [7-7-2013] [PERM ROOT][Noob-Proof]" and for s-off i will try to use this guide "[S-Off] Facepalm S-Off for HTC One XL" any easier suggestions about s-off??
So to make our life easier here is what i get form power button + volume down:
*** UNLOCKED ***
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
Forget about using the toolkit, all it does is act as a crutch and it clearly hasn't succeeded in rooting your device. Plus, it removes some vital learning experience which you definitely need.
You don't need root yet if you're going to flash a custom ROM. All that's required to install a custom recovery is an unlocked bootloader which you already have. The custom ROMs you want to install are pre-rooted.
To install a recovery is very simple, all it takes is a few fastboot commands. Download the modified version of TWRP 2.6.3.0 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
Once you've done this all you need to do is find a ROM and gapps and install them. Take a look at the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain some very valuable information that you'll need.
Sent from my Evita
timmaaa said:
Forget about using the toolkit, all it does is act as a crutch and it clearly hasn't succeeded in rooting your device. Plus, it removes some vital learning experience which you definitely need.
You don't need root yet if you're going to flash a custom ROM. All that's required to install a custom recovery is an unlocked bootloader which you already have. The custom ROMs you want to install are pre-rooted.
To install a recovery is very simple, all it takes is a few fastboot commands. Download the modified version of TWRP 2.6.3.0 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
Once you've done this all you need to do is find a ROM and gapps and install them. Take a look at the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain some very valuable information that you'll need.
Sent from my Evita
Click to expand...
Click to collapse
I found what i did wrong so now i have root my mobile! The guide that you posted is very helpfull, thanks for that! One last question though (hopefully last) i still have to go s-off for flashing CyanogenMod 11.0 since it is in the installation procedure right?? Thanks again.
You do need s-off, because you need to run the 3.18 RUU in order to flash any current aosp ROM. You must have s-off before you run the RUU or you'll brick.
Sent from my Evita
timmaaa said:
You do need s-off, because you need to run the 3.18 RUU in order to flash any current aosp ROM. You must have s-off before you run the RUU or you'll brick.
Sent from my Evita
Click to expand...
Click to collapse
I have done everything exept s-off. So now what i get in the "info" screen is what i had before, but at the begging it says *** TAMPERED *** , root works as well. The thing is i tried s-off using this method "http://forum.xda-developers.com/showthread.php?t=2155071" and i had exactly what it says i mean both in screens and the 92 error, but i always was s-on when system boot to bootloader at the end. I tried more times and after a point i tried the toolkit, from that point error 92 turned to error 99 (unkown error). Now this holds for both ways that i try. Any ideas what i do wrong? By the way i made a backup before starting the whole procedure. Thanks again and sorry for asking, but everything else was solven by reading and i can not reach as many info about s-off as it was for root.
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
timmaaa said:
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just show the so wanted s-off. I read somewhere that error 99 will turn to "normal error 92" after rebooting. So yesterday i did 3 reboots and felt to sleep and today i tried the same procedure and now i am s-off! Sorry for the nagging!!
timmaaa said:
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok i need your help again, if it is possible. I try to flash cm11 rom and i got the:
"E:error executing updater binary in zip ..........
E: error installing the zip file ......."
So i did my research and i thing the problem is due to recovery, right??
In this threat "[Q&A][CM 10.1][4.2.2] CyanogenMod 10.1 Questions and Help thread"
you have said: " Originally Posted by timmaaa View Post
No you can't use TWRP 2.6, you need to use the unofficial modified version of TWRP 2.6.3.0 from our Original Android Development section."
The thing is i am using TWRP 2.6.3.0 downloaded from here: "http://forum.xda-developers.com/showthread.php?t=1677447" should i go for "http://forum.xda-developers.com/showthread.php?t=2558503"??????
some more details (bootloader details):
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
e-MMC-boot
Thank you very much.
Well, only one of those links contains the unofficial modified TWRP 2.6.3.0 which is 4.4 compatible, so the answer should be simple.
Sent from my Evita
timmaaa said:
Well, only one of those links contains the unofficial modified TWRP 2.6.3.0 which is 4.4 compatible, so the answer should be simple.
Sent from my Evita
Click to expand...
Click to collapse
Do you know if there might be a problem with compatibility?? I mean if i try to restore back up made with TWRP 2.5 when i have the unofficial modified TWRP 2.6.3.0??i bet there is a backwords compatibility, right?
thanks again!
From all reports I've seen, they're not compatible. But even if you didn't want to flash KitKat ROMs you should never use TWRP 2.5 because it's super buggy and will cause issues. I'd say just flash the unofficial TWRP 2.6.3.0 and install the KitKat ROM of your choice. If you need to go back to stock there are other ways apart from a backup you can do it.
Sent from my Evita
Related
Ok so i needed to root after i updated to official ICS with the setup.
What i noticed i cant root with any known rooting method so i tried pushing root with recovery.
It turns out i have stock recovery and everytime i try installing zip it says signature verification failed.
So i found that i need flash custom recovery for that.
But i have found that flashing .img of recovery using CMD is not working.
So any ideas? I would really be thankfull i am trying for whole day and no succes.
You already asked the basic same question in this thread and Jack_R1 told you that you need to read and understand more. He is far more knowledgeable than I am, and I agree with him 100%
This has been answered countless times, so I am not going to ive you the answers again - go and search.
As pointers;-
1) Install ADB
2) Fastboot
3) Push Recovery
4) Flash Root
Now - go and read, understand and make sense of what, why and how.
SimonTS said:
You already asked the basic same question in this thread and Jack_R1 told you that you need to read and understand more. He is far more knowledgeable than I am, and I agree with him 100%
This has been answered countless times, so I am not going to ive you the answers again - go and search.
As pointers;-
1) Install ADB
2) Fastboot
3) Push Recovery
4) Flash Root
Now - go and read, understand and make sense of what, why and how.
Click to expand...
Click to collapse
I do read i do understand what to do, i read instructions, i fallow instructions but it just doesnt work for reasons usually and mostly not covered in the instructions...... So can you atleast try to help like for example give me link to set of instructions you know that works couse you used it or something similiar. Couse silencing me like saying go read is just not true, couse i am reasonably knowledgeble and i do read and usually do understand what i read it just doesnt work for some reason.
EXAMPLE:
one of methods to flash custom recovery i tried is this
http://forum.xda-developers.com/showthread.php?t=1484753
Download the zip file attached and extract it anywhere .
Your phone needs to be in debugging mode and you need the lastest usb drivers instaled . ( HTC Sync )
Step 1 : Run Start Here.bat , a comand promt window will open.
Step 2 : Type in "adb reboot bootloader" . <This works on every rom , it will reboot in fastboot mod.>
Step 3 : After the phone rebooted in fastboot , type in "fastboot flash recovery recovery-clockwork-touch-5.8.1.5-saga.img" .
Step 4 : You have your Touch Recovery flashed.
After doing so it just says:
unknown partition 'recovery recovery-clockwork-touch-5.8.1.5-saga.img'
error: cannot determine image filename for 'recovery recovery-clockwork-touch-5.8.1.5-saga.img'
SO you say i dont read but it just doesnt work for some reason.
OK ...
Firstly - don't use CWM. That isn't just my opinion, it is a general opinion round here the 4EXT is far superior, especially on the DS. Try this thread
Secondly, can you please confirm what hBoot you are running?
Thirdly, is the phone correctly booting into FastBoot mode?
Fourthly, did you install ADB correctly (I guess so)?
Maybe this problem is caused by a bootloader that is still locked ?!
(Can recovery be flashed if the bootloader is locked ? I am not sure, but don't think so.)
Did you unlock via www.htcdev.com ?
SimonTS said:
OK ...
Firstly - don't use CWM. That isn't just my opinion, it is a general opinion round here the 4EXT is far superior, especially on the DS. Try this thread
Secondly, can you please confirm what hBoot you are running?
Thirdly, is the phone correctly booting into FastBoot mode?
Fourthly, did you install ADB correctly (I guess so)?
Click to expand...
Click to collapse
OK so i as soon as you started helping me (thanks by the way) i found a couse for my error while flashing custom recovery. And i was able to flash 4EXT as you suggested (it looks awesome (not to mention all cool features ))
Second thingy i need to sort out is how to get my phone rooted
So i now have working recovery and i need myself a zip file to push it using recovery so i gain root.
Tried it and failed so i installed Tweaked 7,1 kernel (kernels already had root when i was using SEx10)
now all my phone does on turning it on is going to 4ext recovery on boot.
TeddyOFLove said:
OK so i as soon as you started helping me (thanks by the way) i found a couse for my error while flashing custom recovery. And i was able to flash 4EXT as you suggested (it looks awesome (not to mention all cool features ))
Second thingy i need to sort out is how to get my phone rooted
So i now have working recovery and i need myself a zip file to push it using recovery so i gain root.
Tried it and failed so i installed Tweaked 7,1 kernel (kernels already had root when i was using SEx10)
now all my phone does on turning it on is going to 4ext recovery on boot.
Click to expand...
Click to collapse
OK. You're at first base with 4EXT Recovery. That is normally the worst bit.
What hBoot are you running?
SimonTS said:
OK. You're at first base with 4EXT Recovery. That is normally the worst bit.
What hBoot are you running?
Click to expand...
Click to collapse
My data on white screen of death sais
***UNLOCKED***
SAGA PVT SHIP S-OFF RL
HBOOT-2.02.0002
TeddyOFLove said:
My data on white screen of death sais
***UNLOCKED***
SAGA PVT SHIP S-OFF RL
HBOOT-2.02.0002
Click to expand...
Click to collapse
Now follow this thread.
TeddyOFLove said:
My data on white screen of death sais
***UNLOCKED***
SAGA PVT SHIP S-OFF RL
HBOOT-2.02.0002
Click to expand...
Click to collapse
On DS there is absolutely no way a kernel to give you root. None of the existing zip files (mine or any others in DS section). You have to flash SU and install busybox (there are apps in the Google Play) after that
Sent from my HTC Desire S
SimonTS said:
Now follow this thread.
Click to expand...
Click to collapse
And what should i do if links on thread are dead at least link for PG88IMG.zip is dead
Can't root and s-off Desire HD
Good morning,
yesterday I start trying mod my HTC Desire HD but unfortunately I have not resolved yet.
I unlocked bootloader with instruction from HTC (I can see unlock when I started bootloader).
In same way after a lot of tentative I installed CWM and it seems installed so when I go in "recovery" I can see menĂ¹ that should let me install custom ROM.
My mystake is that I have not root and S-Off and after installed "Sabsa Prime v5" now my HTC stuck on first screen.
I tried procedure "ace-hack" to downgrade and then have s-off but
fastboot work, ADB doesn't : ADB doesn't list my devices
Pleae help me to recovery a working rom on my device
Thank you
xferdyx said:
Good morning,
yesterday I start trying mod my HTC Desire HD but unfortunately I have not resolved yet.
I unlocked bootloader with instruction from HTC (I can see unlock when I started bootloader).
In same way after a lot of tentative I installed CWM and it seems installed so when I go in "recovery" I can see menĂ¹ that should let me install custom ROM.
My mystake is that I have not root and S-Off and after installed "Sabsa Prime v5" now my HTC stuck on first screen.
I tried procedure "ace-hack" to downgrade and then have s-off but
fastboot work, ADB doesn't : ADB doesn't list my devices
Pleae help me to recovery a working rom on my device
Thank you
Click to expand...
Click to collapse
I'll give you a couple of pieces of advice mate;-
1) Don't simply add your problem on to the bottom of another thread unless it is DIRECTLY related to the OP in the thread
2) This is the Desire S forum. The Desire HD forums are here.
Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S
tookie69 said:
Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S
Click to expand...
Click to collapse
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2
Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.
OK i have unlocked again and re pushed recovery TWRP 2.4.1.0
But I still cant boot into the recovery option..
PLease tell me what im doing wrong..
iElvis said:
Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.
Click to expand...
Click to collapse
I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Kole_Ackerson said:
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
tookie69 said:
I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Click to expand...
Click to collapse
I believe through adv but is way simpler to do it through recovery. Try a earlier version of twrp
Sent from my HTC One X using Tapatalk 2
did you verify you are unlocked now, or did you just assume since you pushed the token again?
Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?
I pushed the same token and rebooted the device at the top its now says unlocked
DvineLord said:
did you verify you are unlocked now, or did you just assume since you pushed the token again?
Click to expand...
Click to collapse
make sure to run "fastboot erase cache" after changing recovery
IM pretty sure.. I also tried and older TWRP still same issue would you happen to have a link ? I have been using the all in one for HTC one X Tool
iElvis said:
Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?
Click to expand...
Click to collapse
bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita
ok i loaded that last night before i went to bed I went this morning to look at the phone and now it just goes to a black screen no madder what I do i put it in the computer the computer goes beep now when its plugged in my computer only the red light at the top flashes and then it disconnects from my computer because i can here the beep of adding and removing hard ware.
is my phone now bricked ?
DvineLord said:
bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita
Click to expand...
Click to collapse
Just relock and boot into boot loader the tampered screen then run a ruu am you should be back to stock
Although I had a EVO before that I flashed the wroung bootloader an bricked it an it wouldn't go anywhere but the bootloader
Sent from my HTC One X using xda premium
If I were you I'd reinstall drivers and manually push the recovery via adb. Use this command- fastboot flash recovery (filename).img
Sent from my HTC One X using Tapatalk 2
Thanks
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one
Rom installation fails on Rogers HTC One X, S-ON, EVITA, HBOOT 2.14.0000
tookie69 said:
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one
Click to expand...
Click to collapse
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.
iccrcmember said:
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.
Click to expand...
Click to collapse
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.
I'll just clarify that when Redpoint said you need to update TWRP you should update it to TWRP 2.6, your current version (2.5) is very buggy. Also, he means since you are s-on you need to flash the boot.img, when you get s-off this will no longer be required.
Sent from my Evita
Thank you redpoint73
redpoint73 said:
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.
Click to expand...
Click to collapse
I made an error. my bootloader was already unlocked. Any how flashing the boot.img of the Rom before installing the Rom worked. Thank you for your insight. My phone is up and running.
For others: below is the rom i flashed:
[ROM] 10/10 Team Venom ViperX 4.0.4 - Sense 5 JellyBean | orig. OTA | Tweaks
http://forum.xda-developers.com/showthread.php?t=2087443
Hi all I need help!!!
My HTC OneXL is unlocked bootloader
Android Version ICS
I dont know which firmware I am running (Rogers One X)
PVT SHIP S-ON RL
HBOOT 1.09
I installed TWRP successfully but I can not install roms!
Please help!
bobyum said:
Hi all I need help!!!
My HTC OneXL is unlocked bootloader
Android Version ICS
I dont know which firmware I am running (Rogers One X)
PVT SHIP S-ON RL
HBOOT 1.09
I installed TWRP successfully but I can not install roms!
Please help!
Click to expand...
Click to collapse
you have to flash the boot.img of a rom if you are s-on
must also be rooted.
1. plug phone into pc
2. mount sdcard in twrp
3. copy rom to your computer
4. extract boot.img
5. reboot to bootloader (also done in twrp)
6. highlight "fastboot" and press power and the phone should say "Fastboot USB"
7. open a command promt (type cmd into search box on windows7) and cd to your adb/fastboot folder
8. type
Code:
fastboot flash boot boot.img
9. reboot to recovery and install your rom
10. reboot system when done
if you arent rooted, use the toolkit in the development area and root.
What ROM are you trying to install? If it's any recent aosp your current hboot version is the problem. All current aosp ROMs require the 2.14 hboot which you can get by running the 3.18 RUU. S-off is highly recommended, if you run a jb RUU with SuperCID and s-on your phone will brick.
Sent from my Evita
I am trying to get cm10.2. so should my first step right now be getting the 3.18 RUU or getting s-off?
Ok, first, please read the instructions of any ROM you're going to flash, it's stated very clearly in the cm10.2 thread that an update is needed before flashing the ROM. One of the most important rules of XDA is to search before posting, proper searching limits the amount of unnecessary threads.
Get s-off first, if you don't already have SuperCID you will need that in order to get s-off. Use the hex edit method to get SuperCID, then you can get s-off in the Facepalm S-off thread. Your best bet to go through this process is to temporarily flash a Sense ROM, any Sense 4 Android 4.1 ROM should be fine. Once all that's done you can run the 3.18 RUU, then flash TWRP recovery again and flash CM.
Sent from my Evita
S Off dude. Read what @timmaaa said.
Sent from my One X using XDA Premium 4 mobile app
thanks timmaaa!!! I need to head out right now but will try it asap! I apologize for not searching before asking but my phone was stuck on ICS and I thought it would be hopeless to install a custom rom.
got super cid and soff!
ok i got both super cid and soff. so my next step is to flash a sense 4.1 rom correct? any suggestions?
edit: i downloaded RageXL so do i just flash in twrp?
No you don't need to do that, I meant you should try a 4.1 ROM in order to get s-off. If you have SuperCID and s-off now you can go ahead and run the RUU.
Sent from my Evita
bobyum said:
I apologize for not searching before asking but my phone was stuck on ICS and I thought it would be hopeless to install a custom rom.
Click to expand...
Click to collapse
Not sure how you got that notion. Its actually a bit easier to mod older firmware versions, due to the fact that HTC keeps plugging the various exploits with successive (newer) firmware builds.
There is currently no firmware version for this device that would leave you "stuck" not being able to flash custom ROMs.
Hi,
I'd like to ask for your help. After an update to Android 4.2.2 and Sense 5.0 on my HTC ONE SV I'd really like to go back to the previous version, I know a lot of people are happy about the update, but I'd really like to go back to the older menus, look etc. I don't mind losing the data.
I'm new over here ... so please bare with me
What info should I provide?
Nina
I can't help you at the moment because I have to get ready for work but for starters you will need to unlock your device, acquire the proper ruu (4.1.2), or if its available on here then a nandroid backup (4.1.2) specific to your device. Then at this point the procedures to take would be based on whether you are S-On or S-off.
Hopefully someone else may chime in on this while I am at work.
Sent from my C525c using XDA Premium 4 mobile app
We need to know, what version of one sv you have (k2u, k2ul, or other).
And if you are S-off, which hboot...
To unlock your device or in simple terms the bootloader you will need to head over to HTCDEV.com and follow their instructions. If you wish to be S-Off you will need to get rumrunner for your phone and follow its instructions - otherwise you may remain S-On.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 07:38 AM ---------- Previous post was at 07:36 AM ----------
old.splatterhand said:
We need to know, what version of one sv you have (k2u, k2ul, or other).
And if you are S-off, which hboot...
Click to expand...
Click to collapse
Sounds like she is legit stock on everything lol. So this may in a sense be easy assuming instructions can be followed
Sent from my C525c using XDA Premium 4 mobile app
Thanks to both of you.
My version is:
K2_UL PVT SHIP S-on RL
HBOOT-2.00.0000
ninamalina said:
Thanks to both of you.
My version is:
K2_UL PVT SHIP S-on RL
HBOOT-2.00.0000
Click to expand...
Click to collapse
Then its quiet easy:
unlock your device at htcdev.com (follow the instruction on that side.
Then you need to flash a custom recovery (i recommend TWRP 2.6.3) with fastboot, and next you flash a 4.1.2 rom with recovery. Now you need to flash the boot.img that was inside your rom zip with fastboot and you are ready to go
All links you need, you will find in my index thread (look at my signature for it).
To flash a custom recovery with fastboot you will need to insure your custom recovery image file is located in the same folder as your fastboot file to keep this next part simple.
Go into your HBoot then select fastboot. Connect device to your pc and in the command window type:
Code:
fastboot devices
This should show that your device is connected. If you see nothing then you will need to resolve that before proceeding. Next , once connection is established type:
Code:
fastboot boot customrecovery.img
You are booting instead of flashing the custom recovery so your stock recovery will be persevered. Each time you reboot your device you will need to follow those steps again to access the custom recovery vice your stock recovery.
If you wish to flash it then:
Code:
fastboot flash recovery customrecovery.img
I don't recommend you flashing it yet unless you get a copy of your stock recovery first.
Sent from my C525c using XDA Premium 4 mobile app
old.splatterhand said:
Then its quiet easy:
unlock your device at htcdev.com (follow the instruction on that side.
Then you need to flash a custom recovery (i recommend TWRP 2.6.3) with fastboot, and next you flash a 4.1.2 rom with recovery. Now you need to flash the boot.img that was inside your rom zip with fastboot and you are ready to go
All links you need, you will find in my index thread (look at my signature for it).
Click to expand...
Click to collapse
Great, thanks!
I'll do everything when i come home
Modding.MyMind said:
To flash a custom recovery with fastboot you will need to insure your custom recovery image file is located in the same folder as your fastboot file to keep this next part simple.
Go into your HBoot then select fastboot. Connect device to your pc and in the command window type:
Code:
fastboot devices
This should show that your device is connected. If you see nothing then you will need to resolve that before proceeding. Next , once connection is established type:
Code:
fastboot boot customrecovery.img
You are booting instead of flashing the custom recovery so your stock recovery will be persevered. Each time you reboot your device you will need to follow those steps again to access the custom recovery vice your stock recovery.
If you wish to flash it then:
Code:
fastboot flash recovery customrecovery.img
I don't recommend you flashing it yet unless you get a copy of your stock recovery first.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, will follow your advice!
Although instructions are clear, I still have problems
I've tried using different computer, turned my av off, but still get this when i try to run the downloaded file from HTCdev.com:
This aplication has failed to start because AdbWinApi.dll was not found.
You are missing files.
You can get them from here: http://rom.android-host.de/DESIRE_C/tools/Android.zip
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