Database Develop

[Q] Can't boot into OS not matter how many times I flash it with Odin...

Hi all I own an international i9000 (Hong Kong version),
My little woe started like this, I was uninstalling RyanZA's OCLF, when I encountered an error where I couldnt uninstall the ext2 tools. I read somewhere on a fix for it, where I downloaded a app called Mount /system (rw / ro) in which i set the system to RW, and then I was able to uninstall ext2 tools.
Afterwards I tried to install the Voodoo lagfix via odin.
After that, it refused to boot to the load screen (Galaxy S logo) and stayed in the i9000 screen saying restore operation then the device reboots itself.
Out of desperation I reflash my phone with my phone's 2.2 firmware "I9000ZSJPE" but that didn't work either, the first time it boots when I flash the firmware, I get taken to recovery mode, and I get this message:
update media please wait
E:Can’t mount /dev/block/stl10
(invalid argument)
E:copy_dbdata_media:can’t mount DBDATA:
your storage not prepared yet,please use UI menu for format and reboot actions.
copy default media content failed
No matter how many times I flash the firmware, I keep getting this message...
Is there any way to get my phone up and running again?
Thanks!

Hey, dont panic, its no biggie... this happened to me last week, you need to find a firmware that contains 'dbdata' im unsure which ones do contain it... i know darkys 9.2 Odin version definately has it... thats the rom i used to fix my phone last week.
EDIT: found this.... this should work :
This one is easy to fix so don't panic.
Download this ROM and extract (Odin 1.7 and 512.pit are included), then do as follows:
-Start Odin and load 512.pit, don't connect the phone yet.
-Make sure "Re-Partition" is checked, don't change anything else.
-Load PDA.tar.md5 as PDA, MODEM.tar.md5 as PHONE and CSC.tar.md5 as CSC.
-Put your Phone on download mode and connect it, start flashing.
When flashing is done, the phone will enter recovery mode, if it get stuck at the same error, simply do a wipe/factory reset and reboot the phone, the phone shall boot normally then.
Link: http://www.multiupload.com/PZNPALHVDW

damn, this is why we NEED XDA forums and other members! I would have hyperventilated if this happened to me! good thing there is a solution posted here

It seems my earlier reply did not send through, but I'll say it again,
Thanks a lot!!! my SGS i9000 is up and running again!!!"

Hey no probs !!! glad to hear you got it fixed nothing worse than the feeling of your beloved precious phone dying infront of your eyes, and the sweat dripping down your forehead when you try mouth to jack input resuscitation.................. or is that just me ??
haha anyways hitting the thanks button would suffice

Unable to boot Galaxy Tab

It's a Sprint Galaxy Tab.
I went to the sticky in the dev forum on how to unbrick. Ran Odin and the stock software, it goes through successfully but when I boot it will have the Sprint splash screen and then just goes to a Samsung screen and never comes off of it.
When I go to the Recovery screen, I get this message:
E: Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E: Can't mount CACHE:log/recovery.log
E: Can't open CACHE:log/recovery.log
E: Can't mount /dev/block/mmcblk0p1
(No such file or directory)
it also repeats this when I try to do a wipe on it.
I've tried putting an update.zip on the SD card and it will go about 1/4 of the way before going to the screen with the exclamation point and the Android guy.
I've tried using the EA24 flasher. When I click the Start Download button to start the software update I get an error that says "Unable to open binary file!"
any other ideas on where to go from here?

