Database Users

Messed up. Can't find a resolution.

Hey all,
I have flashed DJ05, rooted, and installed the Voodoo5 lagfix kernel/JT's super clean ROM via ROM Manager.
This morning, I attempted to install extra fonts using ROM Manager and the device fell into a reboot cycle. I attempted to boot CWM to restore the last backup I made and after that several force close warnings would pop up and the phone would reset itself. (This is where my inexperience and lack of research comes in).
Using Odin, I tried to reflash back to stock DJ05 to start over. Not realizing that I should have removed the lag fix and reflash a different kernel before reflashing using Odin.
Now the device is in a continuous reset loop and won't boot any software at all. I have attempted to reflash CWM and at least get that to boot but nothing.
How bad is my device messed up? Is there any salvaging anything at this point? Is there a way to restore the MBR without CWM and get it to boot correctly? Command line? Anything?

Find a full di01 or dj05 odin flash and use that in odin. It will completely format and reload everything short of touching your sd card. This should in theory get you back to stock. In fact search the forum for "odin restore files to get you back to stock"
SCH-I500 - DL09/Deodexed/JT1134 12.30/Darkstar

I tried reflashing using the stock DJ05 files and it still is in the reset loop. It shows the SAMSUNG screen, then the screen where it shows the /data and /cache partitions being formatted, then resets again.
Could there be something wrong with the /boot partition? Is there a way to restore that partition?

I know it seems redundant but try it with the di01 odin from adrynalyn
SCH-I500 - DL09/Deodexed/JT1134 12.30/Darkstar

Also make sure you use the PIT while flashing the stock images - that will ensure that voodoo is completely removed in the process.

I did that to my first Fascinate and I was never able to fix it, despite several, and I mean several reflashes and methods. Brought it to Verizon and they gave me a replacement. Sorry to be the bringer of bad news
Sent from my SCH-I500 using XDA App

If flashing DI01 stock doesn't work by itself, doing a Master Clear and flashing DI01 again might work. If you still can't get your phone to launch, it's probably time to go with ringleader's solution.
Sent from my SCH-I500 using XDA App

Adrenalyne's DI01 reflash worked! Thanks for the help!

Chewy1576 said:
Adrenalyne's DI01 reflash worked! Thanks for the help!
Click to expand...
Click to collapse
Welcome brother should be able to flash the dj05 odin over that now and be good to go again.
SCH-I500 - DL09/Deodexed/JT1134 12.30/Darkstar

why does this happen?

After I odined back to stock like 2 times, I flashed bionix. At first I had to push the froyo jl5 kernel with voodoo because rom manager couldn't install cwm. The everytime I reboot my phone, settings reset. Why?

try the KA7 kernel w/Voodoo and see if you get the same result.. any reason you want to use the JL5 kernel that Supercurio stated causes some problems in the OP???

dont' use cwm just flash through recovery wipe completely first manually,

helikido said:
After I odined back to stock like 2 times, I flashed bionix. At first I had to push the froyo jl5 kernel with voodoo because rom manager couldn't install cwm. The everytime I reboot my phone, settings reset. Why?
Click to expand...
Click to collapse
Sounds like you have some gremlins in your phone. I had a market issue that I tried everything on, and I mean everything. So, for kicks I installed the TW version of bionix and it fixed it right back up. Give it a shot. There's usually no clear answer for these things, but I always keep a version of rom manager and titanium backup on my external sd card for quick flashing. Shoot me a PM if your phone still gives you grief.

[Q] EB01 - Application not remembering preferencess

Hey folks, I'm hoping one of you can help me out with an issue that just cropped up on my phone. I've been running EB01 since it's release and have had no issues whatsoever except for today when I noticed my apps (Titananium Backup, Tapatalk, Root Explorer) we're remembering preferences anymore and/or every time I exit from them and launch again....it thinks it's the first run again.
Did something hose up my permissions/ownerships? Only think I did recently was flash the de-binged browser via CWM.
Any ideas??

What are you running? It may be a permissions problem. Have you tried uninstalling it and reinstalling it?

