okay so i tried a million times to repartition in odin and cant.. now matter how many times i do its the same... i want to repartition because i been having rotation issues ever since i flashed eugene's jpm froyo, with auto rotate issues... now what ever rom im on the rotate is all jacked.. tried going back to stock no root but it wont repartition wich is what i think (or hope) will fix this problem.
any ideas??
I don't have the reason why you can't partition, but mabey try wiping cache, dalvik cache, and fix permissions in clockwork. Worth a try if you have not already.
Related
I know this is not only happening to me.. But why is it that it is working for some ppl and others it dosnt?
I have tried serveral roms now and they all have the same problem.. No keyboard!
I have installed recovery image v. 1.5.2 .. After that i have copied the rom to the root of my sd.. i have then wiped: Data, Dalvik, SD:EXT, battery, rotation.. However at Dalvik and SD:EXT it gives me the error "Error: Run 'wipe dalvik' via adb!" and "Error: Run 'wipe ext' via adb!" .. Is it because of this and why is this happening?
I have then tried to continue however and flashed the newest radio from the thread and after that i rebooted and flashed the rom .. no errors here.. after rom flash i wiped everything again, but still got the errors at dalvik and sd:ext..
did you previously have davlik to SD. it certainly sounds like that may causing a problem.
do you have another SD card you could try...just to try it out? or format your card using the recovery menu, then copy the ROM.zip back over and apply.
I certainly have no problems with Keyboards.
I've never moved davlik to SD, only Apps.
Good Luck!
Try the rom on the Htcpedia forum, its the clean official update, but with a2sd and overclock which is optional, everything works fine for me
minty1978 said:
did you previously have davlik to SD. it certainly sounds like that may causing a problem.
do you have another SD card you could try...just to try it out? or format your card using the recovery menu, then copy the ROM.zip back over and apply.
I certainly have no problems with Keyboards.
I've never moved davlik to SD, only Apps.
Good Luck!
Click to expand...
Click to collapse
What is davlik anyways?
In other words.. i do not even know what davlik is, so i guess i haven't done anything to it as i do not know what it does or is..
VillainROM 10 should have a working keyboard. It uses HTC IME_mod from xda-dev as the default keyboard
anon2122 said:
VillainROM 10 should have a working keyboard. It uses HTC IME_mod from xda-dev as the default keyboard
Click to expand...
Click to collapse
Well i have tried that one.. Actually the first one i tried.. But it dosnt work in that rom either.. Don't know i must be missing something since you guys dosn't have any problems
I was having this same issue this morning,.. No matter which ROM I flashed the keyboard just didn't want to come up,....
This may be caused by skipping the touch input demo on 1st boot, I never usually bother with it, however,... Just flashed another ROM again, went through the demo, all working fine again!!!
The sequence has to be correct ! I had the same issue with VillainROM 10.
Found out, that the keyboard apk was placed in /data. Means,
if you first flash the ROM and THEN wipe, your keyboard has gone.
Correct sequence:
1. Wipe
2. Flash
3. Reboot
**solved**
Have you tried Eugene's Froyo that doesn't brick? I once have a problem installing the first versions of voodoo lagfix do to my NAND (or something like that) being of a different size than the majority of the vibrants. The phone soft-bricked but I brought it back with Eugene's froyo and flashed back to stock 2.1. I noticed that all my stuff inside the internal SD Card was deleted (or reformatted...i really don't know). Maybe this can help you get rid of the ghosts of past roms. Good luck.
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
No, I hadn't thought of that. I wasn't sure if flashing any more ROMs would be a good idea. I'll try it though and see what it does. Thank you.
Let me know if it worked for you.
Hi,
I tried this and no luck - still the same. I wasn't able to get rid of any of the aforementioned problems.
I'm getting desperate at this point. If anyone knows of anything that could easily fix the problem, even if it carries a risk of making things worse, I'm willing to try anything and not hold anyone responsible for the actions I take...
Surely there are adb commands that can format or delete these ghost files & folders, or if someone could tell me where to go and manually delete files & folders through something like DROIDEXPLORER or ROOT EXPLORER, I'd be willing to try anything.
Again, thanks in advance!
Have you tried checking the "Re-Partition" box when you Odin back to 2.1?
tnimoruen said:
Have you tried checking the "Re-Partition" box when you Odin back to 2.1?
Click to expand...
Click to collapse
Yes, I have. I've tried two different versions of ODIN, the re-partition option, I've formatted the internal and external SD, etc. This is all what leads me to believe that there are files/directories used during the flashing process that are *not* cleared/wiped by ODIN or other flashing methods. There are ghost files, I just don't know how to get to them and get rid of them. Maybe I need a Vibrant Exorcist, LOL.
Wipe dalvik cache had been broken for quite some time, actually there's been some threads about it. If you can't odin the only other option is just wipe data/ factory reset in clockwork recovery.
I've seen those Dalvik cache posts, but I must have misunderstood the issue. As far as the others, I can ODIN - It's just not wiping everything. I can also wipe/reset in CWR, but again, it's not wiping everything. Stuff is getting left behind (I can only assume) which is preventing me from doing certain things. The phone works, but certain things will no longer work - such as not being able to use mini-Kies to go to 2.2, format BOOT in CWR, can't root via SOC due to mount path error, etc.
WIPE WIPE WIPE!!!!!!
Use the Eugene's Froyo...etc. Keep doing it--it might take a few tries. Hell, try re-partition and NOT re-partitioning. Sometimes this phone can get finicky. Just be patient and persevere and it will pop into place. ODIN re-creates all software--but is pretty un-reliable for obtuse issues like yours. Just keep at it.
Get to 2.1 stock NO MATTER WHAT...then flash your choice of rom. It can iron itself out with a little sweat and rage.
Hi
I have a SGS with jpy + voodoo. I have done some CWM backups.
I plan to change to JVP. I assume that I'll need a clean install and some titanium work.
Can I simply use JVP CWM restore to go back to my JPY if I finally get disappointed with JVP?
In that case, it will be an exact photo of the CWM JPY backup or I'll need to reinstall data or apps???
Thanks a lot!!
CalabiYau said:
Hi
I have a SGS with jpy + voodoo. I have done some CWM backups.
I plan to change to JVP. I assume that I'll need a clean install and some titanium work.
Can I simply use JVP CWM restore to go back to my JPY if I finally get disappointed with JVP?
In that case, it will be an exact photo of the CWM JPY backup or I'll need to reinstall data or apps???
Thanks a lot!!
Click to expand...
Click to collapse
You have to do a clean install. With Odin, pit 512, Re-partition and the 3 files. I advise to wipe data and factory reset before flashing.
You should restore the backup titanium applications, but only the applications carefully restored, not the data. JPY to return to the same but now flashing the JPY. If you have any lagfix enabled is recommended to disable it before doing anything. In Spain we say "better safe than sorry."
But then if i go to jvp I'll loose the chance to go back easily to JPY??
I mean that installing cleanly JPY again.,.......
Hello,
went through this today (from JVP back to CWM backup of JSD, never used repartition, flashing tool = heimdall), ran in some problems as I thought that the Gingerbread bootloaders work for Froyo,too (I think I read that somwhere here at XDA).
1) Tried flashing Froyo kernel (speedmod) only and restored CWM-Backup of JSD after factory reset/cleared cache and dalvik cache -> did not work, booting stopped at SGS logo without progress for a really long time (longer than recreating dalvik cache used to last).
2) Flashed a complete self-made JSD-ROM including bootloaders and then installed CWM backup of last running JSD system (again, after factory reset, dalvik & cache clearing) -> worked fine, no problem for hours now.
Maybe I did something wrong at first try, maybe needed the correct bootloaders - don't know.
Hope this helps you a little bit - recreating running system from CWM *full* backup including apps and settings finally worked for me, data on sdcard and external_sd will not be touched (unless you format internal sdcard which is /sdcard directory).
Edit: Be sure to have a copy of your full CWM backup on your harddisk so in case something goes totally wrong you can restore the backup to your SGS recovery, the backups are saved in /sdcard/clockworkmod/backups/)
Yes, I guess this should work. A clean JPY installation, then CWM and then restore...
By the way, we did you go back to JSD??? JVP was faulty??
No, believe me or not, I somehow "feel better" with JSD, JVP made absolutely no problems here, it felt very fast, stable, without (for me) noticable errors, no battery drain.
Maybe I'll try 2.3.4 again in some weeks as I like experimenting with Linux/Android in general but for now JSD is my choice. Only real advantage (again, for me, maybe you don't need this) of Froyo/JSD is that I can reenable logcat using speedmod recovery tweaks.
I use this as a reliable root back to Froyo from custom roms or gingerbread. Not failed me yet. I keep plenty of backups so touch wood, no fowl ups yet.
http://forum.xda-developers.com/showthread.php?t=1100906
are you using the Stock ROM ?
i started noticing that after i flashed a new rom, alot of my settings are set to the way i had them before. and some apps are already installed that would otherwise need a marketplace install..
keep in mind, i always do a wipe of cache/dalvik/sdcard
i think it started happening after i partitioned the sd card for those old sense roms that needed extra space.. cant remember..
but it seems like theres a portion of rom that isnt being wiped and all my settings are being carried over to the next rom flash..
how can i fully wipe my phone or get it back to normal?
this is weird, and i want it to stop. any ideas?
i just flashed back to amonra
TorxT3D said:
i started noticing that after i flashed a new rom, alot of my settings are set to the way i had them before. and some apps are already installed that would otherwise need a marketplace install..
keep in mind, i always do a wipe of cache/dalvik/sdcard
i think it started happening after i partitioned the sd card for those old sense roms that needed extra space.. cant remember..
but it seems like theres a portion of rom that isnt being wiped and all my settings are being carried over to the next rom flash..
how can i fully wipe my phone or get it back to normal?
this is weird, and i want it to stop. any ideas?
i just flashed back to amonra
Click to expand...
Click to collapse
Are you using ROMs that have Google back up enabled?
Also, if the zip isn't set to wipe /data and you're not wiping it then you'll still have all of your data.
That has happened to me too. Are you wiping sdext and android.secure in recovery. I always wipe those and haven't had that happen since I started doing that.
We're comin from a pure power source.
naw i turn off all that google backup stuff.
thats the thing, when i try to wipe sdext it gives me an error (from the last i remember doing it)
Hmmm. Latest version of amon ra?
We're comin from a pure power source.
keep in mind, i always do a wipe of cache/dalvik/sdcard
Click to expand...
Click to collapse
You should be wiping data as well when flashing new roms.
I flash vrsuperwipe everytime I flash, but I use Google backup, so when I flash a new sense ROM it saves a lot of my settings, and my SD-ext apps automatically appear. Good feature imo.
Sent from my PC36100 using Tapatalk
bump for any other answers or advice
thanks guise.
still wondering about other options before testing some new roms
same thing happened to me so I tried repairing sdext and then re-partitioned my card and left it ext2 instead of ext3,wipe data/cache/dalvik cache/system flash superwipe, then flashed rom. don't know which one worked but it stopped. Also I noticed it mainly happens when I flash 3.0 roms but it has happened on CM7 to
TorxT3D said:
i started noticing that after i flashed a new rom, alot of my settings are set to the way i had them before. and some apps are already installed that would otherwise need a marketplace install..
keep in mind, i always do a wipe of cache/dalvik/sdcard
Click to expand...
Click to collapse
You did not wipe data. If you do this you will preserve all of you apps (if they were not on card), data and system settings. This may work for you if the new ROM that you are moving to is similar enough. It can cause big problems if the structure of the ROMs is too different. You can end up with a phone that lags and has wakelocks (at best) or is not functional at all due force closes all over the place.
You should really wipe data as well before flashing a ROM and then do a selective restore of data on the new ROM.
I am running NEXUSHD2 v2.7 and Int2ext± with the "Disable CPU rendering" mod but whenever I try to wipe cache and dalvick wipe, I get a bootloop. any idea? I am trying to add things to the build.prop and need to wipe before actual use, but as seen, I cannot :/
I made this thread before but I think it got deleted
Sent from space..
I think I've read somewhere that if you have an A2sd script such as the one you're using, you should not wipe dalvik. Which may cause a bootloop. but Im not sure, that may not be it.
Try to edit build.prop then restart normally, without wiping, sometimes things just tend to work .
Marvlesz said:
I think I've read somewhere that if you have an A2sd script such as the one you're using, you should not wipe dalvik. Which may cause a bootloop. but Im not sure, that may not be it.
Try to edit build.prop then restart normally, without wiping, sometimes things just tend to work .
Click to expand...
Click to collapse
thank you but I've found an answer:thumbup:
Sent from space..