Dead Samsung Galaxy Note. Need Suggestions. - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

I was trying to root and install a custom ROM on my phone when this happens.
I suffered 3 kinds of brick that I recognized from reading the forum's guides.
So here's the story:
I install SuperUser and CWM through the stock recovery mode.
After that I tried to wipe everything with CWM from my phone as I wanted to downgrade from my update Official ICS back to the stock GingerBread ROM. (This is to prevent any problems to install the new custom ICS. Read on forum also*)
During the wipe, CWM got stucked at somewhere at the start of the process (Forgotten what it was). It was about more than 15minutes before I made my decision to stop it by holding the power button. Obviously this caused a bootloop or something like a soft brick (Stuck at boot screen).
After the first brick encounter, I tried to fix it by flashing the stock GingerBread ROM directly with Odin without wiping anything as it was stucked in the first step. By doing this, I think I had a Super Brick as the installation also got stucked at loading factoryfs.img image file. There's no solution to this as I looked up in the forums for quite some time.
So, I cancelled the installation and my phone wouldn't start up again. There's no sign of battery charging when plugged in and it wouldn't start by holding the power button. Unable to access recovery/download mode. Odin also didn't recognize my device.
Can anyone here kindly advice me on what should I do now? In deep sad mode -.-

cyyong95 said:
I was trying to root and install a custom ROM on my phone when this happens.
I suffered 3 kinds of brick that I recognized from reading the forum's guides.
So here's the story:
I install SuperUser and CWM through the stock recovery mode.
After that I tried to wipe everything with CWM from my phone as I wanted to downgrade from my update Official ICS back to the stock GingerBread ROM. (This is to prevent any problems to install the new custom ICS. Read on forum also*)
During the wipe, CWM got stucked at somewhere at the start of the process (Forgotten what it was). It was about more than 15minutes before I made my decision to stop it by holding the power button. Obviously this caused a bootloop or something like a soft brick (Stuck at boot screen).
After the first brick encounter, I tried to fix it by flashing the stock GingerBread ROM directly with Odin without wiping anything as it was stucked in the first step. By doing this, I think I had a Super Brick as the installation also got stucked at loading factoryfs.img image file. There's no solution to this as I looked up in the forums for quite some time.
So, I cancelled the installation and my phone wouldn't start up again. There's no sign of battery charging when plugged in and it wouldn't start by holding the power button. Unable to access recovery/download mode. Odin also didn't recognize my device.
Can anyone here kindly advice me on what should I do now? In deep sad mode -.-
Click to expand...
Click to collapse
my suggestion is to read this and run before you get bombarded http://forum.xda-developers.com/showthread.php?t=1321268

I think you dont know what you are doing, as you dont know where to post so i think its better off you dont do anything with your phone

It should be in Q&A forum....Moderators please move it to appropriate forum.....

Stop irritating him. How do you feel if your phone got bricked and don't know what to do.
Coming to the topic. You did not follow basic steps, you used the wrong method of rooting that to on ICS. Don't think that your phone is bricked. Did you flash any custom kernel. I think you were trying too many things and your phone is dead. This happened to me once, I thought my phone is bricked and didn't know what to do. But I remembered I had a external battery adapter charger and charged my battery separetly and know what it worked. Try charging your phone separetly.
Sent from my GT-N7000 using xda app-developers app

Bro you should've use abyss kernel with red pill to downgrade to gb... cwm has some sort of bug even if its fixed . Be on the safe side and flash abyss
Sent from my GT-N7000 using xda premium

I have to place my threads in the correct category, and so do you.

first move to the right place
second give more details of what you have done, the steps, the kind of kernel, rom, otherwise we cant give you accurate solutions
Sent from my GT-N7000 using XDA

Start Thread and ask for donations, that's what we all do here.

Yes...I see that's the trend here... I suggest when they got, just buy themself an SG3

xlfate said:
Bro you should've use abyss kernel with red pill to downgrade to gb... cwm has some sort of bug even if its fixed . Be on the safe side and flash abyss
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Agree..use abyss kernel to wipe anything bfore flash any ics rom for ur own safety
Sent from my GT-N7000 using xda premium

Samsung service seems the only solution as you can't get into dl or cwmr modes.
Sent from my GT-N7000 using xda premium

http://forum.xda-developers.com/showpost.php?p=28744408&postcount=5713
This great solution comes from rocket thread, where else.

Galaxtus said:
Stop irritating him. How do you feel if your phone got bricked and don't know what to do.
Coming to the topic. You did not follow basic steps, you used the wrong method of rooting that to on ICS. Don't think that your phone is bricked. Did you flash any custom kernel. I think you were trying too many things and your phone is dead. This happened to me once, I thought my phone is bricked and didn't know what to do. But I remembered I had a external battery adapter charger and charged my battery separetly and know what it worked. Try charging your phone separetly.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I'll post it in right forum to get my queries answered..better to follow the rules...its not hard to understand.better to spend ur valuable time to read it and posting in the appropriate forum to get correctly answered rather than opening topics. Just a suggestion...
Nw come to the point. Please explain the situation what u did and what files u flashed? XDA are always here to help you.
Sent from my GT-N7000 using XDA Premium App