Sounds like you just need to do a factory reset / wipe in recovery (I saw the same errors and did the same when I flashed the Sprint Gingerbread ROM to my Verizon Tab). That worked for me, I'll bet it works for you too.
EDIT: Hmm, sorry I missed that you said you wiped already?
I used Heimdall to flash kernel + factoryfs.rfs in my case, that alone should be enough to be up and running I would think.
update.zip method is *very* fussy, all files are hash checked, needs stock recovery and stock kernel etc., that did work for me one time, but as I say, it's very fussy. I'd think a stock rooted ROM (like here http://forum.xda-developers.com/showthread.php?t=1161033) may be best. Worth a shot anyway.

yep, did the wipe and it pulled that message.
Tried SuperOneClick to see if I could get anywhere but no luck. Was looking through the sticky about trying to root it and run a different ROM to see if that may help but it looks like I need a working unit to do that to get into some of the settings like USB debugging and what not.
I am going to try the heimdall thing next. Hopefully I can get somewhere with that because I'm running out of options. Appreciate the info!

Make sure you use your shipped stock rom... It maybe you have locked bootloaders and it won't allow you to upgrade without unlocking 1st...
Not sure about the CDMA gtabs though as I use a GSM tab, though reflashing the supplied rom seems to fix most things...

One thing to remember if you get errors in cwm is to go to advanced, then reboot recovery. I have gotten errors just like yours and that fixed them. Also a stock heimdall will fix you. Since we don't mess around with bootloaders on the sgt you gonna be hard pressed to brick you tab. Let me know if this helps.
Personally I've given up on cwm until I see some more progress. Heimdall works well and the stock rooted gb is great for me. I've gotten into a pinch quite a few times lately and come through even gotten the phone...!...pc screen freaked me out esp when I wasn't getting odin to pick the tab up. Let me know if you need some help!
Sent from my SPH-D700 using XDA App

[Q] Potential FULLY bricked Note.

This is my first post, go easy on me! I own a few Android devices, all rooted, and flashed over probably hundreds of times. I know all the risks associated with it, and I take full responsibility for anything that happens to my devices. I've never had any problems in the past getting around recovery and dealing with custom ROMS...nothing that can't be fixed anyway (boot loops, force closes, ect...).
I've never seen so many problems with recovery than I have with the Galaxy Note, however. I mean, if you can't depend on a recovery to work, what are you to depend on? I had a bit of a panic flashing some of the ICS leaks, but all was resolved. No biggie. Everything was running smoothly, and somehow my recovery became fully operational again. I was able to mount /system...and was fully able to flash from CWM again, as opposed to Redpill.
Okay, long winded I know...but here I am. I just flashed angelom's newest kernel with touch recovery. "Cool" I thought. Couldn't hurt. So I went in to do a wipe of /cache and it hung up. No biggie again. I held down the magic three buttons, and when I rebooted back into recovery, I get this....over and over again.
"E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
No files found."
I've tried flashing Redpill again and installing, restoring stock back up, powering down and taking my battery out for a while...bashing my head on the wall. No matter what I do, it doesn't get past the Samsung logo. It was hanging up on booting before, but now it won't even go that far. Do I venture down the path of Odin (which I still am not entirely sure how to use)...or do I have a full brick on my hands? Looks like I might have fried the internal storage. If that's the case, I'm ****ed...simply put.
Anyway, ANY help would be greatly appreciated. Hopefully someone else has run into a similar problem and has a fix...no matter how complicated. Thank you for your time!

Try getting into Download mode (Volume down + Home + Power). If you can do this, then just flash any of the older stock Roms with PC Odin - these are easily rootable using zergrush method - and keep on flashing.

chasmodo said:
Try getting into Download mode (Volume down + Home + Power). If you can do this, then just flash any of the older stock Roms with PC Odin - these are easily rootable using zergrush method - and keep on flashing.
Click to expand...
Click to collapse
I can do that! I was always skeptical of ODIN, but it might be a life saver now.
Okay, so I get the little green Android guy and it says "Downloading...Do not turn off target!" So then I download PC Odin, connect USB cable and flash away? Sounds simple enough. I'd really hate to think I have a 700 dollar paperweight. I'll do some homework first. Thank you, by the way!

smalmagal said:
Okay, so I get the little green Android guy and it says "Downloading...Do not turn off target!" So then I download PC Odin, connect USB cable and flash away? Sounds simple enough. I'd really hate to think I have a 700 dollar paperweight. I'll do some homework first. Thank you, by the way!
Click to expand...
Click to collapse
Yes. Go here, download N7000XXKK9 stock Rom and flash it with PC Odin.
Then go here, and root it using Method 2: Root + CWM recovery.

I use Linux, so I'll have to wait to use my friends Windows PC. Installing a virtual box is more trouble than anything. This is how I rooted my device the first time. They don't make things simple for us Linux users! Anyway, I'll let you know how it goes tomorrow. Thanks again!

chasmodo said:
Yes. Go here, download N7000XXKK9 stock Rom and flash it with PC Odin.
Then go here, and root it using Method 2: Root + CWM recovery.
Click to expand...
Click to collapse
Edited: Sometimes after flashing stock Rom you get into bootloop when Odin restarts the phone. Don't panic if this happens. Pull out your battery, wait a bit, put it back, boot into stock Recovery (Volume up + Home + Power), and do factory reset and cache wipe. Reboot and enjoy.

I got the same thing tonight!!! Damn!
I can't do anything with /data partition in any version of CWM - RedPill too. It just hangs. It can't be wiped or formatted. And phone doesn't boot. I flashed KKA 1 file firmware via odin, but the phone still doesn't boot. I'm now downloading KK9 in hope that it is 3 file (because I can't find info whether it is 1 or 3 file) to try to flash it. Also using pit and repartition could fix it, but I am frightened by messages "do not ever tick repartition or you get brick".
Very sad.

