Returning to stock + clean memory - Samsung Infuse 4G

Cant find an answer for my question:
I am reinstalling some ROMs. Came from Captivate a few days ago (dropped in in the toilet and didnt think it would come back to life, it did lol, after i bought an infuse)
When flashing captivate roms the return to stock odin/heimdalls also format your sd cards, I noticed when returning to stock on the infuse my sd card is still full of crap from the last rom, how do I go about fixing that, can I just format it in CWM or will that ruin ROM install, as I had to modify the 3e recovery to even get CWM on?

votum said:
Cant find an answer for my question:
I am reinstalling some ROMs. Came from Captivate a few days ago (dropped in in the toilet and didnt think it would come back to life, it did lol, after i bought an infuse)
When flashing captivate roms the return to stock odin/heimdalls also format your sd cards, I noticed when returning to stock on the infuse my sd card is still full of crap from the last rom, how do I go about fixing that, can I just format it in CWM or will that ruin ROM install, as I had to modify the 3e recovery to even get CWM on?
Click to expand...
Click to collapse
sdcard will format if you do reset phone in the phone menu /settings/privacy/reset
you can also format what you want in cwm

qkster said:
sdcard will format if you do reset phone in the phone menu /settings/privacy/reset
you can also format what you want in cwm
Click to expand...
Click to collapse
Thanks for the answer mate, just wanted to make sure formatting in CWM wouldnt ruin anything, like CWM lol

votum said:
Thanks for the answer mate, just wanted to make sure formatting in CWM wouldnt ruin anything, like CWM lol
Click to expand...
Click to collapse
So...I formatted the SD card in CWM, but now when I try to install any rom after running Heimdall One-Click, I can't get past the SAMSUNG logo screen. I get the robotic woman's voice saying "Convert data partition. Not enough space on partition." Then the phone just boot loops from there.
I can run Heimdall all day, but I can't install any roms. I can't get Odin to work. I guess I need to set a partition, but I'm not sure how to do this or what to set it to.

sd619 said:
So...I formatted the SD card in CWM, but now when I try to install any rom after running Heimdall One-Click, I can't get past the SAMSUNG logo screen. I get the robotic woman's voice saying "Convert data partition. Not enough space on partition." Then the phone just boot loops from there.
I can run Heimdall all day, but I can't install any roms. I can't get Odin to work. I guess I need to set a partition, but I'm not sure how to do this or what to set it to.
Click to expand...
Click to collapse
try flashing the heimdall 1 click once.
Then afterward, click the boot loader box and flash again the second time.
Robotic voice is voodoo ext4 file conversion. The heimdall 1 click return to stock has nothing to do with voodoo file conversion.
If you have corrupted partitions, you need a full re-partitions.

Thanks qkster. I tried your suggestions, but I'm still getting the same errors. I suspect I have corrupted partitions (or missing partitions) since I formated SD card in CWM. How would I get full re-partitions?

sd619 said:
Thanks qkster. I tried your suggestions, but I'm still getting the same errors. I suspect I have corrupted partitions (or missing partitions) since I formated SD card in CWM. How would I get full re-partitions?
Click to expand...
Click to collapse
If you flash heimdall 1 click, it will re-partition your system file.
I don't think it does anything to your SDCARD or external microSD card.
Are you able to get it to boot up on ATT stock?
If you flash with heimdall 1 click and bootloader, you should be able to get back to att stock.
when you are able to get into the ROM, you can try going to menu /settings/privacy and reset.
Then you can go into DL mode, flash the kernel, reboot into recovery and perform file system changes.
In the voodoo: convert lagfix to on (for custom rom) off for stock rfs.
the file conversion toggle should be ON.

I realize that Heimdall doesn't do anything to either SD Card. It's actually working great in my opinion. My problem is that my internal SD Card was formatted (stupid move on my part) in CWM and now, it's basically a blank slate. I can run Heimdall and it boot animation starts up, but then it begins to boot loop after the "Rethink Possible" screen in the animation. I can't get into the ROM at all.

