Database Develop

[Q] Help, phone wont boot no matter what flash

Hi,
I flashed the Pre rooted JP3 from http://forum.xda-developers.com/showthread.php?t=748131 and then installed the [UTIL] One Click Lag Fix 2.0 from http://forum.xda-developers.com/showthread.php?t=751864
I used the phone for a couple of hours and then all of a sudden everything kept crashing.
I booted into the clockwork recovery and reset to factory and then was not able to boot.
I tried flashing back to I9000UGJH2 with Pit512 and Odin and after it flashes successfully the phone starts I see the galaxy S I9000 and then it shows me a grey battery sign and then a busy circle sign and then gray battery and keeps repeating.
When I boot without the usb cable it shows me the Galaxy I9000m sign and then just turns off.
When I tried reflashing the JP3 from the site above and after it finishes it comes to the Android System Recovery <3e> and displays the following message:
Update Media please wait
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E:copy_dbdata_media:Can't mount SDCARD:"
Your storage not prepared yet, please use UI menu for format and reboot actions
copy default media content failed.
When I boot it moves past the Galaxy I9000m screen shows me the galaxy screen with animation and sound, the screen then goes of leaving me with a black screen and the buttons lit.
I cannot format the internal SD card and I cannot seem to get the hone to boot into android, I can boot into downloader.
Any help would be appreciated
P.S. I have ticked the repartition option in Odin

Odin should theoretically work. I've never clicked repartition myself however a lot of people do seem to recommend it.
If you're out of things to try and you want to give the latest (not publicly released) version of Heimdall (my Odin flashing software alternative) a go let me know and I'll PM you the download link.

That gray battery with a spinning circle sounds like the charging screen when the phone is off. Have you tried and let it charge up over night?

The battery is full.
I managed to get the I9000UGJH2 rom up and running by inserting an external sd card.
But here are some issues:
Once booted neither of the SD cards are recognized
If I power down / reboot phone, it will not start again, it shows the I9000m screen and turns off.
I suspect whatever the one click lag did to my SD cards needs to be reversed.

Ok,
So after tonnes of playing around with the device. I can confirm that it has something to do with he internal SD card.
I need to somehow format the entire internal SD card so that even Odin can see it. I tried using the stock recovery and clockworks with no luck.
It just wont see the card.
Any suggestions?

Phone won't reboot ODIN says PASS, Frozen on Galaxy S home screen
I first installed JP2 and was able to get it working. Then I made an attempt to install JP3 but it didn't work. My phone screen kept on flashing i.e. off and on. I then went back and tried to install JP2. While I was installing it, I got an error message saying unable to mount sd card (similar to what rumy got). I am in the exact scenario as rumy and now i don't know what to do. It's a brand new phone and I am very scared.
Any ideas on what I can do now. I am installing JH2 as I write. Hopefully, that will work.
Please help me if someone knows how to get out of this situation.
thanks

galaxys00 said:
I first installed JP2 and was able to get it working. Then I made an attempt to install JP3 but it didn't work. My phone screen kept on flashing i.e. off and on. I then went back and tried to install JP2. While I was installing it, I got an error message saying unable to mount sd card (similar to what rumy got). I am in the exact scenario as rumy and now i don't know what to do. It's a brand new phone and I am very scared.
Any ideas on what I can do now. I am installing JH2 as I write. Hopefully, that will work.
Please help me if someone knows how to get out of this situation.
thanks
Click to expand...
Click to collapse
Well, I am still trying but no luck.
We need an adb expert / odin one to help us somehow repartition the internal sd card I think.
I believe with the lagfix on jp3 it got repartitioned and then corrupted.
I also think we should start adventuring outside this device as there might be more senior trouble shooters / experts who own other htc devices that might be able to help.

I used to get this on my htc dream try going back to original firmware the only I found it to work was rip a rom to pieces get misc.img then enter console via recovery and flash_image misc misc.img then something else but cant seem to remember think its mount-o rw,remount -r yaffs2 /dev/block/mmcblkop3 /system. dont quote me on this try typing the error into google
Sent from my GT-I9000 using XDA App

rumy said:
Well, I am still trying but no luck.
We need an adb expert / odin one to help us somehow repartition the internal sd card I think.
I believe with the lagfix on jp3 it got repartitioned and then corrupted.
I also think we should start adventuring outside this device as there might be more senior trouble shooters / experts who own other htc devices that might be able to help.
Click to expand...
Click to collapse
The lagfixes do not repartition anything so this is (most likely) an issue that is not related to the lagfix.
Try going back to somthing like JF3 with the 513.pit file and repartition enabled.