guys, i need help please. My Note not work in download mode and cwm recovery. I made a homemade JIG, but not works, too. I tested the homemade JIG in a galaxy ace and in a galaxy S2 and enter instantly in download mode but in galaxy note no. my pc and other pc does not recognize the phone either. Can I do anything?
Thanks

eliot_11 said:
guys, i need help please. My Note not work in download mode and cwm recovery. I made a homemade JIG, but not works, too. I tested the homemade JIG in a galaxy ace and in a galaxy S2 and enter instantly in download mode but in galaxy note no. my pc and other pc does not recognize the phone either. Can I do anything?
Thanks
Click to expand...
Click to collapse
plug phone into usb to pc. Take battery out, wait 30 sec, while holding volume down put battery in and keep holding until download screen comes up
see if this helps
or do this if that doesn't help
http://forum.xda-developers.com/showpost.php?p=13856913&postcount=5

B.Maximenko said:
I got the same thing tonight!!! Damn!
I can't do anything with /data partition in any version of CWM - RedPill too. It just hangs. It can't be wiped or formatted. And phone doesn't boot. I flashed KKA 1 file firmware via odin, but the phone still doesn't boot. I'm now downloading KK9 in hope that it is 3 file (because I can't find info whether it is 1 or 3 file) to try to flash it. Also using pit and repartition could fix it, but I am frightened by messages "do not ever tick repartition or you get brick".
Very sad.
Click to expand...
Click to collapse
Yup...exactly...my /cache partition seems fine now...but it's hanging on /data too! Did you flash the new touch kernel from angelom too? I don't want to point fingers, but I would at least like to know what the "root" cause is. Anyway, instead of using ODIN, I used Heimdall. I'm at pretty much the same place I was before, except now I have Samsung's recovery....
Anyway, I'll keep flashing different firmwares, and I'll see where we get.
Edit: I used a .pit file as well. Was I not supposed to do that? I don't think it did any harm, as my phone still turns on!

eliot_11 said:
guys, i need help please. My Note not work in download mode and cwm recovery. I made a homemade JIG, but not works, too. I tested the homemade JIG in a galaxy ace and in a galaxy S2 and enter instantly in download mode but in galaxy note no. my pc and other pc does not recognize the phone either. Can I do anything?
Thanks
Click to expand...
Click to collapse
see my signature

Okay, so I have an idea. I flashed the repack kernel and got CWM back...but obviously my /data partition is still ****ed. Would it be possible to do a repartition of it? Do I need an ICS pit file to do this?...because I noticed the Chainfire repack has a data.img, and I tried flashing it using a GB .pit file, and it hung up...so, I think this might be my last hope!

Hey I also flashed the new ICS kernel posted by angelom...
And having same problem....
getting errors like this while entering CWM
E:can't mount/cache/recovery/command
E:can't mount/cache/recovery/log
E:can't open/cache/recovery/log
E:can't mount/cache/recovery/last_log
E:can't open/cache/recovery/last_log

Okay, so I feel a little better that it's not just me! Obviously no one, including the developer, is to blame...but the kernel is definitely the cause, and I'm having trouble with the fact that I might be spending 650 on another phone, just for the simple fact that I thought it would be intuitive to have a touch recovery. Grrrrrrr.....

