I read on flip board that cm 10.1 is official for our phone and I I want to flash it and I did but the after I flash it and flash the boot.IMG it get stuck on the HTC logo and I see that the soft key button turn on and have vibration when I touch them can anyone help .
Sent from my HTC One S using xda premium
Do you have an S4 or S3 phone
Did you check md5 for good/bad download
Did you wipe all including System 2x in recovery
Which recovery are you using
I have s4 and I didn't check the md5 cause all 4.2 ROMs have the same problem for me,i have twrp
Sent from my HTC One S using xda premium
which version twrp. some of the later 2.3's had issues
otherwise if you are wiping all and fastbooting boot, not sure
fastboot boot after rom and fastboot erase cache before booting onto rom
rugmankc said:
which version twrp. some of the later 2.3's had issues
otherwise if you are wiping all and fastbooting boot, not sure
fastboot boot after rom and fastboot erase cache before booting onto rom
Click to expand...
Click to collapse
I have v 2.3.3.0 for twrp I'll update it and try what you said and report back here if it works
Sent from my HTC One S using xda premium
i had 2.3.3.0 and it was not one of the bad ones
Still doesn't work and I tried force md5 sum check on twrp and it failed could that be the problem
Sent from my HTC One S using xda premium
brandontamas said:
Still doesn't work and I tried force md5 sum check on twrp and it failed could that be the problem
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'd reccomend clockworkmod over twrp, had more bootloops with twrp in the past.
Also, good alternative rom is dark jelly cm10.1 with android 4.2.1 stable and reliable, using it a pretty long time.
Easy install via an automatic installer program called aroma installer, no need to flash boot.img here
http://forum.xda-developers.com/showthread.php?t=2051865
Sent from my One S using xda app-developers app
yes, ck your md5's. i use es explorer and it is easy
as john said you can try another rom, but still ck md5 and wipe system as part of your wipes
if you flash a rom with aroma, don't wipe in recovery and aroma. only one. i prefer recovery
as for cwm or twrp. everyone has their favorite. it is my understanding though cwm hasn't kept pace on updates with later version roms afaik
hope you get it--
Related
can someone please make a video or a very clear post how to download leedroid v6.4 on htc one s because this is the 2nd time i tried it and messed it up where i have to run ruu to go back to factory settings
dude its easy, The instructions are on the thread
1, Unlock Bootloader
2, Flash CWM recovery
3, Flash Boot.img
4, Flash ROM
5, Flash boot.img again (optional)
Done !
It doesnt get any easier than that ^^^
Sent from my HTC One S using xda premium
Still doesn't work I go into a bootloop
Sent from my HTC One S using xda premium
Is there a way to download leedroid tweaks on its own ?
Sent from my HTC One S using xda premium
Leedroid has v6.4 on the one S? or the one X?
V2.1 for the One S
Are there any direct links for the one s latest version only tweaks
Sent from my HTC One S using xda premium
I dont think the tweaks will work on a stock ROM, They require the modded framework.
;( leedroid always messes up when I try download it to my phone
Sent from my HTC One S using xda premium
I am stuck in a boot loop too. Driving me nuts I have been using custom roms for ever.
Btw other custom roms work without issue on my one s except leedroid.
balto said:
I am stuck in a boot loop too. Driving me nuts I have been using custom roms for ever.
Btw other custom roms work without issue on my one s except leedroid.
Click to expand...
Click to collapse
Yeah same that's why I'm asking people for help to do it like on a video are u still in bootloop? I was in bootloop before
Sent from my HTC One S using xda premium
Both of you just post on how you flash the rom. There has to be something easy that is overlooked. Cause i have flashed the rom 4 times with no problems
snwman said:
Both of you just post on how you flash the rom. There has to be something easy that is overlooked. Cause i have flashed the rom 4 times with no problems
Click to expand...
Click to collapse
I put the Rom zip and md5 Rom thing in sd card too I think go into bootloader run that windows.bat thing flash boot.IMG flash Rom run boot.IMG again
Sent from my HTC One S using xda premium
How do you do it? sorry for bad English tired
Sent from my HTC One S using xda premium
k1llacanon said:
I put the Rom zip and md5 Rom thing in sd card too I think go into bootloader run that windows.bat thing flash boot.IMG flash Rom run boot.IMG again
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Did you flash the rom in cwm after the first time you flashed the boot.img? If not then that is probably your issue.
For me I flashed boot flash rom in cwm and for good measure flashed the boot again.
I am going to try a new download of the rom I think that could be my issue.
Right ill basically start from as if i was to flash the rom from if i has a stock phone
1.Make sure phone is rooted and unlocked by Htc dev
2.Have a custom recovery flashed
3.Download the v2.0 and v2.1 of the rom and also the boot.img
4.Place v2.0 and v2.1 files into a folder on your sd card.
5.Now make a nandroid backup of your current rom you are using before you flash LeeDroids rom
6.Extract the boot.img so that you can run the command to flash the .img to your phone
7.Boot phone into bootloader then fastboot, connect phone to pc and it should say fastboot usb.
8.Run the boot.img file to which ever OS you are using (meaning windows, mac etc.)
9.Get back into the bootloader screen and get into recovery.
10. Format system, data and cache also wipe dalvik cache as well. It should be wiped by formatting system and data but only takes 2seconds to do it anyway. You will find it under advanced menu(In Clockworkmod)
11. Find the .zip of leedroids v2.0 and flash it
12.Reboot phone and finish the setup menu and just let the phone settle for a minute or two after you finished it
13. Boot phone into bootloader and then fastboot. Run the boot.img again just to be sure.
14.Boot into recovery and flash v2.1 and then reboot and enjoy.
Now set phone up the way you want
This is the method i have used seems long but only takes 10minutes once you have all the files. I have done this 4 times using this method
I will try this method later so what's the v6.4?
Sent from my HTC One S using xda premium
k1llacanon said:
I will try this method later so what's the v6.4?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
None for htc one s maybe for the one x which lee is also developing for
Oooh I've been trying v6 so only v2 will work for one s? And is it just as good?
Sent from my HTC One S using xda premium
i cannot boot phone into recovery nor can i boot phone normally... I had just installed Viper one S rom on my phone and rebooted into recovery because my wifi wasnt working , so i was just going to revert back to an old rom. After clicking reboot to recovery from Viper rom the screen just went white . I had to power it down manually, after powering it up it would stop at htc screen with the red development lines... tried to go into recovery and it will come up for a second then disapear then phone reboots.... any ideas? oh I also had installed Latest radio in CWM after installing rom.. I hear its buggy in CWM...
I had the same problem. Did you flash the boot.IMG in recovery or fastboot? If you flashed in recovery and its not supported by your hboot version. That could be the issue. Try re flashing the boot.IMG using fastboot. If you still cannot get it to work. I would try reinstalling a custom recovery manually and restarting the Rom flashing process. There are forums all over the place to help with that. Try twrp. Ps this is all assuming you are able to get into your boot loader.
Sent from my HTC One S using xda app-developers app
Problem fixed. Don't ask me how lol. All I did was relock boot loader and flash stock ROM. Stock ROM would not load so I just decided to unlocked boot loader and phone rebooted fine. Recover works to.. crazy.
Sent from my HTC One S using xda premium
That happened to me when I didn't fast boot flash the boot.IMG file, but only the latest Viper has given me grief with that.
Sent from my HTC One S using xda app-developers app
MrPickleFicker said:
That happened to me when I didn't fast boot flash the boot.IMG file, but only the latest Viper has given me grief with that.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Good to know so I won't make the same mistake twice.
Sent from my HTC One S using xda premium
I recently unlocked my HTC One s tmo, HBoot 1.14.004, I recently flashed twrp 2.3.3.0 and it won't flash or wipe roms...it boots into recovery half the time...I tried flashing TD 9.0 and fastboot flashing the boot.IMG......to no avail.. please help
Sent from my HTC VLE_U using xda app-developers app
Please list the exact steps you took, and explain the exact problem.
That way it will be easier to nail down the issue and give you help.
Unlocked phone via HTC...flashed twrp 2.3.3.0 via fastboot, booted into fastboot did a full wipe, flashed trickdroid 9.0 and it wouldn't finish flashing at the point when it was trying to flash the kernel, I rebooted to fastboot and flashed the boot.img.....did that multiple times..just bootloops to recovery
Sent from my HTC VLE_U using xda app-developers app
handman29 said:
Unlocked phone via HTC...flashed twrp 2.3.3.0 via fastboot, booted into fastboot did a full wipe, flashed trickdroid 9.0 and it wouldn't finish flashing at the point when it was trying to flash the kernel, I rebooted to fastboot and flashed the boot.img.....did that multiple times..just bootloops to recovery
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Do full wipe and the use the recovery to reboot back into it then flash rom without the wipe.
handman29 said:
Unlocked phone via HTC...flashed twrp 2.3.3.0 via fastboot, booted into fastboot did a full wipe, flashed trickdroid 9.0 and it wouldn't finish flashing at the point when it was trying to flash the kernel, I rebooted to fastboot and flashed the boot.img.....did that multiple times..just bootloops to recovery
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Wipe and try again... You got impatient the boot.IMG part takes a long time... Just start the flash and put your phone down... Leave it alone until its done...if you don't get an error it will finish just wait...
Sent from my HTC One S using xda premium
Yeah, dont interrupt the installer. It installs some other important stuff after the boot.img.
And yes, it takes a long time. If nothing has happened after 15min or so, then it might be something wrong.
For me, the boot.img part seems to take between 5 and 10min, depending on the weather outside, the alignment of the stars etc
The dialer app is not working at all I can't receive calls nor can I make calls it says "Unfurtunately, the process com.android.htcdialer has stopped" and this just hapens on sense ROMS on every of them, the aosp ones work just great but I want sense right now (Magio ROM R3.6.1) Does anybody knows how to fix this?
remulacha said:
The dialer app is not working at all I can't receive calls nor can I make calls it says "Unfurtunately, the process com.android.htcdialer has stopped" and this just hapens on sense ROMS on every of them, the aosp ones work just great but I want sense right now (Magio ROM R3.6.1) Does anybody knows how to fix this?
Click to expand...
Click to collapse
are you wiping everything before flashing the sense rom?
Try fastboot command:
fastboot erase cache
Then wipe cache in TWRP.
Sent from my Evita
This is a bug from going from touch cwm to twrp
You can either reflash cwm and stay on it or reflash cwm then flash a non touch cwm then flash twrp. Using fastboot erase cache after every recovery flash.
Sent from my HTC One X using xda app-developers app
exad said:
This is a bug from going from touch cwm to twrp
You can either reflash cwm and stay on it or reflash cwm then flash a non touch cwm then flash twrp. Using fastboot erase cache after every recovery flash.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I will try to flash cwm thanks
exad said:
This is a bug from going from touch cwm to twrp
You can either reflash cwm and stay on it or reflash cwm then flash a non touch cwm then flash twrp. Using fastboot erase cache after every recovery flash.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I nkow this is an old post. I hit the thanks button; clearly not enough so I had to post to say it.
THANK YOU!!!!!!
I know it sounds dumb but I search for 2 days before I found this and it work 100%!!! My phone is 100% working again! I can't thank you enough; I was really worried I messed it up because I had tried a "german 4.2.2" on it. It seemed laggy slow* wonder if that would be the recovery. But I got the RUU from HTC for my phone (4.1.1) done that and poof nothing working(your fix worked). still debating on trying the 4.2.2 again. It is nice has some cool features. But I know 4.1.1 works great.
Sorry got of track. THANKS AGAIN!
Hope this help
Sent from my HTC One X using xda app-developers app
Did you have a cwm based recovery then flash twrp? That happens when you switch. If so you have to flash a non touch cwm then flash twrp and wipe cache after every flash
Sent from my HTC One using Tapatalk 4
I think the process is:
Non touch CWM
Touch CWM
TWRP
With fastboot erase cache between each flash.
Sent from my Evita
I just fastboot erase cache
fastboot flash recovery cwm whatever current version is
then installed the rom..
i think that dialer issue affects first gen htc one x owners some sort of dialer issue internally affected it they released a newer model with the fix.
i only say this bc my manager had the first gen and i had to flash cwm for him to get his dialer to work
timmaaa said:
I think the process is:
Non touch CWM
Touch CWM
TWRP
With fastboot erase cache between each flash.
Sent from my Evita
Click to expand...
Click to collapse
scrizo said:
I just fastboot erase cache
fastboot flash recovery cwm whatever current version is
then installed the rom..
i think that dialer issue affects first gen htc one x owners some sort of dialer issue internally affected it they released a newer model with the fix.
i only say this bc my manager had the first gen and i had to flash cwm for him to get his dialer to work
Click to expand...
Click to collapse
no.
This is a CWM - TWRP issue. If he flashes back to CWM it will work again.
Ah ok thanks for clearing that up, was curious because my hox ran fine with twrp 2.6 and venom Rom
Sent from my HTC One X using xda app-developers app
timmaaa said:
I think the process is:
Non touch CWM
Touch CWM
TWRP
With fastboot erase cache between each flash.
Sent from my Evita
Click to expand...
Click to collapse
Like always.. thanks.. u should make a rom.. i feel it would be amazing
classified_noob said:
Like always.. thanks.. u should make a rom.. i feel it would be amazing
Click to expand...
Click to collapse
Lol thanks but I don't have the necessary knowledge to do that yet, I'm still learning, maybe in a year or two.
Sent from my Evita
I bet you can learn fast.. it's like makin a cake. Same way to make just different flavors
Sent from my HTC One X using xda app-developers app