The exact same thing happened to me - installed JP3 then lagfix. Phone was unstable after so I tried to reflash via ODIN (with repartition) and no matter what I did I could not successfully reflash my phone or get it to boot.
Only solution - returned it to the store as a DOA and got a replacement device.
Upon further research, it is known that JP3 screws up the internal SDCARD. Marks it as read only or something like that - search google for JP3 sdcard for more details.
Bottom line - your phone is bricked. Sorry to be the bearer of bad news.

I wonder if this would help fix it.
http://forum.xda-developers.com/showthread.php?t=762135

rumy said:
I wonder if this would help fix it.
http://forum.xda-developers.com/showthread.php?t=762135
Click to expand...
Click to collapse
That installs a different Linux distro underneath android and is totally unrelated! (Not to mention not doable in the state the phone is in)
OT: I don't believe you should give up quite yet. Try flashing a new firmware and afterwards, install Clockwork recovery!
From there you can format your internal SD. You will lose all your data but I strongly believe it will help fix your problem from what I have read here so far!
Edit: I added a warning to the flash guide in my FAQ for I9000M owners for now!

hey try this
Why dont you try to use the odin 1 click downloader over in the captivate forums. I know that we captivate people are running the i9000 firmware with a stock captivate kernal under it. Worth a try.

ice3186 said:
Why dont you try to use the odin 1 click downloader over in the captivate forums. I know that we captivate people are running the i9000 firmware with a stock captivate kernal under it. Worth a try.
Click to expand...
Click to collapse
I'm not sure what you mean. I am pretty sure he used Odin to flash the firmware. I think you are talking about the same program he already is using.

Damn. There are so many known traps out there, yet we don't have a compile of them anywhere. I didn't know that I shouldn't uninstall Google Talk until I actually did it. We need things like this in the FAQ.

snapper.fishes said:
Damn. There are so many known traps out there, yet we don't have a compile of them anywhere. I didn't know that I shouldn't uninstall Google Talk until I actually did it. We need things like this in the FAQ.
Click to expand...
Click to collapse
"Do not uninstall google talk" is not something you need or want in an faq. It's called a frequently asked questions because they are frequent. I have never before seen someone who tried or even wanted to uninstall google talk (not to mention that this is a goggle os and removing central apps like that is bound to produce problems). And if you mess around with root like that you have only yourself to blame for not doing enough research!
Sent from my GT-I9000 using XDA App

Good idea.
Downloading now will try and post. Fingers Crossed!

OK DONOT TRY THIS!
This made things worse for me.
I lost downloader mode too now all i see is the AT&T screen showing up

Calm down and tell us exactly what you did. It sounds like the initial problems that occurred on early recovery. The download mode should still be reachable. I don't think recovery can completely brick your phone.
rumy said:
OK DONOT TRY THIS!
This made things worse for me.
I lost downloader mode too now all i see is the AT&T screen showing up
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App

The problem is related to the message
Update Media please wait
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E:copy_dbdata_media:Can't mount SDCARD:
Your storage not prepared yet, please use UI menu for format and reboot actions
copy default media content failed.​
If you research this error via Google you will find several references to JP3 screwing up the permissions/structure of the internal SDCARD.
I spent several days trying to fix this issue on my phone and no matter what I did (Clockwork or no) I could not get the phone to reset/recognize the SDCARD.
As I said, my only recourse was returning the phone for a replacement. I really hope you find a fix but I think it unlikely.

[Q] Help with phone stuck on Froyo 2.2

Hey guys.
Ok so what happened was that I updated to Froyo and it worked perfectly, had it rooted and installed lag fix. Couple of days later it would boot, go past the samsung logo but then nothing. I would be staring at a black screen and when i press the middle button the two buttons on the side would light up. Now i am not able to go into recovery mode but I can go into download mode. Now I have tried flashing the phone. I tried going stock, stock for other countries and also reflashing froyo 2.2. The most successful is froyo because once I have reflashed and reboot for the first time, it goes into recovery mode telling me it is having problem with a couple of things, one of them being the internal sd card, which is fixed by me doing a sd wipe but the next one is a data error, i think it was called dadata but i am not sure, have to double check. Now i cant get that error to go away even by doing a factory rest and once i reboot the phone, it goes back to the state i mentioned before. Plz can any one help?