thanks for your help, but my note not have signals of life. Thanks

eliot_11 said:
thanks for your help, but my note not have signals of life. Thanks
Click to expand...
Click to collapse
Sorry to hear that elliot. Is it under warranty/ensured?
Sent from my GT-N7000 using Tapatalk

I went in to wipe /cache as well, and that's when it all happened. I don't have a complete brick, but it might as well be. If I can get into recovery and download mode, but nothing works, then what good is it? A constat bootlooping phone is no phone at all. I don't insurance, and as far as I can tell my warranty is void. So I think my best option would be to send the phone directly to Samsung and see what they can do. It's better than nothing.

smalmagal said:
Yup...exactly...my /cache partition seems fine now...but it's hanging on /data too! Did you flash the new touch kernel from angelom too? I don't want to point fingers, but I would at least like to know what the "root" cause is.
Click to expand...
Click to collapse
Yes, it happened right after I flashed angelom 1.1. I used ver 1.0 for some time, didn't try to wipe data, but rom was running OK. Then I flashed imilka's v0.3 and angelom 1.1 on top, tried to wipe data and got that error message. After that, my phone hangs on boot logo and can't do anything with /data partition, and I can't restore any of my backups - it says error in /data. I flashed stock KKA firmware with odin, it didn't fix /data - stock recovery also can't wipe it.

Samsung galaxy note completely dead !!
my rooted galaxy note was on rocket rom which i updated to ics theme, and without rebooting i flashed the zip file to reset binary data count.
all this was happening in cwm.
then i opted to reboot to system and my galaxy note never rebooted.
what to do? where do i go?
phone s rooted but wont go into cwm mode, nor into flashing mode,,, does not even charge...

smalmagal said:
This is my first post, go easy on me! I own a few Android devices, all rooted, and flashed over probably hundreds of times. I know all the risks associated with it, and I take full responsibility for anything that happens to my devices. I've never had any problems in the past getting around recovery and dealing with custom ROMS...nothing that can't be fixed anyway (boot loops, force closes, ect...).
I've never seen so many problems with recovery than I have with the Galaxy Note, however. I mean, if you can't depend on a recovery to work, what are you to depend on? I had a bit of a panic flashing some of the ICS leaks, but all was resolved. No biggie. Everything was running smoothly, and somehow my recovery became fully operational again. I was able to mount /system...and was fully able to flash from CWM again, as opposed to Redpill.
Okay, long winded I know...but here I am. I just flashed angelom's newest kernel with touch recovery. "Cool" I thought. Couldn't hurt. So I went in to do a wipe of /cache and it hung up. No biggie again. I held down the magic three buttons, and when I rebooted back into recovery, I get this....over and over again.
"E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
No files found."
I've tried flashing Redpill again and installing, restoring stock back up, powering down and taking my battery out for a while...bashing my head on the wall. No matter what I do, it doesn't get past the Samsung logo. It was hanging up on booting before, but now it won't even go that far. Do I venture down the path of Odin (which I still am not entirely sure how to use)...or do I have a full brick on my hands? Looks like I might have fried the internal storage. If that's the case, I'm ****ed...simply put.
Anyway, ANY help would be greatly appreciated. Hopefully someone else has run into a similar problem and has a fix...no matter how complicated. Thank you for your time!
Click to expand...
Click to collapse
sometimes it doesnt recover, i had it with the hd2 aswell, it isnt a note specific issue, as for the title, it is misleading, a brick is not being able to turn the phone on, seeing as you coudl where did you get the notion it was bricked?
the errors in the recovery are standard if no rom is installed

I bricked my 8.9 Wifi Tab

My Wifi tab is stuck on the Samsung Galaxy Tab 8.9 Screen. I used odin to flash back to factory rom. Osin said pass and rebooted but still stuck on Samsung galaxy tab 8.9 screen. What do I need to do next? In recovery mode it says: E: failed to mount /system (invalid argument) E: install_application_for_customer:Can't mount. /system copy application failed.
--Appling Multi-CSC...
E: failed to mount /system (invalad argumenrt)
E: install_application_for_customer:Can't mount. /system
E: multi_csc:Can't mount/system