sd619 said:
I realize that Heimdall doesn't do anything to either SD Card. It's actually working great in my opinion. My problem is that my internal SD Card was formatted (stupid move on my part) in CWM and now, it's basically a blank slate. I can run Heimdall and it boot animation starts up, but then it begins to boot loop after the "Rethink Possible" screen in the animation. I can't get into the ROM at all.
Click to expand...
Click to collapse
sd619...Can you tell me step by step what happens when you put it into DL mode and flash the heimdall?
Go through the whole 2 flashes - with the second time with boot loaders checked.
I think that no matter what you did to the internal SD card, once the heimdall runs the second time, with boot loaders, it will re-partition all the dev blocks and place the sbl, sbl2, params, dbfactory, kernel and modem in the appropriate allocations...assuming that the heimdall you have is not corrupted.
It will reset the file system to stock rfs...there shouldn't be any voodoo conversion until you flash the entropy kernel
...we are also talking about uclb3, correct?
if it doesn't work on repeated trial, and you are sure you have a non-corrupt software, it may be hardware.
If you want to try odin - gtg's unbrick - you will need to use a different usb port and re-install drivers or use a different PC

Yes, I'm using UCLB3. Here are my steps:
DL mode
Heimdall Flash
Disconnect USB
DL mode
Heimdall Flash w/ Bootloaders
Reboot
Boot loop during animation

sd619 said:
Yes, I'm using UCLB3. Here are my steps:
DL mode
Heimdall Flash
Disconnect USB
DL mode
Heimdall Flash w/ Bootloaders
Reboot
Boot loop during animation
Click to expand...
Click to collapse
If you take out the battery and put it back into DL mode and flash the kernel in the next step..what happens?
edit: oh...idk if it makes any difference but could you take out the microSD card if you had 1 in and try it WITHOUT the microSD?

I tried that as well. I went back to DL mode and flashed the Entropy DD Kernel. This allows me to get into CWM. If I don't boot into CWM, the Samsung logo appears and the voodoo voice tells me there's not enough room in the partition. Then the phone boot loops from there until I pull the battery or boot into CWM.

sd619 said:
I tried that as well. I went back to DL mode and flashed the Entropy DD Kernel. This allows me to get into CWM. If I don't boot into CWM, the Samsung logo appears and the voodoo voice tells me there's not enough room in the partition. Then the phone boot loops from there until I pull the battery or boot into CWM.
Click to expand...
Click to collapse
ok..if you get into CWM, click on the voodoo menu.
What does it say?

didn't think to do that...here's the info that pops up:
Voodoo lagfix is actually: enabled
next boot: enabled
Options:
/system lagfix conversion: yes
debug mode: no

sd619 said:
didn't think to do that...here's the info that pops up:
Voodoo lagfix is actually: enabled
next boot: enabled
Options:
/system lagfix conversion: yes
debug mode: no
Click to expand...
Click to collapse
try disable lagfix...next boot should say :disabled
change system lagfix conversion to : NO
then reboot
if that works, when you boot into rom: reset
get back into DL mode and reflash the heimdalls again fully

I was hopeful, but that did not work. I'm still boot looping during the Samsung logo. I also tried to turn on debug mode in the voodoo menu, but it didn't seem to change anything either.

Alright.
Last attempt:
go to Mount and Storage:
Format boot. Format system. Format data. Format Cache. Format SDcard.
/system: should read: unmount
/data: should read: mount
/cache: should read: unmount
/sdcard: should read: unmount
/sd-ext: should read: mount
go back: reboot recovery.
go back to DL and reflash.
I don't know why your partitions will not erase as it should.
I have not seen this before.
If this doesn't work, you may need to try Odin on a different pc.
If you need to warranty the phone, change the settings or flash it in a way that it will only have samsung boot loop and no recovery. It would not be wise to have a red recovery and try to warranty it...needs to be on stock blue recovery.
good luck...
let us know if you ever get it sort out.
thanks for the mental exercise.
edit: there was 1 time I got hung up in the cwm and boot loop switching between stock and custom kernel...it was being more difficult than usual but mine sorted out after I did some toggles of voodoo menu and reboot recovery and was able to fix it flashing the heimdall packages...
It may not hurt to try Adam's original UCKJ4 packages also...idk

That last ditch effort didn't work. I can get to blue recovery from Adam's original UCKJ4 right? I've used that Heimdall package before. I don't even know if I can still warranty this phone. Does it have a 1 year warranty?
I'm going to try to Odin on a different PC when I get home. It's frustrating because it's NOT bricked. I hope to have some better luck with Odin tonight.

