Database Develop

2 i9000's keeps rebooting (softbrick) $20 bounty

Hello,
I have read many threads and have tried many solutions with no avail. I am giving out $20 (may not be much but still an insentive) to whomever that will help me solve this.
I have 2 vibrants that keep booting to the Galaxy S i9000 intro and keeps rebooting there. I can't get into the recovery mode, but I can get into download mode and ODIN works just fine.
Please someone help

trojjanhorse said:
Hello,
I have read many threads and have tried many solutions with no avail. I am giving out $20 (may not be much but still an insentive) to whomever that will help me solve this.
I have 2 vibrants that keep booting to the Galaxy S i9000 intro and keeps rebooting there. I can't get into the recovery mode, but I can get into download mode and ODIN works just fine.
Please someone help
Click to expand...
Click to collapse
Just flash another firmware with Odin.Download a stock firmware,click re partition in odin,load all 3 files and pit and flash it.
You see sometimes after flashing with odin in some cases you might have to do a factory reset to boot the phone,since you cant go in recovery you will need to flash a complete stock firmware.This will probably work.

trojjanhorse said:
Hello,
I have read many threads and have tried many solutions with no avail. I am giving out $20 (may not be much but still an insentive) to whomever that will help me solve this.
I have 2 vibrants that keep booting to the Galaxy S i9000 intro and keeps rebooting there. I can't get into the recovery mode, but I can get into download mode and ODIN works just fine.
Please someone help
Click to expand...
Click to collapse
Follow this guide: http://forum.xda-developers.com/showthread.php?t=853950
and flash this firmware: http://forum.xda-developers.com/showthread.php?t=883568

The people above me pretty much said it.
Go into download mode, connect to odin, download a firmware that will work with your phone, flash your phone. That should fix it.
Best of luck! Tell me how it goes

K. Just came back from bell corporate store. Said I can't do anything without a receipt so until I get a hold of my friend that I bought this off of, I will try what you guys have suggested.
By the way, the gentleman (who seemed very knowledgable) tried flashing my phone on the spot behind the counter and now the phone boots with a black screen and the bottom keys glow when pressed.
When entering recovery mode <3e> and try to format internal sd-card, i get the following:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
I will now try what you guys have suggested and keep you updated.

tried kewjoe's suggestion but no luck. Any other suggestions?

Time for a replacement - looks like you've got the ever-so-popular internal SD card death.
If you take it into a Bell store they'll send it out and you should get a new one sent back to you in the mail. Bonus if you have any scratches on the phone or anything.

trojjanhorse said:
tried kewjoe's suggestion but no luck. Any other suggestions?
Click to expand...
Click to collapse
Read some of the bell threads that deal with this sdcard issue. Some people went through samsung directly and didn't need a receipt.
Sent from my GT-I9000

trojjanhorse said:
K. Just came back from bell corporate store. Said I can't do anything without a receipt so until I get a hold of my friend that I bought this off of, I will try what you guys have suggested.
By the way, the gentleman (who seemed very knowledgable) tried flashing my phone on the spot behind the counter and now the phone boots with a black screen and the bottom keys glow when pressed.
When entering recovery mode <3e> and try to format internal sd-card, i get the following:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
I will now try what you guys have suggested and keep you updated.
Click to expand...
Click to collapse
I've had that problem, shouldn't be too hard to fix.
Flash the Rom JPC with a 512 pit, make sure re-partition is ticked.
Then you can go back the original rom you was on without a pit and without re-partition ticked.
Make sure you do all them steps
Hope this has helped!

trojjanhorse said:
Hello,
I have read many threads and have tried many solutions with no avail. I am giving out $20 (may not be much but still an insentive) to whomever that will help me solve this.
I have 2 vibrants that keep booting to the Galaxy S i9000 intro and keeps rebooting there. I can't get into the recovery mode, but I can get into download mode and ODIN works just fine.
Please someone help
Click to expand...
Click to collapse
I had this issue when flashing from JL2 to another
- some of your partitions got messed, first boot odin, put your phone into download mode and make sure odin see's it. Select JL2 in the PDA secion and click the phone boot loader update
- after it's flashed, find the speedmod from hardcore on xda and flash that, also in the pda part, make sure everything else is default so it's best to close odin and reopen it
- after you have the speed mod on you should be able to get back into recovery.
- almost there, flash the stock 2.1 on your phone this has some data that no other rom has, once you flash that you can flash JL2 over top once again and you should be good to go
- msg me if you have issues