Did you format system? Try loading another ROM, seems to me your tablet is without any rom now.

cdc120 said:
My Wifi tab is stuck on the Samsung Galaxy Tab 8.9 Screen. I used odin to flash back to factory rom. Osin said pass and rebooted but still stuck on Samsung galaxy tab 8.9 screen. What do I need to do next? In recovery mode it says: E: failed to mount /system (invalid argument) E: install_application_for_customer:Can't mount. /system copy application failed.
--Appling Multi-CSC...
E: failed to mount /system (invalad argumenrt)
E: install_application_for_customer:Can't mount. /system
E: multi_csc:Can't mount/system
Click to expand...
Click to collapse
If you're using the clockworkmod, try to flash with Odin the stock recovery and the format your device from there, i was having serious problems with clockwork =/

Also managed to brick the GT7300
Hell_LordBR said:
If you're using the clockworkmod, try to flash with Odin the stock recovery and the format your device from there, i was having serious problems with clockwork =/
Click to expand...
Click to collapse
I can't even get into either recovery or download mode! Neither does the 'charging' screen shows when hooking up to power.
I first installed CWM 6.0.1.2 which went fine. Then I installed a new ROM and immediately GAPPS. That last install hung at approx 80% according the progress bar. After a while (more than 5min) I pressed the power button to shut the device down. Now it wont boot at all, not even into any download or recovery mode.
Any ideas?

I might have completely ruined my galaxy p7300 !
efoppen said:
I can't even get into either recovery or download mode! Neither does the 'charging' screen shows when hooking up to power.
I first installed CWM 6.0.1.2 which went fine. Then I installed a new ROM and immediately GAPPS. That last install hung at approx 80% according the progress bar. After a while (more than 5min) I pressed the power button to shut the device down. Now it wont boot at all, not even into any download or recovery mode.
Any ideas?
Click to expand...
Click to collapse
I have the exact same problem! I installed CWM 6.0.1.2. I started installed a new ROM...it couldn't see any program so I hit the power button...Now it is not starting into recovery mode...completely dark!!!
Did you figure out how to sort this?

salimb said:
I have the exact same problem! I installed CWM 6.0.1.2. I started installed a new ROM...it couldn't see any program so I hit the power button...Now it is not starting into recovery mode...completely dark!!!
Did you figure out how to sort this?
Click to expand...
Click to collapse
Same issue here, it wont do anything, screen stays black, tried Power + Vol Down, also Power + Vol Up. Nothing.
My PC is seeing it as APX, which was a broken driver, after some searching I came across NVIDIA USB Boot-recovery driver for mobile devices which my PC now recognises it as.
But it's still not doing anything.

Hi
I had the same. Did a wipe cache and factory reset and everything worked fine again.
Go to this by pressing power and volume up
Verstuurd van mijn GT-I9300 met Tapatalk

jeroenraij said:
Hi
I had the same. Did a wipe cache and factory reset and everything worked fine again.
Go to this by pressing power and volume up
Verstuurd van mijn GT-I9300 met Tapatalk
Click to expand...
Click to collapse
Pressing power & volume up doesn't do anything...the tablet stays black. I am in the same shoes as WodgeFW and others on this forum!
Guys, it seems we're doomed!

See this instruction for hard reset and empty cache
http://m.youtube.com/watch?v=iHNs43oRuo4
Verstuurd van mijn GT-I9300 met Tapatalk

efoppen said:
I can't even get into either recovery or download mode! Neither does the 'charging' screen shows when hooking up to power.
I first installed CWM 6.0.1.2 which went fine. Then I installed a new ROM and immediately GAPPS. That last install hung at approx 80% according the progress bar. After a while (more than 5min) I pressed the power button to shut the device down. Now it wont boot at all, not even into any download or recovery mode.
Any ideas?
Click to expand...
Click to collapse
Same for me. also after flashing CWM 6.0.1.2 and CM9 with ICS kernel. Flash was ok, but boot never ended. So i hit the power button.
Now only apx mode and bootloader seems to be locked - can't use nvflash. Also tried to drain battery - but that doesn't help.

