Think im doomed.. today i updated my phone for doc's XWJPA v9 to stock I9000DDJP6:... now my phone is bricked. it starts up then i see the sparkling S logo and then the screeen goes black and after 2 mins or so the touch button lights lit up and thats it. my phone never worked on 3 button recovery mode... i used rom manager or adb. so basicaly i cant do nothing.!! please Help... i donno much abt these things.. so if someone could kindly write to me a step and step procedure on how to get the phone back to working... it will be really appreciated.. I love this phone
Can you get your sgs to go into download mode?
(Vol down + Home and then powerbutton (while pressing vol down and home))
If so try to reflash with Odin..
nente002 said:
Can you get your sgs to go into download mode?
(Vol down + Home and then powerbutton (while pressing vol down and home))
If so try to reflash with Odin..
Click to expand...
Click to collapse
yes i am able to get into download mode .i have tried reflashing but still of no use.
earlier i had clockwork mod recovery installed and now when is press vol up+home+power android system recovery <2e> appears.
and also in recovery i am getting this:
upadate media. please wait ...
E: Can't mount / dev/block/stl10
(Invalid Argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
i guess earlier i was using One Click Lag Fix - 2.0 but i uninstalled it and i probably the file system didn't fully got converted back to RFS..
..am i right???
Have had this problem myself, did you repartition in odin? Not entirely sure how I solved it, but I flashed JP7 from odin (pda, csc and modem) with repartition selected (pit 512) then reflashed it without repartition and it worked
flash back to the rom you came from? when you say 'uninstall' the lag fix, you mean you uninstalled the apk and didn't undo the lag fix? I had something like that before, when i flashed back to the rom that i had lagfixed it on, it worked again.
I have had the exact same error..I was on Darkky 4.1 and wanted to flash the latest speedmod, so I removed lag fix and flashed the speedmod.
Then rebooted the phone and was stuck with the exact same error.
I googled a little and found a galaxy forum.
There a guy gave the solution... I shall now share...
First flash this zimage:
http://www.4shared.com/file/jHJyZZ32/SO_zImage_opt_ext_root_JPM-JP6.html
Using odin (no repartition and no pit file)
If all is well you can get into recovery mode, clear all cache you can find, and format all there is to format (i got on error on one format can't remember which one..) Then when you are done go back into download mode and connect to odin
Then flash JPM from samfirmware (no repartition) and you are back in business (atleast I was)
The I re did the clockwork recovery and flashed darkky 4.1 speedmod again..
nagrom78 said:
Have had this problem myself, did you repartition in odin? Not entirely sure how I solved it, but I flashed JP7 from odin (pda, csc and modem) with repartition selected (pit 512) then reflashed it without repartition and it worked
Click to expand...
Click to collapse
thanxx nagrom78 for your help.Did whatever you said..you really saved me.
You're welcome mate, I posted my prob in another forum and everyone told me my internal sd card was fk'd! So I know how you feel when your phone don't boot and you see all that crap on your screen, scary stuff, especially the thought of having to send the phone back to Samsung...
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
My SGS seems to have got itself screwed. I had been on Darky's 9.5 but had been getting rapid battery drain, so decided to go back to a stock rom for a while.
Went into Recovery from 9.5 and checked lagfixes were disabled.
Flashed JPY via Odin 1.7 - all worked absolutely fine.
Then tried flashing the JVH file from Samfirmware again via Odin 1.7 - 512 pit file in the appropriate field and the single JVH file in the PDA field. Appeared to flash OK according to Odin - got the usual sequence of messages in the lower left of the Odin screen and the box went to PASS.
However, when Odin rebooted the phone, it went into Recovery which displays the following - coloured as it appears on the screen (items in green are actually yellow, but used green here for clarity):
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
Enter: OK Key, Select: Vol Up / Vol Down
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
format internal sd-card
----------------------------------------
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.
Can perform a factory reset and format the sd-card using the options in blue, but when I then go to reboot, it then pauses on the swirling S animation. SD card buzzes once, then three times in rapid succession and the screen goes to sleep. Pressing the home key lights up the menu and back arrow lights but the screen stays black and the sd card continues the one, followed by three rapid buzzes routine.
Took the battery out and rebooted back to Download mode and attempted to flash JPY back again. Appeared to be successful via Odin, but Recovery still shows the same error messages and will only boot to the S animation as described above.
I've pretty much convinced myself I've bricked it, but do any of you SGS experts have any ideas? Wishing I'd stayed put and kept with Darky's now ...
EDIT: Now fixed - got hold of a JS7 firmware consisting of PDA, PHONE, CSC and 803.pit files, flashed that and all is now fine
Had same thing , actualy its 1.7 Odin is bad , use 1.3 or 1.82 , flashed original JVH for buddy of mine and phone reboots in to recovery and gives me same messages u got , for a moment i though internal memory gon bad , flashed again all files with bootloaders , same e:\ cant mount and etc , took his phone home and on my pc i only have odin 1.82 so reflashed it again and it booted right away with no problem at all
Hitec
Can't say I've had a problem in the past with 1.7, but the irony is I think 1.8 is the version I've got on my laptop - all this was done on my other machine. If that turns out to be the case, will copy it over ASAP!
Either way, it was a bit of a wake-up call not to be so complacent!
A well known error : trying to repartition without dbdata.rfs, it's far from a brick but Recovery log is a little scary for this error
Yes. When repartitioning you need all 3 files. Pda, csc and phone.
I've lost count of the number of times I've told people this recently but odin 1.7 is not designed for the i9000. Odin versions are device specific, you should be using 1.0, 1.3 or 1.8.
See this link from samfirmware.com
http://www.samfirmware.com/WEBPROTECT-programandroid.htm
Sent from my GTI9000 using XDA App, gingerbread 2.3.3 jvh rooted, ADW launcher + gingerbread theme
His fault was using pit and repartition with single file tar, that doesn't have DBData file inside....
This is a soft brick, just install JVB 3 files with pit and repartition and then flash JVH without pit!
ps: odin is not specific, 1.85 works for I9000 as well the 1.7
Sent from my SGS with Simply 3.3 FINAL ROM
You have to flash "dbdata.rfs.tar " as pda. Please read TechKidTarek method for solving this problem.
http://forum.xda-developers.com/showthread.php?t=984140&highlight=stl10
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
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