Database Users

I really messed up the flashing process. Voodoo possibly the culprit. Please help!

Hi everyone, this is my first post. I am one of those who waited patiently for 2.2 that I decided to finally root today. I followed all the instructions to root from the sticky here. The process went without a hitch and I flashed the jk6 stock from Team Whiskey from the development section.
I really enjoyed the 2.2 experience while it lasted until I flashed the JL5+voodoo kernel from supercurio's thread. I was under the impression that you could flash different kernels over the old ones. It went through the process of partitioning to ext4. Once it was done, I went to settings and about phone to see if there was JL5 anywhere and it wasn't. It still showed JK6. So I panicked. I disabled voodoo through clockwork recovery and went to the process of reverting back to rfs which I believed. I used odin to flash back to jfd. I know, I didn't restore the backup from clockwork because I wanted to start over( I still have those backups on my external sd card). To my knowledge, the flashing to jfd would completely wipe the data, replace the baseband, kernel, recovery and os.
I then used samsung kies mini to update to JI6. Everything went ok so I decided to root again. Instead of loading the update.zip to internal sdcard. I decided to use tga_gunnman once click root. That process went great until went it rebooted, the clockwork recovery screen popped up to my amazement. It seemed that there were still original files since the first time I rooted. I checked my files on my vibrant to find that I still had original files such as the clockwork back up, titamium back up, and even voodoo. I thought the flashing would completely remove all the data and files. So I panicked again. At this point, I don't know what I did that now I can't get to my log in screen and the screen I get is a picture of a phone, an exclamation, and a computer on my phone. I tried using odin again through download mode to go back to stock but under the message box on odin, it stops at cache.rfs. It has been stuck there for a long time and nothing is happening. I can't even get into recovery mode either.
Now I am not even sure if I properly disabled voodoo or deleted it which I thought the flashing back to jfd would do. I don't know if my partition is still rfs or ext4. I can't use my phone at all. Did I completely brick my phone? How do I fix the mess I got myself into? I really do appreciate anyone's help. I apologize for the length of this post. I wanted to be detailed as possible. Thank you.
EDIT: Spoke too soon. I used a different version of odin and now im back to stock jfd, but the original files are still there including the voodoo folder. I thought it wipes all the data. Also how do I know that the data partition is originally rfs and not ext4? I want to make sure before I root again. Thanks.

Can you get to recovery and restore your backup you created? I just read where you said you can not get in to recovery. What method are you using to try to access recovery?

well if you are back to stock, but just the folder is lingering around, cant you just reformat your sd card?
settings>sd card phone storage>format.

I did a back up using clockwork. I originally was trying to do to the recovery mode by pressing the vol keys and power and that didn't work. I actually got it back to stock jfd by using a different version of odin. My problem now is that I still have some original files on my phone including the voodoo folder. My understanding of flashing was that it wipes everything from your phone. I am not sure if i still have root access even after flashing back to stock jfd. Also if my partition is back to rfs or still stuck at ext4. I am a little confused here. I am afraid if i root again that the original files and folders from my first root will interfere with the new root method.

so If I format the internal sd card, will it completely erase all traces from my first root?

neotoky said:
I did a back up using clockwork. I originally was trying to do to the recovery mode by pressing the vol keys and power and that didn't work. I actually got it back to stock jfd by using a different version of odin. My problem now is that I still have some original files on my phone including the voodoo folder. My understanding of flashing was that it wipes everything from your phone. I am not sure if i still have root access even after flashing back to stock jfd. Also if my partition is back to rfs or still stuck at ext4. I am a little confused here. I am afraid if i root again that the original files and folders from my first root will interfere with the new root method.
Click to expand...
Click to collapse
When you flash a new rom, or back to stock, it does not (usually) wipe the contents of your sd cards (internal or external). And if you are successfully running stock 2.1, you can rest assured you're back to rfs - so if that voodoo folder is making you nervous you can just delete it (it's only relevant if you have voodoo enabled). You're fine to re-root with whatever method you prefer.
Sounds like the soft-brick you experienced was purely from odin hanging on you, and that icon you saw has become a frequent visitor on my phone since I routinely have odin hanging issues (hence my avatar). I've found that v1.3 treats me the best, but sounds like whatever version you updated to worked, so there's no reason to deviate.

