So,
For the longest time I had a combination of Voodoo Kernel and Super Franken Clean or Super clean 2.2 or some combination of names like that on my Fascinate.
I got the itch to install CM7 because I wanted Gingerbread and the new interface so I followed the Wiki and used Heimdall to install the new Clockwork Recovery 4.0 and then installed CM7.
Everything seemed alright until stuff started going wrong.
I think the file system is wrong for what im using now, because there are like, stray bits of information from my old build, applications are not installing correctly, my sms app opens and closes itself, my context menus press their own buttons etc etc etc. Its a mess.
What is the best way to completely wipe this phone and start fresh with a new partition that is appropriate for CM7.
Right now when it boots into recovery it says it cant access the cache, it cant open or format the system, it cant do anything wipe, format, etc...
What do I do?
http://forum.xda-developers.com/showthread.php?t=1053567
That post doesn't have links to the necessary files.
Where do I get em?
Thats what happens when you dont read up on what your trying to do. you should of odin back to a stock package w/ atlas2.2 pit and repartition checked.
Here is great write up: Just replace vgb with cm7...this guide works for all mtd roms.
http://forum.xda-developers.com/showthread.php?t=1212239
droidstyle said:
Thats what happens when you dont read up on what your trying to do. you should of odin back to a stock package w/ atlas2.2 pit and repartition checked.
Here is great write up: Just replace vgb with cm7...this guide works for all mtd roms.
http://forum.xda-developers.com/showthread.php?t=1212239
Click to expand...
Click to collapse
You're the man now dog
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So get this...
I couldnt get the phantom button presses to stop, so I called Verizon and discussed the situation with them, they sent me a new Fascinate.
I got the new phone, instead of doing the process reccomended above but with CM7, I did it verbatim from the instructions.
Everything was A-OK for 24 hours.
Just now I open up Handcent messaging, damn thing is doing the same thing as the old broken phone, except this one is brand new. Any application I open, it hits the back button and exits out of the app.
What the hell is going on here?
If I use Odin to restore the phone to stock 2.2 it runs flawlessly.
Is there a step i'm missing that is causing this to happen because its really annoying.
Also, the Plain Vanilla GB rom thats linked in above in those instructions is missing a few critical features for the Fascinate.
The LED flash doesn't work, period.
and the proximity sensor doesn't work either, so if you want to hang up a phone call you have to hit the power button, then hang up.
I'd go back to CM7 but that will probably have the same phantom button pressing issue as VGB.
those are common issues in the rom(s) itself. If you dont like or cant deal with those issues flash a different rom. I suggest giving power washed eh09 gingerbread w/ tksgb kernal a try.
Related
No matter which FroYo Release I try, "Fix-permissions" doesnt seem to work properly. Regardless of what i try, it only fixes permissions for the CWM app itself. So its shows two lines of text for CWM, and its done. Any one know why this is happening?
Ps- I've tried completely un installing CWM and deleting its folders and everything associated with it but to no avail. I'm out of ideas...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I take it that everyones ClockWork's "Fix-Permissions" works perfectly fine? Any input would be nice. THanks
You need to get into the actual clockwork recovery and fix perm there. So, open ROM manager, select reboot into recovery, select re-install packages, clockwork recovery should boot up, then goto advance options at the bottom of the list and select, then you should see the fix perm option about half way down the list, select it and your done.
I have the same problem. I'm thinking it's to do with CWM needing to be updated for the vibrant. Since there is no current 2.2 official/supported release it will not be updated as of yet. I haven't contacted koush(dev), but I'm sure he knows.
Even if you do go directly into CWR you can select it, but it doesn't seem to scroll the script...
I am using the stock Froyo eugene posted and I am not having any problems with ROM manager or CWR. I have done two backups with ROM man and wiped cache, dalvik cache, and fix permissions in CWR and it worked. I even got the fix permissions log on my SD card.
This must be it, because same thing happens if i try from the recovery. Is there anyone that can get fix-permissions to actually run the entire script? Would be nice to know if its a select few, everyone, or just us two
All~G1 said:
I have the same problem. I'm thinking it's to do with CWM needing to be updated for the vibrant. Since there is no current 2.2 official/supported release it will not be updated as of yet. I haven't contacted koush(dev), but I'm sure he knows.
Even if you do go directly into CWR you can select it, but it doesn't seem to scroll the script...
Click to expand...
Click to collapse
Im also experiencing this. Im running AOSPish froyo.
I just want to know what I should do to get a solid Kernel and rom. I don't care about speed (well, to an extent), I just don't want to have to pull my battery and keep getting force closes and ****.
Right now I'm on evil fascination with PB&J
EC01 leak worked great for me.. didnt have any problems n it was fully bloated!! updating to community here in a few.. good luck!!
I used to be on voodoo but I had nothing but problems... is it more stable now?
Dan Ang said:
I used to be on voodoo but I had nothing but problems... is it more stable now?
Click to expand...
Click to collapse
i guess i lied.. i am running a voodoo kernall.. n not having too many problems.. occasional force closes but usually its because im running too many programs.. and i had a problem with gmail always force closing.. n i just re downloaded it.. n no problems since
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All of the big ROMS right now should give you stable performance. If they don't, odds are you neglected a step along the way. If you really want to be sure you wiped everything unmount everything in CWR and format it (expect your SD card). Then pick up the EB01 (or earlier) Odin set with a pit file and repartition your phone while flashing back.
Then flash whatever ROM you desire.
bobloblaw1 said:
All of the big ROMS right now should give you stable performance. If they don't, odds are you neglected a step along the way. If you really want to be sure you wiped everything unmount everything in CWR and format it (expect your SD card). Then pick up the EB01 (or earlier) Odin set with a pit file and repartition your phone while flashing back.
Then flash whatever ROM you desire.
Click to expand...
Click to collapse
You sure are a mouthful
bobloblaw1 said:
All of the big ROMS right now should give you stable performance. If they don't, odds are you neglected a step along the way. If you really want to be sure you wiped everything unmount everything in CWR and format it (expect your SD card). Then pick up the EB01 (or earlier) Odin set with a pit file and repartition your phone while flashing back.
Then flash whatever ROM you desire.
Click to expand...
Click to collapse
might i ask how inthe hell u do that?
i mean unounting.. and formatting.. i thought u could only do that to an sd card??? ive never done that??
Hello,
I just flashed my wifi gtab 10.1 with the stock touchwiz ux rom via odin from the development thread.
Now, whenever i start the download mode on my tab, following is coming up:
http://samsunggalaxysforums.com/attachment.php?attachmentid=733&d=1304696743
The shown one here is from a S2, but I get exactly the same screen with my gtab.
Before I flashed it via odin this screen wasn't there and I got directly into download mode.
Even restoring the normal stock rom or installing cwm didn't remove it.
Am I the only one with this warning screen and is it possible to remove it again?
Thanks in advance.
So nobody knows something about this? That's sad. =/
Edit: Sorry for double posting, wanted to edit.
its nothing much
just means you've flashed a ROM
So it's absolutely normal that this warning screen will pop up everytime I start the download mode from now, because I flashed a ROM one time?
Also, there is no way to remove it?
Thanks so far.
on the Galaxy S II you can either get a usb jig or do that flash/reflash trick but on the Tab i dont think there's anything yet. but hey thats no big deal !
....DELETE
No, I think it came with the latest official ROM. I just got my tab the other day, brand new. The firmware on it is XXKG8. I haven't added anything, and as I said, it's new.
I get that message before download mode. I have been actually hesitating to root it because of this, thinking that they have added some sort of counter like on the SGS2.
So this is not the result of adding a rom, it appears on brand new retail tabs as well, it seems.
So from what I gather, nothing happens when you press the yes button to go into download mode after you see that message?
Draygon said:
I just flashed my wifi gtab 10.1 with the stock touchwiz ux rom via odin from the development thread.
Now, whenever i start the download mode on my tab, following is coming up:
http://samsunggalaxysforums.com/attachment.php?attachmentid=733&d=1304696743
Click to expand...
Click to collapse
That is normal, no need to worry about it. I got the same warning once I performed the 11MB update on my UEKG4 build. I have a feeling that warning was "borrowed" from vanilla 3.2, anyone with a Xoom tablet on 3.2 please let us know. Did you had an unlocked bootloader on your tablet (lockpad)?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Because if you did, the update locked your bootloader unfortunately. Still, there is no biggie on that also... Personally, I don't care if it locks the bootloader, as long I can flash the tablet with CWM. That means I can flash a custom ROM, kernel and also root. It makes no difference to have a locked or unlocked bootloader, unless you want to flash something that needs a different bootloader (i.e. Tabuntu).
Hey peoples,
I have Serendipity 8.0 (same has happened on UnNamed.) Both roms use the same kernel (entropy) Let me begin by saying that the Entropy kernel is amazing. I have noticed a minor annoyance and that is the touchscreen driver I suppose has some sort of bug. I blame it on the kernel because I reflashed to full stock and problem is non existent. When you first flash the custom rom it seems to be working ok however on the next restart, it starts. The problem is the "swype line" is not rendered smoothly and feel the "android" keyboard is a tad off calibration. when I swype my finger the blue line starts to zig zag.. not consistetly the same pattern but its not straight like it should be. do you guys feel that it maybe because of undervoltage? It seems like a silly theory considering we have a dual core lol. I'm sorry if my terminology is off, just trying to get my point across.
yes, I wiped/factory before installing the rom.
Has anybody else experienced this? thanks for the posts guys.
Honestly, I have experienced this. I thought it was just me but maybe it is something else. It definitely starts to zig zag creating a lot of errors in my texts. haha
Just checked it on mine. And does not have it. I'm running stock rom with only thing I've done is install Entropy512's kernel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does this count as a double post?
Sent from my SAMSUNG-SGH-I777 using XDA App
well i did a fresh install of unNamed 1.0.4 with entropy and I dont seem to have it anymore. I would do nandroid backup and restores so maybe stuff would get fowled up. Will post again if it happens again. I would definetely do a fresh install.
wipe/factory reset
wipe cache parition
wipe dalvik cache.
install rom.
Does anyone get the issue of the cursor jumping to the left? Sometimes when I try to go to the end of my message the cursor moves on its own, often highlighting words along the way.
Your guys are awesome. I still can't get used to this. I had to uninstall this and use the regular samsung/android keyboard.
sweetboy02125 said:
Your guys are awesome. I still can't get used to this. I had to uninstall this and use the regular samsung/android keyboard.
Click to expand...
Click to collapse
Same boat.
Everytime I reboot, this "app" comes up. I have no idea what it is, but I know it wants me to call cust care...how do I disable this?
If you've never noticed it before or it seems suspect I would scan it with whatever anti virus app you got and uninstall it. I use App Master, you get rid of suspect "system" apps and it can put it in a recycling bin in case you want to reinstall it later.
https://play.google.com/store/apps/details?id=com.droidware.uninstallmaster&hl=en
still happening...confused.
Self service is a system app. You can't normally get to it to run it. Disabling it might stop something from working that the phone needs. When I freeze apps on a fresh install, I don't do that one. I don't know what it does. Under normal conditions, you shouldn't be seeing that app running at boot. Something might be borked with the phone to cause that app to run, and you see it, at startup. I know it's an extreme reaction, but if it were me, and it was really getting on my nerves, I'd back up everything to the SD card. Then I'd power down and remove the card. Next I would flash a full stock Odin tar.md5 of the operating system. That will put things back to where they're supposed to be. Next time, be more cautious when freezing/disabling/removing system apps and files.
oscarthegrouch said:
Self service is a system app. You can't normally get to it to run it. Disabling it might stop something from working that the phone needs. When I freeze apps on a fresh install, I don't do that one. I don't know what it does. Under normal conditions, you shouldn't be seeing that app running at boot. Something might be borked with the phone to cause that app to run, and you see it, at startup. I know it's an extreme reaction, but if it were me, and it was really getting on my nerves, I'd back up everything to the SD card. Then I'd power down and remove the card. Next I would flash a full stock Odin tar.md5 of the operating system. That will put things back to where they're supposed to be. Next time, be more cautious when freezing/disabling/removing system apps and files.
Click to expand...
Click to collapse
I agree with Oscar.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you're getting that message, it means something is wrong with your phone. I'd hope it's only something wrong on the software side of things. What Oscar suggested will, without a doubt, solve any issues related with the ROM.
I like my custom ROMs, so the first thing I'd try is a completely clean flash of your ROM. Wipe data, cache, dalvik cache, and system, then flash any ROM of your choice.
If you're still getting issues after that, then I'd go with the full stock unrooted ROM, as Oscar suggested.
Hope this helps!