cyyong95 said:
I was trying to root and install a custom ROM on my phone when this happens.
I suffered 3 kinds of brick that I recognized from reading the forum's guides.
So here's the story:
I install SuperUser and CWM through the stock recovery mode.
After that I tried to wipe everything with CWM from my phone as I wanted to downgrade from my update Official ICS back to the stock GingerBread ROM. (This is to prevent any problems to install the new custom ICS. Read on forum also*)
During the wipe, CWM got stucked at somewhere at the start of the process (Forgotten what it was). It was about more than 15minutes before I made my decision to stop it by holding the power button. Obviously this caused a bootloop or something like a soft brick (Stuck at boot screen).
After the first brick encounter, I tried to fix it by flashing the stock GingerBread ROM directly with Odin without wiping anything as it was stucked in the first step. By doing this, I think I had a Super Brick as the installation also got stucked at loading factoryfs.img image file. There's no solution to this as I looked up in the forums for quite some time.
So, I cancelled the installation and my phone wouldn't start up again. There's no sign of battery charging when plugged in and it wouldn't start by holding the power button. Unable to access recovery/download mode. Odin also didn't recognize my device.
Can anyone here kindly advice me on what should I do now? In deep sad mode -.-
Click to expand...
Click to collapse
Have you read the post quoted below?
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Please read and see if it helps. Or maybe you have already tried the process outlined.
All the best to you.

I'm sorry to post in the wrong section of the forum. It was my mistake to not read instructions carefully.
Now I have sent it to the service center and waiting for their response. But I didn't do anything like put my phone in the microwave or anything.
So does that means they will find out that I did something to my phone and void my warranty?

smaiitm said:
Have you read the post quoted below?
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Please read and see if it helps. Or maybe you have already tried the process outlined.
All the best to you.
Click to expand...
Click to collapse
Thank you very much for the help but it was too late as my phone is already confirmed hard bricked.
Will try it if I got the chance to bring my phone back to life.

Changed a new note from samsung service LOL

cyyong95 said:
Changed a new note from samsung service LOL
Click to expand...
Click to collapse
Great! Have Happy Times Flashing Safely! Cheers.

Related

[Q] Galaxy note stuck on Samsung logo. Cant enter recovery!

