Related
Hi,
Normally, I try to troubleshoot things myself without bothering others, but I'm in need of help this time. The tricky part is, I just bought this HTC One S from a stranger, so I don't have its complete history. With that said, here's what I need help with. The phone came with Pacman installed (v18.0.0). But, I would like to install this ROM: http://forum.xda-developers.com/showthread.php?t=2082451
It's basically a stock ICS ROM (the lite version mentioned with stuff removed). In attempt to do this myself, I found this post on here:
Yes the only other solution for you involves rooting. It is possible to go back to ICS by rooting your phone, going through a bootloader downgrade, hexediting a particular partition, then running an older compatible RUU... Its all possible, but requires some time to understand and do. And definately requires a few wipes of phone data in the mean time (which can be backed up through titanium and custom recoveries).
Only need to do that if you want to downgrade hboot. All you have to do is root and flash a rom, I have JB radio and hboot and run ICS Trickdroid 8.1.0.
So, I put the ICS ROM in the internal sdcard, did the usual wiping stuff (I've owned several HTC phones, so this part I know how), then installed the ROM. Unfortunately, it didn't work. When I rebooted the phone, it got stuck in boot loop. It would go to HTC logo screen with the development purpose only warning and just keep turning off and on. Fortunately, I was able to get back into recovery and restored it to Pacman. So, apparently, you can't just flash any ICS ROM over JB setup... Can someone help me figure out what I need to do to install that modified stock ROM please? I very much appreciate your help. My One S is S4 from T-Mobile.
Thank you,
GT
Did you flash boot.img?
Sent from my HTC VLE_U using xda app-developers app
thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.
dr_rick13 said:
thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.
Click to expand...
Click to collapse
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.
goldentequila said:
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.
Click to expand...
Click to collapse
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.
dr_rick13 said:
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.
Click to expand...
Click to collapse
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
If the Toolkit can't see your phone then you might need to install the drivers that come with it for it to work.
goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Ya 4EXT is coming soon.
dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Also try rebooting the computer if its still not working.
goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT
goldentequila said:
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT
Click to expand...
Click to collapse
oops, it was late last night when I wrote that.. my bad
Sent from my HTC One S using xda premium
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
we do not have S-OFF yet, so until we do.. people with hboots 1.13+ will need to flash boot.img. But HTC still hasn't said anything about when we will get S-OFF or if we will get it.
pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.
Darknites said:
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.
Click to expand...
Click to collapse
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.
Darknites said:
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.
Click to expand...
Click to collapse
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Yep very good app I did use it in till I downgraded.
help me, i have followed the instruction from htcdev.com to unlock my desire s bootloader with HBOOT 2.00.002.. after that i found my bootloader with text UNLOCKED but still it shows S-ON.
And then i continued to try root my desire s, i followed instructions that i found in this forum (thanks ) after finished, i tried to install some apps that need root access but i found that my desire s is not rooted (the apps said that).
The last things that i want to asked is, when i go to fastboot menu, i point to recovery mode and i found my desire with Revolutionary 4.0.1.4. I searched info about that things (revolutionary), i found many people said that if i have success install Revolutionary that means i have successfully rooted my device.
is there anybody could help and explained to me about those problems? i would very appreciate that
Revolutionary 4.0.1.4 is a custom recovery. Installing a custom recovery alone does NOT give you root access.
READ index thread in the forum and you'll have your answers
Thanks Bro ContactFront i will search in index thread
With the condition that i have now, is it possible if i want to return it back to default? I want to try update my desire to ICS using RUU Official uptade that i downloaded from htc website..
Sent from my Anvyn Desire S. Powered by XDA Developers
short answer is yes, you can go back to stock
Don't use the official ics Ruu, it's buggy and unfinished.
My pessimism extends to the point of even suspecting the sincerity of the pessimists.
—Jean Rostand
Alrighty then! Thanks All
But, do i need to root my device if i want to flash a custom rom? or all that i have done is enough to flash a custom rom? as i explained before, this is what i have done to my HTC Desire S :
HTC Desire S ( Gingerbread)
UNLOCKED using HTCDev
S-ON
HBOOT 2.00.0002
Installed Revolutionary 4.0.1.4
Sent from my Anvyn Desire S. Powered by XDA Developers
zidane_argun said:
Alrighty then! Thanks All
But, do i need to root my device if i want to flash a custom rom? or all that i have done is enough to flash a custom rom? as i explained before, this is what i have done to my HTC Desire S :
HTC Desire S ( Gingerbread)
UNLOCKED using HTCDev
S-ON
HBOOT 2.00.0002
Installed Revolutionary 4.0.1.4
Sent from my Anvyn Desire S. Powered by XDA Developers
Click to expand...
Click to collapse
seems like you still have not read the index.... You need root to flash a custom ROM(duh) since I am in a pretty good mood today so....
1.root your device
2 . Download your preferred ROM
3.flash your ROM
4.IMPORTANT!!!find your boot. img extracting it from the rom you downloaded
5.go to fastboot
6. connect your phone to computer
7.open CMD
8.cd to our directory(ensure you have adb and fastboot first)
9.
Code:
fastboot erase boot
10
Code:
fastboot boot boot. img
11.reboot and enjoy
Sent from my supercharged :tank:
1.root your device - not needed if he is going to flash a Custom. They are all rooted anyway. I think step 1 should be: flash a custom recovery
...
10
Code:
fastboot boot boot. img
- this will boot the kernel only, but after a restart of the device it will be gone. The command to use is :
Code:
fastboot flash boot boot.img
11.reboot and enjoy - that is all right
hisname said:
seems like you still have not read the index.... You need root to flash a custom ROM(duh) since I am in a pretty good mood today so....
1.root your device
2 . Download your preferred ROM
3.flash your ROM
4.IMPORTANT!!!find your boot. img extracting it from the rom you downloaded
5.go to fastboot
6. connect your phone to computer
7.open CMD
8.cd to our directory(ensure you have adb and fastboot first)
9.
Code:
fastboot erase boot
10
Code:
fastboot boot boot. img
11.reboot and enjoy
Sent from my supercharged :tank:
Click to expand...
Click to collapse
Thanks before
Now i have read the index, i found many tutorials to root my device there. i followed some.
but i have a problems when i want to root my device, i tried using SuperOneClick apps. I have done every single requirements of that tutorial.
The problem is i think my device is still not rooted. The first time i used SuperOneClick it shows finished & OK, then i reboot my device.
and then i tried to install some apps that needs rooted device, but those apps tell me that my device isn't rooted!
I tried to root my device using SuperOneClick again, but it always stuck in step #7 (Wait for Device).
any solutions for this problems?
Did i missed something to do?
amidabuddha said:
1.root your device - not needed if he is going to flash a Custom. They are all rooted anyway. I think step 1 should be: flash a custom recovery
...
10
Code:
fastboot boot boot. img
- this will boot the kernel only, but after a restart of the device it will be gone. The command to use is :
Code:
fastboot flash boot boot.img
11.reboot and enjoy - that is all right
Click to expand...
Click to collapse
he already has a custom recovery by revolutionary
Sent from my supercharged :tank:
edit: look here
http://forum.xda-developers.com/showthread.php?t=1525100
hisname said:
he already has a custom recovery by revolutionary
Click to expand...
Click to collapse
Well this is pretty outdated.
The attached is the latest 4EXT Recovery, touch edition.
Extract the recovery.img from the zip and flash:
Code:
fastboot flash recovery recovery.img
Then from the bootloader menu reboot to recovery and select backup/restore -> Backup. After the backup is done go back to the main menu, select wipe/format -> Wipe all partitions (except SDcard). When done select Install zip from the main menu and flash the ROM from your sdcard. After that reboot to bootloader from the Power menu and flash the boot.img as described in my previous post
amidabuddha said:
Well this is pretty outdated
Click to expand...
Click to collapse
true, but at least it is still usable till he gets 4ext or something later....
Sent from my supercharged :tank:
@zidane_argun
see my previous post
hisname said:
true, but at least it is still usable till he gets 4ext or something later....
Sent from my supercharged :tank:
Click to expand...
Click to collapse
amidabuddha said:
@zidane_argun
see my previous post
Click to expand...
Click to collapse
okay okay, roger that!
i will try that, thank you bro amidabuddha & hisname :good::good:
brb..
just realised that even my 4ext recovery is also outdated, thanks for the post :thumbup:
Sent from my supercharged :tank:
lol was trying to reply to your pm. don't know if they went through as they don't show up in my "sent item".
anyway you've got plenty of tips from the folks. so happy flashing
ContactFront said:
lol was trying to reply to your pm. don't know if they went through as they don't show up in my "sent item".
anyway you've got plenty of tips from the folks. so happy flashing
Click to expand...
Click to collapse
haha.. thanks to you too bro! now i'm trying to flash EXT4 first since they (the folks ) said that mine is pretty outdated.. LOL
after that, i want to search which rom is the best one for my Desire S.. do you have any idea which one is best ROM that i have to try?
Sent from my Anvyn Desire S. Powered by XDA Developers
zidane_argun said:
haha.. thanks to you too bro! now i'm trying to flash EXT4 first since they (the folks ) said that mine is pretty outdated.. LOL
after that, i want to search which rom is the best one for my Desire S.. do you have any idea which one is best ROM that i have to try?
Sent from my Anvyn Desire S. Powered by XDA Developers
Click to expand...
Click to collapse
there is really no "best" rom. it's all down to your personal preference.
say, I'm a big cm/aosp fan but if you are a sense fanboy then you may not like aosp based rom at all.
so if you see something interesting then just go ahead give it a try and decide for yourself.
---------- Post added at 09:37 AM ---------- Previous post was at 09:30 AM ----------
oh and speaking of 4ext recovery, i'd recommend installing either the free version updater or purchasing the full version from google play.
http://4ext.net/
it's absolutely worth it. one of the best recoverys you can have
Hello everyone,
I have used you guys in the past for other devices but never needed serious help, so here I am stuck in a looping hell
I have an HTC One X that I am trying to root and install the TWRP (I want to have an android that is factory set without the carrier info and bloatware ect)
The utility I am using is the HTC One X (Tegra 3/International) AIO Kit By Hasoon2000 v2.5. Here is my main issue:
I have successfully navigated all the steps to root the phone (Steps 1-5) and now when I boot into the bootloader I see the following,
***TAMPERED***
*** UNLOCKED ***
evita pvt ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
opendsp-v31.1.0.45.0815
emmc-boot
nov 26 2012,18:37:14:-1
Now from here it was my understanding that under "next, flash a recovery" I would simply pick "TWRP" and then click "flash recovery". This seems to work as the green bar in the top right loads briefly. After that I am at a loss. If I go to "bootloader" then go to "recovery" like the instructions say the phone just restarts and I see the Rogers splash screen again...
If it helps, when I try to flash the recovery using the "clockwordmod" it gives me an error "cannot load recoveries/cwm.img"
So to make this easier all I want is my phone to have nothing to do with the carrier on it, all traces of that wiped off at the single file level if possible.
Any help would be greatly appreciated as I have been at this for almost 6 hours straight
The phone is boot looping because you don't have a tegra3 international one x. You have the evita (one xl). Stop what your doing i will post you a link with correct software in a minute.
Read this and then try again.
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium
You're using the wrong toolkit, the Tegra 3/International is the Endeavor. You have the Evita, which is why it says Evita in your bootloader. You can flash TWRP 2.6 by following the below steps:
Download 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
Now you can enter recovery on your phone and flash a custom ROM. You've been looking in the wrong forum, that's how your ended up with the toolkit for the wrong device. So always stay in this forum (the one you've posted in), and only ever download ROMs from here for Sense based ROMs or here for aosp ROMs. Don't ever download from a different forum or a different site. That leads to bricked phones.
Oh, and next time, do some more reading before you attempt to alter your phone, you're lucky you didn't brick it. It pays to spend 12 hours reading before trying anything, rather than spending 6 hours trying to fix a mistake because you didn't have the necessary understanding of what you were doing in the first place.
Sent from my Evita
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
31ken31 said:
The phone is boot looping because you don't have a tegra3 international one x. You have the evita (one xl). Stop what your doing i will post you a link with correct software in a minute.
Read this and then try again.
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ninja!
Sent from my Evita
timmaaa said:
You're using the wrong toolkit, the Tegra 3/International is the Endeavor. You have the Evita, which is why it says Evita in your bootloader. You can flash TWRP 2.6 by following the below steps:
Download 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
Now you can enter recovery on your phone and flash a custom ROM. You've been looking in the wrong forum, that's how your ended up with the toolkit for the wrong device. So always stay in this forum (the one you've posted in), and only ever download ROMs from here for Sense based ROMs or here for aosp ROMs. Don't ever download from a different forum or a different site. That leads to bricked phones.
Oh, and next time, do some more reading before you attempt to alter your phone, you're lucky you didn't brick it. It pays to spend 12 hours reading before trying anything, rather than spending 6 hours trying to fix a mistake because you didn't have the necessary understanding of what you were doing in the first place.
Sent from my Evita
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
Ninja!
Sent from my Evita
Click to expand...
Click to collapse
you guys are amazing.... im going to try this now... I hope its not too late because I just noticed that I have no network connection to the provider and no signal I will update as soon as im done
WOW its working.... I cant believe its that easy lol....
On a side note I am in the screen that has install/wipe/backup ect.... so I am kinda lost on what to do from here. When I go to install it has a folder view of the internal phone. Is there something else I need to do to have it boot normally?
If you want to keep the stock ROM but have root, you'll need to download a superuser zip and flash that using the install menu in recovery. Wipe cache and dalvik cache afterwards.
Sent from my Evita
timmaaa said:
If you want to keep the stock ROM but have root, you'll need to download a superuser zip and flash that using the install menu in recovery. Wipe cache and dalvik cache afterwards.
Sent from my Evita
Click to expand...
Click to collapse
Do I need to download superuser.zip from somewhere special or does it matter?
As an update when I try to open up SuperSU it says "The SU binary needs to be updated. Continue?" I select continue and it gives me two choices, either "normal" or twrp/cwm"
I clicked twrp/cwm and it just restarts my phone to the recovery mode and I don't know where to go from there.
(I hate asking so many questions, is there a how-to for the recovery that I just installed? I am hunting around and cant find much)
UPDATE: I have successfully installed super user and everything is good to go, the only thing im still struggling with is the superuser.zip to set the phone to factory settings and get rid of all the providers bloatware/splashscreen ect
Ok, so you've already got a ROM on there with superuser? You can just try the normal method of updating instead of recovery method.
Sent from my Evita
inisings very
timmaaa said:
Ok, so you've already got a ROM on there with superuser? You can just try the normal method of updating instead of recovery method.
Sent from my Evita
Click to expand...
Click to collapse
I have the TWRP Recovery installed and also now have on my phone SuperSU installed, the only thing now is to figure out where I download a ROM to wipe out the cell providers bloatware and splash screens ect, I just want an "android" phone with nothing else on it lol
If you want to keep the stock ROM, you can use an app called Titanium Backup to remove bloatware. Or you can go to either of the development sections I listed before to find a ROM you think might suit you.
Sent from my Evita
timmaaa said:
If you want to keep the stock ROM, you can use an app called Titanium Backup to remove bloatware. Or you can go to either of the development sections I listed before to find a ROM you think might suit you.
Sent from my Evita
Click to expand...
Click to collapse
Yea I bought awhile ago titanium backup pro so I will use that for the bloatware, and as for the ROMS that you listed you mentioned Sense based ROMs or aosp ROMs... what is the difference? Is there one I should use over the other?
It really comes down to personal choice. Sense ROMs are what is installed on the phone when you buy it, they contain the HTC Sense UI.
Aosp ROMs are pure android, if you've ever seen a Nexus phone, that's essentially what it looks like. Aosp ROMs are generally a bit snappier.
There are some really good ROMs in both categories. The devs for our device do an outstanding job. I'm fond of both types of ROM. But, right now I'm using MagioRom, I've always disliked Sense ROMs but this one is Sense 5 and it looks a lot better than previous Sense versions, and is nice and smooth with great battery life.
Sent from my Evita
timmaaa said:
It really comes down to personal choice. Sense ROMs are what is installed on the phone when you buy it, they contain the HTC Sense UI.
Aosp ROMs are pure android, if you've ever seen a Nexus phone, that's essentially what it looks like. Aosp ROMs are generally a bit snappier.
There are some really good ROMs in both categories. The devs for our device do an outstanding job. I'm fond of both types of ROM. But, right now I'm using MagioRom, I've always disliked Sense ROMs but this one is Sense 5 and it looks a lot better than previous Sense versions, and is nice and smooth with great battery life.
Sent from my Evita
Click to expand...
Click to collapse
very interesting... I am a huge minimalistic fan... greys and whites are nice too... I appreciate all the help you have given me and I told my buddies who are jumping on the android bandwagon to come to this site...
is there anything special I need to do to install the ROMs? I assume there will be a guide in those links (at work cant view them yet)
jlambe7 said:
very interesting... I am a huge minimalistic fan... greys and whites are nice too... I appreciate all the help you have given me and I told my buddies who are jumping on the android bandwagon to come to this site...
is there anything special I need to do to install the ROMs? I assume there will be a guide in those links (at work cant view them yet)
Click to expand...
Click to collapse
If you like minimalistic, then aosp is probably the way to go for you. If your buddies are gonna get into modding their phones, I have some golden advice: read, read, read, and read some more before attempting anything. Modding is not hard if you know what you're doing, but it it's very easy to turn your phone into a paperweight if you rush in. Also, only ever get information and software from XDA, other sites don't properly distinguish between our model (HTC One XL/Evita) and the HTC One X (Endeavor).
In terms of installing, it's pretty simple:
1: Make a backup of your current setup using the backup function in recovery. That way if something goes wrong, you can restore it and have a working OS.
2: Perform a full wipe (cache/dalvik/factory reset/system).
3: Install the ROM using the install function. Aosp ROMs also require you to install a gapps package specific to the Android version of the ROM (4.1/4.2). Sense ROMs don't require this step.
4. You are s-on (security on) so you need to flash the boot.img for each ROM manually. Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita
I have an AT&T HTC One x. Its ***Tampered*** ***Unlocked*** HBOOT 1 .09. 0000 S-ON
I had been running an older version of TWRP, and decided I was going to clear my phone and do a fresh start. I know, I know, I should have made a backup, but I felt pretty confident in what I was doing, and was in too much of a hurry to rationalize this.
I wiped both the OS and previous version of TWRP in order to update to the new ones. While in fastboot I flashed CLEANrom and the new version of TWRP, and my administrative command prompt confirmed that they were installed successfully. Even cleared the cache afterwards. Now is the difficult part. I've researched, and researched, and cannot find a solution for this problem. I keep having a Boot Loop.... I'm stumped guys... I need some sort of help, be it technical, or something to drink lol
Previous ROM was CM 10, with TWRP and PA GAPPS :good:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
timmaaa said:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
Click to expand...
Click to collapse
I don't see anything in your FAQ that I haven't already tried unfortunately.....
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
It's the newest version of TWRP that is out, and yes, I flashed it via Fastboot, and it says successful on both the recovery install and ROM install.
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
1332858898
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.7. And yes, I have flashed about 4 Roms all succeeded according to fastboot and still getting the boot sequence.:good:
Yes I have extracted the boot.img
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
Click to expand...
Click to collapse
yes the boot.img file was extracted. I get a confirmation that it was successful when I flash it on fastboot
Exactly which ROMs have you tried to flash?
Sent from my Evita
timmaaa said:
Exactly which ROMs have you tried to flash?
Sent from my Evita
Click to expand...
Click to collapse
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
outcold32 said:
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
Click to expand...
Click to collapse
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
exad said:
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
Click to expand...
Click to collapse
If you would have read the thread, you would have noticed, that I am in bootloop, therefor I cannot access the recovery. And I have to have access to the ROM on my phone in order to flash anything via TWRP so this is moot. My question isn't how to flash roms, it's why am I getting a loop when I am successful on a clean partition and clean flash of both the recovery and ROM? And to me, fastboot is way easier than TWRP. I guess I could get a UART and try to debug the sequence myself, but I have more important things to do than that. I was posting to see if anyone had any similar problems. And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place. I ran the RUU after I re-locked the bootloader, and I'm at least out of the loop. I'm just going get to a more stable version so that this process will be more streamline when I re do my unlock and stuff.
So I guess the only solution at this point I have for any problem like this is to use the proper RUU. I tried a couple of times with no success, and it seemed the charm was to re lock the bootloader ( Fastboot oem lock) in order to properly and successfully get the RUU to work.:good:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
exad said:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
Click to expand...
Click to collapse
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Okie dokie. No point in arguing. You're right. I'm wrong. Glad it's all working now.
Sent from my One XL using xda app-developers app
outcold32 said:
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Click to expand...
Click to collapse
Exad is right in saying that the reason you're having problems is because you're attempting to flash ROMs with fastboot. That isn't how it's done. The correct way is to flash your ROM with recovery. You're barking up the wrong tree, not only that but you're arguing with experienced people who are only attempting to help get you out of the mess that you've gotten yourself into. You came here for advice, but there's no point in asking for advice if you're just going to argue and dismiss what you're being told to do.
You said you can't access your ROM so you can't flash anything, that makes absolutely no sense, which leads me to believe you don't really know what you're doing. Get out of the mindset that you need to use fastboot, it's wrong. You're dealing with people who have extensive and intimate knowledge of this device, trust us, we know what we're talking about.
Exactly why can't you access recovery? If you can issue fastboot commands that means you can access your bootloader, if you can access your bootloader that means you can use your volume keys to scroll through the options and the power button to select recovery. What happens when you do that? Exactly which recovery have you flashed to your device? I need to the full filename of the recovery that you've flashed.
Sent from my Evita
outcold32 said:
And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place.
Click to expand...
Click to collapse
S-on is a downright dangerous place to be, if the phone is also SuperCID (which is very likely, since its the AT&T variant). exad is right in recommending s-ff, as he is about a good many things.
I have a one xl cid rogers001 hboot 2.14, baseband 0.23a.3 2.09.29.... jb 4.1 with sense 4+
I tried unlock bootloader by htcdev => ok
install recovery => ok. and when i installed this rom: http://forum.xda-developers.com/showthread.php?t=1868236, it was stuck in bootloader. i fogot root my phone before.
so i relock my device, and tried to flash this stock rom using adb : OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip (was found in this thread: http://forum.xda-developers.com/showthread.php?t=2119610)
On cmd via fastboot i type fastboot erase cache =>ok
fastboot oem rebootRUU => ok
fastboot flash zip "filename.zip" It says " (remote: 12 signature verify fail") in the end cmd
What should i do now?
Thanks for reading and help me pls!!!!
Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita
timmaaa said:
Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita
Click to expand...
Click to collapse
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!
somebody help me pls
veveve said:
somebody help me pls
Click to expand...
Click to collapse
Please be patient, we all have lives outside XDA.
veveve said:
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!
Click to expand...
Click to collapse
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita
timmaaa said:
Please be patient, we all have lives outside XDA.
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita
Click to expand...
Click to collapse
yes, i did it more than once, now it's fixed, but when i mount it to Windows using TWRP, nothing happen, so i can't format it. and the same things when i tried to sideload. But in fastboot mode, it usual.
and i flashed the newest rom in this thread: http://forum.xda-developers.com/showthread.php?t=1868236 ViperXL 4.2 and i didn't check the MD5
back to my previous question, can i fash a custom rom without root?
I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita
Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.
nem1yan said:
Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.
Click to expand...
Click to collapse
I disagree. I think it's a better idea for him to get his head around the simple operations like flashing ROMs before attempting s-off.
Sent from my Evita
timmaaa said:
I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita
Click to expand...
Click to collapse
Full ROM:
Jelly Bean - Android 4.2.2 / Sense 5
ViperXL 4.2.0
Main Link: http://www.androidfilehost.com/?fid=23134718111254927
Mirror 1: http://goo.im/devs/Turge/ViperXL/ViperXL_4.2.0.zip
Mirror 2: http://d-h.st/z4Q
Click to expand...
Click to collapse
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/showthread.php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Thanks!
I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita
timmaaa said:
I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita
Click to expand...
Click to collapse
it is ViperXL_4.2.0.zip
i'll do it next time!
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
veveve said:
it is ViperXL_4.2.0.zip
i'll do it next time!
Click to expand...
Click to collapse
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
You might be onto something.
Sent from my Evita
timmaaa said:
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
You might be onto something.
Sent from my Evita
Click to expand...
Click to collapse
I mean, i didn't do it and i will do it next time
bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
thanks, i will try.
Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita
timmaaa said:
Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita
Click to expand...
Click to collapse
but i still have trouble with mounting internal storage using TWRP on windows, should i try the older TWRP?
What version do you have installed?
Sent from my Evita
timmaaa said:
What version do you have installed?
Sent from my Evita
Click to expand...
Click to collapse
here
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/show....php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Click to expand...
Click to collapse