I was recently using Stunner ICS but decided I wanted to go back to stock and start over. I downloaded the stock N7000XXKJ4_N7000OXXKJ4 firmware and installed it through odin. I did not receive any errors on the phone or on my PC. But now it seems like my phone is stuck in a boot loop. It just keeps showing the samsung boot animation over and over. I used the download jig to get into download mode and tried redoing the firmware twice already with no luck. One thing I did notice is that the jig is no longer resetting the binary counter. Does anyone have any other ideas or is my phone possibly bricked?
This is supposed to be in Q& A section... Anyways... Did you try wipe?
Sent from my GT-N7000 using xda premium
What worked for me having the same problem recently is go to Recovery mode (Volume up + home + power) and you'll see this funny kinda recovery, not at all CWM Do a data wipe/factory reset and then reboot.
Same thing happened with me yesterday, wipe in recovery fixed the problem
priyanv said:
This is supposed to be in Q& A section... Anyways... Did you try wipe?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I'm sorry. Mods please move to appropirate section.
Thank you guys. I was beginning to freak out. I was trying to do the recovery menu but couldn't get it to work. I thought the recovery menu was also hosed but I had the wrong buttons. All is good now! thank you so much!
First thing you need to do if you want to get back GB, flash abyss 3.9 redpill kernel.
After that flash GB rom.
So later you can flash whatever kernel you want
Sent from my GT-N7000 using xda premium
Hanging at Samsung logo; can't boot into recovery; am I bricked???
Hi guys...
I've been semi bricked for about 18 hours now. And it's starting to look like it's a full-brick.
I had the latest Gingerbread ROCKET ROM on my Samsung Galaxy Note GT-N7000, with the latest Franco kernel in place.
I thought I'd give the ICS version of ROCKET ROM a go. Flashed Abyss4.2 kernel without any hassles. Used 'advanced' to boot into recovery. Did my various wipes. Flashed the ICS Rocket Rom zip. And got caught up in the recurring boot-up, mostly upgrade, run, reboot cycle that's been described in many places.
Didn't panic.
Booted into recovery again, and flashed the ICS Rocket Rom again.
But this time, it wouldn't go past the SAMSUNG logo.
Still, I could boot into recovery.
Which I did.
And I tried to restore my Gingerbread build from Nandroid.
Tried it. But it hung on the Samsung logo again.
With one key difference... Now, no matter how much I try, I can't boot into recovery.
I *CAN* boot into 'download' mode. So I've used PC Odin to try and inject a rooted Gingerbread rom into the phone.
The instructions tell me to wait for the phone to reboot twice. Sadly, it tries its first reboot, and doesn't get past the Samsung logo. And that's where it hangs. No recovery mode either.
What shall I do??? Oh, woe is me. Etcetera.
--------------------------------------------------------
UPDATE
--------------------------------------------------------
I found a version of Abyss 4.2 kernel in tar format. I flashed it via PC ODIN, and I now seem to have a phone that can boot again.
Not much more to report at the moment, cos the battery is on about 3%, so I'm charging it now before delving further. Will give more feedback once the battery's up and running again.
Here's a link to the Abyss file: http://forum.xda-developers.com/attachment.php?attachmentid=1072122&d=1337500067
I tried all of this, was on stock ICS 4.0.3 and had it rooted.
I tried to restore a backup which was sadly on GB and then the restore of /data failed
I then tried to flash paranoid custom rom and it was successful but the phone never went any further than SAMSUNG GALAXY NOTE GT-N7000 logo
I then Flashed a direct rootable stock rom via PC odin and all was well but the phone would never go any further than the logo before mentioned
I tried flashing AbyssNote kernel via pc odin but the CWM recovery menu kept on rebooting hence leaving me with not particular choice to select
Tried wiping data, cache mem, dalvik cache but no use and now i am on stock recovery menu. please help me out
i have this Samsung i9220 china i try to flash upgrade the firmware with Odin3 v1.85 . i got stock phone can't power non recover modem non booting logo , does anyone have any ideas ?
I've been flashing custom roms for quite a while but yesterday I got into some trouble and the situation that I have now is this.
I've installed a stock rom using Odin. The flash seems to go ok but when the phone boots it gets to the screen where you touch the green android to continue then a lot of force close messages come up.
I've tried flashing the stock rom with Odin a couple of times but I end up with the same result. Is there anything else I can try besides taking the phone to the repair shop?
Any help is appreciated.
If u flashing a GB stock rom, then i got the same backing from ISC LPY.
So i start phone in stock recovery mode (hold: up volume+power+home buttons) and do a full wipe. After reebot it was all ok. Just remember WIPE OLNY IF U FLASH GB ROM!!!!! Wiping in ICS may causes superbrick. Hope i help
appro77 said:
I've been flashing custom roms for quite a while but yesterday I got into some trouble and the situation that I have now is this.
I've installed a stock rom using Odin. The flash seems to go ok but when the phone boots it gets to the screen where you touch the green android to continue then a lot of force close messages come up.
I've tried flashing the stock rom with Odin a couple of times but I end up with the same result. Is there anything else I can try besides taking the phone to the repair shop?
Any help is appreciated.
Click to expand...
Click to collapse
If a factory wipe/reset does not work. You could try the following steps:
Put AbyssNotekernel42 zif file in your micro sd. Flash Abyss then boot into recovery of Abyss and flash the rom again.
tknguyencsu said:
If a factory wipe/reset does not work. You could try the following steps:
Put AbyssNotekernel42 zif file in your micro sd. Flash Abyss then boot into recovery of Abyss and flash the rom again.
Click to expand...
Click to collapse
This cannot be done from stock recovery.
Hi I was running Helly Bean and I was experiencing some lag that i couldnt fix so i decided it was time to start fresh (phone was getting to be a mess anyways) so i formatted my phone and one-click to a stock rom. (rogers i896 2.3.3 with bootloader). I used heimdell to flash kernel with recovery, then flashed devil kernel, reboot recovery, then flashed helly bean as per thread instruction and my phone kept booting into recovery only. So i tried to start over 2 more times with the same results, I even tried to flash CM9 stable release and it yielded the same results.
Can anyone shed some light as to what i messed up? My only option now is to use stock app since i cant seem to get anything else to work...(pleas dont make me go back to touchwiz)
Any help is appreciated,
Thanks.
PS phone works fine on stock rom
This happened to me once... I think it has to do with repartitioning and Devil kernel. If you flash devil first, it seems that something is telling the CM installer that the partitions are all good to go, even though it is clearly not the case. So use heimdall to flash the first kernel, and go straight to the ROM install, making sure to flash the ROM a second time after it reboots into the new recovery.
korockinout13 said:
This happened to me once... I think it has to do with repartitioning and Devil kernel. If you flash devil first, it seems that something is telling the CM installer that the partitions are all good to go, even though it is clearly not the case. So use heimdall to flash the first kernel, and go straight to the ROM install, making sure to flash the ROM a second time after it reboots into the new recovery.
Click to expand...
Click to collapse
Thanks, works first time!!! Looks like im going to have IMEI problems but thats another battle lol
odin to stock 2.3.6, charge to 100%, then go to recovery, 4w, 2f, then install helly bean.
just went thru this last week.... accidentally flashed incorrect ROM to Captivate and phone started acting wiered.
Then came to know i have the wrong bootloaders and kernel. Just installed GB bootloaders and phone started booting to recovery.
then tried to flash ics rom and soft bricked my phone.
Used the "hold both volume buttons and plugin the USB cable to computer" to get into download. then ODIN to stock GB. then used KKroot and then flashed Slim ICS. Now the phone works great.
Hello, i have had my galaxy note for a couple of weeks now.
bit of this and that, you know how it is, flashing a few roms, checking things out, keeping it safe and stuff.
idiotic of me, didn't do a backup.
now
everything was working perfectly fine.
'till i decided to put some music on my sdcard
so i shut the phone down, open it up, take out the battery, take the sdcard, put it in pc, put some music (music i had on it before, so the files could've somehow magically ****ed up the device) then but it back on.
ever since, my device won't boot, it will go to CWM recovery, it will go to download mode, but not like, properly boot. all it does is show the Samsung Galaxy Note N7000 thingie, then screen goes black, and back again to Samsung Galaxy Note N7000, then black again, over and over again.
i figured, it must be something wrong with the bootanimation, had a custom one put there, so i deleted it, cuz that way it goes back to stock.
did that, didn't help, same thing.
then, decided to flash the rom again, even tho it was working perfectly for a few days now, (stock 4.0.4 deodexed zipaligned with hydracore safe kernel)
reflashed, didn't help, nothing happened.
things were weird, i thought i should go back to a GB rom, that always...fixes the problem.
tried to flash with ODIN, stuck at factoryfs, when i pulled the cable out, it would tell me the thingummyjig with firmware update has encountered an issue please bla bla kies.
then, I EVEN TRIED the kies, it won't connect, even tho my drivers are right, and i used kies with it before.
NOW, i thought to myself, ****, the phone won't go to recovery anymore, won't boot normaly, just in download, well, download a speedmod kernel which is safe and flash it, that should give you a CWM and safe kernel to flash from
did that, worked.
flashed the stock 4.0.4 rom again, then flashed philz latest kernel for the rom, and i'm back to square one.
nothing changed, i still can't use my note.
WHAT. DO?
right, well, i tried flashing alliance rom, and it gets stuck at mounting partitions....
the blue bar goes on and on till it gets out of the designated loading space
i can't wipe cache, i can't wipe dalvik, it just gets stuck.
Etnoscope said:
... tried to flash with ODIN, stuck at factoryfs ...
Click to expand...
Click to collapse
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
ThaiDai said:
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
Click to expand...
Click to collapse
Thing is, phone worked flawlessly before, safe kernel,could flash anything,then this just happened....
Phone doesnt have warranty, sending it to some service would only have me end up with extra costs for putting the motherboard there, which i can do myself
right, welll
i tried flashing speedmod kernel with odin, it worked.
then i tried installing a GB rom via CWM
works well till it gets stuck at flashing modem.
what does this mean?
Etnoscope said:
...what does this mean?
Click to expand...
Click to collapse
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
ThaiDai said:
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
Click to expand...
Click to collapse
tried flashing a stock gb with odin (tried 1 file in pda before, now i tried with 3 files(modem, rom, csc), same thing happened.)
stuck at factoryfs again
i didn't want to get to the partition scanner yet, wanted to clear out any other possibility first, using the scanner as a last resort.
what about pit files?
***
also, i really wanna thank you for showing some interest in my issue, means a lot to me, just wanted to let you know i really appreciate it, and i acknowledge the fact that you're a good, helping member.
thanks bro, you're awesome.
If you have tried also with the correct original pit, then it's time for the scanners to do its job
nokiamodeln91 said:
If you have tried also with the correct original pit, then it's time for the scanners to do its job
Click to expand...
Click to collapse
right
so, i've checked out this thread, about the pit method, and after i opened the emmc_find_brick_start.zip, it started scanning normally, and it finished without being stuck anywhere, and then at the end it said scanned 15027 MiB = 15757 MB completed --> OK then the ---end thingie and done.
so the brick start isn't there, which i assume means my phone is NOT bricked, at least not by the emmc thingummyjig
but if so, what the hell am i to do? like really?
tried flashing gb with cwm, stuck at flashing modem
tried flashing gb with odin, stuck at factoryfs
what the ****?
Get the pit file from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
Then flash the GB rom using pc odin. Make sure pit is selected and the repartition is ticked.
Also if you still have access to cwm try to install a CM10 rom first before trying out the above method.
SOOOOO
bit of an update.
right, after the whole emmc scanning brick mbs and stuff, decided to try and flash allianceROM 4.0.4 final
did it, worked, the flashing.
now i'm stuck at a non blinking, non changing non nothing, Smasung Galaxy Note GT-N7000 screen, with the yello jello triangle, same as before, but its not blinking now.
Ok. Try booting into recovery and performing a full wipe.
nokiamodeln91 said:
Ok. Try booting into recovery and performing a full wipe.
Click to expand...
Click to collapse
full wipe means:
factory reset
wipe cache
wipe dalvik
reboot.
right?
did that, as soon as i hit reboot, it got stuck again there, the frozen CWM screen.
battery in/out, back to square 1
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
nokiamodeln91 said:
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
Click to expand...
Click to collapse
official 4.2.1 will do?
Yeah
nokiamodeln91 said:
Yeah
Click to expand...
Click to collapse
any way we could talk via IM?
would be much better conversation-wise
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
nokiamodeln91 said:
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
Click to expand...
Click to collapse
i get status 7 error when i try to flash a CM rom btw, i know what to do, updating philz kernel as we speak
i want you to know i really appreciate this bro, couldn't have come so far without you. thanks a lot man.
right, well, i was using kangbang kernel, tried to install the cm rom, and it gets stuck at installing update...
been there for too long now,so i guess thats a safe bet.
gonna try with a different cm rom
right, well, apparently anything i try to flash gets stuck at installing update....
any solutions?
Hey!
I've flashed kernel and firmware on my Note successfully several times, but now I encountered a problem:
I'm on Asylum_CM10.1_20130311_n7000 ROM and was using Asylum_CM10.1_20130311_n7000 kernel, all working fine.
Then I flashed a new kernel, HydraCoreNirvana Kernel for Galaxy Note GT-N7000. After this I've been in hell, every time I try to start/boot the phone, it jams on the Asylum startup animation. I tried both from the SD and when the phone wouldn't start, via Odin. Then I tried flashing back to the working kernel above, no help. Now I'm stuck with two non-working kernels and a useless phone. I hope I haven't ruined it already...
I was flashing with the instructions @ rootgalaxynote. com
Any help would be greatly appreciated!
-Larson
larson80 said:
Hey!
I've flashed kernel and firmware on my Note successfully several times, but now I encountered a problem:
I'm on Asylum_CM10.1_20130311_n7000 ROM and was using Asylum_CM10.1_20130311_n7000 kernel, all working fine.
Then I flashed a new kernel, HydraCoreNirvana Kernel for Galaxy Note GT-N7000. After this I've been in hell, every time I try to start/boot the phone, it jams on the Asylum startup animation. I tried both from the SD and when the phone wouldn't start, via Odin. Then I tried flashing back to the working kernel above, no help. Now I'm stuck with two non-working kernels and a useless phone. I hope I haven't ruined it already...
I was flashing with the instructions @ rootgalaxynote. com
Any help would be greatly appreciated!
-Larson
Click to expand...
Click to collapse
Please, I'm drunk and freaking out with this phone (I know 1st world problems).
Do a wipe data in recovery (if u can go to) or ODIN. Then try to see if the phone boots, if it doesn't you can do a clean install of Asylum ROM again. If nothing works(!) Go back to flash a stock ROM via ODIN and then use Philz kernel to re-root.
Varad297 said:
Do a wipe data in recovery (if u can go to) or ODIN. Then try to see if the phone boots, if it doesn't you can do a clean install of Asylum ROM again. If nothing works(!) Go back to flash a stock ROM via ODIN and then use Philz kernel to re-root.
Click to expand...
Click to collapse
Tried all that (went straight to stock). No help, I guess somethings gone wrong with the boot sequence, I flashed Philz kernel and now it loops on the samsung animation. Before, it sometimes showed "Android is upgrading 1/83 (or something similar), the number would go up a while, then the start-up animation again and all over again from 1/83. It always seems to jam on the ****ing animation... Gonna jump off the roof.
larson80 said:
Tried all that (went straight to stock). No help, I guess somethings gone wrong with the boot sequence, I flashed Philz kernel and now it loops on the samsung animation. Before, it sometimes showed "Android is upgrading 1/83 (or something similar), the number would go up a while, then the start-up animation again and all over again from 1/83. It always seems to jam on the ****ing animation... Gonna jump off the roof.
Click to expand...
Click to collapse
I got the phone working again. Did a factory reset from recovery and after that the phone started up. After that installed the HydraCoreNirvana Kernel again and now it works just fine. Thanks very much for the help!