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.
Hey guys,
I'm still on the second snapshot build of 10.1 for the ville, but I'm getting kind of annoyed by the battery life, so I decided to move on to a nightly.
I read in the official nightlies thread that the 7/11 build was one of the most stable and battery friendly builds, so I'll just assume that. I can't, however, find a single source that documents all the steps so I'll just ask it here. Please tell me if I'm missing something, I don't like uncertainties with these things.
As far as I could see, this is what I need to do:
Optional: Gain S-off (not necessary but handy for the rest of this process I think) via Facepalm or so
Update my phone's firmware by these instructions http://forum.xda-developers.com/showthread.php?t=2322755
...including installing TWRP etc.
Wipe my caches (if I didn't already have to wipe everything in the previous step)
Flash the ROM and gapps
Could anyone please confirm this and tell me any things I should pay attention to? As of late, all the things like firmwares, kernels and radios make it a bit more difficult for me to grasp.
Thanks it advance, I hope I'm not the thousandth person asking this. I did look through the threads, you know ^^
P.S. Some interesting things, might you ask: I have S-ON, my HBOOT version is 2.15. If anything else isn't clear, let me know.
ThomasHunter said:
Hey guys,
I'm still on the second snapshot build of 10.1 for the ville, but I'm getting kind of annoyed by the battery life, so I decided to move on to a nightly.
I read in the official nightlies thread that the 7/11 build was one of the most stable and battery friendly builds, so I'll just assume that. I can't, however, find a single source that documents all the steps so I'll just ask it here. Please tell me if I'm missing something, I don't like uncertainties with these things.
As far as I could see, this is what I need to do:
Optional: Gain S-off (not necessary but handy for the rest of this process I think) via Facepalm or so
Update my phone's firmware by these instructions http://forum.xda-developers.com/showthread.php?t=2322755
...including installing TWRP etc.
Wipe my caches (if I didn't already have to wipe everything in the previous step)
Flash the ROM and gapps
Could anyone please confirm this and tell me any things I should pay attention to? As of late, all the things like firmwares, kernels and radios make it a bit more difficult for me to grasp.
Thanks it advance, I hope I'm not the thousandth person asking this. I did look through the threads, you know ^^
P.S. Some interesting things, might you ask: I have S-ON, my HBOOT version is 2.15. If anything else isn't clear, let me know.
Click to expand...
Click to collapse
if you are on hboot 2.15 it seems that you have already updated your firmware.
so you only have to install twrp,wipe system/data/cache 2-3x, flash the rom, flash the boot.img, flash gapps and you should be fine.
i'm on 7/13 nightly and it runs fine so far, no fc reboots and acceptable battery life.
NQNH said:
if you are on hboot 2.15 it seems that you have already updated your firmware.
so you only have to install twrp,wipe system/data/cache 2-3x, flash the rom, flash the boot.img, flash gapps and you should be fine.
i'm on 7/13 nightly and it runs fine so far, no fc reboots and acceptable battery life.
Click to expand...
Click to collapse
Hey, wow, now that you say it... That's kind of weird, I've been off stock for months now so I thought my firmware wouldn't auto update... But you're right. I thought I misquoted my notes in the OP but I just double checked, and I really have 2.15.
Well, thanks for noticing, and for your answer. I think I'll flash it soon then, now that the process is simplified!
By the way, do I have to flash boot.img via fastboot, or can I also do that from within TWRP? Can't seem to recall how I did that the previous time..
ThomasHunter said:
Hey, wow, now that you say it... That's kind of weird, I've been off stock for months now so I thought my firmware wouldn't auto update... But you're right. I thought I misquoted my notes in the OP but I just double checked, and I really have 2.15.
Well, thanks for noticing, and for your answer. I think I'll flash it soon then, now that the process is simplified!
By the way, do I have to flash boot.img via fastboot, or can I also do that from within TWRP? Can't seem to recall how I did that the previous time..
Click to expand...
Click to collapse
if you are on s-on flash the boot.img via fastboot.
if you are no s-off you dont have to do this step.
NQNH said:
if you are on s-on flash the boot.img via fastboot.
if you are no s-off you dont have to do this step.
Click to expand...
Click to collapse
Yeah, I'm S-On. Was just wondering if I could also flash boot.img via recovery, instead of via fastboot. But I'll use fastboot then. Thanks a lot!
Hi all,
Apology if this questions may already been ask millions of time but I am really stucked at the moment and hoping that someone may guide me to the correct direction.
I have got HTC One X-LTE (Evita)
I managed to get S-OFF and also CID - 111111
It has TWRP 2.6
The last time I got it working was on the STOCK 4.2.2 I downloaded from the XDA - then I got into the issues of rebooting and loosing signal from time to time. so I went into my TWRP backup I had and reflashed it using my old backup made from my TWRP.
the reflashed failed and now I can only boot up to the HTC logo and then black screen.
I can get to the TWRP recovery and I have got fastboot and ADB on my PC.
When I run the fastboot devices command --> it shows device connected BUT when i try ADB command ---> no device is found.
It will be much appreciated if someone can guide me to the right direction as I am really stucked at the moment not sure where to start.
I tried searching in the forum but I don't think I went to the correct area/tutorial.
Please help
Thank you
When you made your twrp backup did you select system,data, and boot? If it's hanging at the HTC screen it seems there is not boot.img installed or one that is incompatible with your backup. Open whatever Rom your backup is made from and copy the boot.img to your fastboot directory. Then reboot the phone into fastboot mode and flash the boot.img using this command.
Fastboot flash boot boot.img
Then reboot the phone and see what happens
Sent from my HTC One XL using Xparent Red Tapatalk 2
ImagioX1 said:
When you made your twrp backup did you select system,data, and boot? If it's hanging at the HTC screen it seems there is not boot.img installed or one that is incompatible with your backup. Open whatever Rom your backup is made from and copy the boot.img to your fastboot directory. Then reboot the phone into fastboot mode and flash the boot.img using this command.
Fastboot flash boot boot.img
Then reboot the phone and see what happens
Sent from my HTC One XL using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply.
When looking at the TWRP backup I copied into my PC - does not have the .img - the one I can find is MD5
Can I use the existing ROM I donwload from XDA like : EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip
when I extracted EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip - I can see the "boot.img" can I use this one?
Thanks
ardabelati said:
Thanks for the reply.
When looking at the TWRP backup I copied into my PC - does not have the .img - the one I can find is MD5
Can I use the existing ROM I donwload from XDA like : EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip
when I extracted EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip - I can see the "boot.img" can I use this one?
Thanks
Click to expand...
Click to collapse
I had a somewhat similar experience with Viper 4.0 ROM - I managed to get Cyanogenmod installed correctly (particularly this one). Take a shot and see if it works - atleast your phone will be up and working.
sandys1 said:
I had a somewhat similar experience with Viper 4.0 ROM - I managed to get Cyanogenmod installed correctly (particularly this one). Take a shot and see if it works - atleast your phone will be up and working.
Click to expand...
Click to collapse
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
ardabelati said:
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
Click to expand...
Click to collapse
hmm - Im on ROM dated 09/13, which is not present now. Your best bet would be http://get.cm/get/aOM
Also remember to flash Google Apps (play store, etc.) which is packaged separately here - http://goo.im/gapps/gapps-jb-20130813-signed.zip
ardabelati said:
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
Click to expand...
Click to collapse
Did it work finally ?
sandys1 said:
Did it work finally ?
Click to expand...
Click to collapse
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
ardabelati said:
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
Click to expand...
Click to collapse
It sounds like it might be a bad download or something. I noticed u never mentioned wiping the phone before flashing, Are u clean wiping? And also what hboot are you on?
Sent from my HTC One X using xda app-developers app
ardabelati said:
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
Click to expand...
Click to collapse
You can either flash the kernel, which can be found in the Android Development section, flashing the kernel is just like flashing a ROM, just install in Beastmode. Or you can upgrade your firmware to 2.15, the instructions are I'm the first post of the ROM thread.
Asking which ROM is best/favorite/most stable is against the rules so we can't answer that question.
When you say the phone keeps rebooting, does it ever make it into the OS or is it boot looping (showing the boot animation then starting over)?
Sent from my Evita
timmaaa said:
You can either flash the kernel, which can be found in the Android Development section, flashing the kernel is just like flashing a ROM, just install in Beastmode. Or you can upgrade your firmware to 2.15, the instructions are I'm the first post of the ROM thread.
Asking which ROM is best/favorite/most stable is against the rules so we can't answer that question.
When you say the phone keeps rebooting, does it ever make it into the OS or is it boot looping (showing the boot animation then starting over)?
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply
When you said that flashing kernel is the same as flashing ROM, I did it By going to TWRP and the press install and locate the zip file. Is this what should be done?
What is beast mode?
Sorry for the basic questions
Thanks
Yeah that's how you install the kernel. It must be done after you install the ROM. I kinda worded my reply a bit weird, sorry about that. Beastmode is the name of the kernel, you can find it here:
http://forum.xda-developers.com/showthread.php?t=2165880
Sent from my Evita
I did try to flash it through recovery but it always failed. Not sure why. I copied the kernel zip file into my phone sd and then I went to recovery and press the install and located the kernel zip file but still failed.
Sent from my HTC One XL using Tapatalk 2
Which recovery version are you using?
Sent from my Evita
Recovery is 2.6.3.
The process failed on not able to fine the MD5 file or something like that. We don't need to extract the Zip file do we?
Cheers
Disable md5 checking in settings. You never need to extract a kernel or ROM zip.
Sent from my Evita
timmaaa said:
Disable md5 checking in settings. You never need to extract a kernel or ROM zip.
Sent from my Evita
Click to expand...
Click to collapse
I have checked the setting in TWRP and nothing is ticked.
When I flash the zip, it is still saying "failed due to md5 does not exists".
I am not sure which should be address first but I now noticed that there is an error : "unable to locate storage device"
also came out.
When I plug my phone to PC I can see the storage but why it is saying "storage device not found" in TWRP?
Thanks
I have a CM ROM with Android 4.2.2 running now.
Whenever I try a 4.3 or 4.4 ROM in TWR or CWR I get a failed error during flashing.
If I fastboot flash one of the newer recoveries like the ones listed in the 4.4 rom threads, the phone will just go black when it tries to enter recovery mode and I have to flash back one of the regular recoveries to get back into the phone.
I am pretty sure that the phone is failing flashing the newer mods because the two recoveries I am trying to use can't handle them, but why wont the newer recoveries work when I fastboot flash them, flashboot reads successful.
Any help would be greatly appreciated.
Thanks!
What is the filename of the new recovery you're trying to flash? And what is the command you're using?
Sent from my Evita
timmaaa said:
What is the filename of the new recovery you're trying to flash? And what is the command you're using?
Sent from my Evita
Click to expand...
Click to collapse
recovery.img which is got from the CM 11 thread (http://forum.xda-developers.com/showthread.php?t=2541998)
fastboot flash recovery recovery.img
add this command after flashing the recovery...
fastboot erase cache
bzhmobile said:
add this command after flashing the recovery...
fastboot erase cache
Click to expand...
Click to collapse
Just tried it. Still just goes to a black screen when I try to enter recovery, and then it reboots again into CyanogenMod
Could it be because I am s-on?
Better to be S-off (not mandatory I think), What is your hboot?
Try with latest TWRP or Philz touch recovery to see if it the same
Okay I got S-Off but it still won't boot to any recoveries newer than TWRP 2.6.3.0 or CWMR 6.0.3.1
It's hard to tell what's gone wrong but now that you're s-off you should try running an RUU so you can start with a clean slate.
Sent from my Evita
timmaaa said:
It's hard to tell what's gone wrong but now that you're s-off you should try running an RUU so you can start with a clean slate.
Sent from my Evita
Click to expand...
Click to collapse
Just ran 3.18 RUU and it was successful. Can you link me to the recovery that you're using?
The SCID + S-OFF + RUU 3.18 seemed to have done the trick!
Thanks for all the help!
Good news, no problems. When someone on XDA helps you please press the thanks button on the posts that were helpful as well as saying thanks.
Sent from my Evita
timmaaa said:
Good news, no problems. When someone on XDA helps you please press the thanks button on the posts that were helpful as well as saying thanks.
Sent from my Evita
Click to expand...
Click to collapse
Done and Done!
Now, I have the more difficult task of picking the best KitKat Rom
veritas2884 said:
Just ran 3.18 RUU and it was successful. Can you link me to the recovery that you're using?
Click to expand...
Click to collapse
If you are looking to flash a 4.3 or lower Rom TWRP 2.6.3.0 will be fine.
If you want to go to 4.4 you can try this custom TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
@jrior001 just posted this today.
Madcat8686 said:
If you are looking to flash a 4.3 or lower Rom TWRP 2.6.3.0 will be fine.
If you want to go to 4.4 you can try this custom TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
@jrior001 just posted this today.
Click to expand...
Click to collapse
I will give it a whirl. Thanks! Any suggestion on which 4.4 is most stable? I tried the beanstalk 4.4 build but after about five mins of using it, it devolved into boot loops. I also tried the official CM 11 nightly but it wouldn't even post. Maybe it will work better with the new twrp.
Sorry, but asking which ROM/kernel is best/most stable isn't allowed here. This is because to say one is better/faster/more stable is to infer that the other ROMs are inferior in some way. This isn't fair to the devs who spend countless hours of their spare time providing us with these awesome ROMs free of charge. It's simply a matter of flashing and testing for yourself, it only takes a few minutes to flash a ROM. Reading the last few pages in a ROM thread goes a long way too, you'll find out pretty fast how the ROM is performing.
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.