Related
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.
I turned on my phone today to find that it mysteriously shut off...I went to turn it back on, and it just sits at the first screen forever (the one that says GT-I9000), so I pull the battery and boot into recovery. In the command line section, I get:
Code:
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
copy default media content failed.
My guess is that it's some sort of a partitioning error, but I really have no clue...is this a fixable error? Also, if it makes a difference, my phone is the Canadian Bell version (GT-I9000M), purchased back in September. I've been using i9000 ROMs since I got it though, and they seem to work flawlessly (much, much better than using whatever is out there specifically for the I9000M, anyway).
Thanks in advance!
your phone is fried, just take a quick gaze upon the forums, you have a very common problem, call bell, get a 100 dollar credit and a new phone in 1 week
C.L.Android said:
I turned on my phone today to find that it mysteriously shut off...I went to turn it back on, and it just sits at the first screen forever (the one that says GT-I9000), so I pull the battery and boot into recovery. In the command line section, I get:
Code:
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
copy default media content failed.
My guess is that it's some sort of a partitioning error, but I really have no clue...is this a fixable error? Also, if it makes a difference, my phone is the Canadian Bell version (GT-I9000M), purchased back in September. I've been using i9000 ROMs since I got it though, and they seem to work flawlessly (much, much better than using whatever is out there specifically for the I9000M, anyway).
Thanks in advance!
Click to expand...
Click to collapse
Try formatting your internal sd card via recovery 3e or CWM (what ever you use).
androidsl said:
Try formatting your internal sd card via recovery 3e or CWM (what ever you use).
Click to expand...
Click to collapse
When I try to format it using 3e, I get the same error message as on entering recovery move (can't mount). I've also tried several 3e factory resets and cache partition wipes, and Odin reflashes, but no luck from any of it.
Try flashing with these steps. I didn't have my internal SD die but I could not mount or format mine. Flashing with the 3 part older firmware and then upgrading to a new firmware without repartitioning has saved me several times. Let me know if it works for you.
http://forum.xda-developers.com/showthread.php?t=818556
It happened to me as well, but mine was because battery was dead.
So the obvious advise is to charge the battery completely before you do anything.
Sent from my GT-I9000 using XDA App
The battery is sufficiently charged, I'm pretty sure
After flashing to JPY through Odin, when it finishes and says pass, the screen goes blank, and then the only thing that will work is download mode (holding the power button to turn it on doesn't produce a bootloop). In the morning, I'll probably try the non-Odin method.
C.L.Android said:
The battery is sufficiently charged, I'm pretty sure
After flashing to JPY through Odin, when it finishes and says pass, the screen goes blank, and then the only thing that will work is download mode (holding the power button to turn it on doesn't produce a bootloop). In the morning, I'll probably try the non-Odin method.
Click to expand...
Click to collapse
Read the Entire First post in this thread hopfully it gets you running again.
http://forum.xda-developers.com/showthread.php?t=905975&highlight=JL2
Good Luck.
Flash using odin xxjpk than latest rom like darky v8.1
Sent from my GT-I9000 using XDA App
Did you follow the whole post I showed you? The symtoms you are describing sounds like you jumped directly to flashing jpy which will not work. You need to flash the 3 part jpu first.
They advice to flash jl2 may work as well. Jl2 has actual code changes to address sdcard issues. You may experience issues going to jpy afterwards though.
Sorry...I meant JPU, not JPY
I flashed JL2, which bootloops at the galaxy s screen (where it says GT-I9000M), and can't access recovery mode (it can access download mode though)
What should I do from here?
okay, that is fine. Now you need to flash with an older firmware, then a newer one. 3 part jpu with repartition, then jpy without repartition. If that doesn't work, you may have a dead sd. But I was bootlooping on JL2 just before I fixed mine. Here you can read this thread too where I posted fixing mine.
http://forum.xda-developers.com/showthread.php?t=892534
P.S. its supposed to not boot on the first flash (black screen). Thats why you need to flash it twice. It takes some code from the older firmware and some from the newer.
Tried, and that didn't work, so I'm assuming that my internal SD card is done; thanks for the help, though
does Samsung have an official statement on their "new phone + $100" thing I've seen around? I can't imagine that's something the store I bought my phone at will want to help me with
My friend works at Bell. He told me they are sending phones in for repair or replacement. Takes about a week. He didn't know if they are still giving out $100. He didn't think so.
Crappy about the phone. Was worth a try.....
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
I'd recently flashed the Cognition new build. Yesterday morning I woke up (3 days later) and found that my phone was stuck at the white and blue AT&T screen.
I preformed the Odin 1-click (as I have many times in the past<I'm not a noob to Odin>) I got my phone into a reboot but now it gets stuck at the Galaxy S screen and then goes dark.
Naturally, I used Odin again with different degrees of failure.
1. Gets stuck at file analysis.
2. Gets stuck halfway through and a blue, green or black screen appears.
3. Stuck at the AT&T screen again.
I've used Odin about 25 - 50 times in the last twenty-four hours.
I've also used the other Odin using the I897UCJH2 PDA file that's provided.
The phone booted directly into recovery and gave this error:
E:Can't Mount /dev/block/mmcblk0p1
(I/O error)
E:copy_dbdata_media: Can't mount SDCARD:
copy default media content failed.
And then it went back to the aforementioned black screen of hell.
I have build 1007 in case that's relevant.
I NEED HELP! Preferably a genius.
im having the exact same problem.
please help
I'm not sure if it matters too much, but it could certainly have had something to do with the kernel the newer Cognition would have installed when you upgraded to it.
Are you using I897UCJF6-final-OCD-REV or I897UCJI6-OCD-REV02-Low?
Most people have the first one, I would definitely try the second if it wasn't working.
The last option is to use Odin3 v1.7 (which you seem to have) and using that to update the kernel to a CM7 one and try to install CM7 onto your phone (and then reverting back to 2.1 stock if you wish).
Not sure if any of those options would work, but give me a yell if you need any help with doing any of the above.
You didn't disable the lagfix before you flashed, and your internal partition is still running ext4 but your data partition is back on efs. See this thread.
You will get your phone working, just be patient and go step by step.
Thank You Both
Thank you both but neither of those two options worked.
I was hopeful that the CM would fix it. I played around with that thought yesterday.
I know the difference between ODIN 1-click and ODIN3 v1.70. I've tried both and neither can get me back up and running. I'm hopeful that someone comes to the table with some resolution. This is frustrating.
EDIT:
Oh and I forgot, I've actually used both I897UCJF6-final-OCD-REV and I897UCJI6-OCD-REV02-Low
If you can get into recovery you can get into download mode.
If you tried one-click, what happens when you try to flash back to stock?
I'm able to get into Download Mode AND Recovery.
That's not the problem.
What happens is that when my phone reboots after ODIN 1-click or ODIN v1.70 my phone boots like its supposed to boot and then it gets to the Galaxy S screen and at that point it just craps out and the screen goes black after a few minutes. I think that the problem is that the internal sd card won't mount. When I'm in recovery it says:
"E:Can't mount /dev/block/mmcblk0p1
(I/O Error)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet. please us UI me nu for format and reboot actions"
When I try to format the internal SD using system recovery it says the same thing. I'm able to get my computer to recognize the internal sd card in recovery BUT when I try to access the drive it asks me to format the drive (INTERNAL SDCARD being the drive). It then calls me a sack of SH17 and the computer tells me that it's unable to mount the internal SD.
The problem seems to be that my phone has not mounted any memory what-so-ever. If I were able to perform a masterclear that might help but without it being able to get to the home screen that presents a problem.
It's sh177y because I'll have to end up returning it on warranty AND for that I have to mail it back to Samsung and wait for them to return it to me. I can't go that long without my phone. There are business things that I need this phone for.
Sorry that was just a tiny rant.
You did not read the thread I linked to.
You can't master clear through odin one-click? You should be able to do that without getting to the home screen. Try installing the specific driver package that comes with one click. When the partitions are formatted squirelly, the computer can't recognize the phone as such. Give that a try. You'll get there, be patient.
?
I'm not sure what I missed in that post. I've read and reread that post several times.
To masterclear I believed that you had to be able to get into USB Debugging. I tried to masterclear in both download and recovery mode. Those are the only options where Odin recognizes my phone.
Bwrandon said:
I'm not sure what I missed in that post. I've read and reread that post several times.
To masterclear I believed that you had to be able to get into USB Debugging. I tried to masterclear in both download and recovery mode. Those are the only options where Odin recognizes my phone.
Click to expand...
Click to collapse
I doubt if you have an overclocking kernel from previous rom which you forgot set back to default values when flashing back to stock it's really a pain in the a...
gorgy76 said:
I doubt if you have an overclocking kernel from previous rom which you forgot set back to default values when flashing back to stock it's really a pain in the a...
Click to expand...
Click to collapse
Do you have any suggestions?
Sorry if I seem brash but I've been working on this for three days.
I wish you the best of luck.
ive had similar issues as described in this thread before on ONE pc i have and it can be a real PITA!
Im no real expert but i DO know the pc i use has voltage issues, basically it is running everything fine but things cant seem to charge or external devices tend to act weird occasionally off the usb. What i have done to minimize the similar issues you are describing is
1) plug the usb directly into the back of the pc, basically try different usb ports, some seem to get better voltage/stability.
2) unplug any external devices using usb *printers and whatnot*
3)Alternate PC *sorry this is my end all since i found i have no issues on my laptop*
It doesnt 'sound' like your phone is fubar'd but that your pc isnt getting the strongest connection. again this is comming from someone who had pretty much exactly what your describing and thats what i found
edit: also saw your warranty posting. From me on their 4th captivate and seems to be the final stable one *HORARY!* i can tell you that they will send you a new phone first and you send your defective one back..just do it in the timeframe or they WILL charge your att account
The only thing that I can think of is... Put a kernel that has CWM loaded on to it as recovery (maybe speedmod kernel), boot into recovert (and thus into CWM).
Try deleting all data/cache/etc on it, then try reboot it. Other wise, try and install a ROM straight from CWM (via .zip file, if you can somehow get it on your sdcard).
I'm stuck with phone pc-pc screen. I'v flashed multiple times and went back to stock too without issue. But now... I am stuck at that screen and no button combo works. Ordered a jig but that will take days to get here.. Dont know what to do. And its a work phone. lol Any other things to try?
I'm having a similar issue. I can get into download, and it's recognized by odin. But when I try to write or wipe it just sits at the zimage and does nothing. I've even left it over night to no avail.
Bwrandon said:
Do you have any suggestions?
Sorry if I seem brash but I've been working on this for three days.
Click to expand...
Click to collapse
can your pc still recognizes your phone and copy files towards internal sd card? can you enter 3e recovery? does you lost 3 button combo? file extensions uses lagfix should be one of the culprit and the clock values in the kernel in your previous rom not setting it to default (disabling lagfix and setting voltage and clock speed to default) when flashing back to stock as this would probably causes conflict with the stock 2.1 system. it is realy important not to neglect those default settings as this is the usual reasons for bricked phones that would corrupt the installation process. many people forgot this process due to excitement and ended up with a paper weight phone.
clemmie said:
You didn't disable the lagfix before you flashed, and your internal partition is still running ext4 but your data partition is back on efs. See this thread.
Click to expand...
Click to collapse
gorgy76 said:
file extensions uses lagfix should be one of the culprit and the clock values in the kernel in your previous rom not setting it to default (disabling lagfix and setting voltage and clock speed to default) when flashing back to stock as this would probably causes conflict with the stock 2.1 system.
Click to expand...
Click to collapse
You just can't make it clear enough for some people.
clemmie said:
You can't master clear through odin one-click? You should be able to do that without getting to the home screen. Try installing the specific driver package that comes with one click.
Click to expand...
Click to collapse
Clemmie,
"Try installing the specific driver package that comes with one click."
I'm not sure if you read my OP; I've already done that. I've actually done that several times. I understand how to use ODIN 1.00 and 1.70. I've been using them since they were released.
The lagfix/overclock issue that has been mentioned. I understand that. Fixing it is the problem.
Have you tried my solution? It's definitely worth a try :/
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