Same problem here, after update of clockworkmod recovery to 6.0 my rom installation froze and i pressed the power button after 15 min.
Now all is black, Considering taking a chance with a warranty claim but unsure if it will accepted.
If anyone finds a solution to this it would make my day, if not then i guess its lesson learned.

grape_tonic said:
Same problem here, after update of clockworkmod recovery to 6.0 my rom installation froze and i pressed the power button after 15 min.
Now all is black, Considering taking a chance with a warranty claim but unsure if it will accepted.
If anyone finds a solution to this it would make my day, if not then i guess its lesson learned.
Click to expand...
Click to collapse
Run odin on your pc hold volume up and power check if odin reads the tablet it will show com 1-20 depends on port if so you can recover. Even if your screen is blank give it a go.its worth a try.

Thanks for the suggestion but no luck.
Am currently trying to drain battery by power cycling with constantly pressed power button. After checking other threads with similar issues it seems. To be related to a certain version of CWM. Hopefully a total drain of battery will solve my problem.
Sent from my HTC Vision using xda app-developers app

grape_tonic said:
Thanks for the suggestion but no luck.
Am currently trying to drain battery by power cycling with constantly pressed power button. After checking other threads with similar issues it seems. To be related to a certain version of CWM. Hopefully a total drain of battery will solve my problem.
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Hi, could you tell us what kernel/ROM did you use before brick your tab? Also what CWM version did you use? From what I have read, it has to have both bad kernel and CWM in combination to cause this. Thanks

nexus_g said:
Hi, could you tell us what kernel/ROM did you use before brick your tab? Also what CWM version did you use? From what I have read, it has to have both bad kernel and CWM in combination to cause this. Thanks
Click to expand...
Click to collapse
I have same problem, now i wait full drain of battery. Tab 8.9 32gb-3g. cwm version 6.0.1.2, firmware cm9-2012-09-03-experimental with A1-V1.6.2 kernel. That was nice combination - but google maps reboot my tab. i go to recovery, wipe all(data+cache+dalvik) and try to install latest cm9-nightly. when progress bar was at 60-70% tab freeze. after 10 minutes i press power button for reboot and get black screen, like topic-starter. Maybe that will be helpfull

nexus_g said:
Hi, could you tell us what kernel/ROM did you use before brick your tab? Also what CWM version did you use? From what I have read, it has to have both bad kernel and CWM in combination to cause this. Thanks
Click to expand...
Click to collapse
It's a little more subtle than that. There are essentially 2 kernels on the system: 1 in the recovery image (e.g. CWM) and 1 in the boot image (what is usually called 'the kernel'). Either one of these could cause the problem if it doesn't use the right calls (or, conversely, uses the wrong calls) into the eMMC driver. Since most of us use the recovery to do wipes & resets that is the one most likely to cause the problem. However, it has also been known to be caused by doing factory resets and wipes via the ROM (which uses the boot image kernel).
So, for this to happen you could have: a safe recovery and a bad boot; a bad recovery and a safe boot; or have both be bad.
As has been mentioned, the last 'safe' CWM appears to be 6.0.0.8.
Since the various threads indicate that Samsung is aware of this I'd assume the Stock recovery and boot images use a kernel that is 'safe'. That may be a bad assumption, but it only seems to be the use of non-Stock components that causes this, at least from what I've read so far.
Somewhere along the line a kernel that didn't have this defensive code in it made it into the source trees and then into our lives.

Thanks for explaining that so clearly.

