Database Users

My Droid 2 Global got Stuck on M logo

This is my bad day . My Droid 2 Global got stuck on M logo when I tried to root and install the new ROM . I have tried alot of SBF from the Droid 2 but it's seem nothing fix my phone. So, anyone can help me with the new SBF for Droid 2 Global

Which SBF did you use? I'm not aware of one being released for the D2G and using the one for the D2 will certainly screw up your phone.

There isn't a SBF for the D2G yet. You should have waited for it before trying anything like this.

If the sbf did work after you sbf you need to:
1. Pull your Battery.
2. Replace battery and power on while holding down the X key.
3. Wait for the android triangle to load.
4. Press the Search key (the magnifying glass)
5. Use down arrow and navigate to wipe data/factory reset and press OK.
6. Reboot phone.
If that doesn't work than you might be SOL.
If you get the M logo and you have a backup. (always try and restore a backup before you SBF)
Pull your battery and place it back in after 5 seconds or so (we just want the phone completely off)
(while completely off) Plug your phone into the wall charger.
Then turn your phone on. If you get the charging screen press power again.
now you should be in clockwork recovery so you can do a restore if you made a backup.

I've used all the sbf that I searched in this forum but it wasn't work. I think there are a different SBF for Droid 2 Global.

hamabucon said:
I've used all the sbf that I searched in this forum but it wasn't work. I think there are a different SBF for Droid 2 Global.
Click to expand...
Click to collapse
I assumed so but I also assumed that if the boot loader hasn't changed one could /theoretically/ flash the 2.3.2 sbf and /possibly/ be okay. I wouldn't recommend any D2 G users to flash ROMs or anything until the SBF specifically for the D2 Global is released. I would suggest rooting and getting a backup made if the user want's to eventually flash ROMs.

newk8600 said:
I assumed so but I also assumed that if the boot loader hasn't changed one could /theoretically/ flash the 2.3.2 sbf and /possibly/ be okay. I wouldn't recommend any D2 G users to flash ROMs or anything until the SBF specifically for the D2 Global is released. I would suggest rooting and getting a backup made if the user want's to eventually flash ROMs.
Click to expand...
Click to collapse
I have tried to flash the 2.3.2 but everything seem wrong and I have the Critical error 0047

hamabucon said:
I have tried to flash the 2.3.2 but everything seem wrong and I have the Critical error 0047
Click to expand...
Click to collapse
Did you make a backup with koush's bootstrapped clockwork recovery? if so you should try and restore it. otherwise you might be out of luck until the sbf drops.

Maybe I'm out of Luck . But is there a chance to update the new ROM using the stock Recovery ? . I saw there are the option apply: update.zip

It will only work if you have the rom signed with moto's keys or it won't get through. That's why we use koush's bootstrapped clockwork. Because it doesn't have signature verification. Well it does but we can toggle it off.
Sent from my DROID2 using XDA App

Can you estimate when the SBF for D2 G release ?

newk8600 said:
If the sbf did work after you sbf you need to:
1. Pull your Battery.
2. Replace battery and power on while holding down the X key.
3. Wait for the android triangle to load.
4. Press the Search key (the magnifying glass)
5. Use down arrow and navigate to wipe data/factory reset and press OK.
6. Reboot phone.
If that doesn't work than you might be SOL.
If you get the M logo and you have a backup. (always try and restore a backup before you SBF)
Pull your battery and place it back in after 5 seconds or so (we just want the phone completely off)
(while completely off) Plug your phone into the wall charger.
Then turn your phone on. If you get the charging screen press power again.
now you should be in clockwork recovery so you can do a restore if you made a backup.
Click to expand...
Click to collapse
I have the same problem with the droid 2, except i mistakenly flashed with the droid 2 global without really thinking about it. I'm stuck at the M logo, and i've tried doing all of the above but i cannot get into clockwork recovery. Any suggestions? if I bricked my phone, how would i go about getting it fixed from verizon?

