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?
Related
FYI - I originally posted this in the JI5 thread in the dev forum, but it got lost in the action there so...
I installed the JI5 through Kies, no problems. Then rooted via the one-click method (not OCLF), installed the Mobile AP app, and deleted some bloatware. That's it.
Now I get forces closes when trying to adjust certain settings. I get this message:
The application Settings (process com.android.settings) has stopped unexpectedly. Please try again.
This only happens when I try to set the ringer volume, system volume, and brightness. Every other setting seems to work.
Anyone else having this problem? Any ideas on how to fix? Thanks.
WifiAP has a deodexed settings.apk, probably from JFD firmware. Post in the wifiap thread and see if they can help.
I thnk the only way to back out of that is to restore from rom manager.
Do NOT restore via Clockwork Recovery. I bricked as a result. Different kernel or some such thing...
Trying ODIN now to get back to stock.
pdefazio said:
Do NOT restore via Clockwork Recovery. I bricked as a result. Different kernel or some such thing...
Trying ODIN now to get back to stock.
Click to expand...
Click to collapse
i just restored over clockwork and it was fine...
pdefazio said:
Do NOT restore via Clockwork Recovery. I bricked as a result. Different kernel or some such thing...
Trying ODIN now to get back to stock.
Click to expand...
Click to collapse
It depends on *what* you were restoring to. Some of the custom firmwares (Bionix for instance) are built on JFD's kernel. JI2, JI4, and JI5 are using a newer kernel that the JFD stock kernel builds will not work with (and vice versa...custom kernels like Voodoo, JAC, Kingklick will NOT WORK with JI2-JI5).
Just gotta do your homework ahead of time.
Sounds like you installed the wrong MobileAP zip. Odin JI5 again or install the right one
This has nothing to do with JI5. I have the JI2 version of MobileAP on my Vibrant and there isn't anything wrong with it or JI5. Another reason why people like zipmongsrwerweg run off and say things like JI5 is a bad update.
Hello all,
Been rambling around the forums in ninja mode trying to gain enough knowledge to not mess up my phone before trying to mod it but alas best laid plans....
Anyhoo I was working to put the Froyo leak on my phone and everything was good till I did a cwm wipe of the phone and wammo it had problems. I managed to use Odin to get it back to barebones stock, lost my high score in Angry Birds too dang it.
Now that I am back to this point I tried to run the Verizin updates and it downloads and goes into install mode on reboot and it dies at Updating Modem section. At that point I saw I was rooted so I removed that and tried again, no dice amigo. Did a factory wipe, nothing. Cleared the cache, fail again.
If it helps its trying to do a dh12 to di01 update. Got any ideas?
When you went to stock did you flash the stock kernel and stock recovery as well? I had to do this when I updated to dl09
Good question and yes I believe I did, I followed this: http://forum.xda-developers.com/showthread.php?t=782204&highlight=return+stock thread to get the job done. Let me try it one more time.
Also I load the PIT file with each md5 correct?
Looks like I fixed it on the second time around. Not sure what I missed but the update went through. No worries. Might pay someone to hand hold my through getting DL30 on my phone cause even as an IT guy I'm missing something every time.
Strong thing is, once the DI01 update happens it actually doesn't find any other updates...wifi is off.
VZW pulled the DL09 update due to the e911 bug until it is fixed
Makes good sense. Sooo anyone wanna tutorialize me on how to de-crappify my phone? Its worth a donation from me.
You're on di01 right?
I would odin the dl09 package, then use cwm to flash super clean 2.2. Clean, debloated froyo goodness
Sent from my SCH-I500 using XDA App
Sounds good. The problem lies in me somehow fudging up the process at some point and having to set my phone back to stock again.
Where did you see this?
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
VZW sent a message to all Fascinate owners the other night acknowledging the bug and a fix being in the works. Why would they continue to push it out after that?
Sent from my SCH-I500 using XDA App
Well...
0123456789
New EA update is being pushed out.
Verizon told me to go to a store as some phones will not accept OTA updates. Seems stupid and like a lie, but whatever...
Atst44 said:
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
Click to expand...
Click to collapse
He's right. Google the source if you need it. Please don't take this response as me being snarky, I don't mean it that way.
I think the biggest issue people are having is not being careful and following the directions perfectly.
I was new two days ago and did this with only one hiccup.
1. I followed the Beginner's thread in this forum to get me rooted. First pass with Odin failed as the one click code didn't recognize the phone. 2nd pas worked. Trick was to just turn on USB debugging and plug in phone, do not then click the mount notification. Leave that off as USB debugging was all that was needed.
2. I installed Mod Manager and Titanium backup right after. This was part of the main directions and Titanium (though not mentioned) allowed me to save all my specific apps that had important data, like my 100% completed Angry Birds.
3. I then followed the directions in the developer forum for the How To.. install DL30 for Froyo. This scared me at first because the CW recovery stalled when wiping data. I waited over 30 minutes before getting the courage to pull the battery and start over. Figured its only deleting user data, should be ok. It was and then it worked the 2nd time without fail. I did reboot in normal recovery, but running the update.zip put it back into CW.
4. After that, I rebooted numerous times, checked all stock apps, upgraded firmware in camera, and used Titanium to add back my apps I bought or downloaded as well as restored my bookmarks and memo notes.
In the end I've had no bugs/issues as others have reported. Only functionality not tested is bluetooth as I don't use it for anything.
I hope this helps and if you are walking through it all again, I would be glad to help specific questions based on my experience.
I was DL09 stock OTA at first. I'd recommend getting rooted and using Odin to get the stock DL09 from these forums flashed before you try to put DL30 on. As a developer myself, it just makes sense to always put on builds that are in order of each other. So DI01, then DL09, then DL30.
0123456789
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
dlmcclou said:
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
Click to expand...
Click to collapse
1. Not freeze.. that makes it so app won't run. Backup with Titanium Backup is what you need I think.
2. What is EA28? I don't think the fascinate has had that build.
Just got an update EA28 any ideas what it does
Sent from my SCH-I500 using XDA App
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
Click to expand...
Click to collapse
Cool. Can anyone confirm this?
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.
I have had every android phone and am not a noob...but this voodoo/froyo/cwm is irritating me...
Before flashing any rom, I always do a nandroid backup....well, I was on SuperClean 2.4 with VA green theme...then decided to make a backup and try miui... all was great, but now I am trying to go back to sc (to my backup) and I get the multiple vibrate and it just keeps bootlooping... What am I doing wrong?
Here is what I have tried:
-wiping data/cache
-wiping dalvik
-flashing cwm_froyo.zip
-disabling voodoo
-flashing superclean, then restoring my backup
-flashing superclean, then theme then restoring
-using green cwm
-using red cwm
(yes, I usually reboot in between steps)
I am puzzled because I have never run into this before, but had this happen once with sc...I was able to fix things with just using cwm and flashing a bunch of stuff then restoring, but have no clue for the life of me which sequence I followed...
Can anyone open my eyes to what I am missing? What's the best way to fix this? I know it can be done without odin. Thanks!!!
tats_06 said:
I have had every android phone and am not a noob...but this voodoo/froyo/cwm is irritating me...
Before flashing any rom, I always do a nandroid backup....well, I was on SuperClean 2.4 with VA green theme...then decided to make a backup and try miui... all was great, but now I am trying to go back to sc (to my backup) and I get the multiple vibrate and it just keeps bootlooping... What am I doing wrong?
Here is what I have tried:
-wiping data/cache
-wiping dalvik
-flashing cwm_froyo.zip
-disabling voodoo
-flashing superclean, then restoring my backup
-flashing superclean, then theme then restoring
-using green cwm
-using red cwm
(yes, I usually reboot in between steps)
I am puzzled because I have never run into this before, but had this happen once with sc...I was able to fix things with just using cwm and flashing a bunch of stuff then restoring, but have no clue for the life of me which sequence I followed...
Can anyone open my eyes to what I am missing? What's the best way to fix this? I know it can be done without odin. Thanks!!!
Click to expand...
Click to collapse
Not sure if this would be your issue, but are you using the CWM from the OP in this thread? :
http://forum.xda-developers.com/showthread.php?t=942021
it is called cwm-recovery-all.zip as opposed to cwm_froyo.zip
I think your CWM may be outdated.
I had a similar issue this weekend, in that I went to do what should have been minor surgery and ended up in the FC boot-loop hell that it sounds like you are in at the moment.
I battled it for about an hour before I said "bag it" and used odin to flash one step EB01 Superclean, then I manually put my voodoo kernel back on and then restored my backup, which landed everything exactly where it should be and the phone in full glory once again.
Was it a PITA? sure, but the end result was very worth the effort...
you can find the odin package you need to make this a breeze here.
pushing this will take you to the flavor of EB01 you desire, then you can move on from there, but this is a nice clean, straight-ahead method. There is not an option to go straight to JT's voodoo kernel for EB01, but you can make the leap prior to even restoring your apps via CWM, which will also be up to date using the odin method above.
GL!
Having a backup is always a good thing. I second the ODIN as a fix for your issues, you're just going to get frustrated trying anything else at this point. There's a great resource post Here. Five minutes with ODIN, and then a CWM restore. Really couldn't be any easier then that.
Thanks all!!!! I saw Adrynalyne's post about the triple vibrate, which means something is crashing. I am not sure what it was, but....
I got it back to normal, by wiping, flashing sc again, then the va theme...booting in between the flashes and then just restoring data. Voodoo was disabled all this time. I just don't like using odin...but if it happens again, I will do it, just because something is being stubborn. Thanks again. Hopefully this experience helps someone else as well.
It could be a dbdata position issue.
Try flashing an eb01 odin tar.
So basically, I tried to help out my friends continuum and ended up with some problems.. these are the exact steps I took..
-Flashed adrynalynes test4 cwm file via odin..
-Put yellow_update.zip on the sdcard, and updated it through that, which seemed -to work
-Flashed within CWM, IMNUTS 530 PBJ voodoo kernel, and rebooted
-Converted successfully as stated by the robot voice, but after it was done I had both the scrambled screen issue, as well as I was unable to download things from the market.
-I attempted to convert back to rfs by disabling lag-fix.. but I still had the problems
**After rooting which seemed successful, I also did not have Superuser.apk installed, and since i could not get a file explorer from the market I am basically screwed.
I have done quite a bit of reading and people seemed to have solved these problems so it must have been something that I was doing wrong originally. One thing I found is that I should try using the blue update instead of the yellow one..
Also has anybody flashed the newest IMNUTS voodoo kernel without facing market issues.. or how about the nonvoodoo one??
What I want to do now is get back to stock unrooted, simply so I can be sure that Im starting clean when I attempt to root again.. (or should I just try to flash stock rooted)..
If anybody has faced issues like this or know how i can fix them, please let me know.. THANKS
These problems are known, and you can fix them by flashing adrynalynes kernel and odining to dl17 stock xP
Sent from my SCH-I400 using XDA Premium App
kamikazemike6 said:
So basically, I tried to help out my friends continuum and ended up with some problems.. these are the exact steps I took..
-Flashed adrynalynes test4 cwm file via odin..
-Put yellow_update.zip on the sdcard, and updated it through that, which seemed -to work
-Flashed within CWM, IMNUTS 530 PBJ voodoo kernel, and rebooted
-Converted successfully as stated by the robot voice, but after it was done I had both the scrambled screen issue, as well as I was unable to download things from the market.
-I attempted to convert back to rfs by disabling lag-fix.. but I still had the problems
**After rooting which seemed successful, I also did not have Superuser.apk installed, and since i could not get a file explorer from the market I am basically screwed.
I have done quite a bit of reading and people seemed to have solved these problems so it must have been something that I was doing wrong originally. One thing I found is that I should try using the blue update instead of the yellow one..
Also has anybody flashed the newest IMNUTS voodoo kernel without facing market issues.. or how about the nonvoodoo one??
What I want to do now is get back to stock unrooted, simply so I can be sure that Im starting clean when I attempt to root again.. (or should I just try to flash stock rooted)..
If anybody has faced issues like this or know how i can fix them, please let me know.. THANKS
Click to expand...
Click to collapse
just download dl17 stock odin image and you'll be back to full stock with superuser and market should work.
and upgrade to FROYO, just saying.....
and i am not sure why alot of people had market problems because i used both voodoo and non-voodoo and had no problems at all, maybe i'm just lucky...