Is it still a big "no no" to use CWM on the XL? I remember when I first got this phone we were not supposed to use it? From what I can tell all the ROM's still say flash in TWRP. The thing is I prefer using ROM Manager especially considering ive paid for it. GooManager is a just a bit lacking to me. If i do have to use TWRP it's not such a big deal, but since I'm getting a replacement phone it might be the perfect time to switch back.
I'm looking at using this one (http://forum.xda-developers.com/showthread.php?t=2240660).
Thanks guys.
kyleallen5000 said:
Is it still a big "no no" to use CWM on the XL? I remember when I first got this phone we were not supposed to use it? From what I can tell all the ROM's still say flash in TWRP. The thing is I prefer using ROM Manager especially considering ive paid for it. GooManager is a just a bit lacking to me. If i do have to use TWRP it's not such a big deal, but since I'm getting a replacement phone it might be the perfect time to switch back.
I'm looking at using this one (http://forum.xda-developers.com/showthread.php?t=2240660).
Thanks guys.
Click to expand...
Click to collapse
Using software flashers isn't a great idea. (IE not flashing directly from within recovery)
TWRP seems to have more working features than CWM.
You can use it if you want, but beware that it may not work as well as TWRP. I'd use TWRP unless you absolutely can't. It works a lot better on this phone anyways.
Sent from my evita
That version of CWM is very stable, at least it was when I was using it. The only negative was that Viper ROM wouldn't flash with it because it terminates the install if TWRP isn't installed, unless it's been changed. Other than that I had no problems with Phil's CWM whatsoever. It's not your typical CWM. The way the touch interface works is different than TWRP and kinda cool. It will also restore TWRP backups, which is a nice feature. I only switched back to TWRP because it was the only recovery image I had on my computer after I ran the 3.18 RUU and I was too lazy to download it again, lol.
Sent from my One X using Tapatalk 2
I've been using the "official" CWM, ever since TWRP 2.4 and 2.5 were having so many problems: http://forum.xda-developers.com/showthread.php?t=2148909
Everything on this CWM release seems to work fine for me. I know everything on TWP 2.6 is working fine, I just haven't bothered to go back to it.
Notions that CWM is a "big no no" is based on very outdated info. This dates from back when CWM was not an official release, just a hacked port that caused some serious (and difficult to resolve) issues for some folks.
I use cwm also since twrp was giving me dramas.
I find cwm is more compatible with things.
I've never used CWM personally, I never saw a point as everything has worked for me with TWRP (provided I stuck with 2.3.3.1 until 2.6 came out). I guess it's just personal preference. I've only gone by other's posts in terms of things people have said, not being able to mount or wipe SD card or not being able to charge in recovery. But there certainly is a bug going from certain versions of CWM to TWRP causing FC on Dialer.
The only problem I've found with TWRP 2.6 so far is that it was far too easy for me to wipe my sd card accidentally today. Using advanced wipe and moving a little too fast. No backup either. Whoops.
Sent from my Evita
Related
Hey guys, ok so I am coming from two HTC Heros (CMDA Sprint)
Was running cyanogenmod on both (me and the wife) loved it.
Now that I have the E4GT, I went ahead last week and used ODIN to install LoStKernel.
Now it did give me root and I have used apps like rom toolbox and setcpu.
My main problem is it seems these samsung devices are a lot trickier to tinker with.
Basically I am looking to get Clockworkmod so I can flash roms and make nandroid backups.
From what I have read, I need a kernel that supports and/or has CWM in it.
I tried flashing CWM with rom manager, and it installed - but I have no option to backup/restore I can only flash a zip or clear cache.
There are SO MANY things posted in the development section and I do not know which kernels are the latest, best etc.
I need:
a) CWM/busybox
b) overclocking support
c) FULL stock functionality (no loss of wifi or something stupid like that)
From what I am understanding the kernel is included with a rom. But I can't flash a rom without CWM. So I am rooted but stuck with stock rom and it's kernel.
Confused, lol!
Can someone point me to a proper thread to get me CWM and a well supported ROM to install? Can I get CWM working fully on the stock kernel/rom?
If someone can point me to the right direction, maybe I can find a developer to donate to lol!
No love?
At this point I'm just trying to get cwm. Seems I may have already had it just didn't know it came with lostkernel and now I botched it using rom manager.
Sent from my SPH-D710 using XDA App
You can actually flash a new kernel with CWM in odin
Thats the easiest method
There are several, as for the best I dont know yet
Im still tinkering with my setup
I guess that's my main issue - I can't find one that has CWM, everything I am seeing is a ROM that needs CWM to install.
If I had CWM I'd be all set because then I can backup my setup and try new things without worry, but I don't want to use ODIN to try a kernel that CWM won't take, or isn't there, and then lose what I have ya know?
All set, seems I flashed a kernel that wasn't what it was supposed to be. I apparently flashed his earlier version (pre-LoStKernel) that did not have CWM5 it it.
Just used ODIN last night to drop in LoStKernel and kept root, but also have CWM5 now. After clearing my SD Card, made my first backup. 1.5GB, jesus! lol. Nearly my whole SD card... yes, it's from my old Hero, so, time to get a 32GB.
Hi everyone,
I'm sorry I'm quite new to this, and I'm afraid I've gotten myself somewhat stuck with my Nexus S. Yesterday I managed to root it, install superuser, as well as clockwork mod. Today I wanted to try a new rom and after some attempts, it seems I no longer have any working roms on my phone. After much searching with no luck, I turn to you guys for your expertise.
So I am able to see fast boot upon pressing the volume up and power buttons, and am certainly able to choose recovery and get into clockwork mod. Within clockwork mod I can mount USB storage, so I can transfer roms to the internal SD card. I've tried 3 or 4 roms, some say they install correctly, others not, and after trying to boot after any installation I simply get stuck at the google screen with the lock image at the bottom. The only things I have "deleted" is wiped the data and cache. I have no idea, but I think I may have erased the bootloader image or something else that I should not have that is required.
I have a i9020a model (non-4g model I believe), can you pleeeeeeeeeeeeeaaaassee help me!! I just want to get back to gingerbread 2.3.6, and my phone back up and running the way it was. I've become quite nervous after some searching with some saying a resistor mod is needed on the hardware!!
Your okay cause you can get into fastboot and recovery so don't worry. Maybe the rom you downloaded is not for your phone. Did you make a nandroid backup before flashing the rom? If yes then go into backup and restore from clockwork recovery to go back to stock.
Sent from my A500 using Tapatalk
If you can get to recovery, just flash the stock image FOR YOUR PHONE. Then you can go through and reroot..don't worry, you'll get the hang of it.
Sent from my Nexus S using Tapatalk
So my phone is not "bricked" as they say?? I'm not in big trouble?
I did not make a nandroid backup What kind of image am I looking for and how do I install it on the phone? I know my phone is of the variant i9020a, but how am unsure of how much more specific I should be looking for.
Looking at the following post: http://forum.xda-developers.com/showthread.php?t=1063664.
Should I try installing the Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader option?
Choose the latest 9020a version of the FULL ROM, which is what you have already have eyes on.
I've tried installing the file I mentioned above, but I get a status 7 error when trying to install, and the install is aborted.
Could I get some more assistance please? Can anyone point me to a correct, full rom? Or perhaps I'm installing it incorrectly, could someone be so kind to outline the correct steps to a proper install?
Edit: I think the above mentioned file is for a GSM model, I'm sure I have the CDMA version.
Also, somewhat good news. I managed to install the oxygen rom, but for the 4g version and installed fine with no errors, but I have no service. What does this indicate, as I still want to restore back to a factory version (non-4g) of gingerbread 2.3.6.
What CWM version do you have? Is it 3.0.0.0?
Also, if you have no service, it's likely that you downloaded a ROM with an incorrect radio.
Edit:
If you have CWM 3.0.0.0, make sure to download the latest version, found in this thread: http://forum.xda-developers.com/showthread.php?t=988686 (use 5023-cyan.img). You flash this the same way you did CWM previously, though in the terminal make sure you type out the 5023-cyan.img file name.
Next, download the stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664. Simply look for your phone version, and you'll find the correct software variant.
Maybe you've fixed your phone already; if not, I hope this helps!
I wish you the best of luck. Oh, and through problems like these, you come to learn a lot more about your phone. That's what I've found, at least.
At the thread you mentioned above there is a version with a different radio, you might want to give that one a try.
You also said that you only wiped data and cache, so maybe you should do a full wipe before. Not doing that can sometimes lead to problems.
Sent from my Nexus S using XDA App
To be brief, the phone is up and running as brand new! Thank you so very much everyone. It seems the error was with CWM, as I was able to install and boot a 4g oxygen rom on my phone, I went into rom manager, and at the bottom of the list was an option to upgrade to 5.x. Installed the CWM update, wiped everything and was able to install the factory rom, no issues, and everything works just as I remember
I have most certainly learned more about my phone, and I am going to look at it as a rather stressful learning experience rather than a mistake on my part.
But a sincere thanks to everyone once again, I posted this at like 4am here and had a response within a few minutes, I was pulling my hair out haha!
Flashing to stock rom will help you out. You can get stock roms from Internet simply by searching in Google...
Sent from my Nexus S using XDA App
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
I have noticed a couple of similar threads, but they're older. Pl let me know if a thread is available for my issue: I have flashed multiple roms on my VGS3 for months. Now I can't install a custom rom. I've flashed the stock root update, I've tried CWM, CWM Touch and TWRP, and I am unable to flash a rom that I want. I have tried six different ones, all newer roms updated within the last 30 days. It starts to read the update then it just stops and says "failed" or sometimes I get the unable to install system 7 prompt. Either way it's driving me crazy. I'm used to having the rom of my choice on my phone (this is your guys' fault LOL) and I'm stuck with the stock rom. I have checked, I'm rooted. I can use EZ Recovery and EZ Bootloader with no problems, I can flash different recoveries. I've heard there are other recoveries but I'm not familiar with them. Thanks y'all.
I would Odin back to stock and then root and flash clean. I have never had any problems like you are having. Had some issues flashing with twrp once but I flashed cwm and never had an issue since.
Sent from my SCH-I535 using xda premium
bbqsfire said:
I would Odin back to stock and then root and flash clean. I have never had any problems like you are having. Had some issues flashing with twrp once but I flashed cwm and never had an issue since.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I actually just did that this morning. Could it be an SD card thing? Should I maybe reformat? I'm looking at older threads and that come up a time or two.
Thanks tho, appreciate it. Like I said, never had any problems until two weeks ago.
curious... which recovery for the GS3 is best for the roms availible.
i keep seeing devs put up notes saying use CWM and not TWRP. mainly this seems to apply for the new cm11 builds. does the new twrp not work?
i just happen to like the ui of twrp.. and the fact i can name the files what i want... makes it easier to find my recovery. i have no issues with using CWM... used it for a long time before the s3
so which is actually better and more compatible with roms? will the touch version of CWM work?
please no bashing of the others... i realize everyone has a favorite... this is more a compatability question.
thanks
Newest twrp works just fine on ALL versions of android
Sent from my SCH-I535 using xda app-developers app
wolficus said:
curious... which recovery for the GS3 is best for the roms availible.
i keep seeing devs put up notes saying use CWM and not TWRP. mainly this seems to apply for the new cm11 builds. does the new twrp not work?
i just happen to like the ui of twrp.. and the fact i can name the files what i want... makes it easier to find my recovery. i have no issues with using CWM... used it for a long time before the s3
so which is actually better and more compatible with roms? will the touch version of CWM work?
please no bashing of the others... i realize everyone has a favorite... this is more a compatability question.
thanks
Click to expand...
Click to collapse
Mostly it just comes down to personal preference, however I've heard credible people swear that twrp is more reliable for this phone.
I still use cwm though because I prefer the interface. I'm just more familiar with the layout.
All recoveries will work across all roms, except philz touch recovery, at least until it's updated.
Sent from my SCH-I535 using Tapatalk 2
Personally, I use TWRP. As long as you have one of the latest versions, 2.6.3.1+, you won't have any problems flashing ROMS. The older versions, including the one that is installed by the Toolkit, will have problems flashing newer ROMS.
I tried CWM and didn't like it. Even with newer versions, I had problems flashing some ROMs, despite the ROMs saying "You need CWM". Not to mention the interface is completely stoneage when compared to TWRP. I also had problems browsing any external storage (USB OTG or even ext SD Card).
cool thanks guys
exactly the information i was looking for
Sent from my SCH-I535 using Tapatalk
Twrp works with all roms now... It's my preferred recovery.
Use this Aroma File Manager
Works for all recoveries.
http://forum.xda-developers.com/showthread.php?t=1646108
Sent from my SCH-I535
I got a soft-brick from flashing CM11 with the latest TWRP. Worth noting.