I remembered that i install the stock ROm deodexed for Droid 2 Global . But why my phone bricked ? Is that the problem from my phone?

dotmike said:
I cannot get into clockwork recovery. Any suggestions? if I bricked my phone, how would i go about getting it fixed from verizon?
Click to expand...
Click to collapse
You should sbf your droid 2 with the 2.3.2 sbf. Search in droid 2 android development section. There are two ways to flash it. One in windows the other in linux. I made a tool so people can use any computer to flash in linux. Search in the android development section for the droid 2 and it's there if you need it. I recommend reading and reading and reading then flash it. You'll be wiser and you'll know each step before you do it. It's not difficult and if you are going to flash ROMs you need to need to know how to sbf.
If your phone boots it's not bricked. And read every post here before trying to return it to verizon. If you have the desire to flash ROMs to your phone you can to the research to fix any mishaps. If after you read every post and you still have no idea or the methods applied haven't worked then you have my permission to take it back to verizon with the excuse that the update messed up your phone. Thanks and happy fixing!
Sent from my DROID2 using XDA App

I have just bought another Droid 2 Global , is that work if I have a nandroid backup from the new one and use for the bricked one ?

newk8600 said:
You should sbf your droid 2 with the 2.3.2 sbf. Search in droid 2 android development section. There are two ways to flash it. One in windows the other in linux. I made a tool so people can use any computer to flash in linux. Search in the android development section for the droid 2 and it's there if you need it. I recommend reading and reading and reading then flash it. You'll be wiser and you'll know each step before you do it. It's not difficult and if you are going to flash ROMs you need to need to know how to sbf.
If your phone boots it's not bricked. And read every post here before trying to return it to verizon. If you have the desire to flash ROMs to your phone you can to the research to fix any mishaps. If after you read every post and you still have no idea or the methods applied haven't worked then you have my permission to take it back to verizon with the excuse that the update messed up your phone. Thanks and happy fixing!
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
The phone is Droid 2 Global. There is no sbf available for D2G yet. More and more users are getting confused. Please vote in the thread for dedicated section for D2G @XDA!
Sent from my Milestone using Tapatalk

hamabucon said:
I have just bought another Droid 2 Global , is that work if I have a nandroid backup from the new one and use for the bricked one ?
Click to expand...
Click to collapse
You could try, but you need to get into cw recovery on the broken one first...
Sent from my Milestone using Tapatalk

leobg said:
The phone is Droid 2 Global. There is no sbf available for D2G yet. More and more users are getting confused. Please vote in the thread for dedicated section for D2G @XDA!
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
I was not commenting to hamabucon I was talking to dotmike who it seems has an Orginal Droid 2 (not global) and the advice is NOT for the Droid 2 Global. I'm sorry if it's confusing he posted in a thread about the D2 G and I was trying to help him where he posted his problem. I have not suggested that there is an Sbf for the D2 G. Sorry for the confusion but if we all read what each post relates to will help.
Sent from my DROID2 using XDA App

, Still wait for my little hopeness

leobg said:
The phone is Droid 2 Global. There is no sbf available for D2G yet. More and more users are getting confused. Please vote in the thread for dedicated section for D2G @XDA!
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
newk8600 said:
I was not commenting to hamabucon I was talking to dotmike who it seems has an Orginal Droid 2 (not global) and the advice is NOT for the Droid 2 Global. I'm sorry if it's confusing he posted in a thread about the D2 G and I was trying to help him where he posted his problem. I have not suggested that there is an Sbf for the D2 G. Sorry for the confusion but if we all read what each post relates to will help.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Yes, apologies for taking over a thread with my question, however to newk8600, I didn't know that holding the up key on the keyboard booted into the bootloader! I managed to sbf from there since RSDLite read the phone then.
Apologies for any confusion, and thank you again for the help.

[Q] Any i9000M Experts in Calgary AB ???

