Hello guys,
i was upgrading using clockwork method to the newest cognition room, but while it was at the first at&t logo screen ( after reebooting from upgrade ) my cat jumped on my table and droped my phone and since it was without the batterycover.. the battery just flew away turning it off..
now everytime i try to turn it on.. it keeps frozen on the at&t logo screen
i cant get into recovery or download mode
and when i try to reboot it to download mode using sdk it just gives that message
"-exec "/system/bin/sh"failed: no such file or directory (2) "
what should it do ?
solved it using the odin 3 method.
as soon as connecting the battery just holded both volume buttons and it appeared as a com 7 so i could get it on odin and flash it as normal.
You should brick that pesky feline of yours... just kidding . It's a good thing you still had DM.
Always flash with bat cover on just in case
Captivate
Cog 2.3b6
Nice thread title, had to read just because of that. Glad you got it to work.
Maybe teach your cat to flash for ya?
Issue resolved, Cat chased and thread closed.
Glad you got it working.
hey, i am posting this for a friend who bricked his phone and doesn't know much about it..
he was running serendipity 7 which is a jvo rom, and tried flashing the pauldiddy remix theme, which says is only meant for jvp and jvq roms. i used a jig, to get the phone into download mode, and the computer detected it when i plugged in the usb. but when i tried to use odin one click to go back to stock, it would get stuck at the "Do not turn off target". im not sure if anyone knows a fix for this, or if i should try using the method from this thread http://forum.xda-developers.com/showthread.php?t=1153310 instead, but i figured i would ask before i messed around with it too much
any feedback would be appreciated
how long do you wait before throwing in the towel? it does take a minute or two to finish it's task ? And are you opening Odin before you hook the usb to the phone ?
waited probably about 5-10 minutes. yeah i opened odin first, and it detected the phone and showed the Added! text
Just out of curiosity, what is the phone doing right now that you're trying to use Odin on it?
The reason I ask is that if you can get to CWM recovery, you might just be able to re-flash the rom (assuming it's a wipe package) and it would take care of the issue.
i cant get into recovery, but i can get into download (using the button combos). not sure if that means anything either
Well keep trying, and you might want to try the odin 1 click. I have a Cappy that got dipped in the pool, it would not go into recovery at all but I could get the download all the time, But it kept getting stuck at the i896 screen or the AT&T screen (odin 1 click) after 3 weeks of trying and having to wait 3 days for it to come out of it's coma it now works fine. If you try the odin 1 click it might work for you just make sure it's not ver 10.10 I think (look under battery). What screen does it go to once you press power IE: black screen rogers screen etc. ?
ive tried using odin 1 click.. like i said, the first time odin actually picked up the device, but it wouldnt get past the "do not turn target off" prompt. but i tried plugging it in again, and now it doesnt seem to even pickup the phone. when i when i try to boot the phone, its just a black screen. thanks for the input though
I want to know why this error occurs !!?
"Can't mount mmcblkp01"
basically i've already been into this bootloop problem but it came up again and was watching this thread so i need to clear off why does this happen and why doesn't we have Perfect-FIX !?
and this time i can't have any recovery options (it takes much time to boot twice and after that the 3-button combo the screen displays random static screen like old TV's!! :/ ) but i can get acces to download mode!
Help plz!
Tried this thread ,I can't get this one-click unbrick work it always says..heimdall must be installed even though i copied latest heimdall v1.3 too!!
can i get any help please ?
Hi,
I rooted my note some weeks ago and I was searching the web, reading all kind of threads and thinking what the problem might be for the last weeks. Finally I decided to register myself on xda and to post my problem.
Like mentioned before I rooted my note via CMW and then flashed a franco kernel, unfortunally I dont know which version, but no custom rom. It all worked fine for 14 maybe 16 hours, then the phone froze after opening a app and after that it stuck at the Galaxy Note N7000 logo. I tried to enter recovery but it didn't work, I can enter downloadmode but I ran out of battery before I could do anything.
Now the phone keeps turning itself on and off the whole time when I try to charge it, the battery image comes for like 1 second and after that the screen turns black again. The battery itself is new so that shouldnt be the problem. I charged it like that for like 4 hours and then tried to enter downloadmode but it only says "battery to low to download".
I hope it is not a hardware problem. If anybody has a idea please help me, I am getting desperate.
Greets
weasl
EDIT: I came from offical 4.0.4 ICS
How old is your phone? Try with another good battery.
Suggestion: you may flash gb via PC Odin and check phone back to normal.
Sent from my GT-N7000 using xda premium
I got my phone last april, so it is not even a year old, but I got a new battery some days before rooting it... I'll try/have to get another one anyway.
Could you give me a link for a stock gb rom please.
Thank you for your quick reply.
Kindly go thru Guru 'drketan' threads and posts.
Sent from my GT-N7000 using xda premium
Found it. Should I use a rom with three parts or with only one? And can I use any rom or one with a special "code" that suits my device, e.g. german....
And just flash the rom and then fullwipe or is wiping not necessary?
I am sorry for the questions but I want to do everything right.
You can use any. Wipe in GB recovery.
Thanks a lot.
Yesterday I finally found somebody to charge my battery, today I flashed a GB stock rom, but I still can`t get any further than the Samsung Galaxy Note logo... It worked one time but I turned the phone off to insert my sim card and it got stuck again.
I tried flashing with pit file and bootloader as well, but no luck.
Could it be a hardware problem? Could a J-tag repair fix it?
Thanks in advantage.
weasl said:
Yesterday I finally found somebody to charge my battery, today I flashed a GB stock rom, but I still can`t get any further than the Samsung Galaxy Note logo... It worked one time but I turned the phone off to insert my sim card and it got stuck again.
I tried flashing with pit file and bootloader as well, but no luck.
Could it be a hardware problem? Could a J-tag repair fix it?
Thanks in advantage.
Click to expand...
Click to collapse
Now your on safe GB rom, enter recovery wipe cache, factory reset, wipe dalvick cache.
Let's know the result
I tried, but I am not able to enter recovery... I press volume up + home + power but I only get the N7000 logo. I have read that you have to press the home button in the right moment to enter stock recovery, could somebody tell if that is true and if yes when do I have to press?
Anyone an idea please? I can enter download mode but not recovery, I downgraded to gb 2.3.6.KK5, I flashed abyss 4.2 but I can get to recovery mode or past the GT N7000 logo. Three times it got to the "package installing" page and one time it even started then I switched it off to insert my sim card and again stuck at the N7000 logo.
I need help please...
weasl said:
I tried, but I am not able to enter recovery... I press volume up + home + power but I only get the N7000 logo. I have read that you have to press the home button in the right moment to enter stock recovery, could somebody tell if that is true and if yes when do I have to press?
Click to expand...
Click to collapse
You have to press the three button combo "a long time" and the power button should be the last one to use.
I always wait until the Samsung Logo appeared 2 times and I see the next animation (depends on your kernel/recovery).
So please try again and hold the three buttons longer.
I flashed the 3-part lc1 gb and did a full wipe. The phone now starts sometimes but gets stuck at the n7000 logo most of the time. When it starts the whole UI feels very laggy, eg. while typing. Recovery mode started one time out of 1000 tries. I am afraid that something with my hardware is wrong. Any ideas? Could a Jtag be a solution? Please help.
try again to get into recovery and do a factory reset from Gb recovery..
press it until you get to recovery. DO NOT remove your fingers when you see n7000 bootlogo. keep pressing . keep pressing. keep pressing.
Recognized Distributor™
I made it in the recovery, did another fullwipe, but it still lags while typing or opening/closing an app and still does not boot proper, I have to try several times to get past the logo screen and it works only when I go in downloadmode and boot from there. Entering the recoverymode still only works randomly. Any idea?
Edit: it also lags while scrolling down/up
weasl said:
I made it in the recovery, did another fullwipe, but it still lags while typing or opening/closing an app and still does not boot proper, I have to try several times to get past the logo screen and it works only when I go in downloadmode and boot from there. Entering the recoverymode still only works randomly. Any idea?
Edit: it also lags while scrolling down/up
Click to expand...
Click to collapse
In all you posts here you never wrote exactly what version of which Rom you installed in whatever way.
That's why I'm still not convinced that you have "defined state" and giving good advice is try&error.
So please start telling: how did you flash, what GB or ICS or JB version, Stock Rom or Custom Rom.
,Sorry, I flashed the n7000xxlc1 - open europe with odin PC, stock, prerooted and in 3 parts. After that I did a fullwipe, the phone turns on after a few tries, most time after I go in download mode and restart from there. It lags while it is on, like short freezes, I tried to install the OTA update to ICS but failed.
Before that I was stuck on the Samsung Galaxy Note logo after flashing a franco kernel via CWM (I am not sure which version but it came with the guide to root, so I thought it could not be bad)
Edit: I flashed the xxlsc 4.1.2 jelly bean offical leak via odin PC, and I still have the same problems. I takes 5-6 reboots to actually start the device and it is very laggy, almost unusable. Every second or so it freezes for short time.
Any help please? I would send it to someone to do a JTAG repair if this could help. I just dont want to waste the money, so if anyone has experienced a problem like this please help me.
Is this a brick revived phone?
Hi there! Now, firstly, ive always used Windows Phones but, would like to join Android and discover what it is really like to use... It really does look like fun to use
Anyway, last night i got my mums old Samsung Galaxy S1(G-I9000) and tried to root it and put CyanogenMod on it so i could get arid of the broken TouchWiz(I don't know what the new versions of it are like, but this one was broken and horrible to use) and get updated to Android 4+. Now, the root was successful and i am very happy with myself for doing that.... But here is where it all fell apart....
So, i jumped on their guide on their cyanogenmod wiki and it turns out that doing that first step(The "Installing a custom recovery on Galaxy S") was not needed because i already had ClockWork on my phone and that doing it would apparently break my phone.... I did not realise that till afterwards.
When i tried to reboot into recovery mode to install CM it got stuck on the boot screen. I think to myself maybe its stuffed and ill just reboot it again and see if it work... Nope. Now i try to reboot normally and leave it alone.... Nope. Turns out, all i can do is get into download mode. Now, from what ive found online, using Odin to reflash my phone with the stock ROM is how to fix my phone, problem is, Odin is not finding the phone and Hard Resetting the phone by holding down Lower Volume button and power is not working.... How can i fix this?
I think you can still recover it. However, the reason Odin might not recognize it it's probably because you haven't installed the Samsung USB drivers
If you install them and try to go into Download mode again you might be able to flash the stock ROM back onto your Samsung phone