I'm having a similar issue. Help!
jpolzner said:
Hey folks, I'm hoping one of you can help me out with an issue that just cropped up on my phone. I've been running EB01 since it's release and have had no issues whatsoever except for today when I noticed my apps (Titananium Backup, Tapatalk, Root Explorer) we're remembering preferences anymore and/or every time I exit from them and launch again....it thinks it's the first run again.
Did something hose up my permissions/ownerships? Only think I did recently was flash the de-binged browser via CWM.
Any ideas??
Click to expand...
Click to collapse
I was just about to start a thread about this. I'm having the same problem. I upgraded from blackhole 4.1 (DL30) to Superclean 2.2 EB01 with voodoo lagfix. I got the red CWM flashed via odin and proceeded to install the EB01 modem and the superclean 2.2v (EB01).
The first time I flashed was a disaster, there were issues with Odin completing the flash, so I had to do USB pulls about 4 times (which ended up giving me full "light blue" screens during download mode at times).
After getting Odin to cooperate, I was able to flash the Superclean 2.2v (EB01), and then I restored everything from Titanium Backup, which worked fine until I restarted the phone or left it alone for a couple of hours. Everything would force close (like ADWLauncer Ex, forcing me to use ONLY TWLauncher) and all my preferences were lost. Like gmail would have to resync as if it were new, all the EULA dialogs would come up (like in android market), my trillian profiles were all lost, if i turned off haptic feedback that would turn back on, my ringtones would go back to the defaults, etc.
So I read some other thread in the Development section which said to reflash, and do not do any restores at all. So I reflashed with Super clean 2.3v (EB01), but it happened again, all my preferences would be lost. I also tried to do "fix permissions" from RED CWM, but it just ran for like a fraction of a second and didn't seem like it did anything, as the problem persisted.
I'm planning to go back to DL30 or even DL09 to see if my phone functioned properly or not.
If anyone has a solution to this problem please help!
- Superclean 2.3v (EB01)

I'm thinking it has something to do with flashing either the De-Binged browser or the new market update. Maybe something in the framework-res is getting hosed up?
I just did a wipe and reflashed plain old EB01 and I'm not going to flash any changes and see if the problem comes up again.

emortio said:
I was just about to start a thread about this. I'm having the same problem. I upgraded from blackhole 4.1 (DL30) to Superclean 2.2 EB01 with voodoo lagfix. I got the red CWM flashed via odin and proceeded to install the EB01 modem and the superclean 2.2v (EB01).
The first time I flashed was a disaster, there were issues with Odin completing the flash, so I had to do USB pulls about 4 times (which ended up giving me full "light blue" screens during download mode at times).
After getting Odin to cooperate, I was able to flash the Superclean 2.2v (EB01), and then I restored everything from Titanium Backup, which worked fine until I restarted the phone or left it alone for a couple of hours. Everything would force close (like ADWLauncer Ex, forcing me to use ONLY TWLauncher) and all my preferences were lost. Like gmail would have to resync as if it were new, all the EULA dialogs would come up (like in android market), my trillian profiles were all lost, if i turned off haptic feedback that would turn back on, my ringtones would go back to the defaults, etc.
So I read some other thread in the Development section which said to reflash, and do not do any restores at all. So I reflashed with Super clean 2.3v (EB01), but it happened again, all my preferences would be lost. I also tried to do "fix permissions" from RED CWM, but it just ran for like a fraction of a second and didn't seem like it did anything, as the problem persisted.
I'm planning to go back to DL30 or even DL09 to see if my phone functioned properly or not.
If anyone has a solution to this problem please help!
- Superclean 2.3v (EB01)
Click to expand...
Click to collapse
I'm having the exact same problem. I've been all the way down to DJ05 to see what happens, and when I come back to superclean 2.2 voodoo-ed, I get force closes on everything the first time I restart - that issue was due to the new feature froyo added "automatic restore" in settings > privacy. I got that taken care of by uninstalling all apps.
However, when I restart now, my entire phone defaults back to cleared data. I'm talking every setting that I could think of (usb debugging, sound, brightness, contacts, security pin cleared). I don't get it at all. Everything else has been working right though.
Just thought I would share - I'm kinda still in limbo till I figure out what I should do.

