Database Develop

Is this a problem for others? Or am I doing something wrong?

I've tried an assortment of different costume firmware options. CM from bacon, up to the most recent. King's nexus2desire, etc. I've followed the directions as far as I know completely... But this always seems to happen, with either of the two roms.
I'll get some sort of random bug, and it causes a total freeze to where I have to pull the battery to restart it.. But then once I do that, the phone fails to reboot, in which I have to restore the firmware (factory data wipe + delete dav don't help).
It could be working fine for a couple of days, then all of a sudden this happens and screws everything up? Is this to be expected early on since it's development, or is there something wrong on my end?

wrong section, but yea, never happeend to me before.

I wasn't sure if should ask here, since it's based on the development roms here.
When I flash, I always do complete wipe (Factory, Dav, SD:ext, Batt, rotation), then reboot. I never wipe after flashing new rom. I'm using the newest radio, but have had these issues with all the previous radios too. Could there be a hardware malfunction possibly adding to this?

CDRacingZX6R said:
I wasn't sure if should ask here, since it's based on the development roms here.
When I flash, I always do complete wipe (Factory, Dav, SD:ext, Batt, rotation), then reboot. I never wipe after flashing new rom. I'm using the newest radio, but have had these issues with all the previous radios too. Could there be a hardware malfunction possibly adding to this?
Click to expand...
Click to collapse
Yeah something similar would happen to me. I said F it and had HTC send me a new one.

I have only had experience with CM 5, so if you install 5.0.4.1 and get this issue WITHOUT modifying the ROM with other mods, then you probably have a hardware fault. Warranty case that is.

Moved as not Android Development.

[Q] Restore to Stock

I was hoping to flash Paragon tonight, but it said to flash to stock first and I had a few questions.
Why do some ROMs have you flash to stock while others you can just flash through ROM Manager?
Is the Stock backup I made through ROM Manager sufficient as a subsitute for an Odin flash?
If not, are there any Mac alternatives out there?
I'm trying to get a good understanding of what I'm tooling around with so I don't brick my phone.
Thanks for the answers

I wish I could answer all your questions, I'm guessing it's because the recovery uses a zip file and it does not update everything that odin would. Anyways, if you need any help flashing to stock I know that the FAQ page of the cognition rom found here has directions.
cognition.theidiotshideout.net/mw/index.php?title=ODIN#One-Click_JF6

It is not needed but many think it is best. Depending on the rom you are on you have a cocktail of lag fixes and kernels. Flashing stock gives a clear slate.
You can disable lag fix, delete davlik cache, clear cache. You should be fine but you may run into issues. May.
What are you running?

It's some sort of ancient lore past down from priests of captivate forum antiquity.
As for 'cocktails of lag fixes and kernels,' there is no reason your cwm install can't format those partitions, particularly in light of the fact that it has built-in support for ext4. I don't know why people think the stock flash functions are particularly better at dealing with it.
Do yourself a favor, make sure you have a working download mode combo, purge your mind of the flash to stock FUD and obliviously commence to flashing one froyo ROM right over another. You'll be glad you did.

So if I'm hearing you correctly, it's more of a this will make sure you have no issues and are starting from a clean slate. It's not 100% neccessary to flash to stock before flashing a new rom?
Meanwhile, I was furiously trying to get Odin to work on an old laptop I scrounged up to no avail. Sometimes my need to tinker creates so many problems.
Thanks, guys!

wmbenham said:
So if I'm hearing you correctly, it's more of a this will make sure you have no issues and are starting from a clean slate. It's not 100% neccessary to flash to stock before flashing a new rom?
Meanwhile, I was furiously trying to get Odin to work on an old laptop I scrounged up to no avail. Sometimes my need to tinker creates so many problems.
Thanks, guys!
Click to expand...
Click to collapse
It is like a default disclaimer to flash stock. If you flash the rom and have an issue, one if the first things they will ask is did you flash stock. As mentioned almost all lag fixes use some form of ext 4 filing and most clockwork recoveries can now handle ext 4.
So in summation you do not need to, if you flash and get stuck in a boot loop you need to. I would make sure you can get odin up and running, and recognizing your phone in either case just so you know you can use it if needed

Absolutely no need at all to flash to stock
Would you install Vista in order to install Win7?
As long as you format everything in CWM before you flash a new ROM, then everything is a clean slate. It'll wipe your stock install, so why install stock first?
This and the 're-calibrating' your battery are the two biggest FUDs about Android.

[Q] Never Successfully Restored a Nandroid

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.

CM10 Helly Bean V10 -- Bootloop!

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

PLEASE. Need Urgent help! All apps FC's without warning, regardless which room

So recently my phone was behaving unstable, took a look at XDA, Flashed a new rom, like any other person here.
SO then i figure out that i cannot log into any third party apps, (facebook, instagram) and figure it may just be a bug with the app itself.
Upon further invetigation, i figure out that this happens on, ANY ROM! Even STOCK rom. i ran a restore back to it's original Stock room, flashed, fixed persmissions, wiped calvik,cache, i tried everything!
Everything is closing, nothing works, phone is slow, laggy, hot and everything is ****ED.
Please help a fellow out, i used roms on all my samsungs, nexus 5, now 6. I'm an experience user. Never had this problem before.

saitek1911 said:
So recently my phone was behaving unstable, took a look at XDA, Flashed a new rom, like any other person here.
SO then i figure out that i cannot log into any third party apps, (facebook, instagram) and figure it may just be a bug with the app itself.
Upon further invetigation, i figure out that this happens on, ANY ROM! Even STOCK rom. i ran a restore back to it's original Stock room, flashed, fixed persmissions, wiped calvik,cache, i tried everything!
Everything is closing, nothing works, phone is slow, laggy, hot and everything is ****ED.
Please help a fellow out, i used roms on all my samsungs, nexus 5, now 6. I'm an experience user. Never had this problem before.
Click to expand...
Click to collapse
Did you try flashing the latest stock rom including userdata,img manualy in fastboot, start with fastboot erase system then flash system, userdata, boot, recovery, cache and that should fix iyour problems.

did you wipe your data before flashing a rom? if not, you should have. if you wiped your data before flashing a rom, thus would not happen.

simms22 said:
did you wipe your data before flashing a rom? if not, you should have. if you wiped your data before flashing a rom, thus would not happen.
Click to expand...
Click to collapse
Ofcourse i do.
When coming from a other rom, then always clean flash.
When updates from the same rom, you can dirty flash.

saitek1911 said:
Ofcourse i do.
When coming from a other rom, then always clean flash.
When updates from the same rom, you can dirty flash.
Click to expand...
Click to collapse
when updating the same rom, you can USUALLY dirty flash, but not always. so, did you clean flash this time?

Do a factory reset, anyway.