Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Worse than I thought!
So It's worse than I thought... I gave up and re-flashed slim (ICS)... and the same problem still exists... boots up, looks normal, can't touch anything.... eventually it reboots....
Suggestions?
Would ODIN flash do anything different? I9000 bootloaders?
ScruffMcG said:
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Click to expand...
Click to collapse
sorry I'm just going to post twice so I can post to development...
yeah... 10char
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
Slimmed Down V10 by cbalt
Wipe Data/Factory Reset/Wipe Dalvik
Flash http://www.mediafire.com/?9p212pempybwnj3
Then Flash http://www.mediafire.com/download.php?bdjabcmobz6aw6k
Then Fix Permissions
Then Reboot
Click to expand...
Click to collapse
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
So you think w/bootloaders will help?
I have flashed every odin w/o bootloaders that I have access too and all get me stuck at ATT bootscreen....
Little hesitant to reflash my bootloaders since I was/am already on GB bootloaders, but if it might help I may have to do it...
I actually was on that JB version (but with the normal gapps b/c I wanted google now...)... now I'm on no version of anything hahah
takeoutttt said:
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
Click to expand...
Click to collapse
I met a problem. I do not know wether or not it is common. The phone will reboot by itself sometimes.
Do you have the same problem?
same here
seems as though many of the problems experienced by one are shared by the other
this is logical as they share many common points including the same partition and both jellybean derivations
I was having issues... accelerometer and audio issues.
All came out right as rain after flashing back to stock and reflashing
ScruffMcG said:
yeah... 10char
Click to expand...
Click to collapse
Related
Sorry if this has been asked before but I have searched and didn't find any answers.
I have never been able to restore a nandroid backup on the Galaxy S. I go through the restore procedure in recovery and everything seems to restore correctly, no errors reported, says restore successful, but when the phone boots up from recovery it hangs on the boot screen.
I've tried with lots of different roms/kernels. I've wiped thoroughly before restoring. I'm even trying to restore from the same version, i.e. JVH or JVP, always the same result. I'm not trying to restore between cm7/samsung roms or froyo/gingerbread or even different versions. An example is, I was on Darky 10.1re. I did a nandroid. I tried a few other roms (F1, GingerReal, Tweaky), tried to nand back to Darky's, appears to restore without problems until the reboot where it hangs on boot screen. Also tried to restore to nadroids of the above roms with the same results.
Can anyone tell me where I'm going wrong, I'm sure I'm missing something really obvious as nobody else seems to be having trouble with backups.
Thanks.
I could imagine it would be hard to point out what the exact problem is, unless someone has experienced this issue before. Which I haven't, sorry. Not on my SGS, nor on my SGS2. But it sounds like a compatibility problem to me. You say you've never been able to restore, have you had the same problem with Darky ROMs prior to 10.x, perhaps 9.5? Have you used Darky's Dark Core kernel along with it?
The same thing is happening to me. Used to nandroid restore on froyo and never had a problem. The last 2 times that I tried to restore (with Ginger 2.3.3 and 2.3.4) I had problems, both times with Criskelo´s rom and Darkcore Kernel. The restore begins normally but suddenly stops and there is no way to revert the semi-brick other than odin. BTW, I never use lagfix.
Used nandroid backup and restore successfully on gingerbread on both speedmod and galaxian kernels
Sent using geek power
I have same problem and i ended using nandorid backup which is very usefull.
I think this started at beginning of Gingerbread kernels using.
bitmaster2000 said:
I could imagine it would be hard to point out what the exact problem is, unless someone has experienced this issue before. Which I haven't, sorry. Not on my SGS, nor on my SGS2. But it sounds like a compatibility problem to me. You say you've never been able to restore, have you had the same problem with Darky ROMs prior to 10.x, perhaps 9.5? Have you used Darky's Dark Core kernel along with it?
Click to expand...
Click to collapse
Thanks for your suggestions. The first rom I installed after buying my Galaxy S was the current Darky one at the time, v10 rc something. Didn't try the older ones. At first I always used the Dark Core kernel, even with other roms. Still couldn't restore.
I've also tried a mixture of roms/kernels since then with no luck with the nandroid.
Could it be something to do with the recovery? I noticed different roms/kernels install a different recovery. Maybe it's only possible to restore using the same recovery as was used to take the backup? But if this was the case, surely other people would be having the same problem?
Thanks.
eggshaped said:
Thanks for your suggestions. The first rom I installed after buying my Galaxy S was the current Darky one at the time, v10 rc something. Didn't try the older ones. At first I always used the Dark Core kernel, even with other roms. Still couldn't restore.
I've also tried a mixture of roms/kernels since then with no luck with the nandroid.
Could it be something to do with the recovery? I noticed different roms/kernels install a different recovery. Maybe it's only possible to restore using the same recovery as was used to take the backup? But if this was the case, surely other people would be having the same problem?
Thanks.
Click to expand...
Click to collapse
Darky kernel had a restore problem once but they solved it now.
"Changelog 2.5:
Fixed Nandroid Restore through CWM" from darky forum.
yken said:
Darky kernel had a restore problem once but they solved it now.
"Changelog 2.5:
Fixed Nandroid Restore through CWM" from darky forum.
Click to expand...
Click to collapse
Yes I remember reading about that. That's what I put it down to in the beginning, but now it's been fixed and it still doesn't work for me. Not even with other kernels.
Well, it's not the end of the world I suppose. Just makes me more reluctant to try different roms as I'm too lazy to go through the whole odin/flashing/restoring process every time lol.
Thanks for your suggestions guys
With Dark Core kernel 2.7.x and 2.8 i have the same problems when i'm on rfs, backup function is ok but restore doesn't work. With ext4 conversion enabled backup and restore work as they should.
I've found a solution, just in case anyone else is having the same problem this is how I got around it.
I downloaded and installing the latest cwm using Rom Manager, so any backups are taken on 3.0.0.5. When changing roms I had to download and install the same recovery with Rom Manager and restore using the same 3.0.0.5. For some reason it only works when using rom manager. If I try to restore manually in recovery it doesn't work. If I try to restore with any other recovery version it doesn't work. So for me my nandroid backups only restore between the exact same recovery versions.
Sounds fairly obvious now, after thinking about it lol, but this has been giving me a major headache for weeks now.
I was wondering how perfect of a restore a CWM restore is.
I was running a custom GB ROM (rocket rom to be exact) and it was running flawlessly. I then decided I might try this new CM9 ICS ROM.
So to be sure about the CM9 install, I figure I'd install from a stock GB Rom. So I first did a CWM backup of my current rocket rom and then I restored an older stock (rooted) ROM. It seemed to work fine. Then.... after reading about the (few) issues wit this new CM9 rom I decided I'd wait a bit longer until a few more of the quirks are worked out.
So I then restored back my Rocket rom backup and even doing the flash cache and davik cache also. But now I notice my once working Rocket ROM is experiencing a lot of SODs.
So now I'm wondering how perfect my restore was. I really don't have a lot of apps or wireless networks and can easily restore my contact list. For that reason, do you think it'll help if I do a factory reset wipe and then reinstall everytyhing....or even go so far as reinstall rocket rom and then reinstall everything else manually without any restores...would that be really the best clean install....or would any of this not make a difference at all and wiping/reinstall a toatl waste of time and my prob is actuaully something else....
Thanks
I could do with knowing the answer to these questions too.
It would be good to get a detailed idiots guide to CWM, do's and don't's etc.
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
abhisahara said:
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
Click to expand...
Click to collapse
Sorry for the noob question.... what are SOD's?
adrok76 said:
Sorry for the noob question.... what are SOD's?
Click to expand...
Click to collapse
sleep of death, its the device not waking up properly from sleep
Pus it doesnt include efs, so its not complete backup. Handy if yu stay n same rom version, but thats likely not.
Squicky clean install is always best. Even only app and data recovering thought titanium can mess things up. Make it laggy and nonfunctional etc, Blegh
Sent from my GT-N7000 using Tapatalk 2
1. Install abyssnote42
2. Factory wipe, cache, dalvik
3. Restore your rocketrom backup
That's what i do with my rocketrom v23 backup
Zapped through server hops to XDA forums
its not perfect but its the best so far
all i can say is that cwm is the best and simple thing for me so far and if u get trouble some times while trying to shift from CM9 to normal ics or from gb to ics all I suggest is use redpill recovery from abbysnote
Richy99 said:
sleep of death, its the device not waking up properly from sleep
Click to expand...
Click to collapse
Yeah, mine does that from the clock on Dragon ICS 2.4 when charging it didn't use to, started since I started Dual Booting. 2.5 is out in the next hour or so according to the Dev page. Hope it fixes an otherwise awesome ROM.. Otherwise it's back to single booting and possibly on to Omega 12 until CheckROM is released..
Hi, first of all, I am new to Android devices.
I am having a problem with my AT&T Samsung Galaxy S Captivate. Games and apps seems to be running slower than normal after updating to Gingerbread 2.3.5. I have rooted my phone with Odin3 v 1.85, but it's been running slow even before the root. (In fact, I rooted the phone so I could install a lagfix, but I can't find one for Captivate I897 running on 2.3.5).
Anyway, I don't see the reason for games and apps to be running slow because I've heard that the Captivate has a pretty good GPU. Also, it's not like I've overstocked my phone's storage; I only have a few apps.
I've also made a short video explaining my problem further. Just search "slow captivate" on youtube. I should be the first video: "Really Slow Samsung Galaxy S Captivate - Fix?"
I've searched everywhere for a fix, but I can't find anything, so I came here. Does anyone have an idea on how to fix this, or at least reduce the lag?
Thanks in advance,
-xxTDGPainxx
I was seeing my phone work slower and slower on 2.3.6, I suspected that the developers of the apps I used were starting to develop for ICS and that maybe it was different enough that the updates were causing the apps to misbehave on older versions. I flashed to ICS just to see... and it was a great move, ICS on the captivate flies!!! I used SlimICS, I think it is the right way to go for Galaxy S phones...
xxTDGPainxx said:
Hi, first of all, I am new to Android devices.
I am having a problem with my AT&T Samsung Galaxy S Captivate. Games and apps seems to be running slower than normal after updating to Gingerbread 2.3.5.
Click to expand...
Click to collapse
Have you run any tools to see what is sucking up your phone's resources?
[email protected] said:
Have you run any tools to see what is sucking up your phone's resources?
Click to expand...
Click to collapse
No, I don't think I've checked that. What app do you recommend on checking that?
xxTDGPainxx said:
No, I don't think I've checked that. What app do you recommend on checking that?
Click to expand...
Click to collapse
I would say cpu spy
Sent from my SGH-I897 using xda premium
First of all, lagfix isn't really used anymore. Also, I would say to get rid of those task killing apps. They don't help and only add to your problems. A lot of the symptoms you encountered are pretty common, and I was expecting something much worse. You seem to be running a different kernel that allows overclock; which is it?
If all else fails, try ICS
Sent from my ICS Samsung Captivate
Hey
I tried to upgrade to ICS with Team ICSSGS [Android 4.0.3]. I followed a step by step tutorial using CWM to load "ICS_4.0.3_MR1-RC4.2_Captivate.zip" and installation seems to go well. But after I try to reboot my phone, the AT&T logo comes up, then the "Google" logo comes up, but it just stays stuck at the Google logo forever. ICS never starts up. I've tried removing the battery and then going back into CWM and restarting the process but the same thing keeps happening. What should I do?
xxTDGPainxx said:
Hey
I tried to upgrade to ICS with Team ICSSGS [Android 4.0.3]. I followed a step by step tutorial using CWM to load "ICS_4.0.3_MR1-RC4.2_Captivate.zip" and installation seems to go well. But after I try to reboot my phone, the AT&T logo comes up, then the "Google" logo comes up, but it just stays stuck at the Google logo forever. ICS never starts up. I've tried removing the battery and then going back into CWM and restarting the process but the same thing keeps happening. What should I do?
Click to expand...
Click to collapse
You flashed it twice, correct? Try wiping your data.
korockinout13 said:
You flashed it twice, correct? Try wiping your data.
Click to expand...
Click to collapse
Yeah, I've flashed it a few times. Each time, before I install it, I clear data/factory reset, clear cache, and davlik cache, but it's still just getting stuck at the "Google" boot screen. It's weird because every time, CWM says it installs successfully. I'm starting to think that the .zip I downloaded isn't so good...
Do you know of a good, stable version of ICS I could use instead? Maybe even the same one you're using?
Thanks
xxTDGPainxx said:
Yeah, I've flashed it a few times. Each time, before I install it, I clear data/factory reset, clear cache, and davlik cache, but it's still just getting stuck at the "Google" boot screen. It's weird because every time, CWM says it installs successfully. I'm starting to think that the .zip I downloaded isn't so good...
Do you know of a good, stable version of ICS I could use instead? Maybe even the same one you're using?
Thanks
Click to expand...
Click to collapse
This is the stable ics in my opinion, but i use aokp by sixstrings.... http://forum.xda-developers.com/showthread.php?t=1362092
Sent from my SGH-I897 using xda premium
Maybe don't wipe dalvik cache. That can sometimes result in that happening
Sent from my ICS Samsung Captivate
I gave up on ICS... I could not get it to work for the life of me and it was getting me extremely frustrated. I almost bricked my phone (I think).
Maybe I'll try it again if someone could link me to a detailed step-by-step tutorial to upgrading to ICS. I'm very new to the way android works and a lot of the tutorials are just plain confusing to me...
I ended up reverting back to GB 2.3.4.
Thanks for helping me out though.
Try reading some stickies, there are some great guides. There's also one in my sig.
Sent from my ICS Samsung Captivate
korockinout13 said:
Try reading some stickies, there are some great guides. There's also one in my sig.
Sent from my ICS Samsung Captivate
Click to expand...
Click to collapse
The one in your sig is about the best I've seen. Great job!
GUIDE TO INSTALL ICS, my way at least
Hey if you're looking for a good guide to putting ICS on your captivate I can help, The first time i tried ICS i messed things up and angrily decided that i wouldn't try it again and reverted back to 2.3.5, after carefully trying ICS again i love it so much. I won't ever go back to android 2.whatever.
I used CM9 ICS and have no issues or bugs. It's possible there are other better ICS roms but i prefer this one since i know for a fact that it works great.
http://forum.xda-developers.com/showthread.php?t=1363760
You'll need to download CM9 v17 and a gapps package on your SD card.
trust me, ICS is worth it, it's much better than 2.3
if you have titanium backup backup your user apps (NOT SYSTEM APPS/SYSTEM DATA)
Rom installation:
First things first always do a nandroid backup so you can go back easier, if necessary.
once thats done go to CWM recovery and do a wipe data/factory reset, wipe cache partition. once that's done install the CM9 .zip package for the rom.
IT WILL STOP HALFWAY THROUGH AND REBOOT ITSELF, as this is the new kernel being installed. while it's still rebooting pull the battery and let it turn off, reboot straight into CWM recovery.
once this happens go back to install you CM9 .zip file again. it will finish all the installation after that. once it finishes the install you should definitely install the Gapps.zip. it will load up your google apps (market,gmail,youtube,etc and your google account sync) if you don't load the Gapps you will not have very much functionality to your captivate.
once you have your google apps installed you should be ready to fly with a fast responsive captivate. Hope this helps, it took a few trial and error runs before i figured it out.
If you used titanium backup to backup your apps you can restore APPS ONLY!!! don't restore any system data/system apps!!!! it's very important that you don't do that.
that should be it. enjoy your ICS, it's much better than android 2.blah
Fastness: CM7
Sexyness: CM9
That's the answer to everything.
I have run aokp (my current) and doc's master. Both have been great!
I'm far from an Android guru but if you follow the directions, you will be ok. Both also have relatively supportive forums if you get in a jam.
Sent from my SGH-I897 using Tapatalk
Was wondering if it is safe to restore NAND backup that was made with CM9 on CM9 recovery?
1st i installed CM9
2nd i made backup
3th i want to change DPI but if something goes wrong can i back up via CM9 or do i have to flash GB and CM9 and start again?
I heard that CM9 is "safe"
I'm wondering too, since I wanted to try MIUI (based on CM9) from CM9, and was thinking of doing a backup if MIUI doesn't do it for me.
My guess is that it's "safe", since once you installed CM9 with the proper instructions (from GB and all), you have a proper CWM, buuuut a second opinion would help.
Neomatt said:
I'm wondering too, since I wanted to try MIUI (based on CM9) from CM9, and was thinking of doing a backup if MIUI doesn't do it for me.
My guess is that it's "safe", since once you installed CM9 with the proper instructions (from GB and all), you have a proper CWM, buuuut a second opinion would help.
Click to expand...
Click to collapse
True that. Well at least BackUp went fine but still have no balls to try restore it. And was wondering also that should i install abyssrecovery (red touch) or can i use stock CWM on CM9...
SoonHD2 said:
True that. Well at least BackUp went fine but still have no balls to try restore it. And was wondering also that should i install abyssrecovery (red touch) or can i use stock CWM on CM9...
Click to expand...
Click to collapse
In my opinion it's safe guys. The problem with the procedures in CWM was mostly caused by Wipes. Also the cf-root kernel was definitely something to be afraid.
Therefore in CM9s' CWM there's nothing harmful.
Sent from my GT-N7000 using Tapatalk 2
SoonHD2 said:
True that. Well at least BackUp went fine but still have no balls to try restore it. And was wondering also that should i install abyssrecovery (red touch) or can i use stock CWM on CM9...
Click to expand...
Click to collapse
Well, since MIUI didn't flash (I need to look more into this), I grabbed my balls and tried the whole backup + restore thing, with the "stock" CWM.
And it all went fine. No loss of data, booting up into CM9 like before, all set.
So it's safe.
Neomatt said:
Well, since MIUI didn't flash (I need to look more into this), I grabbed my balls and tried the whole backup + restore thing, with the "stock" CWM.
And it all went fine. No loss of data, booting up into CM9 like before, all set.
So it's safe.
Click to expand...
Click to collapse
The theory is true again!!!
I told you, there was nothing dangerous there.
Sent from my GT-N7000 using Tapatalk 2
Neomatt said:
Well, since MIUI didn't flash (I need to look more into this), I grabbed my balls and tried the whole backup + restore thing, with the "stock" CWM.
And it all went fine. No loss of data, booting up into CM9 like before, all set.
So it's safe.
Click to expand...
Click to collapse
Good to know. Luckily i dont need to use it yet coz romtoolbox dpi cjange went fine and os booted normally and dpi was changed
hi
so i was running NOVA HD 1.0.3 and i wanted to update to 1.1.0, but i didnt know if there was a different way except for flashing to i opened a post on XDA and got respone:"yes, u can just flash over the older version, if u dont wipe data all files will be saved" (thats what it said in short).
So i tried this, booted in latest CWM, wipe cache partition-> install from sd card-> NOVA HD V1.1.0, setup wizard and now i'm in a bootloop...
I took 128mb swap, heavy multitasking and europe gps, the rest i left defaulted as i remember. Then just the reboot after the install wizard, now its in a bootloop. I tried to make a NANDROID backup but when backuping the data it encountered an error so that was a no-go.
It is looping in the cm boot animation, after the lg-logo.
Do i just need to download different ROM and flash that, or back to lg stock software??
hoping for quick response cause i ****ing hate this, and i already lost all my data as it is now, i assume.
got it working now after full wipe
sn0wm4n said:
hi
so i was running NOVA HD 1.0.3 and i wanted to update to 1.1.0, but i didnt know if there was a different way except for flashing to i opened a post on XDA and got respone:"yes, u can just flash over the older version, if u dont wipe data all files will be saved" (thats what it said in short).
Click to expand...
Click to collapse
Refering to my answer in other post??? (http://forum.xda-developers.com/showthread.php?t=1781601)
I NEVER said that your data will be saved if you dont wipe.
When you're flashing a new version (update) of the same custom rom, you dont need a full factory wipe. Only Cache, Dalvik and Battery stats wipe are needed. But if you change, for example, cm9 to cm7, then you need a Full Wipe.
So before accusing people, be sure of knowing what you're doing. We are a community and we try to help other people.
When we say "Make a NANDROID backup" before doing anything stupid, it's not a joke. So before flashing anything new...try to solve your real problem...
Maybe you need to read more then only 1 thread to understand what is working or not when you're flashing new rom or kernel...
Sent from my LG-P990hN using xda premium