Howdy!
(sorry... guess Stampede is getting to me...)
I am looking for a Bell Vibrant (Samsung Galaxy S i9000M) expert in the Calgary AB area.
I have successfully rooted, installed custom ROMs and then "bricked" two (yes, 2) i9000M phones. Both times, I "bricked" when using ODIN.
Yes, I had researched how to use ODIN before using it... trading weeks of my "life" for the said pearls of ODIN wisodm . I've obviously missed something important, have very bad karma, or I am just an idiot...
After "ODINing", both phones ended-up looping at the SGS Logo. I have tried re-flashing via ODIN many times, always with the same result. I can get both phones into "download" mode (i.e. the yellow triangle screen).
Anyways, I am hoping to find a local expert who is willing to meet me somewhere (library???), look at my phones and confirm:
1. My SD cards have crashed; OR
2. I am a uber noob idiot;
I am also hoping that if #2 is proven the case whether the charitable expert individual might suggest a way and/or help me to fix these expensive plastic paper weights.
So, any charitable local experts willing to help-out an unlucky moron?
t.

What version are you flashing via odin?

you'll most likely have to take them in for warranty repair

@ BottleB:
I tried flashing JH2 (Stock Bell Vibrant ROM???) and 512.pit.
I had original installed CM 7.1 RC1 (via CM wiki method). Everything work awesome.
I decided to try some OC'ing, and flashed the Glitch v10 kernel... with spectacular speed results! Unfortunately, post Glitch flashing, SMS would receive but not send. Researched possible causes and cures for this, could not find any, and decided to revert to stock and try again...
... and here I am.
@graison:
I bought these i9000M's "used" off Kijiji (HATE contracts!). Both worked fine until ODINing.
As such, Bell won't "warranty" these devices (tried with the first one).
I have no problems paying for repairs... if the cost is reasonable. Any ideas/suggestions on the "how's and where's" I can go about trying this?