Hello guys. I just upgraded Samsung note n7000 to stock ics rom. I rooted it and all was fine. I wanted to try stunner ics rom so I went to recovery mode and then entered cwm. As soon as I pressed wipe date, it got stuck and now I can't even get into recovery mode. Phone either stuck on Samsung logo or if I try to enter recovery by pressing vol up + home + power, it shows android bot with blue wheel rotating and it keep rotating then again goes to Samsung logo after several minutes. Please advise what to do. I'm new to all this.
If you can get into download mode, Vol down Home and Power, use PC Odin to flash any of stock ROMs and start all over again..
Try flashing GB ROMs first as you are new.. ics roms are not safe ATM..
http://forum.xda-developers.com/showthread.php?t=1610157
Also, just read all the stickies.. They are there for a reason!
Sent from my GT-N7000 using XDA
Ouch. Apologies in advance.. did you not read this? http://forum.xda-developers.com/showthread.php?t=1633943 It sounds like a hard brick. Situations like this should make everyone realise why mods and devs continually drum into users the importance of searching threads and reading stickies.
OMG !! Why did you "WIPE" ?????????
Anyhow...
Try to use ODIN to Get u back to GB. You can flash a Pit file as a last resort. Please go through the numerous threads on ICS and its Risks before flashing.
drgupta1981 said:
Hello guys. I just upgraded Samsung note n7000 to stock ics rom. I rooted it and all was fine. I wanted to try stunner ics rom so I went to recovery mode and then entered cwm. As soon as I pressed wipe date, it got stuck and now I can't even get into recovery mode. Phone either stuck on Samsung logo or if I try to enter recovery by pressing vol up + home + power, it shows android bot with blue wheel rotating and it keep rotating then again goes to Samsung logo after several minutes. Please advise what to do. I'm new to all this.
Click to expand...
Click to collapse
Hope you haven't bricked it. You might not have, and if you haven't PLEASE search and read the stickies.
Sent from my GT-N7000 using XDA
I fear this might be another one in the long line of Superbricks.
My friend had juz successfully overcome the stuck at " NAND Write stuck" in PC odin while flashing the lp1 leak repack...
What we did was to change a different usb port... provided u r still able to go into download mode..
We successed into bringing it back to life...
I hope it mayb some help.. no harm trying though...
Noted From My G.NOTE Using XDA Premium
Yes,its totally hardbrick. The eMMC cant be read while it boot,thats why you stuck in samsung galaxy note logo.. Bring it to sevice centre,and just wish they change your machine. I've experienced it when I was using galaxy s2, fortunatly they put it on guarentee and they change my machine.
Sent from my GT-N7000 using xda premium
trying odin but stuck at factoryfs...
hackerboi said:
OMG !! Why did you "WIPE" ?????????
Anyhow...
Try to use ODIN to Get u back to GB. You can flash a Pit file as a last resort. Please go through the numerous threads on ICS and its Risks before flashing.
Click to expand...
Click to collapse
im trying odin with stock GB rom but its stuck on factoryfs now. i tried different ports. not going ahead. what are my options now?
thanks.
drgupta1981 said:
im trying odin with stock GB rom but its stuck on factoryfs now. i tried different ports. not going ahead. what are my options now?
thanks.
Click to expand...
Click to collapse
Another hardbrick!? I think yes. F***, I feel sad for all of those who are bricking their devices.
I am afraid you have to send it to Samsung. They shall replace the mainboard.
Sent from my GT-N7000 using XDA
i feel sorry for your note but WHY THE HELL DID YOU WIPE??
welcome to *superbrick club*.
one solution is to join the *go-to-samsung-center-and-get-replacement-under-warranty club*
I know a dev(name not to be disclosed) who have recovered from a superbrick (and yeah I'm sure a superbrick) by making a custom kernel.I can let let the info out if any real and very talented kernel dev can make a kernel.I'm not trolling guys....Its real.
vijai2011 said:
I know a dev(name not to be disclosed) who have recovered from a superbrick (and yeah I'm sure a superbrick) by making a custom kernel.I can let let the info out if any real and very talented kernel dev can make a kernel.I'm trolling guys....Its real.
Click to expand...
Click to collapse
My english is not good enough to make out what you are saying. You say it's real....and you say you are trolling. If it's the last.....not funny at all for all those users with bricked devices.
Ce said:
My english is not good enough to make out what you are saying. You say it's real....and you say you are trolling. If it's the last.....not funny at all for all those users with bricked devices.
Click to expand...
Click to collapse
Lol typo mistake....corrected now.I know know it fells when making a bricked phone.So i know I must not make fun and I didnt.A single word changed the entire meaning.
sujal said:
Another hardbrick!? I think yes. F***, I feel sad for all of those who are bricking their devices.
I am afraid you have to send it to Samsung. They shall replace the mainboard.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
But I'm able to go to downloading mode and when i put it on charge, it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again.
Does it still mean I hard bricked the device?
Unfortunately, yes.
You can try to flash a stock GB Rom from Download Mode using PC Odin, but your
flash will fail. We have seen it so many times before...
However, there's no harm in trying, so go for it, maybe you prove to be an exception.
warranty?
if i connect my phone to charger, it says firmware upgrade encountered an issue. please select recovery mode in kies. but kies detects the phone bnut keeps saying connecting....
i am able to go to downloading mode which says
custom binary download:no
current binary: official
i have tried to put stock rom using pc odin but it gets stuck at nand write start.
is there a way out here?
if not, will samsung honour the warranty?
thanks.
drgupta1981 said:
i have tried to put stock rom using pc odin but it gets stuck at nand write start.
is there a way out here?
if not, will samsung honour the warranty?
thanks.
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=1653290
Whether Sammy will honor the warranty? I guess it depends on your local service centre.
i had the same problem. i wiped cache and data. problem solved.
custom binary download:no
current binary: official
Click to expand...
Click to collapse
Yes they will honor the warranty. give an excuse that you got a notification for upgrade to ICS and then your phone wont boot.
all the best

[Q] Superbrick, Softbrick, Pixel Salad ?huh?

Seriously can someone please explain to me what the heck the above mean? I get the notion of a brick but what the heck is the difference between Super brick? Hard / Soft Brick? Finally, not really brick but what's Pixel Salad!?
Thanks!
altrstar said:
Seriously can someone please explain to me what the heck the above mean? I get the notion of a brick but what the heck is the difference between Super brick? Hard / Soft Brick? Finally, not really brick but what's Pixel Salad!?
Thanks!
Click to expand...
Click to collapse
Soft brick= a FAILURE of the device that can be reverted by the user
Hard brick= a FAILURE of the device that has to be reverted via external devices see jtag
Superbrick= a FAILURE of the device where the only solution the service center and a replacement of the component that malfunctions.
Pixel salad = a problem of the graphics unit or the screen to display correctly the image and put instead random colored pixels on some areas of the screen or the whole screen.
This is my interpretation of those issues everyone can correct it if he thinks that those expansions are incorrect.
Hope it helped you understanding few of those issues.
GL& HF
Sent from my GT-N7000 using Tapatalk 2
Braxos said:
Soft brick= a FAILURE of the device that can be reverted by the user
Hard brick= a FAILURE of the device that has to be reverted via external devices see jtag
Superbrick= a FAILURE of the device where the only solution the service center and a replacement of the component that malfunctions.
Pixel salad = a problem of the graphics unit or the screen to display correctly the image and put instead random colored pixels on some areas of the screen or the whole screen.
This is my interpretation of those issues everyone can correct it if he thinks that those expansions are incorrect.
Hope it helped you understanding few of those issues.
GL& HF
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
You are spot on!!
Hi, I flashed N7000ZSLPF ICS with bootloader and rooted afterwards. Everything was perfect until i decided to flash cm9 nigthly signed.zip and did a direct reboot. Now nothing happens when i try to turn the phone on
What kind of brick is this? Can somebody please tell me ?
Is there any possibilities to get the phone fixed?
Thank you all for your answers allready
Wish u all a nice day
Nefret90 said:
Hi, I flashed N7000ZSLPF ICS with bootloader and rooted afterwards. Everything was perfect until i decided to flash cm9 nigthly signed.zip and did a direct reboot. Now nothing happens when i try to turn the phone on
What kind of brick is this? Can somebody please tell me
Click to expand...
Click to collapse
I'm not 100% sure, but performing a flash under lpf isn't recommended. How did you root lpf after flashing? And when you say "did a direct reboot" what do you mean? Also when you say doesn't turn on at all, do you mean no display whatsoever or enters Samsung boot loop? Are you able to enter recovery or download mode?
Sent from my GT-N7000 using xda premium
Nefret90 said:
Hi, I flashed N7000ZSLPF ICS with bootloader and rooted afterwards. Everything was perfect until i decided to flash cm9 nigthly signed.zip and did a direct reboot. Now nothing happens when i try to turn the phone on
What kind of brick is this? Can somebody please tell me ?
Is there any possibilities to get the phone fixed?
Thank you all for your answers allready
Wish u all a nice day
Click to expand...
Click to collapse
You should have read the warning about LPx kernels (LP1, LP5, LP6, LPY, LPF)
Wiping or flashing in recovery will probably cause superbrick.
Sent from my GT-N7000 using XDA
Nefret90 said:
Hi, I flashed N7000ZSLPF ICS with bootloader and rooted afterwards. Everything was perfect until i decided to flash cm9 nigthly signed.zip and did a direct reboot. Now nothing happens when i try to turn the phone on
What kind of brick is this? Can somebody please tell me ?
Is there any possibilities to get the phone fixed?
Thank you all for your answers allready
Wish u all a nice day
Click to expand...
Click to collapse
The way to go from ANY non-CM9-based ICS Rom to a CM9-based Rom is via Gingerbread.
You should've first used PC Odin to go back to GB, root your Rom, then flash CM9.
You have most probably superbricked your phone.
SpyderTracks said:
I'm not 100% sure, but performing a flash under lpf isn't recommended. How did you root lpf after flashing? And when you say "did a direct reboot" what do you mean? Also when you say doesn't turn on at all, do you mean no display whatsoever or enters Samsung boot loop? Are you able to enter recovery or download mode?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Did root using cfs root trough Odin Pc. With a direct boot i mean that i just rebooted without doing the partiton thing just flashed the image and rebooted.
And when i say doesnt turn on at all i mean that absolutely nothing happens, no power at the screen no detection trough usb on pc no download mode or anything.
tryied to flash before and did just reboot, back then did just got the boot looop probem and did a recovery to ics. this last time i tried again to show a friend in a hurry and failed epicly
Nefret90 said:
Did root using cfs root trough Odin Pc. With a direct boot i mean that i just rebooted without doing the partiton thing just flashed the image and rebooted.
And when i say doesnt turn on at all i mean that absolutely nothing happens, no power at the screen no detection trough usb on pc no download mode or anything.
tryied to flash before and did just reboot, back then did just got the boot looop probem and did a recovery to ics. this last time i tried again to show a friend in a hurry and failed epicly
Click to expand...
Click to collapse
You are definitely bricked, I fear. Head to the nearest service centre.
I am from Kuwait ..
I purchased Samsung galaxy Note N7000 15 Days before
I have Installed King Droid ICS mania 2.1 later yesterday i updated to King droid ICS mania 3.0 and Samsung galaxy s3 Mod updated .. after that i restarted my NOTE but its not booting
i can go to Download mode and Recovery mode ..
even i can see the Install ZIP from SD card and all in CW ..when i Update it says
Can't Mount EMMC
I tried to Mount also But failure ..
I tried Stock rom of ICS official to Update Using ODIN 1.85 .. it stops at
<ID:0/008> factoryfs.img ..
I am worried I cant go for warranty Bcoz at Boot It says Binary count (5)
Please Help me Out

Stuck to yellow triangle! under Samsung logo: Nothing is working. Begging for help

Hey all request for great help,
I think I got brick, a great one.
I was running KingDroid v7 with Notecore Kernel but wanted to upgrade to it in KingDroid v7.1.
So I have flashed Abyss 4.2 Red pill Original logo 4.2. after wiping through jbroid but when reboot in recovery I have received Yellow Triangle ! Icon under Samsung Galaxy Note - GT-N7000.
After that I have done all three wipes and flashed again Kingdroid v7 from SD card because I forgot to move KingDroid v7.1 in Internal SD Card.
During KingDroid v7 I have selected NoteCore 9 and LRK and 240ppi like something.
After completing the procedure I have restarted my phone but I found again Yellow Triangle ! Icon under Samsung Logo. I have waited around 10 to 15 minutes but could not see any of reaction so I thought this would not work on my device. So I have again removed battery and by using Vol Up + Main Button + Power and started in CWM.
I flashed again Abyss 4.2 and reboot into recovery. This time I have flashed LRT (Under LRB second Modem) with Speedmod v13 after doing all three wipes.
Here problem comes, after completion of compete procedure, I have reboot the system and waited for 10 to 15 minutes for starting the device but I am just stuck to the Yellow Triangle ! logo under Samsung.
After an half hour I have tried to go for recovery but it is not starting any thing rather just Yellow Triangle Icon !.
Tried many time and still trying to go for recovery mode but nothing happening.
Please do something... help me out....
I am in great tense... I thing its a big brick bug for me...
Thanks to all supporters in advance.....
Can you boot into download mode? If yes, then try flashing stock GB rom for your region (India I guess)
krishkamlesh said:
Hey all request for great help,
I think I got brick, a great one.
I was running KingDroid v7 with Notecore Kernel but wanted to upgrade to it in KingDroid v7.1.
So I have flashed Abyss 4.2 Red pill Original logo 4.2. after wiping through jbroid but when reboot in recovery I have received Yellow Triangle ! Icon under Samsung Galaxy Note - GT-N7000.
After that I have done all three wipes and flashed again Kingdroid v7 from SD card because I forgot to move KingDroid v7.1 in Internal SD Card.
During KingDroid v7 I have selected NoteCore 9 and LRK and 240ppi like something.
After completing the procedure I have restarted my phone but I found again Yellow Triangle ! Icon under Samsung Logo. I have waited around 10 to 15 minutes but could not see any of reaction so I thought this would not work on my device. So I have again removed battery and by using Vol Up + Main Button + Power and started in CWM.
I flashed again Abyss 4.2 and reboot into recovery. This time I have flashed LRT (Under LRB second Modem) with Speedmod v13 after doing all three wipes.
Here problem comes, after completion of compete procedure, I have reboot the system and waited for 10 to 15 minutes for starting the device but I am just stuck to the Yellow Triangle ! logo under Samsung.
After an half hour I have tried to go for recovery but it is not starting any thing rather just Yellow Triangle Icon !.
Tried many time and still trying to go for recovery mode but nothing happening.
Please do something... help me out....
I am in great tense... I thing its a big brick bug for me...
Thanks to all supporters in advance.....
Click to expand...
Click to collapse
Are u able to get into download mode?...if you are just flash a stock GB firmware if not try to get a jig...
There is no need to open the same thread again and again in diff sections. Reported.
Sent From My GT-N7000 Using XDA Premium.
sahilarora2003 said:
There is no need to open the same thread again and again in diff sections. Reported.
Sent From My GT-N7000 Using XDA Premium.
Click to expand...
Click to collapse
Hi Sahil, we appreciate your efforts for keeping the forum organized but you should understand his state of mind, he is assuming his phone is bricked and in these scenarios people do this kind of things, let him resolve his issue first and then you can report one of his thread. Moreover his threads are not in same section.
jeetu1981 said:
Hi Sahil, we appreciate your efforts for keeping the forum organized but you should understand his state of mind, he is assuming his phone is bricked and in these scenarios people do this kind of things, let him resolve his issue first and then you can report one of his thread. Moreover his threads are not in same section.
Click to expand...
Click to collapse
I fully understand his situation and tried to helped him. But we should follow the rules first. Every thread cost a beer(bandwidth usage) for XDA. Hope you understand my point.
Sent From My GT-N7000 Using XDA Premium.
sahilarora2003 said:
I fully understand his situation and tried to helped him. But we should follow the rules first. Every thread cost a beer(bandwidth usage) for XDA. Hope you understand my point.
Sent From My GT-N7000 Using XDA Premium.
Click to expand...
Click to collapse
yup, that's why I posted in his other thread about it being duplicate and never appreciate that
Thanks to all of you....
Dear all Senior Members (Mr. Sahil Sir),
I am really sorry for my such behavior that I have posted two thread for a single problem...
Actually, I was in dilemma that in which genre I need to post this problem. So I thought I will better post in both, in whichever post I will get reply I would solve it after I will tell moderator to delete the thread.
But you guys are like awaken lions, I have solved out within a minute. Actually I have not resolved the problem because I cannot flash until I get GB rom in my PC. so I need to have a nap here. . .
Tomorrow in the same post I will try to reply, what happened with my device...
Thanks to each member who have viewed and looked to this problem..
A joyfull joined hands to those seniors who have converted my tears into smile within a single minute .... Sahil Sir Salute to You....
How I have solved my Problem???
Hello Dear...
I have resolved the issue…
I have followed the below procedure...
1. Go and have coffee after keeping your device in charging first.
2. During this download Dr. Ketan's pre-rooted GB Rom
3. After this remove your battery once.
4. Press Vol Up + Main Button + Power
5. You are now going for download mode so press Vol up to flash Custom Rom.
6. Start Odin in your PC or Laptop.
7. Connect your Cable.
8. Wait until you will receive Yellow color in ID:COM. (Check ticked Reboot + F Reset Time)
9. Locate the downloaded GB Rom in PDA of Odin.
10. Recheck each step properly followed or not. And now press start.
Please take the expert advise before flashing anything, you are about to lose 30k under your kicked ass...
| T h £ G ® £ @ t G ! @ n t G @ | @ x ¥ |\|0t€ |
krishkamlesh said:
I am writing this for those who may face such Yellow Triangle! Icon bug in Future...
Click to expand...
Click to collapse
Just go to Download mode (vol down+home + Power) and let me tell what is Flash counter.
First of all this is not 'Triangle Icon bug' Triangle happens when you flash custom things with Odin, Bug is called when something happens in abnormal way during normal/ routine procedure.
Solution you have wrote is just confusing. I think still you are not clear what issue was and what you have solved.
Just presence of Triangle can't stuck your device.
Triangle which was appeared was due to flashing Custom kernel with Odin, it has no relation with stucking.
Your Flash counter must be high still., Nothing method mentioned above can clear it.
Can you tell me
What was issue you had ?
What you solved?
dr.ketan said:
Just go to Download mode (vol down+home + Power) and let me tell what is Flash counter.
First of all this is not 'Triangle Icon bug' Triangle happens when you flash custom things with Odin, Bug is called when something happens in abnormal way during normal/ routine procedure.
Solution you have wrote is just confusing. I think still you are not clear what issue was and what you have solved.
Just presence of Triangle can't stuck your device.
Triangle which was appeared was due to flashing Custom kernel with Odin, it has no relation with stucking.
Your Flash counter must be high still., Nothing method mentioned above can clear it.
Can you tell me
What was issue you had ?
What you solved?
Click to expand...
Click to collapse
I think it was 1 binary something. . .
I don't know what I have done to my device yesterday but it was like this.
1. I have been advised to install the kernel using Odin and I have flashed NoteCore 13v STD using Odin on PC. (KingDroid Rom v7)
2. I have restarted the device and the Triangle Icon was there. I didn't care about it but I have noticed that my battery was not working well even.
3. So I thought to flash NoteCore v13 OC as it consumes very less voltage compared to the other devices. This time I have used CWM to flash as I felt Odin would be dangerous.
4. After flashing I again found the same battery drainage. So I thought to go on the same basic kernel of KingDroid Rom as it was better than NoteCore for battery life.
5. I flashed Abyss Redpill Original Logo 4.2. and started wiping everything and installed 240ppi something and KingDroid bluetheme. (This was one problem because I need to select either among this.)
6. After completion of this process I felt that the device is not starting. As it was stuck to the Samsung Logo.
7. I removed battery and booted it in recovery mode. Flashed Jboid kernel cleaning. Flashed Abyss Rdpill 4.2
8. Again flashed the KingDroid v7 and in Aroma installer Selected Speedmod Kernel and LRT (under LRB) modem.
9. Flashed by selecting other options and given system reboot.
10. I was stucked here. After I waited half hour but there was not reaction and started posting on XDA.
11. Solution was made and I thought its a time for awareness...
I dont remember much about other things but whatever I know I have shared with you.
After flashing GB + Rooted and after it updated to the ICS.
Everything working well but would like to know in deep what mistake I have done as I read and only after I do flashing..
Please enlighten me...
Let me know your other questions.... Please give thanks if I am increasing my interest bit here...
thanks Dr. Ketan, You are a really great man behind the Galaxy Note XDA development.
I am not a bit responsible for Galaxy Note development, I am just contributor. and i have developed nothing nothing.
But Strongly recommend you to just delete your solution you wrote in previous post.
I never like to report any comment which is posted just innocently, and i believe same for your solution. This is not a solution but misleading guide. I think you still needs to learn and read more before making guide and solution for others. Here still you didn't understand what actually happened to your device and How did it solved.
There are already guide available regarding removing triangle.
Hope you can take my humble request seriously, just for having good to other newbies.
And yes earliest clear your flash counter, just removing triangle have no value in presence of raised flash counter.
dr.ketan said:
I am not a bit responsible for Galaxy Note development, I am just contributor. and i have developed nothing nothing.
But Strongly recommend you to just delete your solution you wrote in previous post.
I never like to report any comment which is posted just innocently, and i believe same for your solution. This is not a solution but misleading guide. I think you still needs to learn and read more before making guide and solution for others. Here still you didn't understand what actually happened to your device and How did it solved.
There are already guide available regarding removing triangle.
Hope you can take my humble request seriously, just for having good to other newbies.
And yes earliest clear your flash counter, just removing triangle have no value in presence of raised flash counter.
Click to expand...
Click to collapse
Thanks a lot for you valuable suggestion...
I mean to be myself as newbie only...
I will delete that post just now ...
I don't know how to clear the flash counter but when I press Vol down + Home button + power it shows following:
Proudct name= GT N-7000
Custom Binary Download: Yes (1 counts)
Current Binnary: Samsung Official
Please guide wherever I do not able to respond well to this forum. . .
Thanks . .. I know you are not a developer but you are being great source of help to me that is why I believe you ans Sahil sir as a man of Galaxy Note...
Thanks . ..
Just use triangle away to reset counter.
If you dont know where is thread, go to 'toolbox' on my signature and look for it.
Till you don't clear count, your warranty is no more valid.
Triangle appears when you flash custom stuff with PC Odin, and you have flashed kernel, thats why you had it. Which was removed as you have flashed stock ROM. but flash counter won't remove with it.
So your issue was not yellow triangle, but bad flashing which made your device stucked. But you have flashed kernel with Odin that why it was counter product along with stuck. Once you have flashed GB ROM and wiped your stuck was removed as well triangle too. But in real sense your counter was not reset (b'coz it is not possible with that)
Now you can better understand, why your title and solution was misleading. and I forced to ask to delete it.
Very well said by sr ketan.... Getting the yellow triangle under boot logo and getting stuck there is a different thing.
Sent from my GT-N7000 using xda premium
dr.ketan said:
Just use triangle away to reset counter.
If you dont know where is thread, go to 'toolbox' on my signature and look for it.
Till you don't clear count, your warranty is no more valid.
Triangle appears when you flash custom stuff with PC Odin, and you have flashed kernel, thats why you had it. Which was removed as you have flashed stock ROM. but flash counter won't remove with it.
So your issue was not yellow triangle, but bad flashing which made your device stucked. But you have flashed kernel with Odin that why it was counter product along with stuck. Once you have flashed GB ROM and wiped your stuck was removed as well triangle too. But in real sense your counter was not reset (b'coz it is not possible with that)
Now you can better understand, why your title and solution was misleading. and I forced to ask to delete it.
Click to expand...
Click to collapse
Actually I have tried to delete the post but could not find option there to delete. I need to learn that to... So I have tried to edit but mean while I had to go so its still there but I will remove it as soon as possible and if I can not delete it I will just edit to correct matter.
I will follow your suggestions properly sir. Extremely sorry if I have created any misunderstanding in you.
I am away from town so very sorry for my late reply. Here internet is even not working...
Thanks a lot lot lot...
Sent from my GT-N7000 using xda premium
PierreTech said:
Very well said by sr ketan.... Getting the yellow triangle under boot logo and getting stuck there is a different thing.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks a lot sir... PierreTech...
You have been great part of help till now..
I will try to maintain rules and regulation here. Please guise me, whenever I find difficulty...:thumbup:
Sent from my GT-N7000 using xda premium
Not to worry
The way you wrote guide was just misguiding, Now you have edited it, so its OK.
However problem is solved. So Mods please close this thread
stuck to yellow triangle
bro. same prob in my phone.. i m trying to install cwm in my galaxy note n7000(indian) through odin. now my phone stuck to yellow triangle under samsung logo nothing is working.. how can fix...????
pls bro help.... sorry for bad english..

[Q] First stuck in a loop in Cyanogen then stupidly I bricked it.

Ok... I'm a NOOB I know, but I screwed up BIG TIME.
Here's my problem (also sorry if this is the wrong place)
I got my Samsung Galaxy S today and I wanted to root and upgrade from 2.3.6 to the most recent ICS that was stable with the phone.
I believe I rooted my phone correctly their was no problem there.
Went in Recovery
It was fine at the most part, cleared out the Cache and all that jazz.
Then Installed Cyanogen, That was fine also.
then... I cleared out the cache and etc again and installed the second file...
then this is where ALL the problems started...
So I installed the second file, then recovery automatically closed out and it seemed fine but it went into a boot loop, I'm not even sure if it can be considered a boot loop.
It continuously loops between the "Samsung Galaxy S i9000" Logo & "Samsung Galaxy S & Cyanogen [MOD]" logo...
I couldn't enter recovery...
Because I'm a fool, I took things into my own hands.
When into Download mode, used Odin and placed TAR file (I think it's called) into the PDA section and tried it.
It failed and it BRICKED!
So I have a double wammy!
Firstly I need help to get out of the Bricked state before I can do ANYTHING else
Then I have a choice.
I could...
Find away to get out the loop and Cyanogen working with whatever ICS it should be running
OR
Find away to take it back to 2.3.6 and never tamper with my phone and leave it to the professionals.
I would prefer going to Cyanogen over 2.3.6
I also believe "XXJW4" will be of help to you to narrow down the problem.
Your help with be EXTREMELY appreciated.
Thank you in advance.
Don't worry, you should've tried harder if you wanted to brick SGS.
My question is: can't you get in download mode?
You may try USB jig or the unbrickable mod. But I ain't able to answer any further due to my lack of accidents during flashing.
It's better for you to wait for some professional opinions.
Unbrickable mod - http://forum.xda-developers.com/showthread.php?t=1330491
belgarion98 said:
Don't worry, you should've tried harder if you wanted to brick SGS.
My question is: can't you get in download mode?
You may try USB jig or the unbrickable mod. But I ain't able to answer any further due to my lack of accidents during flashing.
It's better for you to wait for some professional opinions.
Unbrickable mod - http://forum.xda-developers.com/showthread.php?t=1330491
Click to expand...
Click to collapse
I can get into download mode without a problem, just not Recovery...
I've been looking around if their is a way to flash the recovery but can't see it for some reason :|
I looked at that bricking mod...
Wasn't worth it!
I found another by the same guy I believe and it worked like a charm So the bricking has been removed.
Never thought I would see the day I would actually Unbrick and bricked phone. I feel so special HAHA
Read this and somewhere in that thread there is a download link for "EZbase" download it and follow the instructions in the EZbase folder you downloaded to flash it up in Odin. However if you use Heimdall then I personally told others how I did it on the second page of the thread.
If you have any further questions just come back to this thread...
TheProfessionalIdiot said:
I can get into download mode without a problem, just not Recovery...
I've been looking around if their is a way to flash the recovery but can't see it for some reason :|
I looked at that bricking mod...
Wasn't worth it!
I found another by the same guy I believe and it worked like a charm So the bricking has been removed.
Never thought I would see the day I would actually Unbrick and bricked phone. I feel so special HAHA
Click to expand...
Click to collapse
when flashing ICS from GB 2.3.6 you need to flash twice. see MY Android solution link below , anyway I think your problem already solved, if not just flash a rescue kit to get back to GB 2.3.6 from MY Android collections link below
A truly wonderful resource xsenman, I have somewhere to turn people thank you.
I think I should update my problem.
I'm out of the Brick.
I've Flashed CWM recovery and I can get into recovery and Download, but it only stay on the first boot screen (where it mentions the name of the phone.
I wanted to load "CF-Root-XX_OXA_JW4-v4.4-CWM3RFS" from the recovery but the phone is not letting me saying "E:failed to mount /sdcard"
I Flashed dbdata.rfs.tar to solve it But it didn't work.
Maybe an after effect of the Brick?
so I am stuck here at the moment
Also want to say that I realised I did not properly root my phone so I think I have no choice to call it quits and just go back to 2.3.6.
but I don't have a complete or where to get a "recovery kit" you could call it of some sort which can take me back to 2.3.6 with TouchWiz
Oh wait never mind
I used your recovery
WORKED LIKE A CHARM!
MADE ME A HAPPY MAN AND I CAN GO TO SLEEP!
I wish I could pay you for your effort but I guess I can only say how much I can thank you!
Recovery wont work now, something is corrupt. I don't know exactly what it is... maybe the partitioning or something the ROM sets up is all corrupt. I'd like to know exactly what is wrong here as well tbh.
But you need to flash a recovery kit in Odin or Heimdall because I'm not 110% sure (I could be wrong) official stock ROM is the best way to go atm... I've extracted this link from my thread for you which is EZbase and in the folder you'd download there is instructions for use with Odin.
Hope this helps...
Oppps... didn't see that lmao, glad you fixed it!
in need of help
First off all i am noob when it comes to android but i somehow managed to install cyanogen mod. I have been using it for a while but today i dropped my phone and something happened now i cant start it. when i turn it on its stuck between cyanogen mod and gti 9000 sign. i think its in a loophole. by the way i cant reach recovery mode (vol+ home power). i can star download mode but nothing happens when i plug it to my computer.
I require assistance and tahnks to all further replies.

Help please with flashing Rom (potentially bricked?)

Hi,
I was running the JellyBam installer having rooted using a guide at cursed4eva, using cwm.zip. The only thing I'm unsure of is because the phone was owned before me, whether a custom kernel was installed (perhaps Franco as it was on the sd card)... I wiped everything using recovery mode, and ran cwm.zip, then followed the guide. Everything was going fine, until during the installer it asked if I want to update a kernel or keep the kernel thats already on, but not knowing what to do and not being able to find anything on the internet, I just left it at the default option and updated the kernel. It remained on 2% while uncompressing the image file, but when I looked my phone had turned off and was unresponsive. I was going from rooted stock 4.04. Both recovery mode and download mode aren't available...
Is it likely to be hard-bricked or softbricked, and what do you suggest doing? I haven't had it over a year, so under UK law I should still have warranty on it, right?
Please help!
Warm regards,
Lee
Sounds more like a superbrick.. It's wells known that cwm.zip adviced by cursed4eva in YouTube its dangerous and can trigger the emmc bug.. I don't know why that dude haven't remove that video so far..
Try removing the battery for some minutes and then turn on the device in odin mode (power +volume down +home) and flash a stock gingerbread with pc odin
Tapatalking on my n7000
msedek said:
Sounds more like a superbrick.. It's wells known that cwm.zip adviced by cursed4eva in YouTube its dangerous and can trigger the emmc bug.. I don't know why that dude haven't remove that video so far..
Try removing the battery for some minutes and then turn on the device in odin mode (power +volume down +home) and flash a stock gingerbread with pc odin
Tapatalking on my n7000
Click to expand...
Click to collapse
Thanks for your quick and helpful response. I'll try it in the next few hours, and let you know how it goes. Is the superbrick fix the thing which, if successful loses 3gb of space?
Once again, thanks for your help
angus_mcfisher said:
Thanks for your quick and helpful response. I'll try it in the next few hours, and let you know how it goes. Is the superbrick fix the thing which, if successful loses 3gb of space?
Once again, thanks for your help
Click to expand...
Click to collapse
Yes that's the one.
angus_mcfisher said:
Thanks for your quick and helpful response. I'll try it in the next few hours, and let you know how it goes. Is the superbrick fix the thing which, if successful loses 3gb of space?
Once again, thanks for your help
Click to expand...
Click to collapse
First what it's first.. Flash the stock gb.. If that doesn't work then following question would be do you have warranty?
Tapatalking on my n7000
msedek said:
First what it's first.. Flash the stock gb.. If that doesn't work then following question would be do you have warranty?
Tapatalking on my n7000
Click to expand...
Click to collapse
I haven't been able to access a PC tonight, but I'll try tomorrow. I don't suppose it's possible on a Mac is it? It is within my 1 year statutory rights, so that should be ok
Thanks for all your help guys!
If nothing happens when I've connected it to the PC with Odin open, and pressing Power+Vol Dwn+Home, does that mean its super bricked, or am I just doing something wrong?
angus_mcfisher said:
If nothing happens when I've connected it to the PC with Odin open, and pressing Power+Vol Dwn+Home, does that mean its super bricked, or am I just doing something wrong?
Click to expand...
Click to collapse
You need to put the device in odin mode (volume down + home + Power until a warning shows up) when the warning appear on the screen release everything and press volume up to confirm.. Once in odin mode you can plug the device to the pc.
But before that you need to install either kies or samsung drivers in your pc.. You can find samsung drivers in Dr ketans toolbox in general section.. Once done with this, connect the device and wait for Windows to setup the device..
Once donde you can open odin.. And a yellow block should turn on In the upper left corner..
Tapatalking on my n7000
msedek said:
You need to put the device in odin mode (volume down + home + Power until a warning shows up) when the warning appear on the screen release everything and press volume up to confirm.. Once in odin mode you can plug the device to the pc.
But before that you need to install either kies or samsung drivers in your pc.. You can find samsung drivers in Dr ketans toolbox in general section.. Once done with this, connect the device and wait for Windows to setup the device..
Once donde you can open odin.. And a yellow block should turn on In the upper left corner..
Tapatalking on my n7000
Click to expand...
Click to collapse
Thanks for your quick reply. I tried putting my device into Odin mode, but nothing appeared on the screen (and I held it for about a minute!). I've downloaded the Samsung Drivers, just to double check that it was already installed, and it was.
I can't get anything whatsoever on the screen. I don't even know if it's working at all... I can't get anything even though it's plugged into the mains. Any help would be greatly appreciated
First of all try to charge the battery externally using other phone or a ext charger. make sure there is juice on the battery and try to go to download mode again. battery might not get charged in that phone...
Once that done and still the phone is unresponsive .., no indication of screen display at all.like the N7000 logo (vol dwn+pwr+home) or (vol up+power+home), then it may be hard bricked and need a motherboard replacement .. I guess the samsung warranty is from the date of purchase as on the cash memo
Many thanks. I've had it plugged in and I can feel its warm so it must be charging. I've also tried a replacement battery to no avail. I guess it must be completely bricked. If Samsung only replace the motherboard then I'll try the retailer first, worth a try!
Many thanks for your help
Ok.. and let us know how it goes
nokiamodeln91 said:
Ok.. and let us know how it goes
Click to expand...
Click to collapse
Have to love Amazon! Even though I bought it last May, they're replacing it - no questions asked! Is there a guide on how to do this the best way possible on the new device? There's so much out of date information on the internet, including the guide I initially followed!
angus_mcfisher said:
Have to love Amazon! Even though I bought it last May, they're replacing it - no questions asked! Is there a guide on how to do this the best way possible on the new device? There's so much out of date information on the internet, including the guide I initially followed!
Click to expand...
Click to collapse
Dead its dead... Just return it and please do not ever wipe on ics stock kernels or use cwm.zip just read here or ask... Better ask than burning another device
Tapatalking on my n7000
Well lesson learned my friend and also for everyone else that reads this including myself. Happy to see you are getting it replaced l!
->] [ALLIANCE] [ICS] [FINAL] [<-
angus_mcfisher said:
Is it likely to be hard-bricked or softbricked, and what do you suggest doing? I haven't had it over a year, so under UK law I should still have warranty on it, right?
Please help!
Warm regards,
Lee
Click to expand...
Click to collapse
Hope this will help,
http://forum.xda-developers.com/showthread.php?t=1656635
amjiffy70 said:
Hope this will help,
http://forum.xda-developers.com/showthread.php?t=1656635
Click to expand...
Click to collapse
Hes already getting a replacement
Thanks guys. Yeah, I got a replacement today from Amazon. No questions asked! Just to clarify to install Jellybam, I can follow the steps on http://forum.xda-developers.com/showthread.php?t=1901191 to replace the kernel, and then going into Recovery Mode, flash the zip and then during the installer I don't want to replace the kernel? Right?
angus_mcfisher said:
Thanks guys. Yeah, I got a replacement today from Amazon. No questions asked! Just to clarify to install Jellybam, I can follow the steps on http://forum.xda-developers.com/showthread.php?t=1901191 to replace the kernel, and then going into Recovery Mode, flash the zip and then during the installer I don't want to replace the kernel? Right?
Click to expand...
Click to collapse
Philz kernel is only for stock samsung roms. If the new phone you go is on stock ICS rom, then install this kernel from stock recovery. This will give you root.
The boot into recovery and do all wipes ( factory reset and wipe cache partition dalvik cache)
then go to mounts & storage and do format /system, format/data, format/preload.
then go to Install Zip and install the rom
This rom wont work with Philz kernel. so you need to use the kernel included in the ROM or Hydracore V7.
nokiamodeln91 said:
Philz kernel is only for stock samsung roms. If the new phone you go is on stock ICS rom, then install this kernel from stock recovery. This will give you root.
The boot into recovery and do all wipes ( factory reset and wipe cache partition dalvik cache)
then go to mounts & storage and do format /system, format/data, format/preload.
then go to Install Zip and install the rom
This rom wont work with Philz kernel. so you need to use the kernel included in the ROM or Hydracore V7.
Click to expand...
Click to collapse
Ok thank you for your help! I'll start now and let you know how it goes. Is there anything in this process that I need to be careful to ensure I don't brick it (other than using cwm.zip!)?

Categories

Resources