ive flashed back to Stock and then added different roms and everyone ive gone back to after stock, the settings of Anroid System in Settings is 0. the problem is that everytime I reboot the phone, all my settings aren't there anymore such as volume levels I previously set up or even the selection of keyboard - how can I fix this?
I've had this problem too.. a reboot of my phone on any custom rom always wipes my contact list, settings, messages, and apps but keeps my wallpaper and wifi and google info... I've always wondered why and if there's a way to fix it
Sent from my SCH-I500 using XDA App
what did you do to fix it?
jericho831 said:
what did you do to fix it?
Click to expand...
Click to collapse
that's what im hoping to find out
Sent from my SCH-I500 using XDA App
Corrupt DBdata... a nice odin and reformat should fix.. follow these instructions... http://forum.xda-developers.com/showthread.php?t=1124391 props to the author for the write up...
spyd3r05 said:
Corrupt DBdata... a nice odin and reformat should fix.. follow these instructions... http://forum.xda-developers.com/showthread.php?t=1124391 props to the author for the write up...
Click to expand...
Click to collapse
when I get to a computer will give this a try, thanks.. i've noticed an occasional "error mounting /data" when wiping in CWR but payed it no attention since everything works fine when it boots up on first install
edit: im not using any voodoo kernels or CWR so i don't think that ext4 formats gonna work for me.. however it seems my /data and /datadata corruption problems stem from a simple mistake: not booting into the stock rom once first before odin-ing CWR
Sent from my SCH-I500 using XDA App
Lol I'm going threw that crap now. Did u fix it?
Skip the ext4 part do all of the odin part of the tutorial
seemed to fix it for me.. time will tell if the fix sticks, thanks guys
edit: yeah I odined debloated/deodexed EB01, let it do its own data wipe on booting then powered off. I then odined CWR, booted straight into it, did the usual data/cache/dalvik wipe and flashed ComRom 2.0 and let it boot. I then booted into recovery and flashed the 2.1 patch right over it with no wipe. I let it boot up and presto!! no problems after 2 days, it even keeps data after reboots!! problem solved for me
tapatalked from my KangBanged Fascinate
Related
So the current iterations of cwm seem to have trouble working reliably with the newer froyo ROMs, and koush's recovery (although seeming to work correctly) is quite broken. So......
please find below a new recovery package that should work for any ROM for the fascinate, mesmerize, or showcase.
This is a "red" cwm recovery, and it will work with both voodoo and non-voodoo installations.
cwm-recovery-ALL.zip can be flashed via any cwm recovery.
if you are using odin, then use the cwm-recovery-ALL odin (.tar) package.
updated 3/29 - thanks to GizmoDroid for help with fixing fix_permissions script and root permissions typo that screwed up nandroid restores
updated 3/30 - fixed 'umount' typo - actually *fixed* fix_permissions this time - fixed odin/heimdall recovery attachment
Thanks, I just installed it. I'd rather not have a broken clockwork mod.
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Thanks! Good to have a fully working recovery again.
renf said:
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Click to expand...
Click to collapse
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Well I've had weird things happen when flashing stuff (I was using the "new-cwm.zip") , seemed like data being written where it shouldn't be? Just flashing theme files or own stuff I want to add, and I've had the following stuff happen:
Nuked my radio, had an unknown baseband and calls would never work, fortunately Radio Odin fixed it.
Had some /data apps disappear. Had some /data/data disappear. On reboot had Setup Wizard pop-up, even though I still had my Google account registered.
Hoping this new clockwork is completely safe. I suspected that clockwork was responsible for my weird happenings, so data-wiped and haven't flashed anything, so far fine functioning.
Using this is it easy to flash back to a prior set up, for me it would be back to dj05 w superdark and voodoo5?
Ive been holding off on froyo bc I need wireless tether, preferably unreported tether. But I really want to play around and see what the fuss is about. Ive downloaded every dl30 rom, havent installed one fearing I cant go back easily
Sent from my SCH-I500 using XDA App
/data on the fascinate is on /dev/block/mmcblk0p1
koush's recovery mounts /data as mmcblk0p2 (THIS IS OUR /DATA/FOTA. THAT'S BAAADDD)
under most circumstances this does not matter , because recovery.rc mounts data CORRECTLY before cwm gets to it, but there are circumstances where /data can be unmounted and then remounted, in which case cwm is gonna mount mmcblk0p2. If things get written there, at best you've got a **** load of FC's to deal with. At worst, a dead radio.
I've pointed this out to koush before, but was met with a "half-response", and to date it not been addressed (except for the recoveries that I've posted)
installed. When I go to do a backup, it gives the messages below. Backup seems to run fine though
E: missing bitmap progress_empty (code -1)
E: missing bitmap progress_fill (code -1)
Click to expand...
Click to collapse
Thanks, jt.
Copied to sdcard, booted into recovery, ran the program, keep coming back to green, no red.
ETA: Interesting. If I go to recovery from ROM mgr and try to load from sdcard, it does nothing, but if (while in ROM Mgr) I load from SDcard, it works. Got the blue screen, ran update, red appeared.
I likewise get the error message mentioned previously, but got it at install. Backup seemed to ahve run fine.
Installed like a charm, thanks jt!
sent from my fascinating XDA App
jackmei2 said:
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
Click to expand...
Click to collapse
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
thank you JT!!!!! I thought it was just me, Ive had to start over again with my data about 6 times now becuase of Clockwork either not restoring my backups or my phone freaking out once I restored the backup. Thanks again!!!
beenz said:
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
Click to expand...
Click to collapse
haha thanks... but he said it will be red and that it is not for voodoo, so that's what I wanted to double check since it does have the voodoo menus and all.
superchunkwii said:
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Click to expand...
Click to collapse
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
adrynalyne said:
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
Click to expand...
Click to collapse
The couldn't wipe properly bit me once already. Glad to have a proper recovery.
Sent from my SCH-I500 using XDA App
Thanks very much for addressing this issue.
For a while, I felt like a fresh n00blet, wondering what I was doing wrong. I tried flashing versions of supposedly compatible cwm's in different ways, always coming to the mounting errors.
Other than the errors from the missing graphics, this one works error free.
Scared to mess with this since i haven't experienced any problems with my current cwm stuff from pre dl09... Might just go ahead and do this tomorrow. For some reason I feel more comfortable using the odin method, so I can do all this over my Super Clean 1.0 with Neon GT theme and not have to do any data wiping or anything first?
So this makes no sense and I think its a weird coincident but as soon as I flashed this my beta version of swype started the force close loop..
EDIT: so weird, I had to uninstall the installer and swype itself using titanium backup and then download the installer and install again (had to do it all twice). Seems to be working again now tho..
Superclean 0.7.. aka Froyo.. Thanks devs!
I've been trying to get this on my phone since yesterday..i probably followed the directions over 10 times..and no matter what i do it just hangs at vibrant screen. i tried installing cm7 to see if i was doing everything correctly, it worked..then i tried with miui. big fail..i can't figure out what is going on
JinNguice said:
I've been trying to get this on my phone since yesterday..i probably followed the directions over 10 times..and no matter what i do it just hangs at vibrant screen. i tried installing cm7 to see if i was doing everything correctly, it worked..then i tried with miui. big fail..i can't figure out what is going on
Click to expand...
Click to collapse
Maybe it's a bad download. Try to redownload then reinstall it.
this would be the first time in life i'd have ever had a bad download..i'll try it..thank you
didnt work..lol maybe my vibrant doesn't like miui..sucks for me
Your downloading the rom, not the update right?
since its my first time flashing it..wouldn't MIUI 1.4.1 be the rom or is that the update? or is there somewhere i'd have to start off with
Sounds like whatever package you flashed doesn't have a kernel.
Segnaro said:
Sounds like whatever package you flashed doesn't have a kernel.
Click to expand...
Click to collapse
I've been at this all day..would you be so kind to point me in the right direction..
Go to mounts and storage and go to wipe system data and cache install rom then wipe factory reset
Sent from my SGH-T959 using XDA App
I know I followed directions to the T because I'm running cm7 and its my first time posting because I just couldn't figure this one out..grrr
Sent from my SGH-T959 using XDA App
JinNguice said:
I know I followed directions to the T because I'm running cm7 and its my first time posting because I just couldn't figure this one out..grrr
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Download miui_T959_1.4.1_2.3.zip
Go into clockwork. Format /system, /cache, /data . Flash the zip.
Segnaro said:
Download miui_T959_1.4.1_2.3.zip
Go into clockwork. Format /system, /cache, /data . Flash the zip.
Click to expand...
Click to collapse
done and currently hanging.. i'm confused
okay it works!!! which is weird because i went back to odin the cm7 kernal and i tried to go into recovery and it rebooted... weird method but i'll run with it
To preface this, I have followed all instructions to a T in all threads related to this, so here goes.
I was running CM7 test 7 and all was well, then I updated to build 8 and still ok but no call audio so I flashed the .13 OTB kernel and the phone began to bootloop. I have since been unable to reinstall CM7 and have ODIN flashed the EB01 official and the Atlas .pit probably 10-12 times through the whole cycle to try and reinstall.
Now that I have given up on that I followed the steps to return to UKB 2.1 and after flashing everything booted fine but my touchscreen would not work...so, back to stock again and I have stayed there........but
Now every time I reboot I have to reinstall all my apps(they are still installed but force clse immediately), none of them save any settings or data when I exit and return to them and my launcher is throwing out "Unknown data error" in notifications every time I boot. It also resets all homescreen and system settings to default at each reboot and has to resync all contacts also.
I am hoping that someone can help we with this and that I have not flashed this thing to its breaking point and am totally screwed. Someone have mercy and know something...and yes, I have searched and have found a few threads on the subject but none with any answers.
thanks I hope
If you have most of your contents from your sd backed up on your pc and you have a spare sd card I would try putting your spare one in, put com rom on it and TiBu on it as well
Odin recovery, wipe data/cache/dalvik.. voltage settings too if your recovery has that option
flash ukb 2.0 reboot completely and do the 2.1 patch
I'm not a dev, nor do I know if this will fix anything but I went to cm7 a while back before deep sleep was fixed and when I went back to com rom to hold me over I noticed even after doing the atlas 2.2 and eb01..i still had a bunch of cm7 files on my sd card and it (ukb) was rather glitchey compared to before I tried cm7...i don't think that these can conflict with anything on the rom but if you have a spare sd what's it gonna hurt you said you've flashed/ repartitioned multiple times..what's once more!
If you can't get it fixed I would just go to the newest cm7 its just about perfect, the bugs in it are minor..imo...good luck!
Sent from my SCH-I500 using XDA App
I've got everything up and running with stock once more and everything seems to be good finally.
Honestly after all this I'm a bit hesitant to flash CM7 lol. I may a suit on it for a couple days and decide. Thanks
Sent from my SCH-I500 using XDA Premium App
In the future, I would try the ext4 format utility from navenedrob right after you've returned to stock & before you flash any custom rom. It formats all partitions & may fix something overlooked by odin.
Sent from my SCH-I500 using XDA App
Allright, so there I was, running a rather stable Comm Rom 2.0 Voodoo Rom with the ED10 Kernel/Radio, and then I saw the thread on the OMFGB GB release, that I, of course, just HAD to have...
So, my first mistake was being impatient and not being able to find any installation notes, and pretending that I knew what I was doing by installing the rom via CWM mod.
Here's the rub, for some reason, whenever I did the 3 finger salute, it would pull a RED CWM that went orange when I applied update.zip ... because if I tried to install rom from sd card with the initial CWM boot, it wouldn't install anything, it would just error out unless I applied update.zip. After selecting apply update from zip, it would boot the orange CWM and allow me to install whatever I wanted...
So after applying the OMFGB rom, it showed the Fascinate/ Cyanogenmod 7 bootscreen, then went to boot loop. I panicked, pulled the battery, then backed up everything to my computer, and formatted the sd card in FAT32 with Windows 7 64 bit...
Shortly thereafter, I was using ODIN and the original "return to stock" files, and ended up getting into the stock OS.
Now I never show 3G or even 1x, and never pull data at all... when I go to place calls, it says that verizon cannot authenticate my phone... when I activate, it reboots and says everything was successful, but was noticeably a faster process than standard activation. Upon reboot, nothing improves... the os is there, everything shows that everything is fine, yet I am still not able to place calls...
Here is where it gets weird... My wife called me today, and the call came through... I received text messages, but still couldn't make calls... My bill is zeroed out, I'm not locked out that I know of, and I just want my phone working again...
Running out of ideas. I have flashed ED01 DL01 and even reapplied the stock .PIT in odin... I am going to try heimdall while I wait for help from here, but any quick help would be GREATLY appreciated...
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
riceje7 said:
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I will definately take this into consideration, but first i want to confirm that my phone is in full working order...
I appreciate the quick response, and hope to get some more love from the community.
Sent from my Transformer TF101 using XDA Premium App
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
xwhofarted said:
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
Click to expand...
Click to collapse
Trying this in about 15 minutes, will report asap...
Again, thanks for help...
Sent from my Transformer TF101 using XDA Premium App
when you say OP of CM7 thread, which one, there seem to be many CM7 threads... link please?
martyr2k6 said:
when you say OP of CM7 thread, which one, there seem to be many CM7 threads... link please?
Click to expand...
Click to collapse
also, lets assume I am completely as stock as possible... how should I get CWM on, and which version please link...
Also it miht be worth mentioning, though I think I already did... but when I go to activate my pjone, it says its successful, but then I go to make a call and it say that verizon annot authenticate my phone...
Here's a confusing screenshot...
Sent from my Transformer TF101 using XDA Premium App
Alright the issue is resolved, my main concern was whether or not I could use my phone for phone calls... after finally mustering up the guts to call Verizon, it turned out that the main problem in which I was experiencing was due to some form of typical midnight updates that big red does... apparently, my phone, missed some form of update that ended up de-authorizing my phone, but Verizon was able to help out, even at this late hour.
On the good note, everything went through just fine as far as flashing cm7... I just seem a bit conflicted with which rom is best. I guess its just a matter of personal preference, really. So far I prefer jt's rom just fine, but I might be switching back and forth between jt's and omfgb...
Thanks again for all the help folks, I appreciate it more than you could know.
Sent from my Transformer TF101 using XDA Premium App
xwhofarted said:
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
Click to expand...
Click to collapse
Not sure that I totally understand as to why I need to flash cm7 0713, then omfgb, then reflash cm7 0704... seems a bit redundant.
If you could clarify this for me and what improvement this offers, I would appreciate it.
Sent from my Transformer TF101 using XDA Premium App
Because omfgb apparently doesn't convert to mtd but cyan does, so you have to flash cm first
Sent from my SCH-I500 using XDA App
riceje7 said:
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
yup, that was your mistake. prior to flashing omfgb, you need to be on jt's cm7.
I'm too lazy to read all the posts but try flashing cm7 via cwm4. then, Odin back to stock using the right files and configurations. there's a sticky in the development section.
I have been having this problem even after doing everything correctly:
I wanted to try this ROM here:
http://forum.xda-developers.com/showthread.php?t=1195912
So I went back to stock using the ODIN files from here:
http://forum.xda-developers.com/showthread.php?t=734475
Then used the GB bootloaders from here:
http://forum.xda-developers.com/showthread.php?t=1117990
Installed CMW recovery. Once done, I used the zip to install the rom.
Now the phone boots up, goes to the bullet screen after sometime boots up again. Any idea guys?
go back into cwm and wipe data/fact reset
wipe cache
reboot system now
While in your bootloop get back into recovery and reflash the rom (I had to do this on Miui and Simply Honey when I first installed them)
why would they do that though? ^^^
vabeachfc3s said:
why would they do that though? ^^^
Click to expand...
Click to collapse
I don't know why it worked but it worked for me
Sent from my SGH-T959 using XDA App
Tried both the methods. Nothing seems to work.
I tried disabling vodoo and re-flash. The problem I have then is it just loops. When vodoo is enabled it goes to data parition not enough space issue.
Any help anyone?
Did you wipe date/factory reset, wipe cache, and wipe dalvik before flashing rom then wipe cache and dalvik and fix permissions before rebooting?
EDIT: Also I would backup everything on your SD cards. I got that not enough space on partition before and it ended up wiping my sd cards.
Sent from my GingerZen Vibrant using XDA Premium App
yes I did. Well looks like vodoo lagfix did its number on me. The internal data has been cleaned up , I am having MBR checksum errors and still doesn't work.
Also you can try this instead of odining back to jfd stock. It's worked really well for me when I've had major problems. Cleans everything up really good.
(QUOTE=Br1cK'd;16231313]Themes
I have posted about it in several threads, including my own, so I figured I would finally put it in a central location. This is my FTDNB method for starting with a fresh, clean phone, without any ghosts of roms past popping up to cause you issues.
Download this first, and flash through Odin with your standard 512 pit file
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Then when it reboots to the recovery screen, pull your battery, reinsert it and boot up to dl mode, and flash the following, with your same pit file, and selecting repartition in Odin this second flash only:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
The first link there is Eugene's Froyo That Does Not Brick, but it doesnt work that well as a driver. As an eraser its great though! The second link is the Froyo JK2 leak, with fixed recovery and already rooted. If the first one didnt, the second flash will definitely put you back on Froyo bootloaders.
Thats my whole secret to keeping a clean phone and wiping out any ghosts. You can proceed from there in your desired direction (back to ZD or GZ preferrably) in a safe manner. Its always worked for me to clear up any oddness, and literally takes 15 minutes tops once you have the files downloaded.[/QUOTE]
Sent from my GingerZen Vibrant using XDA Premium App