They most probably had lagfix installed which was not disabled when reflashed to stock. You need to flash the rfs...bin file (i'll upload it later tonight for faster accessing). I found the fix here on xda under a thread on bricked phone.
The lagfix change the filesystem used by the phone. Stock firmware is only compatible with the RFS filesystem. Also, i recommend that you flash KC1 instead oh JH2. Froyo is way better than eclair.
Sent from my GT-I9000M using Tapatalk

Found the fix
Here is the link http://forum.xda-developers.com/showthread.php?t=984140
Sent from my GT-I9000M using Tapatalk

urself25 said:
Found the fix
Here is the link http://forum.xda-developers.com/showthread.php?t=984140
Sent from my GT-I9000M using Tapatalk
Click to expand...
Click to collapse
+1
Pretty sure thats the problem. You flashed stock kernel on a EXT4'ed filesystem.

@urself25,
Ah-ha... I have a feeling that you are right, and that I did miss something CRAP!
I await your upload on bated breath... in the mean time, I will search the million posts for the fix you mentioned.

ooops... you beat me to my response.

Tell us how it went when you'll try the RFS fix.

Tried the RFS fix as per the instructions in the link.
After rebooting, both phones go into a SGS start-up screen loop.
Downloading ODIN files right now (JVE - Gingerbread???). I will try and reflash and let you know how it goes.

I'm in Airdrie, don't flash gingerbread! Sell me both phones for $100. Or search for the "trick to unbricking my sgs" thread. It worked for me. Though I am worried that because they were on Eclair firmware, they may be dead if they never got the bootloader update. I repeat, DO NOT FLASH GINGERBREAD!
Sent from my GT-I9000 using XDA Premium App

try a deodexed KC1 (current firmware for Bell Canada) firmware from [Ramad]
Using ODIN -- use a 512.pit file, re-partition ticked, Bootloader Update (just in case), and put PDA -> PDA, PHONE -> PHONE, etc.
http://forum.xda-developers.com/showthread.php?t=948790
IF it takes you to android recovery 2e or 3e (i cant remember), do a factory reset/cache wipe, and even format sd if you want. it SHOULD work (i just did this too and it worked mint.

Holy crap! It's near 4:30 a.m., and I FINALLY restored/recovered my two phones! Truth be told, I spent half the night screwing up my phones WAY worse than they were ... and the second half of the night cleaning up my mess
@urself25 & @BottleB - I can't say definitively whether or not your link really helped me any... but it definitely put me on the right path. Thanks a lot boys!
@xWarMachine04 - Thanks for the directions and link! I *kinda* went that route in a round-about-way... I just wished I would have check my post and found your reply 4 hours ago! Regardless, my gratitude.
@hansonator - Thanks but no thanks; for $100, I'd use my bricked phones as door stops. REGARDLESS, I do thank you for your gingerbread warning. I did have problems with gingerbread, and (successfully) shifted to froyo on your recommendation. Thanks dude!
All's well that ends well...
- t.

Most probably the firmware didn't install properly because fo the problem RFS problem. A fresh reinstall of the firmware with bootlader finally fix the problem. Glad everything worked out for you.

I'm in Calgary. But I'm hardly an expert. I think you've gotten further than I have.
So I have nothing to contribute to this thread. I'll see my way out.

Glad u got your phones up and running! Good thing is you probably learned a lot during that night!
Sent from my GT-I9000 using XDA Premium App

BottleB said:
Glad u got your phones up and running! Good thing is you probably learned a lot during that night!
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
~~~~~~
Learned a lot? No kidding...
Why is it that the biggest/best lessons always have to be soooo painful???
I must admit that my opinion of ODIN has sure changed; it's a pretty slick piece of software when it works right (i.e. when you have half a clue about what you are doing)!
@urself25 - It wasn't so much a firmware installation problem, as much as the SD card file format (like you suggested in the first place). I kept getting a message along the lines of "can't mount sd; storage not ready... blah blah blah... file format blah blah blah...". I did have to do a complete reinstall (PDA, Phone/Modem, CSC) WITH repartition... and on the second phone, a Bootloader update. Didn't do the repartition in the first place because 95% of the threads out there advise against it. Anyways, my solution was pretty much @xWarMachine04's approach/solution.
Unfortunately, I have developed the "randomly self-invoking" back button problem on the second phone. Fortunately, there seems to be an easy fix for that... but that's what I thought at the beginning of this journey!
Again, thanks everyone!
- t.

Now if you want to flash gingerbread it should be OK. I only advised against it because the phones were bricked. Good to hear you got it sorted out.
Sent from my GT-I9000 using XDA Premium App

davanw said:
I'm in Calgary. But I'm hardly an expert. I think you've gotten further than I have.
So I have nothing to contribute to this thread. I'll see my way out.
Click to expand...
Click to collapse
i'm in Calgary too, but i am no expert either... however i have been able to upgrade my phone from froyo (after taking my i9000m to market mall due to the internal card dying back in December), to gingerbread.
First went with Darky's 9.5... then upgraded to 10 and had NO issues with GB. I'm on GB still using the F1 Rom V9 now and love this.
For the OP: Glad to see you were able to fix both of your phones! Congrats... definitely no easy feat!

There you go, the leaked signed Chinese GB Rom

Disclaimer: I won't be responsible for any damage done to your phone due to flashing this rom.
I have just returned home after a day of tiring work. Grabbed this stuff from the Chinese forum and uploaded it to mediafire (It took quite a while as I am using ADSL) .Phone is charging and I'll try to flash right after it's fully charged. Screenshots are all around that forum though so I guess it would be safe to give it a shot. Enjoy, guys!
Note:
1. It is said to have quite a number of bugs.
2. Can't access recovery mode. Edit: it is possible but the key combination changed. You press "vol up+vol down" INSTEAD OF "@" after getting the yellow exclamation sign.
3. Old drill, no Google stuffs pre-installed.
4. Downgradeable to Froyo.
http://www.mediafire.com/?7bwfc0qvqs428k3
Edit:
I flashed and it boots.
1. Multitouch bug gone and the screen is way more responsive.
2. Yeah 2.3 old TV lock screen animation.
3. New window transition animation.
4. Attempted to root with SuperOneClick 1.7... failed.
5. Seems getting no luck with Gingrebreak neither...
6. I'm going back to uk 2.2.2 since without Google Services I can't live LOL... good luck guys
7. Successfully go back to froyo (damn i miss the red moto logo). Have fun with GB guys

Thanks a lot!!
Downloading now. But speed slow today on my internet. Will let u know if it works.

Flashing it right now, wish me luck

looking forward to your progress

It boots!! It boots!!!

yay!!!!!!!!!

Multitouch bug gone and the screen becomes way more responsive

can you root it?

Liori said:
Multitouch bug gone and the screen becomes way more responsive
Click to expand...
Click to collapse
Any bug that u have noticed? Everything works fine? Wifi, gps, data, sensors, etc. Im downloading right now XD

Hi Liori
one question... this sbf is downgradeable to froyo???

How about UI, fresh UI Motoblur?
Sent from 2nd age of the Milestone

rodrigocor said:
Hi Liori
one question... this sbf is downgradeable to froyo???
Click to expand...
Click to collapse
I am still playing around.. but folks in gfan (where it first leaked) say it is downgradable.

diditnya said:
How about UI, fresh UI Motoblur?
Sent from 2nd age of the Milestone
Click to expand...
Click to collapse
brand new.

rodrigocor said:
Hi Liori
one question... this sbf is downgradeable to froyo???
Click to expand...
Click to collapse
Wondering about that one too. I guess it should be possible. Can't wait to try it out. Let's hope I can sideload the Google Apps At least Gmail and Google Talk that is

Liori said:
Multitouch bug gone and the screen becomes way more responsive
Click to expand...
Click to collapse
good to hear this
just some questions,
do I need to wipe data before/after flashing the sbf? or everything works fine without a wipe? since you mentioned this ROM cannot be rooted (maybe yet xd), so it would be unable to use titanium backup to restore my apps
and could this be downgradable to 2.2.2 if i flashed the old sbf again? =]
thanks =D

WongJames said:
good to hear this
just some questions,
do I need to wipe data before/after flashing the sbf? or everything works fine without a wipe? since you mentioned this ROM cannot be rooted (maybe yet xd), so it would be unable to use titanium backup to restore my apps
and could this be downgradable to 2.2.2 if i flashed the old sbf again? =]
thanks =D
Click to expand...
Click to collapse
well i came from uk 2.2.2 rooted without wipe, and it works without major problems. right now i'm trying to root with gingerbreak, if i still got no luck then i think i would go back 2.2.2 (painful decision as this leaked GB is so great) since without google service i cant get my contacts, schedules back.

