Hey guys,
I just recently wanted to Cyanogenmod my friends' phone (which I have done with many others already) and never could get it to actually boot anything but the stock rom.
I S-OFF'ed it via HTCDev and installed the 4X recovery. (not sure if the name is right, I don't have the phone here)
Then I Installed the custom Rom after Wiping Cache/Dalvic/Factory Reset and it went through, but every Rom gets either stuck at the "HTC" screen or in the case of Cyanogenmod (Official) it got the the Boot animation and then looped.
Anyone knows what could've gone wrong? I re-flashed the stock Rom after giving up and now the phone seems to have issues with the WiFi connection.
So how do I get a custom Rom to actually Boot?
bobdowl said:
I S-OFF'ed it via HTCDev and installed the 4X recovery. (not sure if the name is right, I don't have the phone here)
Click to expand...
Click to collapse
you can't S-OFF via htcdev
post your bootloader details
bobdowl said:
Hey guys,
I just recently wanted to Cyanogenmod my friends' phone (which I have done with many others already) and never could get it to actually boot anything but the stock rom.
I S-OFF'ed it via HTCDev and installed the 4X recovery. (not sure if the name is right, I don't have the phone here)
Then I Installed the custom Rom after Wiping Cache/Dalvic/Factory Reset and it went through, but every Rom gets either stuck at the "HTC" screen or in the case of Cyanogenmod (Official) it got the the Boot animation and then looped.
Anyone knows what could've gone wrong? I re-flashed the stock Rom after giving up and now the phone seems to have issues with the WiFi connection.
So how do I get a custom Rom to actually Boot?
Click to expand...
Click to collapse
As rzr said you can't s-off via htcdev. Activate smartflash in 4ext recovery and try again.
Sajito said:
As rzr said you can't s-off via htcdev. Activate smartflash in 4ext recovery and try again.
Click to expand...
Click to collapse
Okay, sorry I just asked my friend (who is in possession of the phone)
I unlocked the Bootloader via HTCDev, I will contact my friend to make sure what I did. (It's been a week)
Related
Hey, first time posting something on this forum but to all devs reading this thanks alot for everything you do!
And Thanks to anyone who can help me!
Now my problem is as following,
My stock rom is RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed.exe
I followed this guide to unlock the bootloader and get root http://forum.xda-developers.com/showthread.php?t=1583427
I used this recovery "Official CWM of koush (HTC One S)" (both toutch and regular has been tested)
Then i downloaded MIUI at first and flashed that(full wipe), it installed fine so i rebooted.
Once i got passed the htc boot screen everything went black, no boot animation.
After that i tested some more Roms, ParanoidAndroid and AOKP Milestone 6.
The exact same thing happend with and exeption for AOKP where the toch keys turned on.
I also noticed it showed up as a removable device in windows from time to time when plugged in (dont if that helps).
After that i restored my one s to stock and then did all the steps again but that yeilded the same results.
I have no idea what the problem is and im hoping its something that has an easy fix and im just to dumb to see it.
If you need any more info just ask, and again thanks for any help!
Before flashing rom through CWM, did you flash boot.img through fastboot. Every rom comes with a boot.img that must be flashed through fastboot when not using TWRP.
T-MobileUS HTC One S running Stock Rooted 2.21.
fmedrano1977 said:
Before flashing rom through CWM, did you flash boot.img through fastboot. Every rom comes with a boot.img that must be flashed through fastboot when not using TWRP.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
Thanks alot! I can't belive i missed that, well it was an easy fix just as i figured.
Daikar said:
Thanks alot! I can't belive i missed that, well it was an easy fix just as i figured.
Click to expand...
Click to collapse
just use twrp and problem solved.
CWM IMO sucks in comparison. Not to mention the level of support with TWRP is so far and above ANYTHING you will get with CWM.
Long time lurker first time poster. I had a Nexus One two years ago so I was here very very often.. Since I got my Desire S a year ago, I haven't been able to flash a custom rom OR S-OFF.
Unlocked with HTCdev, rooted, HBOOT 2.00.0002 (downgrading hboot never worked either), S-ON
Last night I tried again to get onto ICS (official RUU doesn't install either). I installed 4EXT touch, flashed recovery, had my ROM (Fallout) on SD ready. Rebooted phone into new recovery to find that is was still the OLD revolutionary recovery and not 4EXT. This was 4am so I thought I'd try the usual wiping + rom flash. It went through normally and said completed although the progress bar only got about 1/3rd before jumping straight to finished. Rebooted.. stuck at white HTC logo screen.
My issues are that I cannot install HTC Sync phone drivers without phone powering up to be recognised by the PC, AND I cannot turn USB debugging on for obvious reasons
My phone is veryvery important and I'm now scared I won't be able to get it working again. Please help me.
TLDR; stuck on White HTC logo screen, no Android installed, cannot see how I can install one, help!
If anyone could shine some light on what I need to do next, I'd be very grateful.
Thanks in advance.. and afterwards
How did you flash the recovery? In fastboot? And did you flash the boot.img (also in fastboot) of the Rom you flashed?
You should definitely have read more before flashing anything...
teadrinker said:
How did you flash the recovery? In fastboot? And did you flash the boot.img (also in fastboot) of the Rom you flashed?
You should definitely have read more before flashing anything...
Click to expand...
Click to collapse
For the 4EXT recovery I 'flashed' it from inside the touch app thinking that was enough these days.. naively. Had just been fighting with GF at 4am and was fed up and about to go to bed and in Revolutionary recovery so I thought what the hay, I'll wipe etc in here and use this to try and flash the rom.
I did not flash the boot.img. I goofed. I understand that but now I'm just desperate for any route back to a functional device.
I never stopped installing ROMs and etc on my old Nexus One but that was a while ago and everything just seemed to work. Desire S is being a nightmare.
Decide what you want to do.
If you want to upgrade the phone to official ROM - relock your bootloader and run RUU.
If you want to use custom ROMs - flash the recovery from fastboot and don't forget to flash the kernel from fastboot too.
I won't get into any more details, searching for the right info with these pointers will get you whatever you might need.
Thank you, I'm all fixed. Simply found an old 2.3.5 ROM and flashed and booted fine. Reason I was so stuck was because I had formatted my PC since last installing phone drivers so I couldn't do much hurdur
So my At&t One X (evita) has been rooted and the bootloader has been unlocked for some time now. I came from the old Htc Hero on Sprint, so I am use to rooting and flashing roms. The issue is I decided to try Cm10 and I flashed it correctly through the flash gui app. An update appeared at the top so I (like a noob) decided to install it.. I realized after the fact how I had messed up by not using flash gui (boot.img ,etc..) , So it would boot to the Htc logo and then just blackness would occur. I could and still could go to the bootloader successfully though. My mistake was doing a whole factory reset from the phone so no more TWRP recovery unit... I went back to the utility that I rooted and unlocked my bootloader on and relocked it just in case I needed to flash something such as a RUU (whatever that is) but I do have one ready to be installed. I tried to do it myself and kept getting the sentence in the picture posted... Can anyone help me??
that picture doesn't help much, my not relock bootloader run the .exe ruu. then reunlock and flash twrp then flash a rom? also flashimagegui doesnt flash a rom all it does it flash boot.img and modules or recovery. you still have to reboot into recovery and flash the rom zip. since youve used android before it is an easy fix. so fix it already =)
hrrsncrawford14 said:
So my At&t One X (evita) has been rooted and the bootloader has been unlocked for some time now. I came from the old Htc Hero on Sprint, so I am use to rooting and flashing roms. The issue is I decided to try Cm10 and I flashed it correctly through the flash gui app. An update appeared at the top so I (like a noob) decided to install it.. I realized after the fact how I had messed up by not using flash gui (boot.img ,etc..) , So it would boot to the Htc logo and then just blackness would occur. I could and still could go to the bootloader successfully though. My mistake was doing a whole factory reset from the phone so no more TWRP recovery unit... I went back to the utility that I rooted and unlocked my bootloader on and relocked it just in case I needed to flash something such as a RUU (whatever that is) but I do have one ready to be installed. I tried to do it myself and kept getting the sentence in the picture posted... Can anyone help me??
Click to expand...
Click to collapse
Had that happen to me. But just had to flash a kernel for it to boot properly. Everything fine after that.
Sent from my HTC One X using Tapatalk 2
THANKS!!! I have it working now thanks to the suggestions! :laugh::laugh:
DvineLord said:
that picture doesn't help much, my not relock bootloader run the .exe ruu. then reunlock and flash twrp then flash a rom? also flashimagegui doesnt flash a rom all it does it flash boot.img and modules or recovery. you still have to reboot into recovery and flash the rom zip. since youve used android before it is an easy fix. so fix it already =)
Click to expand...
Click to collapse
glad u got it working again. i would recommend doing s-off so you don't have to flash boot.img separately anymore.
This morning I used the Hasoon all in one for ATT/Rogers (Evita)
1. Unlocking the boot loader went OK. Says UNLOCKED. Also says TAMPERED above it. Noticed also S-on
2. Flashing TWRP 2.4.1.0 went OK (I think). When it rebooted I was at a HTC screen telling me that 'This was for developers' or similar, then went directly to TWRP 2.4.1.0.
At this point I am a little lost. (My first attempt at this.)
a) Is my original ROM still there or did it disappear when I flashed TWRP? If it is there how can I bring it back?
b) If it is not there, how do I download a ROM (zip file) so that TWRP can flash it. As I said I have not been able to get out of TWRP.
In the past I rooted a Nexus One and did a number of ROM flashes using CWM. I thought TWRP would be similar where it had a number of ROM that I could download from the ROM.
Any help is very much appreciated,
Regards,
David
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
qabi said:
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
Click to expand...
Click to collapse
Do you have Ville (S4) or Ville C2 (S3) model?
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery --> http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville/philz_touch_6.19.3-ville.zip
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
PLS check if you have S3 or S4
LS.xD said:
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
Click to expand...
Click to collapse
Thanks for your suggestion.
Actually I don't know. I think only one HTC One S was ever in my market (Denmark).
In the meantime I succeeded installing the TwistedKat ROM and have it running now.
Does anybody know of a tutorial for resetting to stock ROM? (Just in case I want to revert).
-qabi
Unable to enter clockwork recovery?
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
qabi said:
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
Click to expand...
Click to collapse
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
Which recovery do you use? Are you S-OFF // SuperCID // HBOOT 2.15??
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Rapier said:
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Click to expand...
Click to collapse
Rapier, can you explain this? A while back I loaded TWRP (S-ON) then loaded one of the CM series (either 11 or 10, can't remember). Then after I flashed boot.img, I was stuck in boot loop with HTC/red letters.
The reason I was asking what he did was I never did get to stop the boot loop myself. I paid to get it fixed, but I would like to know what I should have done to fix the boot loop after flashing the boot.img and having the problem. Seems like a lot of people get this so, so would be nice to know.
I was basically following everything listed on a web page and everything was working. Unlocked boot loader, SuperSU, TWRP etc... the last thing I did was flash the boot.img and then the problems occurred.
As far as the double try for CWM, I am S-OFF, 2.15 and I noticed it happens every now and then. I don't have this issue with TWRP at all.
It is hard to say why, apparently you did all right. What I can think off is a bad download or a bad flash or you could have used a wrong TWRP version. Also that ROM you have tried could have issues. It is very hard to know why without some logs that shows what went wrong
Sent from nowhere over the air...
LS.xD said:
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery -->
Click to expand...
Click to collapse
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
qabi said:
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
Click to expand...
Click to collapse
I think so. I am running the latest CWM and never had problems before this.