sd619 said:
That last ditch effort didn't work. I can get to blue recovery from Adam's original UCKJ4 right? I've used that Heimdall package before. I don't even know if I can still warranty this phone. Does it have a 1 year warranty?
I'm going to try to Odin on a different PC when I get home. It's frustrating because it's NOT bricked. I hope to have some better luck with Odin tonight.
Click to expand...
Click to collapse
good luck.
Blue recovery when you flash only the ROM portion. Red recovery and voodoo when you flash the kernel over the ROM.
Warranty should still work.
Scenario: I had no idea what happened! I plugged in the kies-mini and it kept doing this...

Qkster....I tip my hat to you...
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2 Beta-5

Related

[Q] Stuck - flash always fails on movinand.bin

So, I've been running GummyCharged FE 1.9.1 with voodoo lagfix enabled for the past few months and the phone has been awesome. Two days ago, however, the phone went into a boot loop. I was listening to sirius on it when it locked up, restarted itself, then would lock up again when loading the homescreen widgets. This progressively got worse until it got down to a boot loop at the Samsung screen. I booted to CWM Recovery to try a wipe but it couldn't mount most of the partitions. So, I tried to reflash GCFE 1.9.1, which failed.
I worked on it for the better part of yesterday, trying everything I could find. I tried flashing stock ED1, ED2, EE4, in both Odin and PST, with and without repartitioning with the PIT file, trying different usb cables and ports, battery in, out, and they all fail when they get to the movinand.bin file. I also replaced the SD card as a last resort, but no dice.
The only thing I CAN get to successfully flash is a build of GCFE 1.9 that didn't have movinand.bin and a few other files in it.
After all that, here is the current state my phone is in:
-It boots directly (after Samsung logo) to CWM Voodoo Lagfix Recovery v4.0.0.8 without holding down any of the recovery mode keys.
-I was able to get the lagfix disabled by creating the disable-lagfix file on my sd card (or at least, it went through the process with the voice without any errors & voodoo recovery shows it disabled)
-CWM recovery gives an error when trying to mount /cache, /data, and /sdcard
Does anyone have any ideas on this?
Are you leaving the battery in when you flash?
Sent from my Droid Charge running Infinity Beta
Yep...battery out to connect to computer, then I pop it in once its in download mode.
can you flash a recovery? try flashing the newer 8/17 orange 4.0.1.4 version, I believe that's the one that will allow you to mount partitions correctly
Ok, I got CWM recovery 4.0.1.4 flashed. I still can only mount the /datadata and /system partitions, BUT when I rebooted from CWM, it booted all the way up to the Droid eye, then looped there for a while. (didn't fully reboot, just went back to where DROID flashes on the screen, then the eye is shown). I let it go a few times and it showed the status bar at the top of the screen, but the rest was black.
enf108 said:
Ok, I got CWM recovery 4.0.1.4 flashed. I still can only mount the /datadata and /system partitions, BUT when I rebooted from CWM, it booted all the way up to the Droid eye, then looped there for a while. (didn't fully reboot, just went back to where DROID flashes on the screen, then the eye is shown). I let it go a few times and it showed the status bar at the top of the screen, but the rest was black.
Click to expand...
Click to collapse
sounds like progress.. does anything flash? like Gummy GBE 2.0 final for example, only because I know that rom is one you can flash over anything
blazing through on my 4G Droid Charge
Is there an odin file available for GBE 2.0? I looked for a while and couldn't find one, and I can't do a CWM flash since it won't mount the sd card.
I tried flashing stock EP1W and ED1 again, and even tried it from another computer, but both failed at movinand.bin. I can mount /cache now, though, so something's happening.
enf108 said:
Is there an odin file available for GBE 2.0? I looked for a while and couldn't find one, and I can't do a CWM flash since it won't mount the sd card.
I tried flashing stock EP1W and ED1 again, and even tried it from another computer, but both failed at movinand.bin. I can mount /cache now, though, so something's happening.
Click to expand...
Click to collapse
Nope. It is only available as a CWM.

Galaxy TAb 7.7 brick, please help

Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
I also tried to flash it with .pit, PDA, PHONE and CSC. I got this screen and then stopped and Odin says "Now Writing, Please wait about 2 minutes."
I appreciate your help!
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
TML1504 said:
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
Click to expand...
Click to collapse
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
Click to expand...
Click to collapse
again thx,
but the problem is seems to be "deeper" than only a corrupt /data!
The tab doesnt boot further then "samsung 7.7", if data is corrupt then
at least android will load (bootanimation) and go into a bootloop in some stage!
Also, I didn't change or install or flash anything in rom-manager, I "only" used the reboot function!
After reflashing the device with repartition and HongKong.pit I think I messed up the partitions totally, so I would really need the PIT for 6810 (6800 has different partition layout) to repair this!
But as it seems no one has this PIT or is willing to provide it,
so I ordered an new tab which will arrive in the next hours, and return this one within the next days!
Where did you find the PIT file ? You may just destoried the partition. God bless you!
matth3w said:
Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
Click to expand...
Click to collapse
I have a familiar problem....
I have not flashed or rooted my device - it is exactly how it came out of the box...
One morning while using it it froze - I did are reset by holding the power button down and then let it reboot but when it did it can not get past the "Samsung Galaxy Tab 7.7" screen.
Can get it into download mode, but if I go to recovery mode then all I get it a headline saying "Manual Mode" which grabs some manual .apk files and then just goes back into the boot mode with the "Samsung Galaxy Tab 7.7" screen.
Any ideas?
Had a Galaxy Tab Original and got the Galaxy SII and have mod them to death - just though for this one I would leave it original and enjoy the OTA updates as the were delievered - especially considering ICS in a matter of days
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
suwandiapr said:
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
yes, that is what he means.
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem.
Obviously you will lose all user data!
suwandiapr said:
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
davp said:
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem!
Click to expand...
Click to collapse
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
Yes you right, thats what i mean..
TML1504 said:
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
Click to expand...
Click to collapse
Im sorry , my answer cannot solve your problem.. You say your device "stuck on Samsung logo" right? your recovery and download mode seem ok, from my experience its because /data corrupt or something crash on your filesystem..
If you can go to recovery menu, do factory reset,..
I cannot help you with pit.file coz i actually dont have the device right now..
Aspi914 said:
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Click to expand...
Click to collapse
Good luck..
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
Click to expand...
Click to collapse
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
白い熊 said:
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
Click to expand...
Click to collapse
You either get it from a full flash of stock firmware, or make your own tar with just recovery.img in it (extracted from stock). And flash with odin in the pda.
It is handy to be able to switch recoveries. CWM doesn't seem to match the 3e data wipe/factory reset.
The problem was:
I was playing a game, in the middle of it the Tab reset, I've never had it reset. Then it rebooted to the Samsung Tab 7.7 logo.
I thought, I'm lucky, made a CWM backup. So tried to restore the CWM backup. When the restore got to /data the tab rebooted again, i.e. something was messed with it.
So got stock firmware, flashed it from PC odin, flashed with success. But rebooted to the logo again.
Tried to get into the stock recovery, but it would only show "Updating..." something, I don't remember anymore, but the stock recovery wouldn't boot. Flashed it a couple of times, same result. Had to take the Tab back to the store...
Am kinda afraid to mess with it now, since I don't want it to happen.
So am wondering what to do if the same happens, or just forget CWM and flash stock recovery.img just to be safe?
I had similar issues after hard power-off [long hold power button]. Confirmed with adb into insecure cwm recovery that /data was corrupt. It explained why my restores stopped at /data.
Cwm data wipe, or format data did not help.
I flashed the stock 3e recovery.img in a tar with odin.
3e data wipe/factory reset. Reflash whole stock firmware with odin.
Check system boots ok.
Reflash cwm, then do restore ok.
I have seen stock 3e recovery fail to start properly. It seemed to be related to files/directories on the external sd card. It came up and said something like 'manual mode', 'updating'.
I tried clearing cache and hidden.
I know I deleted at least tmp_sec_fota directory off the external sd card, maybe someting to do with fota is upsetting our tabs from time to time.
Yep, exactly, that's it, it was "Manual mode" and "Updating", same symptoms, I couldn't get past it.
So what you're saying, I had a MicroSD in it, and that's why it was stuck at this? Not sure if I had an SD in it, but I flashed stock like three times, and then still couldn't enter 3e recovery, all the time had this "manual mode" come up...
Thanks for the guide of what you did.
Am downloading the latest Thai firmware now, to extract the stock recovery, so that I'm ready just in case.
Do you just tar the recovery.img and use that for flashing if necessary? No special permissions, nothing?
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd. It is possible the problems are in multiple locations,
It is also possible that multiple attempts have an effect.
I personally feel I need both stock 3e and insecure cwm [and odin and adb] to be able to recover this tab. The broken 3e/reboot was my worst experience on this so far.
Use linux tar or the tab's busybox tar, to create an uncompressed tar with recovery.img as the only file. Do not use 7zip to create the tar, it didn't work for me (although it works fine to extract from the stock).
davp said:
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd.
Click to expand...
Click to collapse
You mean you did this in CWM recovery? Because I hastily flashed the stock ROM when it wouldn't boot, and then I couldn't get into the recovery anymore and there was no way to flash CWM recovery from PC Odin, or is there?
SD you mean internal? Since with external you just pull it out...
This was my worst experience as well, and want to be ready if it ever happens again.
So to sum it up. If the /data is messed up, should we do the following?
1. In CWM recovery clear cache, clear hidden.
2. Flash stock e3 recovery.
3. In stock recovery wipe everything.
4. Flash stock ROM.
5. Boot.
6. Flash CWM recovery.
7. Restore backup.
please i have the same problem,where i find the stock e3 recovery?
thanks Davp!
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
please,post a link for download the recovery.img tar for to flash with odin.this is my last hope!

Showcase mounting error problem

I've just rooted a Showcase and I followed Cyanogen mod guide for installing their rom. Everything went smooth. Minutes later I started having problems with signal. Since I did a nandroid backup I decided to restore. Everything said completed successfully. When I reboot it stuck into boot loop.
I went back into recovery and tried to wipe cache and dalvik. Error mounting cache. Error mounting system. Error mounting /datadata
I tried to go back to cyanogen and the same Error mounting cache. Error mounting system. Error mounting /datadata. I changed into various clockwork mod versions and the same.
I tried restoring on two versions with Odin and I dont get any logo at all but straight into recovery. saying invalid argument and the same Error mounting cache. Error mounting system. Error mounting /datadata
Did cyanogen changed partition ext (MTD/BML?)? Im out of ideas. I spent the entire day yesterday checking different forums and trying out anything within the showcase area to make this phone boot.
I even tried to find a way to manually restore with the nandroid backup but the partitions wont mount. The only ones that does are /boot and /data and the /sdcard.
The nandroid backup is there. All i need is to be able to restore. The clockworkmod 4 I have now doesn't activate adb so I cant access the phone via command prompt.
UPDATE: I managed to restore my phone. After trying different tars and making tar with nandroid images I found a tar file of {EI20} 2.3.5. I tried it an it boot up well. I install a voodoo CWM and let me restore! Though the phone is not activated on the cdma network, at least its on factory state with the own carrier's software. Its only a matter of them activating the phone back.
UPDATE: I managed to boot it up with a Verizon Odin tar but the Phone is from another carrier so it wont go past the activate screen. I tried flashing the clockworkmod and restoring but im getting the same error mount on system. Any ideas?
lilizblack said:
I've just rooted a Showcase and I followed Cyanogen mod guide for installing their rom. Everything went smooth. Minutes later I started having problems with signal. Since I did a nandroid backup I decided to restore. Everything said completed successfully. When I reboot it stuck into boot loop.
I went back into recovery and tried to wipe cache and dalvik. Error mounting cache. Error mounting system. Error mounting /datadata
I tried to go back to cyanogen and the same Error mounting cache. Error mounting system. Error mounting /datadata. I changed into various clockwork mod versions and the same.
I tried restoring on two versions with Odin and I dont get any logo at all but straight into recovery. saying invalid argument and the same Error mounting cache. Error mounting system. Error mounting /datadata
Did cyanogen changed partition ext (MTD/BML?)? Im out of ideas. I spent the entire day yesterday checking different forums and trying out anything within the showcase area to make this phone boot.
I even tried to find a way to manually restore with the nandroid backup but the partitions wont mount. The only ones that does are /boot and /data and the /sdcard.
The nandroid backup is there. All i need is to be able to restore. The clockworkmod 4 I have now doesn't activate adb so I cant access the phone via command prompt.
UPDATE: I managed to boot it up with a Verizon Odin tar but the Phone is from another carrier so it wont go past the activate screen. I tried flashing the clockworkmod and restoring but im getting the same error mount on system. Any ideas?
Click to expand...
Click to collapse
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
jbreakfield said:
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
Click to expand...
Click to collapse
The carrier is Open Mobile; its a local carrier on PR. The is no way to get an odin tar of this company unless you take another showcase and via command prompt extract it directly from the phone or another user who did it share it over the internet. The only way I can make the restore say completed is flashing verzon odin tar, flashing CWM 4, flashing cyanogen and rebooting into recovery via cyanogen. I noticed the flashed CWM via odin is only good for flashing cyanogen. It would give allot of error. If I boot into recovery via cyanogen rom I get a CWM 5.0 instead of 4 (when booting on key commands). The CWM 5.0 allow me to restore nandroid and mount partitions but when i reboot device Im stuck at the samsung logo. I left it a few minutes and nothing.
Do you think an MTD to BML converter in a flashable zip will help booting my restore?
jbreakfield said:
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
Click to expand...
Click to collapse
I already tried it and get the invalid argument error. no boot image and straight to recovery
lilizblack said:
The carrier is Open Mobile; its a local carrier on PR. The is no way to get an odin tar of this company unless you take another showcase and via command prompt extract it directly from the phone or another user who did it share it over the internet. The only way I can make the restore say completed is flashing verzon odin tar, flashing CWM 4, flashing cyanogen and rebooting into recovery via cyanogen. I noticed the flashed CWM via odin is only good for flashing cyanogen. It would give allot of error. If I boot into recovery via cyanogen rom I get a CWM 5.0 instead of 4 (when booting on key commands). The CWM 5.0 allow me to restore nandroid and mount partitions but when i reboot device Im stuck at the samsung logo. I left it a few minutes and nothing.
Do you think an MTD to BML converter in a flashable zip will help booting my restore?
Click to expand...
Click to collapse
When you flash the verizon odin tar file, are you using an .pit file, and checking repartition? This will get you converted back to BML. The tar file must be a full flash for the repartition to work.
So I am probably breaking a rule but you need help go over to www.rootwiki.com . Go to there forums and look there they have a bunch of people over there developing for the showcase.
Sent from my SCH-I500 using Xparent Blue Tapatalk 2

[Q] CWM Data Wipe/Factory Reset gets stuck on formatting SD card

I waited 2 nights to register so I could wade through fixes and tips and have seem to come up with little to nothing. I have CWM flashed on my phone through ROM Manager with the recovery file replaced in the system/bin and the update zip in the root of the SD card.
When I access CWM and click on Wipe Data/Factory reset it breezes through the first few steps pretty quickly and then gives me this error:
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
It continues past this and then goes on to "formatting sd_card" and then just freezes. I left it on for 30mins and there was absolutely no progress. I've tried battery pulls and re-attempting the wipe with the same result. Have re-flashed CWM, ODIN'ed back to stock, etc etc and still run into the same snag. I'm beyond frustrated because since it never gets past this part I can't install the custom ROM I'm eying and it wipes enough data to have to ODIN every single time and re-root all over again. Just to be clear this error is NOT popping up on bootup but only during Data Wipe/Factory Reset and the only way out of the freeze is to do a battery pull which results in a soft brick.
If it helps any here is what I did prior to ever having run into this problem.
Rooted with SuperOneClick V.2.3.3
Installed ROM Manager
Installed RootBrowser Lite
Downloaded recovery and update zip
Placed both into root of SD card
Used RootBrowser Lite to move recovery file into system/bin
Booted into recovery mode
Attempted to Wipe Data/Factory Reset
Ran into snag on first try and every try thereafter
Can someone please tell me what I'm doing wrong, how to fix it or a workaround?
If possible a very detailed walk through would be appreciated as this is my first ROM flashing. Your help is greatly appreciated!
MidniteKitten said:
I waited 2 nights to register so I could wade through fixes and tips and have seem to come up with little to nothing. I have CWM flashed on my phone through ROM Manager with the recovery file replaced in the system/bin and the update zip in the root of the SD card.
When I access CWM and click on Wipe Data/Factory reset it breezes through the first few steps pretty quickly and then gives me this error:
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
It continues past this and then goes on to "formatting sd_card" and then just freezes. I left it on for 30mins and there was absolutely no progress. I've tried battery pulls and re-attempting the wipe with the same result. Have re-flashed CWM, ODIN'ed back to stock, etc etc and still run into the same snag. I'm beyond frustrated because since it never gets past this part I can't install the custom ROM I'm eying and it wipes enough data to have to ODIN every single time and re-root all over again. Just to be clear this error is NOT popping up on bootup but only during Data Wipe/Factory Reset and the only way out of the freeze is to do a battery pull which results in a soft brick.
If it helps any here is what I did prior to ever having run into this problem.
Rooted with SuperOneClick V.2.3.3
Installed ROM Manager
Installed RootBrowser Lite
Downloaded recovery and update zip
Placed both into root of SD card
Used RootBrowser Lite to move recovery file into system/bin
Booted into recovery mode
Attempted to Wipe Data/Factory Reset
Ran into snag on first try and every try thereafter
Can someone please tell me what I'm doing wrong, how to fix it or a workaround?
If possible a very detailed walk through would be appreciated as this is my first ROM flashing. Your help is greatly appreciated!
Click to expand...
Click to collapse
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
azcledel said:
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
Click to expand...
Click to collapse
No, actually, I didn't. I haven't seen a guide point it out or a video that went through this step. Lemme' give this a shot and see if that helps with the problem I'm running into Thanks for the quick response, hoping this is what I was missing!
azcledel said:
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
Click to expand...
Click to collapse
Unfortunately this didn't seem to fix my problem. Still encountering:
E:format_volume: make_ext4fs failed on /dev/block/mmblk0p2
Formatting /sdcard/ .android_secure...
And frozen again -_- It's bad enough that the sidekick sucks as stock (took me this long to finally want to do something about it) and that it's being difficult and resisting change.
Hmmm was your phone stock before you did anything to it? Or did you get the phone used or something?
My advice would be Odin to stock and start over try redownloading the recovery.zip to make sure it wasn't a bad download. And try again go slow and tripple check to make sure your following the instructions word for word. I've messed them up a few times cuz I got cocky but I got everything down from doing it so much and checking my work. The first time I rooted my sk4g I did it with adb not superoneclick and it was my first android phone it took me 2 hours of reading and following steps perfectly.
Sent from my Team Nightmare Amaze4G with Sense 4.0
go back to stock with odin,
Then root http://forum.xda-developers.com/showthread.php?t=1100513
Flash cwm http://forum.xda-developers.com/showthread.php?t=1124453
And them flash this kernel http://forum.xda-developers.com/showthread.php?t=1663622 (dont freak out with the first boot with this kernel let it convert the partitions to ext4 and a loud voice will tell you what is going on)
Ive had that problem from flashing recovery from rom manager, and when it comes up i just return to stock. try to save and remove the update.zip from the sd card and see if you can get into recovery again and just flash the kernel(if cwm come up)
ultraprimeomega said:
go back to stock with odin,
Then root http://forum.xda-developers.com/showthread.php?t=1100513
Flash cwm http://forum.xda-developers.com/showthread.php?t=1124453
And them flash this kernel http://forum.xda-developers.com/showthread.php?t=1663622 (dont freak out with the first boot with this kernel let it convert the partitions to ext4 and a loud voice will tell you what is going on)
Ive had that problem from flashing recovery from rom manager, and when it comes up i just return to stock. try to save and remove the update.zip from the sd card and see if you can get into recovery again and just flash the kernel(if cwm come up)
Click to expand...
Click to collapse
You are my saviour! I seriously love you! This worked PERFECTLY! I'm now running Glorious Overdos v3.3 and loving every single second of it. Because of you my phone is no longer a nightmare. You deserve a thanks

E:format_volume: rfs format failed

(For the ones who will ask, yes i have read a lot of threads with this problem and tryed almos all of them, and i even read about other phones with this problem so the point is fix this.)
Hi,
I write cuz i got this problem in mi sisters galaxy i9003 SL.
Shi is a basic user, just use the phone for calls and whatsapp. It had Pou and go Locker installed and nothing else.
The phone got slow so we decided to do "factory reset", but it doesnt formated and keep the user information even programs, so decided to flash the phone so it would be forced to wipe the data, i'vr got the same phone and flashed it a lot of times.
Flashed with odin 1.85 the PIT (latona) and no problem
Then XXKPE 4 Files, and it seems no problem, but it didnt restart so got into bootloop.
So re flashed XXKPE.
Here is when the problem starts, the phone got into a strange mode, at last i never saw it before, i ve got the android robot saying something about kernel with a loading bar, i let the phone work til it got discarged, but when i turned it on again i ve got the problem(E:format_volume: rfs format failed). Then the phone stopped charging. i manage to enter recovery mode but for my surprise it was the normal recovery from samsung and i flashed clockworkmod and even tested it. So i re flashed clockworkmod and it works, but if i flash anything it comes back to samsung recovery mode. i still can get to download mode.
I have tryed the following:
Re flash room stock entel chile ------> problem
Re flash XXKPE 4 archivos---------> problem
Re Flash clockworkmod-------> works but if i flash anithing it comes to samsung recovery again.
Re flash Kernel-------> problem
I have read about the dead memory of the phone an take it back with a SD card, i dont want to sorry. Here the SD card costs more than the phone.
So i want to try tosolve this. not a very advanced user, but i can learn quickly.
I'm open to ideas.
Thanks.
yvel21 said:
(For the ones who will ask, yes i have read a lot of threads with this problem and tryed almos all of them, and i even read about other phones with this problem so the point is fix this.)
Hi,
I write cuz i got this problem in mi sisters galaxy i9003 SL.
Shi is a basic user, just use the phone for calls and whatsapp. It had Pou and go Locker installed and nothing else.
The phone got slow so we decided to do "factory reset", but it doesnt formated and keep the user information even programs, so decided to flash the phone so it would be forced to wipe the data, i'vr got the same phone and flashed it a lot of times.
Flashed with odin 1.85 the PIT (latona) and no problem
Then XXKPE 4 Files, and it seems no problem, but it didnt restart so got into bootloop.
So re flashed XXKPE.
Here is when the problem starts, the phone got into a strange mode, at last i never saw it before, i ve got the android robot saying something about kernel with a loading bar, i let the phone work til it got discarged, but when i turned it on again i ve got the problem(E:format_volume: rfs format failed). Then the phone stopped charging. i manage to enter recovery mode but for my surprise it was the normal recovery from samsung and i flashed clockworkmod and even tested it. So i re flashed clockworkmod and it works, but if i flash anything it comes back to samsung recovery mode. i still can get to download mode.
I have tryed the following:
Re flash room stock entel chile ------> problem
Re flash XXKPE 4 archivos---------> problem
Re Flash clockworkmod-------> works but if i flash anithing it comes to samsung recovery again.
Re flash Kernel-------> problem
I have read about the dead memory of the phone an take it back with a SD card, i dont want to sorry. Here the SD card costs more than the phone.
So i want to try tosolve this. not a very advanced user, but i can learn quickly.
I'm open to ideas.
Thanks.
Click to expand...
Click to collapse
so what you are saying is every time you try to flash something... even your stock firmware via odin the phone just resets to its orignal state (i.e E:format_volume: rfs format failed).what I see from here is your device system data has been completely formatted but failed to flash any firmware.... try with memory card and sim card removed and flash KPE(all files)... there isn't any need to flash any kernel on stock so just avoid it...
follow these steps
*Get samsung USB drivers and install on the pc/laptop.
*Download ODIN and the KPE files.(for I9003 only)
*Connect your phone in Download mode.
*ODIN will detect the device and flash the stock.
*If your flash was successfull you will get your phone back in running condition.
GOODLUCK
mustafahussain said:
so what you are saying is every time you try to flash something... even your stock firmware via odin the phone just resets to its orignal state (i.e E:format_volume: rfs format failed).what I see from here is your device system data has been completely formatted but failed to flash any firmware.... try with memory card and sim card removed and flash KPE(all files)... there isn't any need to flash any kernel on stock so just avoid it...
follow these steps
*Get samsung USB drivers and install on the pc/laptop.
*Download ODIN and the KPE files.(for I9003 only)
*Connect your phone in Download mode.
*ODIN will detect the device and flash the stock.
*If your flash was successfull you will get your phone back in running condition.
GOODLUCK
Click to expand...
Click to collapse
Same thing happend to my SL and now its dead so good luck
Thanks,
Still trying to make it work, after a few tryes to flash xxKPE it stopped charging but some how re flashing xxkpe got it to work back again, but doesnt start the OS, still in bootloop.
yvel21 said:
Thanks,
Still trying to make it work, after a few tryes to flash xxKPE it stopped charging but some how re flashing xxkpe got it to work back again, but doesnt start the OS, still in bootloop.
Click to expand...
Click to collapse
The internal SD might be broken like mine.
Try boot into recovery, then adb shell, execute and paste output in this thread again:
Code:
ls -l /dev/block/mmcblk*
fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk1
There are several ways it can get broken, and i know a few ways to customize firmwares to workaround them.
i faced this problem in I9000 & I9003 and solution is .....
get memory card and format it on yr pc
make file system is fat32
when done put sd card into phone
flash the phone with pit file
make sure to mark repartion
and when done
yr phone work just fine
P>>S
never get out this sd card from phone
or it will go to loop mode again
try and post result here
B.R

Categories

Resources