I had a big problem since last night. My only hope is you XDA Geeks
the problem is about crashed galaxy note and not flashing a rom via ODIN.
Please read the story below I went through.
I rooted it by using CMW, and made a back-up via CMW so that I can use it in case of any disaster.
After having successful rooting on my phone, I deleted some factory applications such as social hub. Then, TwLauncher did not work
Because of having the "back-up", I restored the phone by using CMW.
However, after restoration finished and it restarted, the screen stopped on here: "SAMSUNG GALAXY NOTE - N7000"
After that screen, I tried to start boot-up screen by pressing Volume-up+Power+main_button. However, it didn't worked.
Because of that, I started the "downloading screen" by pressing Volume-Down+Power+main_button so that I can flash by ODIN. But Odin could not flashed.
Although I tried every option on the ODIN and stock roms, ODIN did not allow me to flash a rom.
The flashing process stops on downloading screen. You can see the last two picture on below.
And you can see existing situation on my phone with the pictures below
I am not sure if it is bricked. What I want to do is only flashing a stock rom.
Please help me to solve it. Thanks for all.
p.s I have also two gingerbread and one ics stock roms.
N7000XXLQ2_N7000XXLPT_N7000XEULP4_HOME.tar
N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.tar.md5
CODE_N7000XXLC1_CL1003701_REV02_user_low_ship.tar.md5
So it is hanging up at the factoryfs.img and not going on past it??
That's not a good sign. That probably means it damaged the emmc.
What ROM were you on when you did a restore in CWM??
Yes, exactly it is hanging up at factoryfs.img
I hope not damaged.
I was latest ICS stock rom. I do not remember codes.
Thanks
andreww88 said:
So it is hanging up at the factoryfs.img and not going on past it??
That's not a good sign. That probably means it damaged the emmc.
What ROM were you on when you did a restore in CWM??
Click to expand...
Click to collapse
bexreim said:
Yes, exactly it is hanging up at factoryfs.img
I hope not damaged.
I was latest ICS stock rom. I do not remember codes.
Thanks
Click to expand...
Click to collapse
That's your problem then. You did a restore in CWM in stock ICS. There are threads about this. You should have flashed AbyssKernel, rebooted recovery, and then restored the backup.
You are bricked. The restore in CWM activates the MMC_Cap_Erase command just like wiping and it looks like it did it to yours. There is a thread on here that MIGHT fix your phone by redoing the partition but it probably won't run great.
Your best bet is to get it to a samsung service center and get the motherboard replaced. Do you have a warranty? Is there a yellow triangle on the main boot screen? I'm sorry....
andreww88 said:
That's your problem then. You did a restore in CWM in stock ICS. There are threads about this. You should have flashed AbyssKernel, rebooted recovery, and then restored the backup.
You are bricked. The restore in CWM activates the MMC_Cap_Erase command just like wiping and it looks like it did it to yours. There is a thread on here that MIGHT fix your phone by redoing the partition but it probably won't run great.
Your best bet is to get it to a samsung service center and get the motherboard replaced. Do you have a warranty? Is there a yellow triangle on the main boot screen? I'm sorry....
Click to expand...
Click to collapse
OMG!
Yes, I have a warranty and there is no yellow triangle because in the beginning this screen shows up on the picture.
bexreim said:
OMG!
Yes, I have a warranty and there is no yellow triangle because in the beginning this screen shows up on the picture.
Click to expand...
Click to collapse
If you can, take it to a service center and I wish you the best. It says connect to Kies. Have you tried that?
andreww88 said:
If you can, take it to a service center and I wish you the best. It says connect to Kies. Have you tried that?
Click to expand...
Click to collapse
I hope the warranty still valid because of rooting. What do you think?
When I try Kies, there seems no movement on phone screen and kies shows the following screen and no process.
Mate i say use this link to recover ur mobile http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12 but ul lose some memory due to bad sectors.... for that u use triangle away first to remove the yellow triangle then flash a stock gb and then take it to samaung service....
I think this is the best bet to get ur mobo replaced without any hassle
bexreim said:
I hope the warranty still valid because of rooting. What do you think?
When I try Kies, there seems no movement on phone screen and kies shows the following screen and no process.
Click to expand...
Click to collapse
That screen doesn't look promising if it is just sitting there. But, if you can ONLY get to that one screen when you turn it on then w/o them digging deep they really can't tell if it is rooted or not that I am aware of. Just take it there and find out.
bexreim said:
OMG!
Yes, I have a warranty and there is no yellow triangle because in the beginning this screen shows up on the picture.
Click to expand...
Click to collapse
I don't know wat about ur place but here in VN the warranty is voided once the device is rooted.
andreww88 said:
But, if you can ONLY get to that one screen when you turn it on then w/o them digging deep they really can't tell if it is rooted or not that I am aware of. Just take it there and find out.
Click to expand...
Click to collapse
His download mode screenshot says
CUSTOM BINARY DOWNLOAD: YES (1 counts)
They don't have to dig very deep to see that.
chasmodo said:
His download mode screenshot says
CUSTOM BINARY DOWNLOAD: YES (1 counts)
They don't have to dig very deep to see that.
Click to expand...
Click to collapse
Hey, I am currently in this same situation but I was able to reset the binary download count to show CUSTOM BINARY DOWNLOAD: NO and CURRENT BINARY: SAMSUNG OFFICIAL
But rest of the things are still same. On start I still get the message that says "Firmware upgrade has encountered an issue. Please try recovery mode in Kies and try again". So is this fine enough to get warranty?
sudarshanpbhat said:
Hey, I am currently in this same situation but I was able to reset the binary download count to show CUSTOM BINARY DOWNLOAD: NO and CURRENT BINARY: SAMSUNG OFFICIAL
But rest of the things are still same. On start I still get the message that says "Firmware upgrade has encountered an issue. Please try recovery mode in Kies and try again". So is this fine enough to get warranty?
Click to expand...
Click to collapse
Yes, It is enough because I had the same message and called the customer service. They send me free shipping package. So, changed the main board or a chip inside. Returned back. That was ok. Dont woryy
reset flash counter
if CUSTOM BINARY DOWNLOAD: YES (1 counts) then
try to reset flash counter to reclaim warranty
http://forum.xda-developers.com/showthread.php?t=1354888
its better to use the triangle away app
nokiamodeln91 said:
its better to use the triangle away app
Click to expand...
Click to collapse
But it needs device to boot up normally :crying:
Related
I was on Stunner ICS Rom and then decided to try out CM9 so i did the following
1.backed up everything using CWM Backup
2.Copied the main cwm rom and google apps zips onto internal zip card
3.Booted into recovery using CWN menu option.
4.Navigated to install zip from internal sd card and selected the zip
5.Then nothing. no progress bar,no movement etc.
6.Waited for about 10mins, still nothing.
7.Powered off the phone and removed battery.
8.PHONE WONT POWER ON AT ALL.
Anyone had a similar issue and is it resolvable?
Thanks.
I think not!, Sorry, mate - it looks like you've bricked your phone.
Haven't you read this in CyanogenMod 9 Discussion Thread:
- I STRONGLY RECOMMEND TO FLASH FROM A CF-ROOTED STOCK GINGERBREAD ROM, JUST TO AVOID YOU HARD BRICKS.
and
- DON'T flash FROM i9220 LEAKED REPACK!
all found here!!!
Well is wrong way because you miss return to gingerbread before flash cm9 first.
Overall,try to flash rooted gingerbread indownload mode with pc odin bro
Good luck
xovox said:
Overall,try to flash rooted gingerbread indownload mode with pc odin bro
Click to expand...
Click to collapse
No harm in trying, but I think it's too late for that now.
Motherboard replacement is in order, I fear....
Can you get into download mode? I had a similar problem and fixed it by getting into download mode, connecting to pc, then run Odin and load CF-Root-SGN_XX_SER_LA6-v5.0-CWM5.tar, this reloaded my CWM recovery and then wipe cache etc and install anything. But by using Odin you will be stuck with that yellow triangle
As you said it would not turn on try the following.
Remove the batteyr for about 1hr or so when plug it back in and try to go directly yo downalod mode.
If you can flash a GB Rom and you "should" be OK. If you still can't start it you most likely need to send it in to replace the motherboard.
if its still on warranty, tell them this happened because of kies update fail.
sometimes, its inevitable to lie...
kuriandungu said:
I was on Stunner ICS Rom and then decided to try out CM9 so i did the following
1.backed up everything using CWM Backup
2.Copied the main cwm rom and google apps zips onto internal zip card
3.Booted into recovery using CWN menu option.
4.Navigated to install zip from internal sd card and selected the zip
5.Then nothing. no progress bar,no movement etc.
6.Waited for about 10mins, still nothing.
7.Powered off the phone and removed battery.
8.PHONE WONT POWER ON AT ALL.
Anyone had a similar issue and is it resolvable?
Thanks.
Click to expand...
Click to collapse
try a usb jig... if it is able to force ur mobile into download mode use pc odin to flash a gb rom... otherwise the only alternative is motherboard replacement
Thank you guys for your Responses. i appreciate them.
I returned the phone to Samsung Repair office and they said it looked repairable. (fingers crossed). They'll get back to me in a couple of days.
[user_99] said:
I think not!, Sorry, mate - it looks like you've bricked your phone.
Haven't you read this in CyanogenMod 9 Discussion Thread:
- I STRONGLY RECOMMEND TO FLASH FROM A CF-ROOTED STOCK GINGERBREAD ROM, JUST TO AVOID YOU HARD BRICKS.
and
- DON'T flash FROM i9220 LEAKED REPACK!
all found here!!!
Click to expand...
Click to collapse
No i didnt read that! i got instructions from theandroidsoul.com page called cm9-galaxy-note Which doesnt talk about coming from a Gingerbread rom etc. I should have come straight to XDA and i'm paying the price!
Hope the samsung repair shop can restore it. One representative said they have quite a number of such cases but somehow they get the phone to work again. So i'm hoping mine will work out.
musashiro said:
if its still on warranty, tell them this happened because of kies update fail.
sometimes, its inevitable to lie...
Click to expand...
Click to collapse
i told them it failed during an update....didnt say which update (economy with truth
belveder69 said:
Can you get into download mode? I had a similar problem and fixed it by getting into download mode, connecting to pc, then run Odin and load CF-Root-SGN_XX_SER_LA6-v5.0-CWM5.tar, this reloaded my CWM recovery and then wipe cache etc and install anything. But by using Odin you will be stuck with that yellow triangle
Click to expand...
Click to collapse
Thanks for the reply. Already took it to Samsung.
Really Bricked note
Just got news from Samsung local repair office that its beyond repair. Hard to believe that the software is so deeply intwined with the hardware that a software process can kill the phone.
Will try get the usb jig and see if it will work.
Thanks to everyone who had a suggestion or comment.
I swear I did the same a few weeks ago and flashed a N7000 STOCK Rom PC Odin and I was ok.
Really Bricked note - had to get new motherboard
Guys...read this before attempting to flash ... I had to buy a new motherboard after trying to flash CM9 on Stunner Rom.
http://forum.xda-developers.com/showthread.php?t=1633943
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
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
Hi,
Tried to install Kingdroid 1.5 yesterday. since than I'm trying to fix my note with no success.
This is what I tried to do:
http://forum.xda-developers.com/showthread.php?t=1652831
I failed to do the following step:
-We went into recovery and install this kernel without leaving the recovery going to advanced and reboot in recovery
And the rom was not installed successfully.
because of panic, tried to restore my device to stock ICS from a previous backup - failed.
Tried another backup of GB - Failed.
Tried ODIN for Stock ICS and succeeded.
After success on this, tried restoring again to my previous backup, and since than I'm stuck on " factoryfs.img"
Tried Abd, but my device was not recognized on 3 Win machines and 1 linux box.
I have download mode available, and also recovery mode.
Currently, I'm bricked, thinking to take it to the shop I bought it at...
Any other Ideas?
Thanks a lot!
asafki said:
Hi,
Tried to install Kingdroid 1.5 yesterday. since than I'm trying to fix my note with no success.
This is what I tried to do:
http://forum.xda-developers.com/showthread.php?t=1652831
I failed to do the following step:
-We went into recovery and install this kernel without leaving the recovery going to advanced and reboot in recovery
And the rom was not installed successfully.
because of panic, tried to restore my device to stock ICS from a previous backup - failed.
Tried another backup of GB - Failed.
Tried ODIN for Stock ICS and succeeded.
After success on this, tried restoring again to my previous backup, and since than I'm stuck on " factoryfs.img"
Tried Abd, but my device was not recognized on 3 Win machines and 1 linux box.
I have download mode available, and also recovery mode.
Currently, I'm bricked, thinking to take it to the shop I bought it at...
Any other Ideas?
Thanks a lot!
Click to expand...
Click to collapse
If you have download mode available, then you're not bricked, only soft-bricked perhaps.
Try flashing again with Odin...
From my knowledge, superbricks occur when wiping on an unsafe ICS kernel, such as old i9220 leak repack, LPY...
eug3n91 said:
If you have download mode available, then you're not bricked, only soft-bricked perhaps.
Try flashing again with Odin...
From my knowledge, superbricks occur when wiping on an unsafe ICS kernel, such as old i9220 leak repack, LPY...
Click to expand...
Click to collapse
in fact all ics kernel will have chances of superbricks, since he trying to restore....which wipe data will take place... that is superbrick i think
whitepandaaa said:
in fact all ics kernel will have chances of superbricks, since he trying to restore....which wipe data will take place... that is superbrick i think
Click to expand...
Click to collapse
CM9 kernels, based on i9100 update 4 are safe. That makes official Cyanogen Mod 9 Nightlies and ROMs like Asylum and ParanoidAndroid safe
From his post I got that he was able to flash official ICS with Odin once, meaning it didn't get stuck at factory.fs...so...might be still hope
From what I get, we should add another one to the long list of hard bricks.
Sent from my GT-N7000 using XDA
If you are stuck on NAND write, factoryfs.img you are super bricked. Sorry......
I'm guessing you tried restoring your backup in CWM??
My Galaxy note is stuck on black screen no response from buttons just black screen.
This was after I did a wipe data and installed CM9 rom.
What options do I have, will one of these jtag dongles help me?
I just saw some ebay sellers offering an unbrick service for about £21 (im in the uk) where you post it to them to fix.
Any help appreciated
aquanuke said:
My Galaxy note is stuck on black screen no response from buttons just black screen.
This was after I did a wipe data and installed CM9 rom.
What options do I have, will one of these jtag dongles help me?
I just saw some ebay sellers offering an unbrick service for about £21 (im in the uk) where you post it to them to fix.
Any help appreciated
Click to expand...
Click to collapse
I think you have SOD.Its a known issue with cm9 to have SOD's.Sorry to ask this silly question,did you try to pull out the battery and boot he phone???
What is SOD ?
Yes pulled the battery, but cant get anything from phone. Even if I put it on charge nothing.. just a black screen
aquanuke said:
What is SOD ?
Yes pulled the battery, but cant get anything from phone. Even if I put it on charge nothing.. just a black screen
Click to expand...
Click to collapse
SOD is screen of death.Its nothing but when deep sleep the phone doesnt wake up again and needs to be restarted.
try to put the phone in download mode though the screen is not seen and connect it to odin and see if it gets detected.
Tried to put it in download not mode but buttons are not responding, nothing when I connect to pc either
aquanuke said:
This was after I did a wipe data and installed CM9 rom.
Click to expand...
Click to collapse
What Rom were you on prior to flashing CM9?
chasmodo said:
What Rom were you on prior to flashing CM9?
Click to expand...
Click to collapse
KingDroid_ICS_NoteMania_Edition_v1.6
aquanuke said:
KingDroid_ICS_NoteMania_Edition_v1.6
Click to expand...
Click to collapse
Ah that means you didnt read the guide correctly.It clearly states that you need to be in proper gb with cf-root kernel.
aquanuke said:
KingDroid_ICS_NoteMania_Edition_v1.6
Click to expand...
Click to collapse
You are Superbricked. Get your phone to a Samsung Service cetre for the motherboard replacement.
JTag is not an option here, it won't work.
ooopppsss ok thanks.
I even tried re-partitioning using Odin and PIT file. seems that it is always stuck on the same spot.
Fixed!!!
I used this: http://forum.xda-developers.com/showthread.php?t=1682444
Nice asafki shame I can't try that as o2 gave me a brand new note :good:
asafki said:
Fixed!!!
I used this: http://forum.xda-developers.com/showthread.php?t=1682444
Click to expand...
Click to collapse
check how much data space you lost.
Sent from my GT-P1010 using XDA
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!)?