Database Users

What can I flash on samsung's stock recovery too flash a rom?

I bricked my phone and kept trying too recover it with odin. I never completed the process but now i am able too get into recovery. Can anyone give me a update.zip that will flash in the stock recovery? I tried SPH-D700-DG27-8Gb-REL and changed the name into update zip, but it says
Install from sdcard..
Finding update package..
E:Cant mount /dev/black/void/179:1
(no such file or directory)
E: Cant mount SDCARD:update.zip
Installation aborted

Unfortunately, once your phone is bricked, the only way to recover it is using odin. When your phone is bricked, it's because the filesystem on the nand is messed up (like when you unplug a hard drive halfway through a format, it no longer has a filesystem and needs to be formatted). If you're having trouble with odin, first make sure you're setting it up and using it correctly, here's a link to the odin guide: http://forum.xda-developers.com/showthread.php?t=773032]link Also, that tar file isn't in the format the update.zip method in recovery is expecting, and that's why it fails to mount the zip you created. Plus, you can't simply rename a tarball into a zip without actually changing the encoding, they are two completely different file types (Would you change the brand badge on your mazda to a nissan and expect a nissan only shop to know how to fix it simply because it says nissan? :]).
If that doesn't work, try turning off BOTH your phone and computer. Pull the battery out of your phone and boot up your computer. Login and start up odin. THEN put your phone in download mode and FINALLY connect to the computer. Start the flash. Let me know if this helps !
fyi, where odin is getting stuck is also an important detail.
EDIT: Almost forgot, make sure you are using the drivers posted on these forums. There are many versions out there that are known to cause problems.

How do I get clockwork 2.5.1.2 back when I'm already in ext4? (solved)

So I have been on ext4 for a few days using quantum 2.5. Everything was working as expected there with clockworkmod 2.5.1.0 and 2.5.1.2 installed and available. This morning, I tried flashing the new midnight rom, but my file was corrupted so I went back to Mammon's Bonsai4All 1.0.4 with an ext4 kernel. Now, I can't get back into cwm 2.5.1.2. Bonsai4All should have a working recovery redirect, so I'm guessing I need to reinstall 2.5.1.2. The problem is, I can't flash the prepare.zip to ext4 with 2.5.1.0. So the question is, what do I need to push to the phone to get the modded recovery back? I have the prepare.zip and all other files from the onelickext4 1.3 and I'm not afraid of adb or using the terminal on my phone.

Boot into recovery. Goto advance. Select reboot recovery. That should bring you to v where you wanna be. If it don't then its time to odin
Sent from my SPH-D700 using Tapatalk

If you boot into CWM then go to advanced then reboot recovery that should put you in 2.5.1.2
Beat me to it.

mysteryemotionz said:
Boot into recovery. Goto advance. Select reboot recovery. That should bring you to v where you wanna be. If it don't then its time to odin
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
The problem is, that when I reboot recovery, it brings me back to 2.5.1.0. I have a working phone right now, so I don't feel like using Odin again, yet.
It seems like there should be a way to get the correct recovery back on the phone with the terminal or adb. I've only been using android since October, so it is taking some work to learn how everything is done in the android world. Luckily, I went to school for programming on linux, but I'm a little rusty.

found this tidbit in an the ext4 thread over at ppcgeeks
Please note that until other ROMs add support (namely the new recovery binary in /system/bin/recoveryfiles) I cannot guarantee recovery will function properly
Click to expand...
Click to collapse
So I'm going to try pushing the recovery file from the prepare.zip and see if that works.
edit: It works! I'm getting errors from missing bitmap files, but that should be pretty simple to copy over as well.

Bonsai4All 1.0.4 does not support ext4. I'm surprised your phone even boots, which leads me to believe that you may still be rfs.

DiGi760 said:
found this tidbit in an the ext4 thread over at ppcgeeks
So I'm going to try pushing the recovery file from the prepare.zip and see if that works.
Click to expand...
Click to collapse
Midnight has those files already
Sent from my SPH-D700 using Tapatalk

You could download the QuickBoot app from the Market. Selecting Recovery from within the app automatically boots the phone into Clockwork 2.5.1.2