Download OCLF from the market and you will find out if you are currently rooted still.

There are a few misconceptions on what the wipe is.
/sdcard and external SD card are user accessible areas of the phone, and when it states that the ROM wipes your phone it does not touch these (there was only one incarnation of TW ROM's that inadvertently formated the entire filesystem for some users).
If you must format the phone to its complete stock form in ODIN you can use re-partition check box - the results are still mixed if it formats the entire FS or not, but most probably it will for you. So all your pictures, etc. should be backed up no matter what.

I appreciate the help guys. Thanks very much. The version of odin I used originally was v1.00 and the one I used to fix the problem was v1.70. My question now is did I properly flash the JL5 kernel over the JK6 even though when I checked the information on my phone it still stated as JK6? Also how do you properly reflash to a different kernel as well as modems? Do you overwrite the kernel or do you have to go back to stock before trying a new one? Thanks.

neotoky said:
I appreciate the help guys. Thanks very much. The version of odin I used originally was v1.00 and the one I used to fix the problem was v1.70. My question now is did I properly flash the JL5 kernel over the JK6 even though when I checked the information on my phone it still stated as JK6? Also how do you properly reflash to a different kernel as well as modems? Do you overwrite the kernel or do you have to go back to stock before trying a new one? Thanks.
Click to expand...
Click to collapse
I'm not sure why you would flash the JL5 kernel. Does it have any added benefit over the JK6? If you want, you can flash the JL5 MODEM through clockwork using the JL5_modem.zip file posted in many threads.
You should not have to go back to a stock kernel before trying a new one, but if you flash a Voodoo kernel that converts your system to ext4, then you must convert it back to RFS before flashing another kernel. An easy way to be postively sure that you are in RFS is by getting "Terminal Emulator" from market, and type "su" press enter, and then "mount" and press enter. If you see rfs next to data, dbdata, datadata, and system, then you know your system is converted back to RFS. Otherwise, in Voodoo mode it will read ext4 next to those.
Also, if you are really paranoid about getting a fresh start, you can mount your internal SD on your computer and just delete everything on there. Don't worry, all the important Android system files will be restored upon each reboot. All the other crap on there will be erased.

oldrom to stock(odin) to newrom 10min flat

i dont think this has been posted if so let me know and i will retract this.It is just i think the quickest way to get to a new rom while flashing back to stock first.
disclaimer:this is for people that know what im talking about. If something happens to your phone it jumps off a cliff and laughs at you or anything else i am not responsible.
alrite as usual you should have already backed up all your apps, have your new rom on your internal sd card, and odin up and ready before this.Alright so here it is i have 3 button combo working on mine if you dont use adb i guess.
Pull battery insert battery hold volume up and down and put in cable from computer to phone download mode.It should pop up press start on odin. Now wait for it to say reset then wait for the boot animation of the signal bars right when those pop up before the sound even. Now pull battery insert battery hold up down and power button untill att pops up twice.Then select reinstall packages (this is if you already have the update.zip on your sd card for cwm if not dont bother) it will reinstall clockwork mod recovery (sometimes you have to push reinstall packages twice it just depends). Almost done now just do as normal install zip from sd card select the rom of your choice and then yes(install whatever rom your wanting to flash ) then bam your done no needing oneclick root dl rom manager instal cwm from there no need to even look at it...
and there you go done in 10 min i do this everytime and have never had any issues EVER im just trying to make flashing a new rom quick and easy and id love to hear your feed back

shadowscreation said:
i dont think this has been posted if so let me know and i will retract this is just the quickest way to get to a new rom while flashing back to stock first
disclaimer:this is for people that know what im talking about if something happens to your phone it jumps off a cliff and laughs at you or anything else i am not responsible
alrite as usual you should have already backed up all your apps have your new rom on your internal sd card and odin up and ready before this so here it is i have 3 button combo working on mine if you dont use adb i guess
pull battery insert battery hold volume up and down and put in cable from computer to phone download mode should pop up press start on odin wait for it to say reset then wait for the boot animation of the signal bars right when those pop up before the sound even pull battery insert battery hold up down and power button untill att pops up twice select reinstall packages (this is if you already have the update.zip on your sd card for cwm if not dont bother) it will reinstall clockwork mod recovery then (sometimes you have to push reinstall packages twice it just depends)now just do as normal install zip from sd card select the rom of your choice and then yes then bam your done no needing oneclick root dl rom manager instal cwm from there no need to even look at it
and there you go done in 10 min i do this everytime and have never had any issues EVER im just trying to make flashing a new rom quick and easy and id love to hear your feed back
Click to expand...
Click to collapse
Can you say: Run on sentences makes no sense.
Plus, wrong section

I agree. Some capitalization and punctuation would go a long way. Also, if speed is your goal then just drop the ROM zip on the sdcard, boot to recovery and install it.

opcow said:
I agree. Some capitalization and punctuation would go a long way. Also, if speed is your goal then just drop the ROM zip on the sdcard, boot to recovery and install it.
Click to expand...
Click to collapse
im talking about speed and the rom actually booting. I have done it that way a few times and most of those times at get failure at line watever update aborted this way has worked for me 99.99999999999999999999999999% of the time

shadowscreation said:
im talking about speed and the rom actually booting. I have done it that way a few times and most of those times at get failure at line watever update aborted this way has worked for me 99.99999999999999999999999999% of the time
Click to expand...
Click to collapse
Sorry to hear about your bad luck. It has worked for me 100% of the time.

That thing should have ended with:
"Posted using a broken older version of Swype while pressing the buttons with my face"
Comma. Semicolon. Space Bar. Enter key. Period. Pick one.
Hell.......pick a bunch.

evoic said:
"Posted using a broken older version of Swype while pressing the buttons with my face"
Click to expand...
Click to collapse
That's hilarious!
Thanks for the laugh while I'm stuck in morning traffic.

Thanks, I appreciate the info. I will try this. I had no problem understanding your post, and didn't even notice the lack of punctuation. I think punctuation is way over rated, and if you are a good reader you shouldn't need it. I threw in a few periods and comas so these Cretans could understand this.

My "10 min or so..." ROM Upgrade Guide
Backup apps/data using Titanium Backup
Remove all garbage folders from internal SDCard
Odin back to stock.
Insert <AWESOME ROM XX> onto internal SDCard
Use the update.zip for CWM when rebooting into recovery. (Reboot into recovery - run the update.zip - reboot again into CWM)
Install <AWESOME ROM XX>
Sign into Google and have it replicate contacts etc.
Restore Apps/Data using TiBu.
Usually takes a little more than 10 minutes due to backup/restore of TiBu - but the actual Odin/Install new ROM part takes under that.
But this isn't for those new to flashing - beware that this process can screw up forcing you to ODIN - and if you didn't keep a copy of your TiBu restore somewhere other than your Internal SDCard you'll be fubard.

avgjoegeek said:
My "10 min or so..." ROM Upgrade Guide
Backup apps/data using Titanium Backup
Remove all garbage folders from internal SDCard
Odin back to stock.
Insert <AWESOME ROM XX> onto internal SDCard
Use the update.zip for CWM when rebooting into recovery. (Reboot into recovery - run the update.zip - reboot again into CWM)
Install <AWESOME ROM XX>
Sign into Google and have it replicate contacts etc.
Restore Apps/Data using TiBu.
Usually takes a little more than 10 minutes due to backup/restore of TiBu - but the actual Odin/Install new ROM part takes under that.
But this isn't for those new to flashing - beware that this process can screw up forcing you to ODIN - and if you didn't keep a copy of your TiBu restore somewhere other than your Internal SDCard you'll be fubard.
Click to expand...
Click to collapse
@ avgjoe This is about it. But I would add one suggestion which will help out a ton with Odin.
[*] Ensure you have a good usb cable. Make sure to wiggle the cable. If the the phone loose connection to the pc while wiggling cable save your self 20 minutes and get a good cable.
I have 5 cables. Best to worse...
- 1 BlackBerry Cable ***** Best for me. I trust it. No connection loss
- 1 Stock Jabra Cable **** Worked good for me. No connection loss
- 1 Ericson Cable shaved *** Tight fit. No connection loss
- 2 Samsung stock cables* What was Samsung thinking
This is my experience. I remember the first time I flashed my Captivate. I felt sick and I blame it on my cable. I barely touched my phone and I heard the beep-beep from my pc when it detected the USB was detached and re-attached. Atleast bricking a Captivate is better than bricking a Tilt2.

An even faster ROM upgrade guide:
-Boot into CWM
-Wipe data and cache
-Install ROM zip from SD
If that fails, try again or:
-Odin one-click (or Odin to JH7 for certain batch 1010 Captivates)
-Enable debugging and sideload z4root. Permanent root.
-Install CWM using ROM Manager or manually with the update.zip
-Follow three steps above this section.
There is usually no need to go back to stock between flashes (and there are more serious risks [soft-brick, hard-brick, damaged bootloader] from a bad Odin flash than from a bad CWM install [fc's, stuck at boot logo]). Wiping your data and cache partitions (and making sure you disabled lagfix if not supported by the new ROM) should be sufficient.

avgjoegeek said:
My "10 min or so..." ROM Upgrade Guide
Backup apps/data using Titanium Backup
Remove all garbage folders from internal SDCard
Odin back to stock.
Insert <AWESOME ROM XX> onto internal SDCard
Use the update.zip for CWM when rebooting into recovery. (Reboot into recovery - run the update.zip - reboot again into CWM)
Install <AWESOME ROM XX>
Sign into Google and have it replicate contacts etc.
Restore Apps/Data using TiBu.
Usually takes a little more than 10 minutes due to backup/restore of TiBu - but the actual Odin/Install new ROM part takes under that.
But this isn't for those new to flashing - beware that this process can screw up forcing you to ODIN - and if you didn't keep a copy of your TiBu restore somewhere other than your Internal SDCard you'll be fubard.
Click to expand...
Click to collapse
It's a rather easy process, done it like 3 already. What I hate about going back to stock using Odin is that I always have to this:
Enable USB Debugging
Root the phone
Log in so I can use the market.
Download Rom Manager, Install CWM
Reboot to stock recover.
Apply package
Apply package again.
Install new rom
I wouldn't mind but the whole process until you are finally able to install the new rom takes at least 10 minutes of tapping and typing. It's rather annoying. I'm not complaining though...

avgjoegeek said:
My "10 min or so..." ROM Upgrade Guide
Backup apps/data using Titanium Backup
Remove all garbage folders from internal SDCard
Odin back to stock.
Insert <AWESOME ROM XX> onto internal SDCard
Use the update.zip for CWM when rebooting into recovery. (Reboot into recovery - run the update.zip - reboot again into CWM)
Install <AWESOME ROM XX>
Sign into Google and have it replicate contacts etc.
Restore Apps/Data using TiBu.
Usually takes a little more than 10 minutes due to backup/restore of TiBu - but the actual Odin/Install new ROM part takes under that.
But this isn't for those new to flashing - beware that this process can screw up forcing you to ODIN - and if you didn't keep a copy of your TiBu restore somewhere other than your Internal SDCard you'll be fubard.
Click to expand...
Click to collapse
It's a rather easy process, done it like 3 already. What I hate about going back to stock using Odin is that I always have to this:
[*] Enable USB Debugging
[*] Root the phone
[*] Log in so I can use the market.
[*] Download Rom Manager, Install CWM
[*] Reboot to stock recover.
[*] Apply package
[*] Apply package again.
[*] Install new rom
I wouldn't mind but the whole process until you are finally able to install the new rom takes at least 10 minutes of tapping and typing. It's rather annoying. I'm not complaining though...
Wiping your data and cache partitions (and making sure you disabled lagfix if not supported by the new ROM) should be sufficient.
Click to expand...
Click to collapse
Would it work if you install the rom, THEN, flash a kenerl that supports lagfix (without rebooting at all)?

Xstop said:
Can you say: Run on sentences makes no sense.
Click to expand...
Click to collapse
agreed. someone should start drinking decaf
sent from the midget in mah belly

cumanzor said:
It's a rather easy process, done it like 3 already. What I hate about going back to stock using Odin is that I always have to this:
Enable USB Debugging
Root the phone
Log in so I can use the market.
Download Rom Manager, Install CWM
Reboot to stock recover.
Apply package
Apply package again.
Install new rom
I wouldn't mind but the whole process until you are finally able to install the new rom takes at least 10 minutes of tapping and typing. It's rather annoying. I'm not complaining though...
Click to expand...
Click to collapse
you never have to log into your JF6 stock rom if you odin back to stock. you dont even have to boot to it. just keep the update.zip from CWM on your sdcard and boot into recovery...reinstall packages, and you are in CWM..flash your ROM, and enjoy

Nobody master clears anymore?? I do, and never have a single issue or FC. It just takes an extra five minutes to do the MC and then let the phone boot and transfer ROM of choise as well as update.zip for CW recovery to the root of my sd. But master clear is the same as a reset or a data wipe, so its not completely necessary. Just makes me feel safer!

silverslotcar said:
Nobody master clears anymore?? I do, and never have a single issue or FC. It just takes an extra five minutes to do the MC and then let the phone boot and transfer ROM of choise as well as update.zip for CW recovery to the root of my sd. But master clear is the same as a reset or a data wipe, so its not completely necessary. Just makes me feel safer!
Click to expand...
Click to collapse
nope. i never do any more. sometimes i have to flash back to stock, when i have a broken flash, but i still dont master clear. you dont actually gain anything by master clear, since it just wipes your internal sd...

>>[*] Log in so I can use the market.[*] Download Rom Manager, Install CWM
you can skip that step by simple "recycling/reusing" the recovery-update.zip from CWM. Download it once and then save it on your external sd and your pc.
When you want to use another ROM you can reuse the recovery-update.zip .
Just rename it update.zip and then reboot recovery and then do you thing.....

cumanzor said:
Would it work if you install the rom, THEN, flash a kenerl that supports lagfix (without rebooting at all)?
Click to expand...
Click to collapse
I've heard it's a bad idea to install kernels without first allowing the phone to fully boot. I've never tried it myself, I just convert to rfs without any backup or restore (using the ULF included in hardcore's Speedmod kernel) before flashing.

Stupid Questions
This is a stupid question (two actually). I think the answer is YES, but I'd like to make sure...
I've installed several ROMs by the "standard process."
Is the "update.zip" on my internal SD card the one that has cwm?
Does running "reinstall packages" from stock recovery just apply the "update.zip"?

[solved] need help recovering epic 4g after trying to install a ROM

Sadly, I have goofed up my phone right out of the gate. I do not think it is bricked, but I'm unsure how to proceed and more than a little spooked by how quickly things went from great to non-functioning.
I took my stock Epic 4G and followed a tutorial to install Froyo. That went without a hitch. I then used noobnl's one-click script method to root the phone, and that also seemed to work well.
Then I tried to install the Nebula ROM with DK28 modem and pit, using Odin3 v1.61. Since then, my phone will not boot past the Samsung logo. I can still get into Clockwork, but repeating the ROM installation process has not made any difference. I then noticed that I'm running Clockwork Mod Recovery v2.5.1.0, when Nebula apparently requires v2.5.1.5 or newer.
So can anybody help me fix what I've broken? I've tried searching the forum for this problem, but have not been able to find anyone with my particular form of stupid.
Thanks in advance for suggestions.

Cincinnatux said:
Sadly, I have goofed up my phone right out of the gate. I do not think it is bricked, but I'm unsure how to proceed and more than a little spooked by how quickly things went from great to non-functioning.
I took my stock Epic 4G and followed a tutorial to install Froyo. That went without a hitch. I then used noobnl's one-click script method to root the phone, and that also seemed to work well.
Then I tried to install the Nebula ROM with DK28 modem and pit, using Odin3 v1.61. Since then, my phone will not boot past the Samsung logo. I can still get into Clockwork, but repeating the ROM installation process has not made any difference. I then noticed that I'm running Clockwork Mod Recovery v2.5.1.0, when Nebula apparently requires v2.5.1.5 or newer.
So can anybody help me fix what I've broken? I've tried searching the forum for this problem, but have not been able to find anyone with my particular form of stupid.
Thanks in advance for suggestions.
Click to expand...
Click to collapse
Odin back to this http://forum.xda-developers.com/showthread.php?t=794138 then root using this http://forum.xda-developers.com/showthread.php?t=770388 then install this if you want cw3 and ext4 if not skip it http://forum.xda-developers.com/showthread.php?t=897612 but check on the rom ur flashing because most rom are now using ext4 and cw3. Also if you want and ur rom has the option for no journaling flash this before flashing a rom http://code.google.com/p/bonsai/downloads/detail?name=ext4-format_nojournal-1.1.3.zip&can=2&q= . I know Bonsai and Midnight roms have the option for it. Well best of luck to you and if you have any question or concerns please post them here and ill or one the many helpfull people here at xda will assist you.

Thanks, asj2583, for the quick response. For whatever reason, it did not occur to me to try putting the phone in download mode!
So to get the phone back on-track, I:
1. Started Odin3 v1.61
2. Removed the SD card from the phone
3. Plugged the Samsung USB cable from the phone to the computer (which is running 32-bit Windows Vista)
4. Clicked on 'PDA' in Odin3, then selected the Froyo TAR that had worked before, then I clicked on 'START.'
5. Let Odin3 do its thing, and now my phone is back up and running unrooted Froyo.
Moving forward, I:
1. went here and downloaded One Click Root 2.5.5.
2. On the phone, went into Menu/Settings/Applications and enabled 'Unknown sources,' then unplugged the USB cable and clicked on /Development to enable USB debugging and Stay Awake.
3. I plugged the USB cable back into the phone and ran the 'run.bat' file I extracted from the One Click Root 2.5.5 download. In short order my phone rebooted into rooted Froyo. (confirmed by going into Applications and seeing that 'Superuser' is installed)
Now it's time to set up CW3 and ext4:
1. I went here and downloaded a different One Click Root (anyone know if I could have used this instead of 2.5.5?).
2. Again, with USB debugging enabled and the USB cable plugged in, I clicked on 'run.bat' extracted from the One Click Root CWM3 download. After a brief wait, the phone rebooted. Theoretically, at this point I have Clockwork Mod 3.0.0.5 and my phone can handle ext4 filing. (Speaking of ext4, I thought that was intended for handling LARGE files on teranyte-plus HDDs. How is it the right choice for a smartphone?)
And to try a new ROM:
1. I went here and downloaded CyanogenMod 6.2 prebeta 14 and saved it to the root directory of my phone's SD card.
2. Powered down the phone, and reinserted the SD card.
3. Powered up into ClockworkMod Recovery. The screen showed that it was running v3.0.0.5. ClockworkMod automatically checked for ext4 but failed to mount. ClockworkMod suspected my files are still in rfs (admittedly, I never reformatted my SD card to ext4). ClockworkMod created a backup named 'before-ext4-convert-1296478915' in case I need to restore. At this point, I found myself in ClockworkMod's menu.
4. In ClockworkMod, I ,ped data/factory reset 3 times, cache partition 3 times and, under /Advanced, wiped Dalvik cache 3 times. I then went back to install zip from SD card and chose the CyanoGen Mod I wanted to try, but it failed. ClockworkMod noted that Amend scripting (update-script) is no longer supported and that I need to switch to Edify scripting (updater-script and update-binary) to create working update zip packages. So I went back to my SD card and told ClockworkMod to install gapps-hdpi-20101218-EPICv1.0.3.zip, which completed without error. Then I told ClockworkMod to install NebulaMod. The phone rebooted and all seems well.
Thanks! I sure was stuck last night, and just needed a nudge in the right direction.

Whoah. Whatever you do, don't follow my advice. This just bricked the phone. It will not even power up any more. Damn.
Correction. Not bricked. Just really, really scary. Thanks to Koadic I'm back at unrooted Froyo. I think maybe I'll stay here for a while.

Cincinnatux said:
(Speaking of ext4, I thought that was intended for handling LARGE files on teranyte-plus HDDs. How is it the right choice for a smartphone?)
Click to expand...
Click to collapse
Ext4 wasn't intended solely for handling large files. It made some changed to ext3 that allows handling of larger files and also increases the subdirectory limit, which makes it suitable large files or large disks. Ext4 also added journaling. These are not the reasons we use ext4 on our phones. I think all of our ext4 roms mount the disks with the noatime flag, and many people are running the no-journal mod. This makes ext4 act more like ext2 with the ability to allocate extents instead of individual block.

"Amend scripting (update-script) is no longer supported and that I need to switch to Edify scripting (updater-script and update-binary) to create working update zip packages."
My phone also says this when I try to install the Truly-Epic rom. I'm on DK28 like the rom says to be on, and on CWM3 and EXT4...yet...it doesn't want to install. Anyone know what for or what might be any problems?

how long did it take for your phone to power up after rooting with ext4 and cwm3? mine has been at it for a while now. i flashed back to stock dk28 using odin and did the process over and it gets stuck backing up my information and just keeps creating before ext4 back ups til my memory is gone

help(resolved)

Hey I just seriously screwed my self over bassicly I tried to get miui to boot from the samsung fascinate however when I installed it in cmr it spassed out then powered of then went to the bootloader and I get a red error message saying can't mount data or something so then I tried to reinstall Eco 3 Odin using Odin and it worked it booted but it says I have zero data on my phone and I can't install anything. I also tried the oneclick soft unbricker but it fails saying adb divers are not installed when they are. I'm doing this on my phones browser witch is the only thing that seems to be working right now I also tried a band restore but I got the same data error message.

Have you tried restoring to DL17 and then re-upgrading to 2.2?

And how about a good old odin flash?
In worst case, I would ask imnuts for the full odin package, or use a fascinate full odin package to get you off your feet, then reflash the modem, and recovery, then wipe In recovery cyan cwm... Then flash ec03
Sent from my SCH-I400 using XDA Premium App

wait wait, is this on a Continuum or Fascinate?

Nuckin said:
wait wait, is this on a Continuum or Fascinate?
Click to expand...
Click to collapse
He is on a Continuum, but you can use a fascinate Odin package to reformat partitions if they get messed up, then just reflash recovery and start fresh if you can get in then... That wasn't a really good thing though to suggest to a newcomer necessarily, so thank you for pointing that out

okay heres what happened firts i wanted to see if i could get the miui rom for the samsung fascinate to boot on the continuum there pretty much the same phone minus the ticker and screen size so i went into clockwork mod and wiped everything then went to install zip from sd card and clicked on the miui rom witch was the process we always used on the hero. then after i clicked on it, it started to install then my screen started shacking and my phone turned off. when i turned it back on it when to the bootloader and a red error message poped up saying
e:cant mount /dev/blockstill(invalid argument
and when i go to recovery it says the same thing when i try to wipe/restore nand it says the same thing. so at that point i powered off and went to download mode and reinstalled eco3 odin using pda mode on odin and it worked then it rebooted and i got to the set up screen and i got 2 force closes daily brefeing and something else i went ahead and skipped all that stuff and it loaded fine after that. however now for some reason it says i have zero system memory so i cant install any apps or save data however it does recognize my sd card but i cant install to sd card. so bassicly the phone functions just no internal memory. at this point i honestly dont know what to do everything on the hero was simple and straight forward and we never ran into these kind of problems. ive also tried to restore my nands and reinstall clockwork mod but still no dice. what i need to do now i guess is get the necessary files to go completely stock and see if that helps. and if someone could point me in the direction to those files i would really aprechiate it. oh and i tried the one click unbricker it sayed success but didnt really do anything.
oh and i know trying to install miui was stupid but i was just wanting to see if it would boot lol.

Download the PIT file in the Development forum, as well as the DL17 Odin package from the FAQ of the EC03 post I made. Flash the DL17 in PDA, with the PIT, and re-partition selected. After that, you should be back on DL17, and can do whatever you want from there.

huzzza!!!
thank god that worked thank yall so much i still cant believe that just happened but restoring the stock odin image worked and all is well. so i guess tommorow i can reroot and restore my nand.
once again thank yall for the help.

Galaxy Tab 2 10.1 Recovery Post Mortem

A story you might find some useful morsels in . If you are impatient, yes, a happy ending.
Monday night I opened the case on my tablet and it was booting. I figured that was strange and after a few minutes realized it was just stuck booting. So I rebooted it. Came up... and then suddenly during the everything loading up phase, rebooted. This repeated several more times.
Uh oh. Working quickly between boots I unset the default on Apex launcher (since it updates frequently) and turned off the live wallpaper. I also shut off Wifi. No effect.
Next stop recovery. Cleared caches, etc. Nope. I had a fairly recent backup but took another one and it worked (whew). Decided that I would do a data wipe from recovery. Uh oh. Any attempt to format /data causes a crash.
I go to Odin to see if I can repartition flash. I can't find a PIT file for the P5113 but did find one for a 16K 7 inch model. Odin repartitioned it but still no joy. Wiping data causes a reboot. So does trying to restore a backup to /data.
Next stop Kies. You can tell it to reload firmware but you need your serial number which is written on the back of your tab (yes it is, it is about the height of a carbon atom). However, it asks you to enter "recovery" mode by pressing buttons that aren't on the tablet. I tried Odin mode but it couldn't connect. Using CWM recovery didn't work either.
So I decided I needed stock recovery. I could not find a P5113 stock recovery that wasn't bundled with an entire update package. So I unpacked an update package to get recovery.img. Flash_image didn't work (seems like it never works on this tablet, and now that I think about it, I think I wrote a thread on how to do it with dd that I forgot about last night! Duh: http://forum.xda-developers.com/showpost.php?p=31293383&postcount=32). Instead, I repacked just recovery.img with tar. Odin was able to flash this and I was back in the ugly stock recovery.
I never did try Kies though because I asked the stock recovery to reformat /data and it worked! Back to Odin to reflash CWM and then the backup I made Monday night rolled back on and I was back in business.
Restore my screen saver, redefault (is that a word?) Apex, and turn Wifi back on. Oh yeah, and run Triangle Away
So I'm not sure what to make of all this. Open questions:
1) Did I need to repartition? What's the right PIT file to use? I sure wish Odin could dump a clean image, but if it can, I don't know how.
2) What mode does Kies want? This could have been a VirtualBox problem but I got it to work before I got Kies installed on my wife's real Windows box (man Kies is slow!).
3) Why could stock recovery reformat /data but CWM could not?
4) Would it have been sufficient to just reflash the stock recovery, do the data wipe? I suspect so, but don't know.
Anyway.... things are back to normal. Love the tab, but sure wish these big companies wouldn't assume we don't know how to fix our own stuff and muck things up with "simplified" tools. By the way, this is the "touch" CWM that seemed to fail to fix /data. I did not try the normal one.

wd5gnr said:
A story you might find some useful morsels in . If you are impatient, yes, a happy ending.
Monday night I opened the case on my tablet and it was booting. I figured that was strange and after a few minutes realized it was just stuck booting. So I rebooted it. Came up... and then suddenly during the everything loading up phase, rebooted. This repeated several more times.
Click to expand...
Click to collapse
Here we go again. Same problem but I'm not even getting into the boot. Does anyone know how to actually reformat and rescan flash for bad blocks? I have a feeling I have a bad flash block that is doing something evil.
Sigh.

Tried a different approach this time.
Booted to recovery and did an fsck on /data since it seemed to have the problem.
It did a lot of clean up and now I'm back up. Not sure what got damaged if anything though. Time will tell.

Good to hear that it is a happy ending, bro!
Sent from my AT1S0 using xda app-developers app