Hi all,
I've been running the stock UK ICS, flashed with PC Odin, for a couple of months now. I rooted using Dr. Ketan's guide, flashing CF-Root, then flashed the speedmod kernel initially, but was not too happy with the battery life, then the NoteCore kernel about a month ago (can't remember the exact version).
So I haven't flashed anything new for a month. Today I noticed the phone getting very hot in my pocket, and noticed that it was stuck on the Samsung Boot screen (I hadn't restarted, so happened without my input). Taking out the battery and restarting didn't work, so I was worried by this. Restarting to CWM was also worrying, since I couldn't mount the internal or external storage - the phone wasn't recognised by adb either. I therefore re-flashed the stock UK ICS firmware using Odin on the PC, and this seemed to work successfully, getting the green light with Odin.
However, when it rebooted, I was stuck on the Samsung logo again, and he phone won't boot. Is the device bricked, or is there anything else I could try?
Kitteridge said:
Hi all,
I've been running the stock UK ICS, flashed with PC Odin, for a couple of months now. I rooted using Dr. Ketan's guide, flashing CF-Root, then flashed the speedmod kernel initially, but was not too happy with the battery life, then the NoteCore kernel about a month ago (can't remember the exact version).
So I haven't flashed anything new for a month. Today I noticed the phone getting very hot in my pocket, and noticed that it was stuck on the Samsung Boot screen (I hadn't restarted, so happened without my input). Taking out the battery and restarting didn't work, so I was worried by this. Restarting to CWM was also worrying, since I couldn't mount the internal or external storage - the phone wasn't recognised by adb either. I therefore re-flashed the stock UK ICS firmware using Odin on the PC, and this seemed to work successfully, getting the green light with Odin.
However, when it rebooted, I was stuck on the Samsung logo again, and he phone won't boot. Is the device bricked, or is there anything else I could try?
Click to expand...
Click to collapse
Try flashing a gb rom then perform data, cache, and dalvik wipe before rebooting. Do this while in gb rom only.
jonpaslim said:
Try flashing a gb rom then perform data, cache, and dalvik wipe before rebooting. Do this while in gb rom only.
Click to expand...
Click to collapse
+1
Related
I was on MidTeam 1.3. i decided to change my lcd density via an app and this messed up everything. i went to CWM and do a wipe/factory reset. After this the system failed. I flashed a GB rom via Heimdall, everything went well, the phone booted as usually, i've seen the "click android to start" screen but when i clicked on it phone freezed. I tried to flash different ROMs both customs and stocks, they are all being flashed via heimdall succesfully but stacked at the same place. I finally flashed CM9 (again via heimdall). It booted normally, i saw the lock screen, i unlocked it by touching the screen then the phone freezed again. I made a search on the forum but did not find a similar case. Can anybody help? CWM is working fine, i can do wipe/factory reset or mount any partition.
jayaka said:
I was on MidTeam 1.3. i decided to change my lcd density via an app and this messed up everything. i went to CWM and do a wipe/factory reset. After this the system failed. I flashed a GB rom via Heimdall, everything went well, the phone booted as usually, i've seen the "click android to start" screen but when i clicked on it phone freezed. I tried to flash different ROMs both customs and stocks, they are all being flashed via heimdall succesfully but stacked at the same place. I finally flashed CM9 (again via heimdall). It booted normally, i saw the lock screen, i unlocked it by touching the screen then the phone freezed again. I made a search on the forum but did not find a similar case. Can anybody help? CWM is working fine, i can do wipe/factory reset or mount any partition.
Click to expand...
Click to collapse
see if anything in my signature can help you... good luck!!!
Thank you for the answer. I've succesfully flashed LPY rom from the list you provided the phone restarted, boot animation is ok, then the phone stacked at samsung logo. I've waited like 45 min but nothing has changed. I gave a try with a gingerbread rom but the odin process was freezed during datafs. I'll try another GB and if same thing happens, will try LPY of LPF once again.
jayaka said:
Thank you for the answer. I've succesfully flashed LPY rom from the list you provided the phone restarted, boot animation is ok, then the phone stacked at samsung logo. I've waited like 45 min but nothing has changed. I gave a try with a gingerbread rom but the odin process was freezed during datafs. I'll try another GB and if same thing happens, will try LPY of LPF once again.
Click to expand...
Click to collapse
It looks like you have got a Superbrick on your hands, mate.
It looks so, but as the phone opens both in download and recovery mode and stock lpy rom can be flashed, i still keep the hope for a possible miracle :/
Happy End
After trying hundreds way, my galaxy note is working now.
every rom i try to flash via Odin had some issues. LPY was flashed with succes but stack at boot.
LPF was not able to write DataFS
but i was able to enter CWM. So i flashed abbys kernel. Then i realised that wipe/data factory reset was working.
I formated /data and /system
then i mounted /data
reboot in recovery
again i mounted/data and then flash darky's rom. Everything looks running properly now.
Never ever i'll try a lpy rom
dont try LPF and LPY roms for now..
dont know why they kept making roms for it despite the constant warning... i guess a lot of people love the thrill of bricking expensive things.. lol..
I was flashing ics roms from rocketrom, criseklo, some others, and i flashed 15 toggle theme for 4.04 but systemui kept crashing. I wiped in cwm ics kernel because someone mentioned not to use abyss for criskelo aroma install. I did some wipes couple more times before doing some more clean install but systemui kept crashing,
so I proceeeded to pc odin to flash gb rom.
and now my phone is stuck on samsung galaxy gt n7000 logo.
Please help!
I was on notecore kernel the last before this happened.
so far i can only go into download mode, and revert to gb on odin passes.
i thought they fixed the issue with wiping command for the latest kernels? is my phone bricked?
is there anyway to fix it? worst case scenario, how do i do the warranty step to get the motherboard replaced? i bought mine on amazon few months ago
Problem solved: Before I was trying to flash a pre rooted KJ1 gb rom, and so I gave a stock kka gb rom and it did the trick. So glad my 720 dollar phone didnt go to waste
despine said:
I was flashing ics roms from rocketrom, criseklo, some others, and i flashed 15 toggle theme for 4.04 but systemui kept crashing. I wiped in cwm ics kernel because someone mentioned not to use abyss for criskelo aroma install. I did some wipes couple more times before doing some more clean install but systemui kept crashing,
so I proceeeded to pc odin to flash gb rom.
and now my phone is stuck on samsung galaxy gt n7000 logo.
Please help!
I was on notecore kernel the last before this happened.
so far i can only go into download mode, and revert to gb on odin passes.
i thought they fixed the issue with wiping command for the latest kernels? is my phone bricked?
is there anyway to fix it? worst case scenario, how do i do the warranty step to get the motherboard replaced? i bought mine on amazon few months ago
Problem solved: Before I was trying to flash a pre rooted KJ1 gb rom, and so I gave a stock kka gb rom and it did the trick. So glad my 720 dollar phone didnt go to waste
Click to expand...
Click to collapse
As i was reading your post i thought this is superbrick because your wiping on ics kernel until i read your last input. Well im glad your just fine.
My N7000 just shows a black screen indefinitely after the 'Samsung Galaxy Note GT-N7000' logo.
The soft keys light up when I press them, so it is on during this time.
It is rooted and does this when I flash any of the official CM10 JB nightlies after October 3. (October 1 nightly still works)
Apart from this there is no indication there is anything wrong with my phone.
It is overclocked and undervolted but safely so (it only crashed when I was testing the voltages 2 months ago) (it usually runs at 1.6 GHz and 1250mV)
The only other things i flash are Hydracore 5.4 and SuperSU 0.96, and I've tried booting without these to no avail.
What do i do??????
Thanks in advance!
flash stock ROM and start again, Stick to stock voltages and stock CM kernel and see if it works then.
If not, we can look a bit deeper in to the cause
Edit: forgot to mention that I was already running PA 2.16 with Hydra 5.4oC.
I had the same problem last night, after flashing PA 2.17 it didn't boot up anymore.
It's stopped after the N7000 logo.
I flashed a stock rooted GB ROM with ODIN PC (Dr Ketan guide) and was able to boot once.
When I went back to the CWM recovery it got stuck in the recovery itself and I had to start all over again but with the SGN_XX_OXA_KJ1_FACTORYFS rom there was no improvement, it always booted back in the recovery and there was no way to leave it, factory reset didn't solve the problem either.
Then I flashed N7000XXLA6_N7000XEULA1_XEU with separate CSC and modem and since that moment it came back alive and I restored my last back up.
It took me damn 2 hours to get it back running again.
Note to myself, never flash a rom again before going to sleep.
azzledazzle you were right! Its a kernel problem.
After flashing SGN_XX_OXA_KJ1_FACTORYFS, I installed cm-10-20121005-NIGHTLY-n7000.zip, and it worked!
The thing is any non-stock kernels still cause the original problem.
Stock kernels are fine with me, but do you know how it might be fixed?
Got no clue if it's a kernel problem or how it can ben fixed.
I'm running PA 2.16 + Hydra 5.4 and all is fine again.
Will keep it that way for a while.
Edit: nevermind.
Glad you got it to work
guitarplayerone said:
Edit: nevermind.
Glad you got it to work
Click to expand...
Click to collapse
Ive done the same thing to mine, or shall i say similar.....i was rooting mine to cm10 jelly bean and it booted up fine, i tried to restore it to its former rom and my battery was low and the phone just died on me:silly:
now the logo comes on and after that nothing, blank screen...
it go's in to download mode but not recovery mode....
by the way....am a complete noob:crying:
anyone HELP!!!
aky47 I suggest:
flash SGN_XX_OXA_KJ1_FACTORYFS which is here: d-h.st/HJM using this method: forum.xda-developers.com/showpost.php?p=20963718&postcount=2
put the desired ROM on your phone
enter recovery (hold home+vol up+power until 'Samsung Galaxy Note GT-N7000')
select 'install zip from sdcard'
select 'choose zip from internal SD' (can't quite remember the exact text - its the last option though)
choose the ROM
confirm
wipe data/factory reset from main recovery menu (optionally wipe cache and wipe dalvik cache)
reboot
Note (<(Y)) this worked for me. If it doesn't work for you, I'm not responsible.
And don't do this if you have important stuff on your phone cos you'll lose it.
I was on an ICS based MIUI, when I tried a stock JB ROM (Angry v3).
I have been pretty wary of the EMMC bug, hence I first installed a stock GB ROM and then rooted it through the zergrush method guide Dr Ketan has posted.
Post which I installed the JB ROM, all went well the phone was working for the night. However in the morning at work the phone froze and restarted and was stuck on the Samsung screen (not the boot logo). I did not want to try anything so I got home, the phone was booting in the download mode, so I tried installing the stock GB ROM again through ODIN. All went fine, I got the pass screen on ODIN and the phone rebooted but stuck again at Samsung screen.
Now I cannot even enter the recovery mode, So I am stuck with a paperweight ?
Try connecting the charger. Battery could be dead empty. And this is not Q & A Forum.
Boy124 said:
Try connecting the charger. Battery could be dead empty. And this is not Q & A Forum.
Click to expand...
Click to collapse
Battery was at 80% last checked. Will have the thread moved, and try charging the phone too.
By the way, if thou are on gingerbread firmware; it's safe to factory reset.
first switch off your phone then press the home+voluke up+power button in combination then you can bootup into the stock gb recovery from their format everything(presumed that you are on gb) and please dont post question in general thread..reported
Sent from my GT-N7000 using Tapatalk 2
Hmm, I tried installing another version of stock GB ROM through ODIN, was successful. I was able to to load into recovery, a wipe data and wipe cache allowed me to boot the GB ROm Am downloading the JB Jellybam ROM. A last question, should I be wary of stock leaked versions of JB? I quite liked TW
As always this forum has been of infinite use
A last question, should I be wary of stock leaked versions of JB? I quite liked TW
Click to expand...
Click to collapse
Its pretty safe as there are lots of roms using Leaked TW JB and has safe kernel Philz. till the time you are on a safe kernel.. nothing to worry about..
Hi, I found my old bricked note and decided to try and resurrect it.
When it's not plugged in, I get nothing at all, it won't turn on.
When it's plugged in I get a grey battery animation briefly, and then it reboots. Occasionally I see a green Android animation and a loading bar, but it never makes it far before rebooting.
I can get to Download Mode and tried putting on philz_touch_6.26.6-n7000 recovery, and the stock N7000XXLT9_N7000OXXLT3_CPW files using Heimdall on OSX, after flashing It reboots and I see the Samsung N7000 logo briefly, then it reboots and it's back to the grey battery bootloop.
I bought a new PBA from ebay and switched it in, same issues, though I could at least get into stock recovery for a while, until I flashed over the above files again.
Any advice would be welcome, I've long since replaced the phone but I'd love to get it working again to gift to my brother.
Try flashing philz recovery... Not the one you flashed earlier but XXLTA one. Then try to get into recovery. If you get Cwm, factory reset.. Then flash rom again or flash a custom rom using recovery.
nokiamodeln91 said:
Try flashing philz recovery... Not the one you flashed earlier but XXLTA one. Then try to get into recovery. If you get Cwm, factory reset.. Then flash rom again or flash a custom rom using recovery.
Click to expand...
Click to collapse
Thanks, I flashed over the Philz XXLTA Kernel, no change, I'm struggling to find the Recovery that matches.
Stuck Odin and Kies on a win7 machine I have, and I'm noticing that although I can flash entire stock roms, any of the Philz recoveries I try (although I can only find back to 6.0.1.1) error out with "Complete(Write) Operation failed." They seemed to go fine in Heimdall but I'm wondering if this is a clue. Are there any non Philz recoveries I can try? I also can't download any GB Stock roms from Sammobile, they just download a couple of hundred bytes, and most other links seem to have been on Hotfile, which no longer exists.
Speedmod kernel by hardcore also has Odin flashable files.. Although I really doubt that you are not able to flash PhilZ kernel due to error at your end and not a phone issue.
Resolved it!
Bought a cheap replacement battery from eBay, stuck it in and it booted into the stock 4.1.2 Samsung ROM I flashed last! No problems getting into recovery either.
I'm wondering now if I needn't have bothered buying a new PBA, and it was the battery that caused the hangups and eventual brick last time.
I checked the voltage on the old battery and it's reading 4.14V, which seems like a full charge. Any idea what might have been the issue?
The replacement battery was at around 60%, I'm hoping things don't go wrong again when it finishes charging.