i remember when i first started hearing about TWRP their were issues with flashing certain files and most people just stuck with CWM Recovery. but that was a long time ago and i've heard a lot of good things about TWRP lately. at this point, are they both the standard with developers, meaning i wouldn't have any issues flashing any files with either recovery?
I prefer TWRP. I like its UI and for the most part I think everything is similar or exactly the same. You shouldn't have any problems flashing. I read somewhere CWM isn't working for the N5 yet, but I don't know. TWRP is I believe.
Related
Hi guys,
I'm having trouble with this. I'm rooted and unlocked with CWM, and after flashing CM9 I can't mount the SD card through CWM. I flashed the latest CWM (5.8.4.0) but it doesn't seem to have helped. Does anyone have any ideas on how I can solve this?
Flash TWRP http://forum.xda-developers.com/showthread.php?t=1677447
Our device is not officially supported by CWM. TWRP is the way to go, as the post above suggests.
Its a known issue with CWM and our device. As others suggested, best to use TWRP. Everything works, and it officially supports our device (CWM does not).
Also that version of CWM isn't meant for an EVITA HTC One X. Damned AT&T demanding the name of this device be the same as a completely different phone. causes all kinds of problems.
Thank you all! I came from the galaxy family so I assumed CWM was the best, but apparently not here.
First noted this is first time installing a custom rom. Long time lurker, first time problem!
HTC One S from Bell (Canada) Rooted/unlocked. CWM for Recovery.
Installed the from Zip in CWM. Cleared everything, went and flashed with fastboot for the boot. Everything looked good. Went back into CWM and cleared cache again.
Went to boot, hanging at htc screen but has the additional red text as well.
What did I miss ?
Thanks for any help or insight into this issue.
Is your phone s-off ... If not thm install 4ext recovery n flash the rom by enabling smart flash in 4ext recovery... Search for 4ext recovery n how to flash rom with s on ull b done
If I hve helped you press the thanks button ...
sent from HTC sensation
No idea what the above poster is on about but... My engrish isnt that good.
CWM is a crappy recovery for our phones. You should use TWRP instead.
But that doesnt seem to be the issue here. The issue you are describing is exactly what happens if boot.img isnt flashed through fastboot.
So, I suggest trying to flash it again through fastboot (fastboot flash boot boot.img).
If it still doesnt work after a couple of tries, change recovery to TWRP and start over from scratch (wipe everything, flash viper, flash boot.img).
Goatshocker said:
No idea what the above poster is on about but... My engrish isnt that good.
CWM is a crappy recovery for our phones. You should use TWRP instead.
But that doesnt seem to be the issue here. The issue you are describing is exactly what happens if boot.img isnt flashed through fastboot.
So, I suggest trying to flash it again through fastboot (fastboot flash boot boot.img).
If it still doesnt work after a couple of tries, change recovery to TWRP and start over from scratch (wipe everything, flash viper, flash boot.img).
Click to expand...
Click to collapse
Thanks so much, It worked. I was starting to stress out. Re-did the flash and BAM music happened. Just sitting at the HTC One screen now. I assume that takes a couple minutes.
Yeah. We dont have 4ext recovery yet for our phones. Only an old outdated version of clockwork, and of course a good updated version of TWRP. I havent used 4ext but have heard interesting things. I hear in the new year there will be some work on bringing it to HTC One S, although I dont know if it will have any features that arent already covered in TWRP.
AKToronto said:
Yeah. We dont have 4ext recovery yet for our phones. Only an old outdated version of clockwork, and of course a good updated version of TWRP. I havent used 4ext but have heard interesting things. I hear in the new year there will be some work on bringing it to HTC One S, although I dont know if it will have any features that arent already covered in TWRP.
Click to expand...
Click to collapse
Yeah im going to be switching over to TWRP. Sounds like its allot better to work with. I know with cwm you can't even mount usb storage, so you end up pushing files on using adb.
was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
srk10 said:
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
Click to expand...
Click to collapse
not sure but it can be possible that some partitions are damaged.
run the latest ruu to restore all the partitions.
twrp 2.5.0.0 have some problems with custom roms,
try twrp 2.3.3.0, it seems that this version has mostly no problems with flashing roms.
do not forget to flash the boot.img after flashing the rom or you will get a bootloop.
before flashing a rom wipe 3x system 3x data 3x cache to be sure that your phone is clean of old system stuff.
here is the link for twrp 2.3.3.0
https://www.dropbox.com/s/pvspwkekl42zkqa/openrecovery-twrp-2.3.3.0-ville.img
Thanks so much for the reply. I downgrade to twrp 2.3 and managed to use the windows utility to reformat my sd card. Wasn't sure that wasn't going to shoot me in the foot, but it worked and I am back in business with a phone that boots.
Hello,
I am running KK on system version 182.46.10.xt926.
My boot-loader is unlocked and I am rooted.
I have xt926-KK-CWM-6048 installed.
When I try to boot into recovery I get a blank, black screen.
I know recovery worked at one time, but do not understand why it stopped.
I was wondering if I should re-flash xt926-KK-CWM-6048 or flash CWM6049-RAZR-HD_M-KITKAT.
Would this actually take care of my problem? Would there be anything else I would have to do?
Thanks for any input.
HydroMx
Try flashing the newer 6.0.4.9 CWM. I also had that black screen problem occasionally with 6.0.4.8 and I think other people did as well. FYI, I was able to get to recovery eventually if I kept rebooting. Sometimes it works on the first try, sometimes it doesn't.
But I flashed the TWRP 2.7.1.0 image that dhacker posted last night and I haven't gotten any black screens yet, even after booting into recovery several times just to test it.
Thanks for the quick reply. Question for you.
If I flash TWRP 2.7.1.0, does that overwrite CWM or will I have two recovery options?
It will overwrite CWM. Stick with whichever recovery you're most comfortable with. I prefer TWRP but some people like CWM more.
And my last question....
Where do I get TWRP 2.7.1.0? Can you send me a link?
And thanks for all the great information. Appreciate the help.
HydroMx
You can get it here:
http://forum.xda-developers.com/showthread.php?t=2776515