brettdacosta said:
I'm having the exact same problem. I've been all the way down to DJ05 to see what happens, and when I come back to superclean 2.2 voodoo-ed, I get force closes on everything the first time I restart - that issue was due to the new feature froyo added "automatic restore" in settings > privacy. I got that taken care of by uninstalling all apps.
However, when I restart now, my entire phone defaults back to cleared data. I'm talking every setting that I could think of (usb debugging, sound, brightness, contacts, security pin cleared). I don't get it at all. Everything else has been working right though.
Just thought I would share - I'm kinda still in limbo till I figure out what I should do.
Click to expand...
Click to collapse
I wonder if it has to do with the type of EB01 we're using or the CWM. I flashed CWM red via Odin, rather than updating via Rom Manager or update.zip. Also I used the EB01 Walkthrough in the fascinate developers section, the link is:
http://forum.xda-developers.com/showthread.php?t=948722
***UPDATE***
I resolved the problem... I think. I noticed there was a difference in the file names of the EB01 Modem in the walkthrough link I provided on the last line of the paragraph above and the EB01 Modem given in the original EB01 stock thread (http://forum.xda-developers.com/showthread.php?t=948679). I flashed with the eb01a_modem.tar given in the stock thread and then upgraded to Super Clean with Voodoo (v. 2.4 as of this writing). The market DID restore all the apps, before I was able to stop it, but after I restarted, there were no force closes nor were there any loss of preferences. I hope the modem issue was what was wrong...

Started doing it again this morning. This time I did not flash any mode via ROM Manager. Only things I did was de-bloat using Root Explorer and Titanium Backup.
Not every app started forgetting preferences, some still reemebered. Any of the devs have an idea of what's going on here? I'm running the plain old, fully-bloated EB01 ROM. No voodoo, no de-odexed, or anything like that.

I think it's a dbdata partition issue. I can't say how to fix because it's above my paygrade, but you may have to wait until it is officially released.

jpolzner said:
Started doing it again this morning. This time I did not flash any mode via ROM Manager. Only things I did was de-bloat using Root Explorer and Titanium Backup.
Not every app started forgetting preferences, some still reemebered. Any of the devs have an idea of what's going on here? I'm running the plain old, fully-bloated EB01 ROM. No voodoo, no de-odexed, or anything like that.
Click to expand...
Click to collapse
Try the Odin back to stock...DI01, wipe everything. Reroot and and get cwm. Then ODIN EB01 Modem Tar followed by super clean 2.4 install through cwm. Be sure to wipe data and cache before flashing super clean.

I there a reason I have to go all the way back to DI01, or can I use any All-In-One Odin package that writes the ROM, Kernel, & Radio?

jpolzner said:
I there a reason I have to go all the way back to DI01, or can I use any All-In-One Odin package that writes the ROM, Kernel, & Radio?
Click to expand...
Click to collapse
I suggest that typically before anything else b/c it seems to help most. I've never experienced these issues but many suggest this is a viable method to remedy certain problems. Don't see why you couldn't try the odin DL09 all-in-one and wipe the hell out of it and try again. Good Luck.

Is the corruption in the dbdata partition caused by an older version of CWM or a problem in the EB01 ROM itself?
Is it safe to go back to EB01?

jpolzner said:
Is the corruption in the dbdata partition caused by an older version of CWM or a problem in the EB01 ROM itself?
Is it safe to go back to EB01?
Click to expand...
Click to collapse
I believe it's currently inconclusive. There is speculation about exactly what causes it hence the reason I suggest wiping everything and then flashing the most recently provided stuff. That way it'll narrow things down. Someone can correct me, but if you odin back to stock, I'm 99% sure super cleans 2.4 voodoo kernel includes the new cmw. I was on green cmw unitl I flashed the seperate voodoo kernel posted by jt. I haven't had any issues.

Its almost certainly dbdata corruption. The cause is...yeah questionable. Seems most common with voodoo with the current hack being used to get it working with froyo.
Sent from my SCH-I500 using XDA App

I've never run Voodoo on my phone, but I did my initial install of EB01 with one of the older "Green" CWM versions.

adrynalyne said:
Its almost certainly dbdata corruption. The cause is...yeah questionable. Seems most common with voodoo with the current hack being used to get it working with froyo.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Any other suggestions or fixes?
I went all the way back to DI01, then flashed to EB01 using an Odin All-In-One and now 48-72 hours later, my apps (most notably Tapatalk, Root Explorer, and Titanium Backup) think it's the first time they've run every time I launch it.
Shouldn't have going back to DI01 fixed the corruption since it reformats the ROM partition? Also, something I notice was that flashing to DI01 or EB01 using odin did not get rid of the new CWM Recovery.
Would running the permission fix correct the issue?

jpolzner said:
Any other suggestions or fixes?
I went all the way back to DI01, then flashed to EB01 using an Odin All-In-One and now 48-72 hours later, my apps (most notably Tapatalk, Root Explorer, and Titanium Backup) think it's the first time they've run every time I launch it.
Shouldn't have going back to DI01 fixed the corruption since it reformats the ROM partition? Also, something I notice was that flashing to DI01 or EB01 using odin did not get rid of the new CWM Recovery.
Would running the permission fix correct the issue?
Click to expand...
Click to collapse
No...are you running voodoo? And what rom are you using?

EB01 Fully Bloated, Non-Voodoo Kernel
Baseband version: S:i500.04.V.EB01
Kernel version: 2.6.32.9
Build number: SCH-I500.EB01

http://forum.androidcentral.com/ver...roms-w-root-new-clockwork-updated-2-15-a.html
Try This...
This will hopefully repartition and clean dbdata corruption. BTW, I couldn't get 2.2 to run on my phone until I odin flashed a ROM which allowed me to then flash Adrynalyne's 2.4.
DI01, DJ05, DL09 did not work for the fix. Eclair worked fine, but Froyo would not work until I flashed a 2.2 odin.

Do I need to check the "Re-Partition" option in Odin when flashing or does it do it automatically?

Guess I screwed something up :O

So I was trying to go from comrom to OMFGB nightlies, and didn't know you have to go to OMBG first. When I tried to do that. I odined the ED05 modem, then flashed OMFGB, then the GAPPS. It wouldn't work, and then I read I had to flash a new kernel, so I flashed the Glitch high leakage. Then it started to work, but after it went to the boot screen, it went to a new CMW, blue, and tried to install GAPPS? I think that's what it was doing, but it went really quickly, and said something like it couldn't mount the sd card, which is weird. So I took out the sd card, and it said waiting for mount, or something similar. I put it back in, but it wouldn't work. So then, I flashed back to UKB with the pb&j kernel, to see if I could get things going from there. It booted fine, but when I tried to just flash OMFGB, it would go to the boot screen, and then go back to CWM. So I tried to go back to UKB, and then it did the same thing, didn't change the boot screen at all (so now it's stuck with Galaxy S Cyanogen mod boot screen). I tried to flash OMBG then, but it was still going back to CWM. I'm thinking about odining the eclair package, and then trying from there. What do you think. Oh and usually I go to android central, but they don't have OMFGB nightlies there, so here I am.
TL;DR: I flashed a bunch of GB stuff in what I assume to be in the wrong order, now I'm stuff. Help me?
EDIT:After flashing a bunch of stuff, I don't remeber what or what order, just that the Glitch was last, I managed to get it to boot, first with a glitch boot screen, then the android boot screen. I'm not sure what I'm on, I think it is OMGB, at least that is what the widget says when I booted it up. I'm really confused. Anyways, I think I got it.
EDIT2:Nope, stuck at the boot to CWM loop. I'm going to try to go back to UKB (froyo) through that sticky in dev
EDIT3:Well I'm waiting for it to download, so what I did that worked was flash OFGB in red CWM, weird, but it worked. I'm leaving it at that for now, cause nobody is replying.

While I'm glad you got things to work, you should probably start from scratch if things start to get weird again. I highly recommend this thread as the proper way to go from CM7/MIUI/OMFGB back to stock, and from there back to whatever you want: http://forum.xda-developers.com/showthread.php?t=1124391
Remember that when you flash stock DL09 or EB01 or ED05, you also have to have the atlas 2.2 pit file and "repartition" checked in ODIN.
Finally, while you still have things working, I recommend you do a nandroid backup. If you need to go all the way back to stock before coming back to gingerbread, you can do an Advanced Restore > Data Restore in order to get your apps and such back pretty painlessly.

Yeah thanks, that's the sticky I was talking about. I didn't know about the re-partition button having to be checked, thanks for that And the Data restore is through CWM? I assume so. And for that, I just need a regular nandroid backup?

Yes, in CWM you can choose backup and restore, and then do a system backup.
When you want to go back to a given setup (i.e. your apps, widgets, etc.) you can do an advanced restore where you choose to restore just data, and not the whole nandroid system backup.

That's pretty cool, I never new about that. So I tried the *228 1 and 2 thing, cause I couldn't download the beta swype, and I thought it I needed too, but it said my phone couldn't be activated, and to try again, then the I lost all signal. I rebooted, and it came back, but I couldn't activate it again. It's being weird still, and in the morning, I'm starting over like you suggested. I'm still receiving calls though, and I get good connection. For the morning, I was wondering if I could just check to see if I have everything I need. I have:
CI500_VZW_ED05_FROYO_REL.tar.md5 from the thread you posted for odin
OMGB 1.2.0
OMFGB nightly build 7/21
Glitch High leakage v11.1
The CWM for all roms (red)
lithid gapps (unless you think the other gapps is good)
and I think that is it. I don't have the atlas 2.2 pit file, can I just search here for that? Thanks for all the help
EDIT:Found the atlas 2.2, and I use that at the same time as the md5 file, right?
EDIT2:Okay, I tried to do a nandroid backup, but with the CWM recovery 4.0.1.0 (I think that's what it is), it didn't show anything, like it said backing up system, then it didn't show what part it was backing up, and the status bar stayed blank, then it moved on to data after a while, and that. It said it failed to back up sd-ext, which I'm guessing is why it wasn't working properly. I'm doing the odin restore to froyo, and if someone could tell me the correct order to install/flash/odin stuff to get to the OMFGB nightlies, that would be amazing!
EDIT3:I think I did it right. Odined to froyo, Odined the ED05 modem, Odined the CWM for CM7, flashed CM7, Rebooted, Flashed Glitch Kernel, then Flashed OMFGB nightly build 7/23. I still need to do gapps though.
EDIT4:I did gapps, and almost everything looks good. I can't activate my phone through *228 1, and when I try to set up my google account, it says it couldn't establish a reliable connection to the servers. And After I call to activate my phone, my service goes dead. I can still text and receive calls though
EDIT5:man, a lot of editing. I flashed OMGB 1.2.0 on top, and now I can set up my google account. Still not activating though :/

Unrelated question, how come sometimes my wifi and signal bars are grey, sometimes blue (I'm using cyanbread)? I think when they are grey, I'm not using signal? How do I make them blue?

s4 stuck on reboot

I'm running an S4 and have this very weird issue where after installing a custom rom, the phone would reboot and load the rom successfully, but if I ever reboot it, it never wants to go past the Samsung logo.
If I try entering TWRP and fixing permissions or factory reset, it just comes up with errors and fails. The only way around it is to format data, then reflash the rom.
But now I have a nandroid backup so everytime I reboot, I basically have to reflash the rom.. It's happened on at least 2 roms!
I've used the search function on the forums and found a thread was inconclusive so I've made this thread.
Thanks in advance
(This is my first Android phone too, so I'm not 100% familiar with all the different software and techniques, but I can definitely learn!)

Try flashing the ROM with the latest stock CWM. TWRP can cause issues.

Kesh09 said:
I'm running an S4 and have this very weird issue where after installing a custom rom, the phone would reboot and load the rom successfully, but if I ever reboot it, it never wants to go past the Samsung logo.
If I try entering TWRP and fixing permissions or factory reset, it just comes up with errors and fails. The only way around it is to format data, then reflash the rom.
But now I have a nandroid backup so everytime I reboot, I basically have to reflash the rom.. It's happened on at least 2 roms!
I've used the search function on the forums and found a thread was inconclusive so I've made this thread.
Thanks in advance
(This is my first Android phone too, so I'm not 100% familiar with all the different software and techniques, but I can definitely learn!)
Click to expand...
Click to collapse
go into the wipe options on twrp - go to advanced and select - cache, dalvik, system, data - swipe
then do a normal full wipe
reflash the chosen rom
power off rather than reboot
then power up
something gets fracked with the wipes somewhere and thats how i fixed it.
either that or flash philz recovery through odin and do a "new rom" wipe

Gotcher said:
Try flashing the ROM with the latest stock CWM. TWRP can cause issues.
Click to expand...
Click to collapse
For some reason, whenever I install CWM, it keeps getting stuck at "recovery booting" and once in maybe 30 times it works, haven't got it to work in a while.. Not sure what's happening, but if I flash TWRP again, it boots up fine. Am I doing anything wrong? Using Philz touch..
scottyf79 said:
go into the wipe options on twrp - go to advanced and select - cache, dalvik, system, data - swipe
then do a normal full wipe
reflash the chosen rom
power off rather than reboot
then power up
something gets fracked with the wipes somewhere and thats how i fixed it.
either that or flash philz recovery through odin and do a "new rom" wipe
Click to expand...
Click to collapse
This hasn't worked for me, and yeah, I can't seem to get CWM to like my phone..

Kesh09 said:
For some reason, whenever I install CWM, it keeps getting stuck at "recovery booting" and once in maybe 30 times it works, haven't got it to work in a while.. Not sure what's happening, but if I flash TWRP again, it boots up fine. Am I doing anything wrong? Using Philz touch..
This hasn't worked for me, and yeah, I can't seem to get CWM to like my phone..
Click to expand...
Click to collapse
try flashing the rom twice in succession. it will stick eventually but its just getting the right combo. these S4's are a right pain in the ass just now.
also another option would be downloading a rom with Aroma installer onto a micro sd and see if that gets you out of the problem. ive found on other devices ive had that a rom with Aroma can sometimes get you moving (id suggest Omega rom as a good solid base)

scottyf79 said:
try flashing the rom twice in succession. it will stick eventually but its just getting the right combo. these S4's are a right pain in the ass just now.
also another option would be downloading a rom with Aroma installer onto a micro sd and see if that gets you out of the problem. ive found on other devices ive had that a rom with Aroma can sometimes get you moving (id suggest Omega rom as a good solid base)
Click to expand...
Click to collapse
The rom I'm flashing (twice) now is Omega actually!
I'll see how this goes! Hoping it's okay!

..
try to install another rom clean & stable and do full wipe or trust me the best to turn the phone to default firmware.

Kesh09 said:
The rom I'm flashing (twice) now is Omega actually!
So are you suggesting I install Omega, get it run, then install Aroma installer and reinstall it?
Click to expand...
Click to collapse
no i just meant flash the rom twice IF it didnt have Aroma.
try GoldenEye rom from micro sd (obviously downloaded and placed on the card through a pc and put back in the phone).
Or as above - you might have to start from scratch and use Odin to revert back to stock and re-root etc again.
Although i said Aroma sometimes helps, being honest it was a rom with Aroma that started causing me a similar issue in the first place (Not Omega or Foxhound though)

No luck guys... I think I'd rather start from a stock rom too. When I created my stock rom backup, it was through nandroid and an CWM format, but CWM did work, it froze when it was checking for MD5 or something...
But now I'm trying to find the right firmware for my phone, is there any thing I need to look out for? Gt-i9505 from Australia?
http://forum.xda-developers.com/showthread.php?t=2265477
In that thread, there's two of them, I'm downloading the one closest to when I bought it which was June