Zink6 said:
Hey guys.
Ok so what happened was that I updated to Froyo and it worked perfectly, had it rooted and installed lag fix. Couple of days later it would boot, go past the samsung logo but then nothing. I would be staring at a black screen and when i press the middle button the two buttons on the side would light up. Now i am not able to go into recovery mode but I can go into download mode. Now I have tried flashing the phone. I tried going stock, stock for other countries and also reflashing froyo 2.2. The most successful is froyo because once I have reflashed and reboot for the first time, it goes into recovery mode telling me it is having problem with a couple of things, one of them being the internal sd card, which is fixed by me doing a sd wipe but the next one is a data error, i think it was called dadata but i am not sure, have to double check. Now i cant get that error to go away even by doing a factory rest and once i reboot the phone, it goes back to the state i mentioned before. Plz can any one help?
Click to expand...
Click to collapse
Follow this guide.
If you still get error try finding a rom from samfirmware that has pda modem and csc then flash them with odin3 v1.70.

Sounds like you have a bad internal sd. You may have to take it back for warranty
Sent from my GT-I9000M using XDA App

ya so it says that it has some problem with dbdata and that it cant mount internal sd card. Am I screwed?

Zink6 said:
ya so it says that it has some problem with dbdata and that it cant mount internal sd card. Am I screwed?
Click to expand...
Click to collapse
Ok i have just managed to solve a similar problem on my phone..
donwload the file from this link (it's from samfirmware)
add in all
code file into pda, modem file into modem and csc into csc
and add in the 803 pit make sure repartition is checked.
If that doesn't won't i can't help no more..
Any success?

No my friend, no luck. Thanks for the help though. Any one else have any other suggestions?

I have the same problem with my other i9000m. No amount of flashing with odin with whatever firmware helped. I took it into a local 3rd party repair shop. They have fixed 10+ corrupt sd card phones. They said they needed to keep it for one day which tells me its not just a simple flash job. Maybe they have some sort of jtag setup that allows them to reformat the flash chip or something.
Or maybe they are actually removing the chip off the mainboard and reformating it. Whatever it is they are doing, its worth the $70 to get my phone working again. There is definately a fix out there though. And at $70, it's just for labour. They're definately not replacing parts.
Sent from my GT-I9000M using XDA App

Zink6 said:
No my friend, no luck. Thanks for the help though. Any one else have any other suggestions?
Click to expand...
Click to collapse
Have one last try with the jf3 firmware with the 512 pit.. again in odin v3 1.7 code in pda..modem in modem and csc in csc there are two not sure which is better i tried oxa..
JF3 Link
If that doesn't work then yer i guess your only option is take it into a shop.. or send it back to samsung to see if they will fix it for you.

helpp please...

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

!SOLVED! Vibrant Internal Memory application storage 0b, please help!

!PROBLEM SOLVED!
Hi there,
I hope I am posting in the right place, I hate clutter. I also hope there is something that can be done about this:
I was trying to install a ROM and as usual I used ODIN to go back to stock (JFD) and from there on I would use the One Click Root and then via ClockWork flash the ROM I wanted to try.
This time the ROM said (yes, it was talking) that some partition had not enough space. So, when I went back to ClockWork I saw an option to Partition the drive.. so I did that, and from then on only nightmares...
Nothing would flash properly, even via ODIN. I would get error message about MBR not being able to mount and such. After countless hours of black screen after the Galaxy S logo I finally managed to get a Eugene ROM flashed via ODIN, but now I have a new issue - I cannot install anything, no Titanium, no ClockWork, because my Application Storage is 0B. My external SD is its normal size (a 16GB card, shows 14.83 I think), but the internal storage is 14GB or so and there is virtually NO Application Storage..
* I tried re-flashing things - nothing works other than the Eugene ROM. No JFD, no JI6, nada..
* Would not manage to use an update.zip from the manual recovery (I get the stock Samsung Recovery, it sucks!)
* Cannot install ClockWork and try to fix it from there (or flash another rom via CWR)
* I tried to re-partition via ODIN - no dice.
* I tried to re-partition with Partition Magic (I know... that was my desperate attempt at 1 am after 14 hours of struggle) and it doesn't seem to work (duh).
I am out of ideas and I could really use some help. Did anyone have this issue and what was the solution?

I had this issue, I don't remember the exact steps but I do remember I used "parted" to repartition.
http://forum.xda-developers.com/showthread.php?t=1046220
edit: I remembered: delete the smaller partition, then ODIN to stock w/ repartition checked, and you should get you app storage back.

Thank you, I will give it a try and let you know how it goes! Much appreciated!
german103 said:
I had this issue, I don't remember the exact steps but I do remember I used "parted" to repartition.
http://forum.xda-developers.com/showthread.php?t=1046220
edit: I remembered: delete the smaller partition, then ODIN to stock w/ repartition checked, and you should get you app storage back.
Click to expand...
Click to collapse

german103 said:
I had this issue, I don't remember the exact steps but I do remember I used "parted" to repartition.
http://forum.xda-developers.com/showthread.php?t=1046220
edit: I remembered: delete the smaller partition, then ODIN to stock w/ repartition checked, and you should get you app storage back.
Click to expand...
Click to collapse
Okay, no idea to use "parted". I did download the zip file with the six little guys, but now what? Android SDK? Oh my... no clue...
Any chance for a step by step?

So I download the Android SDK and got the 6 files into the "tools" directory, but now I have no idea what to do...
UPDATE: Okay, I managed to get the ADB going, but when I try to push them files with the command it says failed to copy (the path) "Permission denied"

SOLVED!
Guys, problem solved. Here is how in a nutshell:
So, I saw this post - http://forum.xda-developers.com/showthread.php?t=1081732 and although it is for the I9000 I figured I didn't have much to loose anyways. So I did look for EZbase ROM as one of the users suggested (http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/) and got busy. Finding the files was hard (because of expired links and such), but the link above seemed to work.
Once I collected all the files I performed the process just as described (with the partition checked) and ended up with the Galaxy S I9000 boot (instead of Vibrant) and it was in a boot cycle.
Then I managed to bring the phone to Download Mode (key combo is different now, it is power and Vol Up, not as it used to be) and flashed JFD via Odin (checked the re-partition here as well, although I don't know if that mattered).
And a few minutes later I ended up with a working stock Vibrant. The funny thing is that when you boot the device it first shows the I9000 boot image and then switches it to Vibrant (but I really don't give a damn about that).
So there it is! Hope this helps some poor souls who are in the situation I was.
Cheers!
And it worked!

just put a froyo bootloader on an the 1900 will go away

hachaduryan said:
Guys, problem solved. Here is how in a nutshell:
So, I saw this post - http://forum.xda-developers.com/showthread.php?t=1081732 and although it is for the I9000 I figured I didn't have much to loose anyways. So I did look for EZbase ROM as one of the users suggested (http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/) and got busy. Finding the files was hard (because of expired links and such), but the link above seemed to work.
Once I collected all the files I performed the process just as described (with the partition checked) and ended up with the Galaxy S I9000 boot (instead of Vibrant) and it was in a boot cycle.
Then I managed to bring the phone to Download Mode (key combo is different now, it is power and Vol Up, not as it used to be) and flashed JFD via Odin (checked the re-partition here as well, although I don't know if that mattered).
And a few minutes later I ended up with a working stock Vibrant. The funny thing is that when you boot the device it first shows the I9000 boot image and then switches it to Vibrant (but I really don't give a damn about that).
So there it is! Hope this helps some poor souls who are in the situation I was.
Cheers!
And it worked!
Click to expand...
Click to collapse
No dice. Didnt work for me

hachaduryan said:
Guys, problem solved. Here is how in a nutshell:
So, I saw this post - http://forum.xda-developers.com/showthread.php?t=1081732 and although it is for the I9000 I figured I didn't have much to loose anyways. So I did look for EZbase ROM as one of the users suggested (http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/) and got busy. Finding the files was hard (because of expired links and such), but the link above seemed to work.
Once I collected all the files I performed the process just as described (with the partition checked) and ended up with the Galaxy S I9000 boot (instead of Vibrant) and it was in a boot cycle.
Then I managed to bring the phone to Download Mode (key combo is different now, it is power and Vol Up, not as it used to be) and flashed JFD via Odin (checked the re-partition here as well, although I don't know if that mattered).
And a few minutes later I ended up with a working stock Vibrant. The funny thing is that when you boot the device it first shows the I9000 boot image and then switches it to Vibrant (but I really don't give a damn about that).
So there it is! Hope this helps some poor souls who are in the situation I was.
Cheers!
And it worked!
Click to expand...
Click to collapse
So it seems that there are easier methods to solve this issue now.. glad you worked this out

[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