siphuyoda said:
You could download the QuickBoot app from the Market. Selecting Recovery from within the app automatically boots the phone into Clockwork 2.5.1.2
Click to expand...
Click to collapse
He can't boot up so how would he get a app
Sent from my SPH-D700 using Tapatalk

You all misunderstand.
I can boot just fine. I was on Quantum 2.5 and switched to Bonsai4All 1.0.4, which was pre-ext4. I installed the ext4 kernel at the time of flashing, so the phone works.
No matter how I got into recovery after installing Bonsai4All, it went to 2.5.1.0. That includes using quickboot or reboot recovery from within recovery. And I can't flash anything with 2.5.1.0 since it won't flash to ext 4.
How I fixed it:
1. Remount as rw
2. Copy /system/bin/recoveryfiles/recovery and /system/bin/recoveryres/* from the prepare.zip to my phone.
3. Remount as ro
And voila! Now I can get into 2.5.1.0 and 2.5.1.2.

Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer

I too have epic experience 2.0.07 working with ext4. I actually have the same problem he's having so I'm gonna try his method. It boots up fine and and works but can't get into CW 2.5.1.2. Funny thing is I can still flash zip files through regular CW. Probably because they're not roms. I've checked through adb and and it says I'm using ext4. I can also tell the differance to. My quadrant score is like 1536. I know quadrant it ain't real world but the dev of midnight rom has a video in his blog showing the differance. I'm pretty close to what he got.
Sent from my SPH-D700 using XDA App

musclehead84 said:
Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer
Click to expand...
Click to collapse
The new Dual Kernel maybe? It bridges the gap between the two file systems.

musclehead84 said:
Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer
Click to expand...
Click to collapse
You can make other DK28 roms work with ext4 by flashing an ext4 compatible kernel after flashing the rom. If I had just tried to flash bonsai without an ext4 compatible kernel, it would freeze at the samsung screen and I would have to Odin out of it. I made that mistake once already when I stopped paying attention to what I was doing.

It says (solved) but I don't see the solution. guess that means I'm still an android n00b.
Stuck at SAMSUNG screen (Help!)
I had CWM3 and EXT4
I flashed Quantum Rom 2.7
tried to flash Nebula Rom 1.6 but it didn't take cuz of EXT4
I flashed ReRFS.Format.ROM.DK28-signed.zip to bring me back to RFS
reboot - hangs at SAMSUNG splash
reboot back into recovery, now 2.5.1.0
tried flashing Nebula Rom 1.6 - but reboot still hangs at SAMSUNG
tried flashing Quantum Rom 2.7 - but reboot still hangs at SAMSUNG
tried Odin, but I don't know what to do with Odin except flash the DK28 modem, so I did that, but it didn't help
so I'm basically trying a bunch of crap without knowing what I am doing, and as fun as this is - I'm kinda stuck - just going in circles

plus I keep seeing "E:can't open /cache/recovery/log" while in ClockworkMod Recovery 2.5.1.0 - and when I do the Reboot Recovery as people have said to make it go to 2.5.1.2, it still just hangs at the SAMSUNG splash...

I found SPH-D700-DK28-8G-REL.tar.md5 and flashed that and now I'm back in business - **phew**

Cobaltikus said:
It says (solved) but I don't see the solution. guess that means I'm still an android n00b.
Stuck at SAMSUNG screen (Help!)
I had CWM3 and EXT4
I flashed Quantum Rom 2.7
tried to flash Nebula Rom 1.6 but it didn't take cuz of EXT4
I flashed ReRFS.Format.ROM.DK28-signed.zip to bring me back to RFS
reboot - hangs at SAMSUNG splash
reboot back into recovery, now 2.5.1.0
tried flashing Nebula Rom 1.6 - but reboot still hangs at SAMSUNG
tried flashing Quantum Rom 2.7 - but reboot still hangs at SAMSUNG
tried Odin, but I don't know what to do with Odin except flash the DK28 modem, so I did that, but it didn't help
so I'm basically trying a bunch of crap without knowing what I am doing, and as fun as this is - I'm kinda stuck - just going in circles
Click to expand...
Click to collapse
Clarification on how I solved my problem is below. I had a usable phone the entire time, I just didn't have the cwm I needed.
It almost sounds like a your problem is a kernel issue, except you have it with so many roms. There may have been an error in the file system conversion somewhere that is causing you trouble. You don't usually get the "E: can't do whatever" error if your cwm is compatible with your file system.
My suggestion to you would be to Odin back to a good image. You do it basically the same as doing the modem. Uncheck everything on the left. Put your .pit in the pit section. Put your .tar file (or .tar.md5) into the box that says pda (the first box). Then, plug your phone in and flash.
After that, you can run the one-click root and recovery to get root and cwm 2.5.1.0 back. Then you can start playing again. Remember, if you use ext4 then you must have an ext4 compatible kernel. If you use rfs, you must use an rfs compatible kernel. You can use any rom on ext4 if you flash an ext4 kernel immediately after you flash the rom and before you reboot the phone. If you forget to do the kernel, you will hang at the samsung screen. Some roms are ext4 or rfs only, and some have a dual file system kernel. Currently, you can mix and match any dk28 kernel with any dk28 rom. Don't try to mix kernels and roms from different builds, though.
Now for further clarification on how I got 2.5.1.2 back when using a rom that didn't have it baked in:
DiGi760 said:
How I fixed it:
1. Remount as rw
2. Copy /system/bin/recoveryfiles/recovery and /system/bin/recoveryres/* from the prepare.zip to my phone.
3. Remount as ro
And voila! Now I can get into 2.5.1.0 and 2.5.1.2.
Click to expand...
Click to collapse
I guess my solution was about as clear as mud. In order to do this, it helps to be somewhat comfortable using a command line.
I used the prepare.zip that was a part of the original ext4 conversion to get the recovery files. When you open the prepare.zip it has the standard flashable zip structure and is organized according to where the files are supposed to end up on your phone. Open the zip, open the system folder, open the bin folder and copy the folder named "recoveryres" to your sd card. Then open the "recoveryfiles" folder and copy a file named "recovery" to your card as well. Put these files somewhere easy to find, like a folder named "cwm" at the root of your card.
Next, use a terminal emulator to remount your phone to rw so you can write to the protected areas. Most of our roms included a small remount script, so all you have to do is type "remount rw" without the quotes. Later you will use "remount ro" to make things read only again.
Now, you're going to copy those files that you got from the prepare.zip to their proper places on your phone. You did leave them somewhere easy to find, right?
Copy "recovery" to /system/bin/recoveryfiles/ and copy the "recoveryres" folder to /system/bin/. You may have to watch and make sure it doesn't skip any files when copying the recoveryres folder.
After that, remount ro and you are done.

[RECOVERY] 3e Recovery Modded w/ No Verification

NOTE
This is took from untermensch's thread in the Vibrant forum so I take no credit for this (http://forum.xda-developers.com/showthread.php?t=833423)
I have noticed some of you are having issues after installing a new kernel or rom, when you boot into recovery you now have 3e, which does not allow unsigned zips to be flashed. With this version of 3e it has no-verification check, now allowing you to flash whatever you want.
This zip has
1) 3e recovery modified to disable signature checking
2) disables the forced wipe after installing any update.
Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
You can either leave the modded 3e recovery or you can now flash CWM via Rom Manager
**Just like anything else, I am not responsible if this bricks your phone, this is fairly simple, follow the guide...Do at your own risk**

Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.

designgears said:
Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
Click to expand...
Click to collapse
I done the exact method above and works fine for me...
Place extracted recovery file in /system/bin/ , reboot and flash cwm via rom manager, works perfectly fine...the reason I posted was, if you read Hardcores thread, and seen this in other threads, that after flashing his kernel, when they goto recovery they now have 3e (depending on which method when entering recovery)..alot of people have done it the way I posted with no issues...im not trying to argue with you, you by far know more then me, just posting what worked for me and some others

sounds like a good idea for the people that updated to Rogers froyo that has the 3e recovery. You could just flash a new kernel, but this is definately a good alternative.
Thanks
Sent from my SGH-I897 using XDA App

If you look at Darkyy's rom he has a script that does this.

Thanks, this works flawlessly on a Rogers Froyo Stock. Now I have CWM working and good to go. The only thing left would be to apply some kind of lagfix.

Tested and works with Rogers 2.2 Rom. Thanks

skorchir said:
Tested and works with Rogers 2.2 Rom. Thanks
Click to expand...
Click to collapse
I also have.
Thanks

Works great on Rogers 2.2. Thanks

I tested it on Galaxy S i9000m bell and it work A+
i do not have to flash cf-boot to make unsigned zip to be installed
thanks a lot for your hard work.
only thing is botton function become different then original 3e
but its working A+

I'm a little confused on how the Recovery works..... I have a I897 that I flashed Cognition 2.3b8 to with ROM Manager/CWM and when I chose "reboot into recovery" from ROM Manager from inside Cognition, it worked fine after reloading packages once. A few days ago, I flashed Perception 10.1 with the firebird kernel. After noticing the battery didn't last as long as it used to with Cognition, I did some research and found the SpeedMod kernel K12L. Before I flashed it, I did a backup from ROM Manager which rebooted into CWM with no problems and did the backup with no problem. I have since flashed K12M and K12N. Now I thought I would give Cog 3.0 a shot and wanted to back up my current config with Perception 10.1/SpeedMod K12N. From ROM Manager, I chose to backup, named my backup and the phone rebooted into 3e Recovery and gave the errors you listed above but I don't understand why? Is it because of the I9000 kernel which doesn't make sense since Firebird is a I9000 kernel. Was it from flashing SpeedMod? Also noticed, that only the volume up/down buttons worked, not the power button which is also the select key. Only way out was to 3 button reboot (or pull the battery) which rebooted into CWM and then initiated the ROM Manager backup.
Any ideas why? Also, if I was to ODIN flash JH6 back to the phone, would that restore the Stock 2e Recovery? Sorry for the long post, but I'm still trying to learn this stuff and think you guys are awesome. The captivate would be a crappy phone if it wasn't for you all.

I guess if I had read your second post a little closer I would have seen that flashing SpeedMod causes it. I used your fix in the OP and when I tell it to "Reboot into Recovery" from ROM Manager, it boots into what I assume is 3e (Goes by real quick) and shows something about MOVI and verification and then boots into CWM Recovery v2.5.1.2. If I 3 button boot into recovery, it boots into CWM v2.5.1.0 SpeedMod ULFK. Seems to work now but I'm still confused. Thanks again.

Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.

davidis57 said:
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
Click to expand...
Click to collapse
Use a terminal emulator or adb shell and type...
Code:
chmod 777 /system/bin/recovery
That should give r/w permission to the file, ...i just tested to verify it and it worked for me. also if you have Root Explorer you can just long press the file and select Permissions and check all the boxes.

Exact the same thing is happening to me! Beforehand I had flashed CF Root to get Superuser also at the same time when rooting. I Still can boot into recovery with 3BR and come into the speedmod ULFK settings. Speedmod introduces 3e and you need signed packages. You must have 2e for this I assume!? Can anyone tell me what goes wrong?

Im using the Speedmod kernel and it always pissed me off that everytime I wanted to flash somethng via CWM that I had to pull the battery and restart my phone for it to finish because of the 3e 'no signed packages'
I did the steps in the OP and I noticed that I didnt even have a recovery file in system/bin but I put it in there anyway. I rebooted and flashed a different modem just to check and sure enough, it worked. Now I dont have to worry about pulling my battery and having to reboot my phone everytime I want to flash something.
Thanks for this!

Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?

davidis57 said:
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
Click to expand...
Click to collapse
Once you install cwm and reboot back into 3e, select reinstall packages, it will install cwm and then load into it , if it doesn't then the file didn't copy over, make sure it replaces it ok, I've used this quite a few times and it works everytime, and everyone that has posted has not had an issue, so it does work
Sent from my SGH-I897 using XDA App

It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App

davidis57 said:
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Try starting over, delete the recovery file and also delete the update.zip on the root of the sdcard, then copy the modded recovery over to /system/bin/ , then open rom manager and install cwm again, something could have happened with the update.zip, cause if you are able to get into 3e and select reinstall packages and it actually starts but errors out with the update.zip, then something could possibly be wrong with the update.zip .. it might restart after you select reinstall packages, but it should then load in to cwm, if it doesnt and boots back into android, then go into rom manager and select restart recovery and see if that works

[HOWTO#GT-i9000] The way I fixed my phone (E:failed to mount...))

First of all, sorry for my poor english, its not my mothers language, but I hope you will get what I mean.
My experience with errors during custom rom flashing & fixing them.
A lot of people have had this problem, when they try to mount internal SD card from recovery (to access it on PC) they get this error:
Code:
E:Can't mount /sdcard, E:Unable to write ums lunfile (No such file or directory)
I can't explain why its occurring, what is causing it, but from time to time I fixed it by just rebooting again to recovery, or in android, then turn it off, take out battery, then put it back, and boot again in recovery, well for me it was like a lottery, sometimes its worked sometimes not.
Last time I was unable to get pass that error, tried everything but still no luck. So I thought maybe I will flash stock firmware, and its gonna be OK. But no, not this time, I took as usually XXJVU firmware, PIT512, Odin3 v1.3 (with re-partition checked) and let the flashing to begin. In Odin everything was OK, till I got into phone after restart, where its should copy all the media files, and finalize firmware installation. What I got there was this:
Code:
-- cpoying media files...
E:failed to mount /sdcard (file exists)
E:copy_dbdata_media:cant mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
Aplied the CSC-code 'KOR'
Successfully applied multi-CSC.
After this I tried few other 2.3.x stock firmwares, but all of them got stuck at the same place.
I did a lot of searching on google, I found a few "worth to try" solutions (mostly from XDA members) but none of them actually fixed my problem. And I also seen that many people are getting the same exact thing. So I did a temporary fix, I put an old 1GB SD card into my phone, trough recovery mounted it successfully and flashed CodeNameAndroid, I was able to boot into android, but many things wasn't working, and still, internal SD card wasn't accessible, so next thing was, while I was on my break, I bring my phone to a phone repair shop, and the guy said that he can try to flash it back to stock firmware, so I gave him a shot, later when I came by, he said that he was unable to fix it, so that was where its all ended. But still I didn't believed that my almost 4 months old phone's internal SD card just simply died. So what I did, I went home and tried once again. And here is what I did:
Solution
1. Took the same XXJVU firmware
2. Flashed it using: Odin3 v1.3, PIT512, Re-partition ON.
After that I got into SGS logo bootloop, and the same thing, and I was ready to threw my phone against the wall. But before I still had a hope that maybe I can fix it, so this time I did these steps:
3. Same firmware
4. Flashed it using: Odin3 v1.3, PIT503, Re-partition OFF, and Phone Bootload update ON
And guess what ? Its worked!
There wasn't any errors, nothing, its just booted and I had my phone in service again.
I hope this will help someone who has exactly the same problem, and can't find a way to fix it.

Please, can u upload the 503 pit file ?

When Re-partition is OFF the PIT-file will NOT BE FLASHED by Odin.
Partition Information Table of whatever PIT-file will have no effect on phone.
Most Samsung ROMs need 512.PIT to set correct file system RFS and size of /system /data + + partitions. Not necessary to reset your partitions/filesys every time you flash ROM.
Use 512.PIT when you have ext4 (lagfix) filesys, CyanogenMod, MIUI or ICS ROMs and want to return to Samsung stock.
Bootloader (Sbl) of Froyo and Gingerbread are not the same. Odin will take care of updating bootloader IF PHONE.tar includes sbl.bin.
DO NOT tick update bootloader, just flash PHONE, MODEM, CSC and you'll get updated bootloader.
More here: http://forum.xda-developers.com/showthread.php?p=14273101
Sent from my GT-I9000

Problem with internal SD not solved yet
O-T said:
When Re-partition is OFF the PIT-file will NOT BE FLASHED by Odin.
Partition Information Table of whatever PIT-file will have no effect on phone.
Most Samsung ROMs need 512.PIT to set correct file system RFS and size of /system /data + + partitions. Not necessary to reset your partitions/filesys every time you flash ROM.
Use 512.PIT when you have ext4 (lagfix) filesys, CyanogenMod, MIUI or ICS ROMs and want to return to Samsung stock.
Bootloader (Sbl) of Froyo and Gingerbread are not the same. Odin will take care of updating bootloader IF PHONE.tar includes sbl.bin.
DO NOT tick update bootloader, just flash PHONE, MODEM, CSC and you'll get updated bootloader.
More here: http://forum.xda-developers.com/showthread.php?p=14273101
Sent from my GT-I9000
Click to expand...
Click to collapse
After applying the methode as described in post 1, it did not resolve my problem. Internal SD still not usable.
When following the above (link to post) all the possible solutions did not work.
Could someone please let me know how to fix the internal SD so it can be used again?
Thanks in advance!:good::good:

Tab 7.7 P6810 SERIOUSLY bricked..!! :(

Hi Folks,
I'll try to be as detailed as possible..days ago, I flashed a custom ROM on my ICS 7.7 stock Tab, however it kept on a boot loop. I made a backup via CWM so I tried to restore back to ICS...can't restore it ("Error while restoring /system") OK, no worries....
I tried to flash the HC and ICS stock back using ODIN....can't do it (in both times, It keeps getting stuck at "factoryfs.img" at the beginning)...starting to get worried..
Tried to use adb shell and e2fsck -cy /dev/block/mmcblk0p9.... no luck (kept getting the "error reading block *numbers increasing* (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps. Ignore error? yes Force rewrite? yes" and then nothing happened...tried to wipe/format data...CWM crashed
Tried to flash a P6810 PIT file to repartition the tab...no luck, ODIN still stuck at "factoryfs"
Tried to flash Android Stock Recovery...finally got wipe/format data to work...tried to flash "SkyHigh ROM" based on stock ICS (Remember that ODIN method doesn't work?) it installs, BUT when rebooting, it just stays looping at the Samsung Logo... now oficially Freaked out..!!:crying::crying:
Finally everytime I went to recovery mode, I get the following:
"E:failed to mount /preload (Invalid argument)
E:install_application_for_customer:can't mount /preload
your storage not prepared yet. please use UI menu for format and reboot options
copy aplication failed"
Like I said, I can wipe/format data and cache on stock recovery (can't do it on CWM) and also can flash ROM .zips (can't do it in ODIN)
So, to sum it up:
- Can't flash anything using ODIN (stuck at factoryfs)
- Can't flash using CWM (getting Samsung logo bootloop)
- Can't wipe/format data on CWM, it crashes (althought I can do it with stock recovery)
- VERY BASIC skills in adb shell (don't know to use it very much)
- I know (hope) it's not hard bricked because I can enter Download and Recovery modes
- Basically at this point, yeah I'm pretty sure to start banging my head on the wall
Can anyone help me out on this one..??? It's been 4 days trying everything
Any, ANY help will be deeply appreciated... :crying:
Thanks

have you wiped using the stock recovery? this happened to me before (there's a thread here entitled stuck at bootscreen/boot loop) some let the device drain it's battery, what I did was wipe it using the factory wipe the connect via ODIN to install the stock HC ROM

I wiped using the stock recovery...however, everytime I try to flash HC or ICS stock ROM using ODIN, It gets stuck at the very beginning of the "FACTORYFS" phase....
Last night tried to adb shell but now it gives me the "/system/bin/sh failed: no such file or directory"
I've been reading every single thread about how to revive it, but somehow I can't....

Go to notes forum they have threads how to repartation yr tab n make it work
Sent from my GT-P6800 using xda premium

i got stuck at the 'FACTORYFS' in ODIN no matter what i tried. i had flashed CWM using ODIN, but no ROM would flash.
turns out my usb cable being plugged into a USB hub was the culprit. it still flashed CWM like that, but the first time i tried flashing the ROM with the USB plugged right into my desktop, it worked.
just throwing that out there.

Yes. Seems like you have emmc bricked your tab. There is a fix for it. Search for emmc bug
Sent From the Tab

idiotekniQues said:
i got stuck at the 'FACTORYFS' in ODIN no matter what i tried. i had flashed CWM using ODIN, but no ROM would flash.
turns out my usb cable being plugged into a USB hub was the culprit. it still flashed CWM like that, but the first time i tried flashing the ROM with the USB plugged right into my desktop, it worked.
just throwing that out there.
Click to expand...
Click to collapse
to add to this. while i was experiencing this, i too could not flash any zip rom via CWM, it would bootloop also.
however i could wipe cache using CWM, which you can't.

Finally got it working... !!! However I could only installed CM9 "successfully" since it keeps freezing and crashing...Is there any stable custom ROM that I can install via CWM..?? (Odin keeps hanging at "factory's")