is this issue still on ongoing?
try this (if you haven't tried it before):
1. Launch Odin
2. Put the necessary stock firmware + PIT file that goes with it
3. tick re-partition (not sure what partition you are currently in so that's why I'm suggesting repartition)
4. Go into DL mode and plug the phone in via USB
5. Flash it
6. Once done, go flash hardcore's latest speedmod kernel via Odin again
7. Go to cwm recovery (hardcore's speedmod will give you this)
8. wipe partition cache+factory reset + clear dalvik cache
9. reboot system (will take a several minutes to boot out of the Galaxy S screen)
10. Hopefully your problem is solved.
11. If my method worked for you, PM me. I'll ask you to give that $20 to a local charity of my choice. Street kids needs some love too in the new year

Had this problem yesterday. I wrote in this post how to fix it. Looks like similar advice to what others are telling you.
http://forum.xda-developers.com/showthread.php?t=892534

this will work for sure..
download jpu from here http://hotfile.com/dl/88094739/f5545cc/I9000XXJPU.exe.html
after self extract
put the phone on download mode
open odin
select the files (pda, csc, pit )
check repartation , reboot , reset time

[Q] Flashed my Captivate and seriously f*cked up (I think)

DISCLAIMER: I am amazingly new to the Android, as I have been a hardcore Apple fanatic for years now (Since iPod Touch 1G came out).
I tried flashing my Samsung Captivate i897 from 2.2 Froyo to Cognition 4.3 and I some how seriously screwed up. I rebooted into CWM's recovery mode, but got "E:unable to authenticate whole-file verification"
I tried multiple times and continued to get the same result, so I uninstalled and reinstalled CWM and tried again, only to get the same result. After trying 8, or so, times, I decided to try to flash a CWMrecovery.tar with Odin only to have it fail.
My phone, after rebooting got the [phone]--!--[computer] image and was frozen.
After entering download mode successfully, I tried re-flashing a stock ROM, only to have IT fail as well...
And now we get to my Captivate's current state. My phone automatically boots into an odd system recovery screen.
It sorta looks like this:
Android system recovery (2e)
Samsung Recovery Utils
- for BML -
[ reboot system now ]
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
__________________________
E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount /dev/block/stl11
(Invalid argument)
Since I cannot mount /dev/block/stl11, I cannot apply an sdcard update, and wiping cache does me no good. I try to factory reset, but am confronted with a PRESS VOLUME UP TO CONTINUE AND VOLUME DOWN TO CANCEL screen.
This wouldnt be a problem except that the up button is not a working button in this mode. The touch buttons at the bottom work, and the volume down works, but power and volume up wont. The menu button hides the "console" text, the home button selects the option, and the other 2 are useless.
I probably sound like a complete moron and I know I cannot fix this on my own, as I have tried everything I can think of, from the Odin One-Click (which wont work because I have no 3-button mod for download mode), to factory resetting (which doesnt work because the menu I am at doesnt support the up volume button), to reflashing with Odin (which cant read my phone without download mode). The only thing I can come up with is buying a download mode jig and using the Odin One-Click to see if that would work.
So my question to XDA-Dev. is this: "What must I do to get my phone back onto a stock 2.2 Froyo ROM?"
Please help in any way and any comments are welcome, and thank you for taking the time to actually help a complete idiot.
~iZ3RO

iZ3RO said:
DISCLAIMER: I am amazingly new to the Android, as I have been a hardcore Apple fanatic for years now (Since iPod Touch 1G came out).
I tried flashing my Samsung Captivate i897 from 2.2 Froyo to Cognition 4.3 and I some how seriously screwed up. I rebooted into CWM's recovery mode, but got "E:unable to authenticate whole-file verification"
I tried multiple times and continued to get the same result, so I uninstalled and reinstalled CWM and tried again, only to get the same result. After trying 8, or so, times, I decided to try to flash a CWMrecovery.tar with Odin only to have it fail.
My phone, after rebooting got the [phone]--!--[computer] image and was frozen.
After entering download mode successfully, I tried re-flashing a stock ROM, only to have IT fail as well...
And now we get to my Captivate's current state. My phone automatically boots into an odd system recovery screen.
It sorta looks like this:
Android system recovery (2e)
Samsung Recovery Utils
- for BML -
[ reboot system now ]
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
__________________________
E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount /dev/block/stl11
(Invalid argument)
Since I cannot mount /dev/block/stl11, I cannot apply an sdcard update, and wiping cache does me no good. I try to factory reset, but am confronted with a PRESS VOLUME UP TO CONTINUE AND VOLUME DOWN TO CANCEL screen.
This wouldnt be a problem except that the up button is not a working button in this mode. The touch buttons at the bottom work, and the volume down works, but power and volume up wont. The menu button hides the "console" text, the home button selects the option, and the other 2 are useless.
I probably sound like a complete moron and I know I cannot fix this on my own, as I have tried everything I can think of, from the Odin One-Click (which wont work because I have no 3-button mod for download mode), to factory resetting (which doesnt work because the menu I am at doesnt support the up volume button), to reflashing with Odin (which cant read my phone without download mode). The only thing I can come up with is buying a download mode jig and using the Odin One-Click to see if that would work.
So my question to XDA-Dev. is this: "What must I do to get my phone back onto a stock 2.2 Froyo ROM?"
Please help in any way and any comments are welcome, and thank you for taking the time to actually help a complete idiot.
~iZ3RO
Click to expand...
Click to collapse
ok all i can say is read next time read, then ask questions because alot of the information is dated and doesnt apply in 2.2. 2.2 has 3e recovery that only accepts digitally signed update.zip files. 2e recovery runs self signed update.zip files
cwm cannot be flashed in odin as far as i know, instead you need a kernel with cwm baked in, speedmod is my kernel of choice for this as it has a .tar version and is super stable.
you are lucky and not beyond repair but we may need to try a few things. did you try a master clear(in recovery mode not download mode)? then another flash?
you can odin flash 2.2, i need to find the thread. once on 2.2 flash speedmod kernel in odin, from there you can do all the mods you need.

most on att are using kies to get 2.2 after they flash 2.1. still looking for the kb1 odin. i can get you the thread for the rogers rom if you want.
http://forum.xda-developers.com/showthread.php?t=995143
this odin is safer(dont forget 512.pit file). if you get the phone bootable put a custom rom on the sdcard>flash speedmod kernel>boot into recovery(phone wont boot on 2.1 rom and speedmodkernel but will enter cwm recovery)>flash rom. that's the quickest way to a custom rom, also maybe the quickest way to root
for a safer alternative i can .tar unhelpfuls kernel v1.7 which has cwm as well and will boot on jf6 but im not gonna test it for you, still a lot of risk involved.

are you rogers by chance? i had the cant mount/dev/block error from flashing a bad stock and incorrectly choosing to use pit.
the error is due to the "stock rom" not having dbdata file and using PIT. which will repartition and format, loosing your original dbdata.
if you are rogers, use the stock in my sig to fix!!
if you are AT&T use the Odin-one-click downloader. not the odin flashing util

Trusselo said:
are you rogers by chance? i had the cant mount/dev/block error from flashing a bad stock and incorrectly choosing to use pit.
the error is due to the "stock rom" not having dbdata file and using PIT. which will repartition and format, loosing your original dbdata.
if you are rogers, use the stock in my sig to fix!!
if you are AT&T use the Odin-one-click downloader. not the odin flashing util
Click to expand...
Click to collapse
oh didn't realize that can be a problem, im definately taking a note of that.

I had that problem once. Try removing the battery, hold both volume up and volume down then put the battery in. That may put you into download. If not buy a jig. I use mine all the time when I soft brick. Once in download mode you can use odin one click to go back to 2.1 stock. Then I use baywolfs AIO toolbox to root and load the first 2.2.1 ROM back in. Just make sure you dont mount your SD card.

Thanks for the help guys. I ended up going to RadioShack and building a solderless jig to get back to download mode.

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] Messed it up and need help

This WAS the situation before the problems:
Rooted Gingerbread rom, all working fine. Decided to unroot and install the full version of the official German ICS rom by using PC Odin. All went fine and used my Note for over two days. Because of the lags en slow responses I decided to reflash the ICS rom. From that moment on I messed it up. I've been reading and searching hundreds of posts for almost a day but didn't find a solution.
This IS the current situation:
I can get into download mode
I can get in recovery mode
However, in recovery mode I can not install a rom, every flash (CWM, both ICS and GB - even using chainfire's rom needed for rooting) stops on a random moment...but never gets it to the end, even if I wait several hours. Installing is very...very....very slow.
In recovery mode i can not restore a Nandroid backup, both ICS and GB. Every backup stops when /system has te be installed. errormessage.
In download mode I can connect my Note to PC Odin. I can select a rom and start flashing. However, after appr. 80% installation halts during "nand write start", no error message. The flashing does not finish, even after hours.
Funny is, i can install a kernel like Abyss.
So, I can't restore, i can't flash using cwm in recovery and I can't flash using PC Odin. My device seems not fully bricked. The max I get when rebooting (knowing that the process has not finished) is the triangle screen.
Any advise is appreciated.

Do not flash thru CWM... Flash a good GB kernel like "franco.Kernel" but thru PC Odin then u can flash whatever u want from franco's CWM... Good luck

Don't need help anymore
Note is officially bricked. After several attempts to recover from a softbrick the screen of my Note didn't turn on anymore. No button or button combination works, no recovery and no download mode, just a black screen.

Ce said:
Don't need help anymore
Note is officially bricked. After several attempts to recover from a softbrick the screen of my Note didn't turn on anymore. No button or button combination works, no recovery and no download mode, just a black screen.
Click to expand...
Click to collapse
Flat battery? It's also possible that it's just the screen that's not working. Try entering download mode "blind". So hold power+home+vol down for ~10 seconds, then press vol up. Hook it up via usb and see if Odin can recognize it.

Thanks, didn't think of that. But unfortunately no response from the device.

So now that it looks like your phone is officially bricked, I think you should just take it to Samsung and make up a story. Like you were updating your software with Kies and something happened and the phone is just not booting up.
I am sorry you bricked your note though..

try AMORA Filemanager.. flash via recovery and you have a file manager,,, take a look on your partitions
just my idea, you got nothing to lose

musashiro said:
try AMORA Filemanager.. flash via recovery and you have a file manager,,, take a look on your partitions
just my idea, you got nothing to lose
Click to expand...
Click to collapse
I would like to but it's very hard when you can't see anything on the screen...

Maybe it's just the battery, try to charge it externally and try a JIG also
Sent from my GT-N7000 using XDA

Just a quick, final, update.
My Note was superbricked. Had to send it to a Samsung Service Center. No additional questions were asked. Samsung replaced the mainboard. Didn't have to pay anything.
Great service!!!

try this out buddy, do it on your own risk!!! anyways you have messed it up.
Ce said:
This WAS the situation before the problems:
Rooted Gingerbread rom, all working fine. Decided to unroot and install the full version of the official German ICS rom by using PC Odin. All went fine and used my Note for over two days. Because of the lags en slow responses I decided to reflash the ICS rom. From that moment on I messed it up. I've been reading and searching hundreds of posts for almost a day but didn't find a solution.
This IS the current situation:
I can get into download mode
I can get in recovery mode
However, in recovery mode I can not install a rom, every flash (CWM, both ICS and GB - even using chainfire's rom needed for rooting) stops on a random moment...but never gets it to the end, even if I wait several hours. Installing is very...very....very slow.
In recovery mode i can not restore a Nandroid backup, both ICS and GB. Every backup stops when /system has te be installed. errormessage.
In download mode I can connect my Note to PC Odin. I can select a rom and start flashing. However, after appr. 80% installation halts during "nand write start", no error message. The flashing does not finish, even after hours.
Funny is, i can install a kernel like Abyss.
So, I can't restore, i can't flash using cwm in recovery and I can't flash using PC Odin. My device seems not fully bricked. The max I get when rebooting (knowing that the process has not finished) is the triangle screen.
Any advise is appreciated.
Click to expand...
Click to collapse
i was not a member when i commited this mistake. but then big thanks to this community it helped me back from softbrick.
first you do is install a stock kernel of ics on your note go into recovery and just clear cache partition, thats it no wipe/data factory reset.
then,
install the pit file from this thread, also read it completely before proceeding. http://forum.xda-developers.com/show....php?t=1667886 , hoping yours is 16gb version and also read this thread for additional info but its quite complicated for me so im just telling you the direct method and hopefully itll get your note back to work. so once you download the 16gb pit file unzip it and in the unzip folder you will find a separately lying pit of 16gb stating patched-standard thats the one you want.
then,
goto samfirmware and download the latest ics firmware(i downloaded the indian one as it is in file .tar),
unzip it till you get .tar file.
open odin- click pit-select 16gb patched standard pit- check wether repartion is ticked- click pda-select the .tar file you extracted connect your phone and start. this time i wont stop at factory.fs.....
NOTE THAT AFTER THIS PROCEDURE IS COMPLETED SUCCESSFULLY YOUR INTERNAL STORAGE WOULD BE ONLY 8GB INSTEAD OF 11 GB STOCK WHICH YOU WERE GETTING.
I REVIVED MY NOTE THROUGH THIS PROCEDURE. PROCEES AT YOUR OWN RISK.
one your phone is working you'll be able to reset the counter with a jig and get your phone under warranty and get your motherboard changed by teliing at the Samsung Service that you are getting only 8gb instead of 11gb you used to get earlier(warranty only if you had any).
hope this helps mate.
BEST OF LUCK!!
A BIG HUGE THANKS TO hg42.....

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).