**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.
Related
So I tried installing the new ASOP rom, and was getting a bunch of force closes. I tried using CWM to revert to a previous backup, unfortunately the force closes continued in the backup. So I want into ODIN to get back to stock. I loading the stock files, did a factory reset, and everything seemed to be fine. However when I went into the market to reinstall appbrain and get my programs back, I kept getting an Out of Space error. I checked the internal memory and sure enough it says 0.00.
I've never installed Voodoo on my phone, because I was trying to avoid issues just like this one. I read over the a similar thread on this issue, but that fix isn't working for me. I tried to reroot, but the SU apk's don't have any place to go, since the phone says there is 0 internal memory.
Luckily I can still use my phone, but every time it turns off it resets, and I can't load my apps back on. Anyone got any suggestions?
The fix should still work for you. I would suggest flashing stock rom, kernel, pit, and cwmrecovery thru odin. After that you can follow the instructions posted on how to completely remove voodoo. Main thing is you need to get the original mbr to your phone.
Well he said he never installed voodoo so he shouldn't have to go through the steps to remove something he never installed in the first place
Sent from my SCH-I500 using XDA App
ckochinsky125 said:
Well he said he never installed voodoo so he shouldn't have to go through the steps to remove something he never installed in the first place
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hmm I read that part too, but if he follows adrynalyne instructions he should be fine. It is taking care of the same problem. Corrupted rfs. The op just achieved it in a different way. If that does not work for him then maybe some dev will be able to figure out another way to fix the problem.
I'd be curious to see mount results.
Run it from adb shell.
So the short story is I fixed my phone, from force close and zero memory hell.
I noticed when booting into recovery I was getting an error related to /dev/block/mmcblk0. I used the adb code to install the MBR file. Went in CWM and flashed the stock.zip kernel, restarted and got a ton of force closes. Went to the "How to escape the force close loop of hell" thread over at androidcentral, flashed the stock nandroid image, and someway, somehow the android gods took pity on my poor soul and my internal memory partition was restored.
I don't understand exactly how I fixed my phone, and I'm relatively new to this so I'm a little concerned. I'd like to learn from these mistakes, so does anyone understand what I did to fix my phone?
Sounds like it was the nandroid image that did it.
It is, effectively, the same issue the voodoo users have seen.
My "easy" fix was almost exactly the same as yours.
replace mbr, flash stock, revert to backup (which is basically what nandroid is).
I used my original CWM backup instead, and that worked for me. (I now have this stored on several drives/devices)
I also went back in to Root Explorer and nuked the "databases" folder in /dbdata and then wiped cache/data (CWM, then "settings"). Pretty much fixed it all for me.
Couldn't update to D101 for some reason after that, but the unsigned apk for that did the trick nicely. I suppose I'll have to retry the "odin to stock" bit if the 2.2 update fails the same way on me. Not looking forward to that one...
Froyo on my wife's phone runs like crap. This is the official update from minikies and it's applied to both my phone and her phone. We did them back to back. On my phone, I did the update and tossed it on the nightstand. On her phone, we did the update and rather than wait for things to "settle out", she started surfing the web, etc, immediately.
Any thoughts?
just do a reset....
As in, what, a reboot? It's been rebooted quite a bit.
Each phone may run different as using it after an update should not affect speed at all. My phone ran butter smooth with JI6 while others reported lag. You may want to wipe all the user data and cache data through the phone's recovery. To access recovery:
Shut down phone.
Hold both volume buttons along with the power button.
When the Vibrant screen comes up release the power button but hold onto the volume buttons.
A blue menu comes up and use the volume buttons to scroll and power button to select.
Keep in mind this will erase all her data and may or may not work.
Try to erase the cache first though(also through recovery). It won't erase the user data but refreshes the phone again. Start up may take a while though.
yeah I had done the cache and the other data wipe. I was seriously hoping to avoid wiping the user data because she's purchased textbooks from third party appstores and I'm not sure if they will live.
So the next question - If we move these apps to the memory card (the textbooks) and then tell the phone to nuke the user data, they will survive the experience or does wiping it also wipe the SD?
tiber said:
yeah I had done the cache and the other data wipe. I was seriously hoping to avoid wiping the user data because she's purchased textbooks from third party appstores and I'm not sure if they will live.
So the next question - If we move these apps to the memory card (the textbooks) and then tell the phone to nuke the user data, they will survive the experience or does wiping it also wipe the SD?
Click to expand...
Click to collapse
There's never a guarantee that no data will ever be lost. To be safe and sure, backup to a computer or backup everything on your external Sdcard and remove it before doing anything.
Keep in mind that RFS(Sammy's file system) will slow down over time and is only fixed in android 2.2.1 (mostly). Your best bet would be to flash a new custom rom with ext4 or just a voodoo kernel but stay stock.
SO FUNNY YOU MENTION THAT. As of 2.2 (the official froyo flash from tmo), Clockwork doesn't install so consequently I can't make voodoo go. It's the 3E bootloader. Also I've had no luck with pushing the 3E fix whomever it was discovered. It simply doesn't take. If there's a workaround, I'm all ears. My first thought was "oh just remount it as RW" and I'm clearly missing something.
Ideas on making voodoo go? That was my low hanging fruit I was trying for initially.
tiber said:
SO FUNNY YOU MENTION THAT. As of 2.2 (the official froyo flash from tmo), Clockwork doesn't install so consequently I can't make voodoo go. It's the 3E bootloader. Also I've had no luck with pushing the 3E fix whomever it was discovered. It simply doesn't take. If there's a workaround, I'm all ears. My first thought was "oh just remount it as RW" and I'm clearly missing something.
Ideas on making voodoo go? That was my low hanging fruit I was trying for initially.
Click to expand...
Click to collapse
Want to install a custom rom. Drop back to 2.1 then flash a custom rom.
Maybe there's something I'm missing here, but if clockwork doesn't work on the phone, how shall I install a different rom - even an older one?
Moot point - I figured out how to get the recovery binary moved to /system/bin on my phone, but the goal was to fix the existing froyo rather than flash a custom rom. If there was a way to drop back to 2.1, I would drop back to 2.1 and then have the tmo official update it. So let me propose something...
Given that I now have 3e recovery doing The Right Thing, I would guess I need to install clockwork, grab the 2.2 Tmobile UKVA6 ROM, then use clockwork to flash that in place. Since I'm flashing from 2.2 to 2.2 and not changing anything, will her user data live through the experience or do these flashes reset the partition with her apps on it?
I encrypted my 10.1 yesterday without thinking all the way though. I found out that I could no longer flash kernels while the tablet is encrypted, since the SD card is not accessible in CWR.
I've tried doing a factory reset on my tab and each time, it boots up like nothing happened. I've also tried removing the pin that I put on it and the option to remove it is grayed out.
Do any of you know of a way to do a full wipe on the 10.1? Or could I reflash it using ODIN?
Thanks in advance.
id like to know this as well
still nothing? im starting to think this is an easy fix that nobody has posted about yet
there has to be something that im missing
try post # 6 in the linked thread, restore with unmodified vanilla version image from second link provided in the post, after booting from fastboot into recovery with clockworkmod recovery img; pushing it into the device sd with adb commandline, check the post for modifications and the link for details.
http://forum.xda-developers.com/showthread.php?t=1161325
whenever i try to reset to factory defaults, it just reboots like nothing happened
re-flash a stock firmware via odin as tar or fastboot/nandroid as img (backup restore)
Ones the tab is encrypted, there's no way to un do it. Unless you do what mughalgxt suggested. Good luck
Thanks guys, I went through some of these steps and found some other good tutorials to get me back up and running. All i wanted was to try the new kernel/bonsai rom out and I'm now able to do that
**** encryption, put a lockscreen password and be done with it.
I'm still struggling with this, as well: off to read some of the linked threads, because even with flashing a stock image with ODIN I'm still not able to recover the device. At least I managed to proceed past the boot loop I WAS in (when attempting to flash from CWM) - but now, I can get to the point where the device prompts me for the decryption key (meaning, it's clearly not yet restored to factory defaults) - but can't get it boot to completion. I also note that I've still got CWM Recovery, not stock.
It seems, at some point, encryption-key be damned, right? Meaning, if I don't care about recovering the contents of the encrypted partition - surely these low-level tools have the ability to simply format the partitions? Perhaps not - at least, not CWM - as attempts to format /data continue to fail.
Off to review the linked threads to try to gain some additional insight.
I ran into this same issue a long while back. As I recall (and it's been a while), you won't be able to wipe from CWM, but you can wipe from Settings / Privacy / Factory Data Reset. I could be wrong, but I know that I didn't have to do any adb pushing or anything with special images.
Hi SacTilt-
Thanks for the reply - and agreed: Had I actively started the effort from a functioning device, I think I could have selected that option.
As it turns out - I ran CWM, rebooted into recovery, and... next thing I knew, I was in boot loop hell.
I've tried flashing a variety of files via ODIN: Some at least allow the device to boot to the point where I get the initial password prompt - which I can provide, and proceed past... but then the device just 'goes blank'.
What I'm looking for is a 'start-from-scratch', no concern for data loss, delete the dang encrypted /data folder already, will ya?... approach.
As I've mentioned, a variety of ODIN files from a myriad of sources haven't seemed to quite do the trick. I feel like I'm missing something obvious - but can't find the right angle to spot it.
Perhaps fastboot might be what I'm looking for?
FWIW: the device was rooted when I started, so I've got full Titanium backups, with which I can restore, once I recover the actual device / OS.
Thanks for any insight.
Hey guys...if anybody finds a solution to this, please let me know...I am stuck with this same damn experimental ROM I've had from day one...it's getting really old. All I want is to get rid of this stupid encryption. Thanks for any help. Tried ODIN flashing, wiping data from security screen, wiping from CMR, etc.
Have you tried formatting the sd? Whenever i had my ns4g i accidentially did the same thing and i wiped the SD and it removed the encryption.
Sent from my GT-P7510 using XDA Premium HD app
I've searched around various forums to learn how to do a complete wipe of the system to start completely brand new. I'm not talking about simply deleting user data, but system folders as well that may have gotten modified over time. I'm looking for the equivalent of an iPhone restore (it completely wipes out everything and loads the specified firmware).
So far I've seen people saying just to click on factory reset/restore in Android's settings or in CWM, but those only take care of user settings and files. I've also seen some people say that what I want is not possible.
Please clear it up for me. Is there a way to wipe everything (or reformat) to start off new with a chosen firmware from Asus? If not, then what's the closest thing I could do to achieve what I want?
Thanks
+1
need to go back to the start. sick of the android.launcher always force closing.
help would be appreciated.
I just did this yesterday by following the unroot guide on the sticky page. It takes you back to a 8.2.something ROM with the stock recovery and then the OTA brought me right back up to the latest .11 fw.
IT also wiped CWM and now it's bone stock.
zeus2you said:
I just did this yesterday by following the unroot guide on the sticky page. It takes you back to a 8.2.something ROM with the stock recovery and then the OTA brought me right back up to the latest .11 fw.
IT also wiped CWM and now it's bone stock.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but it seems to me like this just removes/replaces the rooted files with the regular stock files, then loads the stock ROM over existing files. Yes it will appear as if you are back to out-of-box stock, but I believe you will still have random leftover files spread throughout your filesystem that had to do with modifications to root or whatever.
I'm looking for the equivalent of PC's reformat hard drive, install OS.
Spd2Last said:
Someone correct me if I'm wrong, but it seems to me like this just removes/replaces the rooted files with the regular stock files, then loads the stock ROM over existing files. Yes it will appear as if you are back to out-of-box stock, but I believe you will still have random leftover files spread throughout your filesystem that had to do with modifications to root or whatever.
I'm looking for the equivalent of PC's reformat hard drive, install OS.
Click to expand...
Click to collapse
I went a similar route, mainly by accident. I went through NVflash, which i believe formats and recreates partitions and will flash a rom of your choice. I went straight from format to prime 1.5 in this way. Qualitatively, it does appear a bit snappier than my previous install (root from factory > upgrade to prime).
yeah! i have noticed the leftover files etc too..
I would love to know if you found a way, specially how to format /sdcard and the internal storage
Backwardsblade said:
I went a similar route, mainly by accident. I went through NVflash, which i believe formats and recreates partitions and will flash a rom of your choice. I went straight from format to prime 1.5 in this way. Qualitatively, it does appear a bit snappier than my previous install (root from factory > upgrade to prime).
Click to expand...
Click to collapse
Is there a way to customize what it is you want to flash? I've only found guides on how to use nvflash with a permade packages.
A coworker of mine installed the OTA update Verizon was pushing down, after rebooting the phone was stuck at the Samsung logo.
We can get the phone into download mode, but recovery errors and none of the buttons respond. (Similar to this thread)
If need be I can take a screenshot or type out the error text he receives trying to go into recovery (stock)
A little more info i can give as is: his phone is stock rom, but I do believe he has it rooted.
I have flashed roms onto my phone (Captivate) so I am familiar with working with Odin, but the problem is that he has data on the phone he needs to recover.
ADB does not recognize the phone, but his computer does seem to detect it.
Does anyone have any advice on getting something to recognize the phone so we can pull data, or is there a rom/setting that would leave his data as is?
If you odin a rom or even flash a rom it doesnt touch any of the data on the SDcard. he will loose call history and sms history. Pictures and things will be left on the sdcard untouched.
This is the most complete and up to date guide for the fassy:
http://forum.xda-developers.com/showthread.php?t=1238070
Thanks for the heads up.
Just to be clear we are talking about the internal SD card right? Not the removable one.
He is apparently mostly concerned with losing his app data. As long as that will be safe I can have him up and running in a matter of minutes, especially with your link.
NO app data will be gone as well
What rom did he have or was it stock?
when i said the sd card i was referring to the removable one.
I figured that was the case
He is running the stock Froyo rom.
Would it be possible to use Odin (or some other tool) to push CWM onto the phone and maybe get it to mount from there?
He did say Odin recognizes a device when it's plugged in.
You may be past the point of no return. Since the phone is boot-looping and not actually booting up there may be no way to root the phone to flash CWM.
Odin is unfortunately a one-way street. Its designed to flash data ON to the phone, Not pull data off.
the phone does not have to be rooted to odin cwm....that being said, op try odining cwm2.5.1.x red and three finger into recovery, wipe cache & dalvik, then go to my guide section 1, use ccampos powerwashed ed05 froyo. That rom is close enough to what stock froyo is, so it might work! Or you can try geewiz froyo also, but one of those might get the phone back up and running without completely wiping everything.
just fyi once you odin a full rom all app data is gone. I have never attempted to pull app data from the mounting of the internal memory using cwm.
xwhofarted said:
just fyi once you odin a full rom all app data is gone. I have never attempted to pull app data from the mounting of the internal memory using cwm.
Click to expand...
Click to collapse
Thats why I suggested to try and flash a close to stock froyo rom in cwm without wiping data. odin will do a full wipe, so thats his only option that I am aware of.
Could he odin a recovery, make a back up, flash a new close to stock rom, advanced restore data? It would probable have alot of issues but may give him the opportunity to make a backup.
mentose457 said:
Could he odin a recovery, make a back up, flash a new close to stock rom, advanced restore data? It would probable have alot of issues but may give him the opportunity to make a backup.
Click to expand...
Click to collapse
my co-worker had something similar happen and this is what I had him do. It didn't fair too well but it was worth a shot.
Ended up using odin to push a stock verizon rom and started over. Then I MADE him put cwm on his device and make a backup immediately incase it were to happen again.