DON'T FLASH IT YET!
You may get stuck in a non-rootable/non-downgradable rom
I will wait for the fixed SBF + nandroid backup.
Sent from my Milestone 2 XDA App

Anybody could write a "how-to upgrade to 2.3" ?
Does this chinese GB leak supports accents in messages ?

Is it non-downgradeable? That kinda uhm... sucks... as I already started the flashing. Let's just wish for the best.

dangpzanco said:
DON'T FLASH IT YET!
You may get stuck in a non-rootable/non-downgradable rom
I will wait for the fixed SBF + nandroid backup.
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
I am going to downgrade to UK 2.2.2 and it is said to be feasible according to gfan forum users. But before that I am going to take some nice pics for you guys.

[Q] Running roms from the sd card?

Thanks for your time and help. I have tried to research this before posting.
the problem:
My girlfriend's HTC Glacier has the bad emmc chip. It started with the random restarts earlier this week. It has been getting more and more sluggish over time. On the way home today, it lost all network connectivity, even after a restart, then pulling battery, sim, and sd, replacing then restarting.
What has been done to the phone so far:
It was unstable several months ago at which time I permarooted it, unlocked it, and flashed the rooted gingerbread update from the permaroot post here on xda. ( we didn't try to rdma it because it was an ebay purchase and already past manufacturer warranty) I did not flash the engineering bootloader (wish I had and that will probably be one of my first steps now). It has cwm flashed and a backup of the rom. It is turned off now while deciding how to proceed. Other than that, It has had no custom roms flashed or anything else of the sort.
What I am hoping is possible:
I have a Samsung 16GB class 10 (rated up to 23 MB/s read and 21 MB/s write). I am wondering if it is possible to create a bootable sd and run cm7 (for example) like the nook color.
Is this possible? Would it require a custom kernel to bypass the emmc and use the sd card as the rom instead?
Any help or suggestions are greatly appreciated. I am hoping to help my girlfriend nurse this phone to the end of her contract. Is it worth the effort or is it a lost cause?

if you can still boot into the android system... go to market and find Bootmanager.. it's $2.99 but wayy worth it.
but also, read my guide here:
http://forum.xda-developers.com/showthread.php?t=1394238
hope it helps.

Boot manager by init2winit apps on the market
Sent from my HTC Glacier using xda premium

Thanks, that is one of the threads that I hadn't gotten to yet, but was already open in a tab. I will post an update. I am curious about the possibility of running roms from the sd card.

driftinganomaly said:
Thanks, that is one of the threads that I hadn't gotten to yet, but was already open in a tab. I will post an update. I am curious about the possibility of running roms from the sd card.
Click to expand...
Click to collapse
I can run 5 from my SD
Sent from my HTC Glacier using xda premium

Do you think that multibooting would be a workaround for the failing emmc? I will be trying it out.
I am going to follow saranhai's guide and try to stabilize the phone as much as possible first.
I had read that flashing the engineering bootloader is important, would you say that that should be my priority?

driftinganomaly said:
Do you think that multibooting would be a workaround for the failing emmc? I will be trying it out.
I am going to follow saranhai's guide and try to stabilize the phone as much as possible first.
I had read that flashing the engineering bootloader is important, would you say that that should be my priority?
Click to expand...
Click to collapse
i don't think any software related thing can be a workaround for the failed eMMC chip...
once the chip is dead, it's dead. you can't write anything to it. you can't flash ROMs, you can't wipe anything, you can't even boot the device up. if the bootloader is showing Fail-PU when you're trying to restore back, then sorry friend, but it's gone...
as we see it now, nothing besides replacing the hardware itself will fix it.
yes, having the Engineering bootloader is a definite must, that's how you flash radios and such.

As an update, amidst nonstop FC's, I got the engineering bootloader pushed to the phone and installed.
I wiped the cache and dalvic then restored to a cwm recovery. It seems stable so far, but only time will tell.
As soon as I get a chance, I will be installing boot manager and setting it up to boot from the sd. I am glad to get the phone somewhat stable before trying though. I hope that it will take the strain off the emmc and let us keep it going through the end of contract.
Thank you for your help!
Sent from my SCH-R720 using Tapatalk

Okay, for an awesome solution to the problem: his and hers Samsung Galaxy SII Epic 4G Touches!!
Woot!!!
Sent from my SPH-D710 using Tapatalk

driftinganomaly said:
Okay, for an awesome solution to the problem: his and hers Samsung Galaxy SII Epic 4G Touches!!
Woot!!!
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Haha well there ya go! You could send me your old mytouch if ya don't need it anymore
Sent from my HTC Glacier using xda premium

[Poll] I have bricked my Note while..

[Poll] I have bricked my Note while..
Here is thread to boost up confidence of newbie, many new to android asking chances of bricking of note.
I think you brick it, if you don't follow guide properly
Last option for all, whether you have bricked it or Not
Let's watch, what poll says !

I never bricked mine, largely thanks to your guides.

Thanx for compliments
Sent from my GT-N7000 using xda premium

Just make sure you have a jig handy (~£7 off amazon)
Sent from my GT-I9100 using xda premium

How do i identify whether a phone is bricked? I've got into a lot of **** spots, but gotten out of them. If i brick my phone does it mean i can never use it again?

bharat4ever said:
How do i identify whether a phone is bricked? I've got into a lot of **** spots, but gotten out of them. If i brick my phone does it mean i can never use it again?
Click to expand...
Click to collapse
brick - mean it will not boot up

Softbrick means recoverable
Hardbrick means dead

brick? never. not following instructions. yes im guilty.

dr.ketan said:
Softbrick means recoverable
Hardbrick means dead
Click to expand...
Click to collapse
Is it even possible to hardbrick via Odin?
Sent from my GT-I9100 using xda premium

I think,Wrong pit n wrong rom(different device) can lead to it

bharat4ever said:
How do i identify whether a phone is bricked? I've got into a lot of **** spots, but gotten out of them. If i brick my phone does it mean i can never use it again?
Click to expand...
Click to collapse
a proper bricked phone will not turn on or do anything

otester said:
Is it even possible to hardbrick via Odin?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Hmmm yeah!! There is this Kernel, no matter how you flash it, there is something inherent that would corrupt the flash drive, a rare instance where you have Download mode and recovery working but you cannot do a thing to restore your phone. Things happen, you know?

Only time mine has ever soft bricked has been on those few occasions when I have tried ICS and then tried returning to GB. There is always a way to get through a problem I think. Although I understand that there was a hard bricking episode recently with ICS on the note.
Luckily I was busy when that happened otherwise I'd have bricked mine.... No doubt
Sent from my GT-N7000

Oh yes, I soft brick my Note alright.. just yesterday... while I tried to flash to CheckRom RevoHD v6.... (had a v5 already installed)....
It would just stuck on the Samsung Galaxy Note N7000 Logo....
Restored it back using PC Odin
Personally, I don't think it has something to do on not reading properly the instruction on flashing.... I read it to a tee mind you.. yet the instructions presented have some gaps and loopholes that if the user isn't aware of it... most likely it would end up bricking their note as well...
Anyway, as the famous lines say 'That which can't kill you, makes you stronger...', I will continue flashing to whatever Custom Rom I want and I welcome the challenge of encountering the famous 'Bricking' again...
let's get it on!

@prem1
I think your poll option better fit in this option
It was issue with specific ROM n Kernel
isn't?

chasmodo said:
I never bricked mine, largely thanks to your guides.
Click to expand...
Click to collapse
+1. followed dr.ketan after reading it a thousand times. I am fortunate and cautious enough to stay away from ICS at the moment because I heard switching back to gingerbread is behind my skills.
Sent from my GT-N7000 using Tapatalk

Only time I bricked my phone was while deodexing. 'CP' command was not working, then I did not know about 'BUSYBOX CP' command. So I copied and pasted all deodexed apps and framework files using Root Explorer and dang! It was bricked =)).
If every newbie follows DrKetan's guide carefully there're 0% chances of ending up with bricked phone.
Trust the guide - make your mind.

Yesterday i think i soft bricked my Note. I tried to put pre rooted LC1 via *Odin 1.85 but it went wrong. Was stuck in factoryfs part. I pulled it off the cable.
It did only boot to recovery screen or download mode, so i just downloaded the stock rom LC1 and got it back online!

It is almost impossible to brick the Note. Unless you do it on purpose

offenberg said:
It is almost impossible to brick the Note. Unless you do it on purpose
Click to expand...
Click to collapse
I don't know if the emmc/mainboard got fried recently by flash/using the monster kernel/touch cwm whatever belongs to a brick, if it is, it's not impossible to brick the note, even you are an experienced user. Anyway, there's a risk on flashing, so be 100% careful.
Sent from the forgotten Atrix"2