Did anybody using other than cwm 6.0.1.2 and got brick too? Just wondering if other cwm version has problem with ICS kernel. Because apparently we suddenly have many deadbrick tabs appearing after we get the ICS kernel for our tab. Thanks
---------- Post added at 03:22 AM ---------- Previous post was at 03:14 AM ----------
boscorama said:
It's a little more subtle than that. There are essentially 2 kernels on the system: 1 in the recovery image (e.g. CWM) and 1 in the boot image (what is usually called 'the kernel'). Either one of these could cause the problem if it doesn't use the right calls (or, conversely, uses the wrong calls) into the eMMC driver. Since most of us use the recovery to do wipes & resets that is the one most likely to cause the problem. However, it has also been known to be caused by doing factory resets and wipes via the ROM (which uses the boot image kernel).
So, for this to happen you could have: a safe recovery and a bad boot; a bad recovery and a safe boot; or have both be bad.
As has been mentioned, the last 'safe' CWM appears to be 6.0.0.8.
Since the various threads indicate that Samsung is aware of this I'd assume the Stock recovery and boot images use a kernel that is 'safe'. That may be a bad assumption, but it only seems to be the use of non-Stock components that causes this, at least from what I've read so far.
Somewhere along the line a kernel that didn't have this defensive code in it made it into the source trees and then into our lives
.
Click to expand...
Click to collapse
persoot recommend using cwm 6.0.1.1 on his website http://droidbasement.com. wondering this cwm is safe also? Have someone used this version before?

nexus_g said:
persoot recommend using cwm 6.0.1.1 on his website http://droidbasement.com. wondering this cwm is safe also? Have someone used this version before?
Click to expand...
Click to collapse
I think that only exists for the 10.1, and was not released for the 8.9...

cdc120 said:
My Wifi tab is stuck on the Samsung Galaxy Tab 8.9 Screen. I used odin to flash back to factory rom. Osin said pass and rebooted but still stuck on Samsung galaxy tab 8.9 screen. What do I need to do next? In recovery mode it says: E: failed to mount /system (invalid argument) E: install_application_for_customer:Can't mount. /system copy application failed.
--Appling Multi-CSC...
E: failed to mount /system (invalad argumenrt)
E: install_application_for_customer:Can't mount. /system
E: multi_csc:Can't mount/system
Click to expand...
Click to collapse
Can you get it to download mode by pressing start+volume down buttons simultaneously and flash original HC ROM and start from there? I believe yours is not caused by the brickbug. If you have brick bug your tab will have black screen (someone correct me if I am wrong about this).

[Q] My Samsung galaxy s gt-i9000.. is broke?

After looking through forums and gathering information about rooting my device i decided to give it a shot, I followed the instructions to a 'T after using Odin and my preferred pda I found my phone had got stuck on the Samsung start-up screen. I looked more and was told i had bricked my phone ..
I was also told it was 'unbrickable' which means I could fix it by loading a PIT into Odin, I followed the instructions on how to achieve this, Odin told me everything went successful and Now my phone wont turn on or charge, In fact it's Black as the night..
I'm telling myself this might could be fixed, I would very much appreciate any help anyone can offer me on this problem
Darren

darthebar said:
After looking through forums and gathering information about rooting my device i decided to give it a shot, I followed the instructions to a 'T after using Odin and my preferred pda I found my phone had got stuck on the Samsung start-up screen. I looked more and was told i had bricked my phone ..
I was also told it was 'unbrickable' which means I could fix it by loading a PIT into Odin, I followed the instructions on how to achieve this, Odin told me everything went successful and Now my phone wont turn on or charge, In fact it's Black as the night..
I'm telling myself this might could be fixed, I would very much appreciate any help anyone can offer me on this problem
Darren
Click to expand...
Click to collapse
Try remove your battery for a while and restart it

I think you are flashing wrong file. Check the history of releases for your model by your carrier and get the right stock froyo or gingerbread file to flash.

muhammadnajmi96 said:
Try remove your battery for a while and restart it
Click to expand...
Click to collapse
Thank you, I give this a try and have access to the 'Downloading screen' again. I still can't get to the Recovery option.

darthebar said:
Thank you, I give this a try and have access to the 'Downloading screen' again. I still can't get to the Recovery option.
Click to expand...
Click to collapse
just flash stock rom with odin
Sent from my GT-I9001 using xda premium

Jonboy2011 said:
just flash stock rom with odin
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
Thanks for your input mate. I took your advice, For some reason my phone still won't boot
E:failed to mount /dbdata (invalid agument)_dbdata_media
E:failed to mount /dbdata (File exists)
E:copy_dbdata_media: can't mount /dbdata
your storage not prepared yet. please use UI menu for format and reboot actions.
Been through and nothing sems get it going