I've got a Tmo GS5 that I've rooted, but am still running the stock rom. I see that the clockwork mod website lists some GS5 stuff, but the actual app won't recognize my phone. It also doesn't have it in the list for me to select, so I'm left with "Unsupported Device". Is the GS5 not supported yet? Is this normal?
I don't think I have actually heard of anyone running clockwork mod on the GS5 - TWRP seems to be doing just fine though, I'm running 2.7.0.0.
Philz recovery is working as well. Just do a google search for it.
I haven't used CWM in some time, but I strongly suspect that the poster above is correct. That it may simply be that CWM doesn't fully support the S5 at this time. You can do a forum search for the CWM support thread and no doubt find more information about the status there.
TWRP does support the S5 properly.. well maybe not encryption, but everything else. And lots of posters have stated that Philz is working fine on the S5 as well.
.
Related
I hope it's almost completed so we can start flashing some ROMs
I've never built a CWM binary before (CWM integration has been done my someone else on every other device I've developed for) and it requires a full CyanogenMod source tree - mine got corrupted so I lost a few hours doing a full resync.
CWM integration is a poorly documented black art - especially on Samsung devices.
I've got something compiling now, maybe 10% chance it works. If it doesn't I won't be touching it again until sometime this week, as a friend of mine is arriving in town in about an hour to visit.
Edit: It booted, but it acted like the VolUp key was stuck (just kept looping up through the menus) and it spewed a ton of errors
Edit 2: Somehow it's treating side-to-side tilt as up/down, and I need to move recovery.fstab somewhere else...
Right now I have it compiled and not spewing errors,however:
Our accelerometer spams /dev/input/event1 with a lot of crap. CWM treats this spam as keypresses, making CWM unusable. I need to figure out how to filter out event1 keycode input to get anything workable.
This is really interesting, please keep us posted! I'm really looking forward to a good custom ROM for my Galaxy 5
Atleast we got a good kernel already :d
Im using rj kernel for sgp 5.0, and its working fine. The games who had some lags after some time playing are runing smooth so far.
Rumirand and I are close - we probably would have it if I didn't have such a busy week.
His beta has a few issues from the looks if it - but he fixed the problems I had and I think my next github push will have fixes for his.
@Entropy512 - Thanks a ton for you efforts! Really looking forward to this.
Entropy512 said:
Rumirand and I are close - we probably would have it if I didn't have such a busy week.
His beta has a few issues from the looks if it - but he fixed the problems I had and I think my next github push will have fixes for his.
Click to expand...
Click to collapse
That's the open-source philosophy.
With r7 kernel, you can do full Nandroid backup and restore (system, data, cache and dbdata). There are issues yet, but hopefully will be fixed soon.
Sorry to bump an old thread, but this thread seems relevant, and I'd like to not make another thread for just the same thing.
QUOTE: "What's the status on CWM development for 5.0?"
What device exactly is this referring to?
I'm assuming this refers to the Samsung galaxy player 5.0?
CWM, that is clockwork mod?
Would the person coding this be connected with ROM Manager?
I read someone was working on a CWM for Samsung 5.0 and they seemed to be close to an answer or something...
I was wondering if you were affiliated with ROM Manager in some way and the clockwork mod recovery and its device list...
zBusterCB87 said:
Sorry to bump an old thread, but this thread seems relevant, and I'd like to not make another thread for just the same thing.
QUOTE: "What's the status on CWM development for 5.0?"
What device exactly is this referring to?
I'm assuming this refers to the Samsung galaxy player 5.0?
CWM, that is clockwork mod?
Would the person coding this be connected with ROM Manager?
I read someone was working on a CWM for Samsung 5.0 and they seemed to be close to an answer or something...
I was wondering if you were affiliated with ROM Manager in some way and the clockwork mod recovery and its device list...
Click to expand...
Click to collapse
ClockworkMod Recovery comes from the same guy who maintains ROM Manager, but they are NOT the same thing.
CWM's source code is published, so people can port CWM without Koush's involvement. Which is what rumirand and I did - we have CWM 5.0.2.7 working on the USA and International Galaxy Player 5.0 units at this point. (You necroed an outdated thread, we've had CWM working for a while now.) For CWM on a USA version, install my kernel, for CWM on an International unit, install his.
Thanks but I'm having problems.
Entropy, I have your Kernel installed and I can boot into the CWM-based recovery but ROM Manager doesn't recognize that I have CWM installed and won't let me do anything. Does this happen to you too?
I have really been having a HELL of a time trying to do things with this since support for this device is so scarce. I couldn't find anything about Clockwork Mod for this device anywhere. I searched for hours and kept hearing people referencing the xda developers site so I decided to look here and I installed your kernel hoping it would help and it does. But ROM Manager still doesn't recognize that CWM is installed and tells me to install it and gives me a list of phones which my device is not on and doesn't let me do anything until I install a version of CWM.
So is there an official port for CWM available that ROM Manager will recognize or is there only the ports contained in your and your friends kernels??
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water
Running stock everything, Android 2.2 froyo.tljl3. A few minutes ago I attempted to install CWM through ROM Manager. Everything seemed to work fine until I rebooted into the recovery to discover that it was still stock Android. So I tried it again, same thing. Phone is confirmed rooted and for some odd reason my flash_image is missing. It's not in system/bin, nor is it hiding in system/xbin. Just gone.
Is there any comparatively easy way to replace it and get a custom recovery working so I can do away with the stock OS, or do I need to restore the phone completely yet again?
Apologies if this has been posted before, my SGSII LTE shot itself in the head so I just wanna get this thing working to some extent.
Also, I feel it noteworthy to state that this is the Telus Fascinate (T959D), which apparently has some different hardware and may be relevant.
Check here instead ------------------> http://forum.xda-developers.com/showthread.php?t=1540809
Well, its safe to say I'm at a bit of a loss on this one. Even the great sea of information here and on Google can't quite explain whats going on here.
So I'm trying to flash TWRP over CWM 6.0.4.4 on my already rooted SGS4 from Verizon. I have installed roms in the past on this phone, specifically PAC-Man rom, which so far has been working well but like many others I was hoping to move to TWRP for my shenanigans. I'm already aware that nands made in CWM cant be used with TWRP and vice versa but that's not my problem.
I tried following the guide for installing TWRP using GooManager. Downloaded and verified it got the right .img file and allowed it to install until the inconspicuous popup indicating it was finished showed up. Just to make sure everything worked I hit reboot into recovery and as you would expect the phone restarted and "Recovery Booting" showed up in the upper right like always...only for CWM 6.0.4.4 to load up instead of TWRP. What gives?!
Any help would be much appreciated!
biglightbt said:
Well, its safe to say I'm at a bit of a loss on this one. Even the great sea of information here and on Google can't quite explain whats going on here.
So I'm trying to flash TWRP over CWM 6.0.4.4 on my already rooted SGS4 from Verizon. I have installed roms in the past on this phone, specifically PAC-Man rom, which so far has been working well but like many others I was hoping to move to TWRP for my shenanigans. I'm already aware that nands made in CWM cant be used with TWRP and vice versa but that's not my problem.
I tried following the guide for installing TWRP using GooManager. Downloaded and verified it got the right .img file and allowed it to install until the inconspicuous popup indicating it was finished showed up. Just to make sure everything worked I hit reboot into recovery and as you would expect the phone restarted and "Recovery Booting" showed up in the upper right like always...only for CWM 6.0.4.4 to load up instead of TWRP. What gives?!
Any help would be much appreciated!
Click to expand...
Click to collapse
2.5.0.2 is the most stable. This is flashable. It is from the twrp thread.
https://db.tt/YeZ3cp4c
Travisdroidx2 said:
2.5.0.2 is the most stable. This is flashable. It is from the twrp thread.
Thank you much That did the trick. Wish I knew what actually caused the issue with GooManager but hey, at least its working now! Although I'm still finding the Volume Down + Home key combo still boots it into ODIN instead of TWRP.
Click to expand...
Click to collapse
I'd like to start this thread in establishing that I am not familiar with how all this works, nor do I have any idea how to fix it, which is why I'm here. I only know the system info, such as version, firmware, etc.
In attempting to add cyanogen mod on my already previously rooted Samsung Galaxy Tab 2 7.0 gt-p3113, I watched a video that directed me to install clockwork recovery and root in a single bundle using Odin, (which I successfully did). I then proceeded to install cyanogen mod while in clockwork recovery, which it then told me to factory reset wipe all data before doing so. After going to the "main page" of CWM and resetting the device like it told me, I then went back to install cyanogen mod, only to have it tell me that CWM is out of date. I tried rebooting the device, but it would take me back to CWM, which im assuming means I deleted to OS on accident.
After all that, I finally concluded I'm stuck on an old version of Clockwork Recovery with no OS installed. I can access download mode, however when I'm not in download mode the device automatically boots up to the old version of clockwork mod, and I'm stuck there.
As I have no idea how all this stuff works and did pretty much everything from a YouTube video, I'm hoping a more experienced developer can help fix the problem and somehow help me regain use of my tablet. At this point I don't care whether I can get cyanogen mod installed or not, and I would appreciate all the help I can get.
Thanks
EvilPenguin42 said:
I'd like to start this thread in establishing that I am not familiar with how all this works, nor do I have any idea how to fix it, which is why I'm here. I only know the system info, such as version, firmware, etc.
In attempting to add cyanogen mod on my already previously rooted Samsung Galaxy Tab 2 7.0 gt-p3113, I watched a video that directed me to install clockwork recovery and root in a single bundle using Odin, (which I successfully did). I then proceeded to install cyanogen mod while in clockwork recovery, which it then told me to factory reset wipe all data before doing so. After going to the "main page" of CWM and resetting the device like it told me, I then went back to install cyanogen mod, only to have it tell me that CWM is out of date. I tried rebooting the device, but it would take me back to CWM, which im assuming means I deleted to OS on accident.
After all that, I finally concluded I'm stuck on an old version of Clockwork Recovery with no OS installed. I can access download mode, however when I'm not in download mode the device automatically boots up to the old version of clockwork mod, and I'm stuck there.
As I have no idea how all this stuff works and did pretty much everything from a YouTube video, I'm hoping a more experienced developer can help fix the problem and somehow help me regain use of my tablet. At this point I don't care whether I can get cyanogen mod installed or not, and I would appreciate all the help I can get.
Thanks
Click to expand...
Click to collapse
Well, I would say that may be a bigger problem ! Now what I think better for you would be trying to flash the stock ROM over to the device again I am sure you have your hands over the flashing. So head over to the sammobile/firmware section and try getting the stock ROM downloaded and flash it over your device.