Database Develop

Boot Loop - Tab dead?!?!?

Tab is running CWM Recovery and Gingerbread Overcome Rom beta 1. Has been running fine for 3/4 days. Yesterday the tab froze and rebooted twice. Tab was left on last night while on charge. This morning when I unplugged the tab it was off, so I switched it on but it is stuck in aboot loop. The Galaxy Tab Samsung screen displays but then just reboots.
I can get in Recovery and have performed a data wipe and cache wipe, made no difference.
I made a CW backup on Tuesday and checked afetr that it was on the sdcard, it was. However if I now try and do a restore from CW it claims there is no backup...
Is my tab dead? Is my internal memory dead?
I'm comlpetely lost now....

Can you get to the flash zip option in recovery? If you can try to reflash the ROM from the SD card. Have to tried starting over using Odin? Hope this helps. Good luck.

I can get to the flash zip but they are not there? This is whats making me think maybe there is an issue with the internal memory?? The tab has been freezing and rebooting at least once a day for the past 2 weeks or so?
Haven't tried the odin route yet, will give that a go tonight

If you wiped everything then yes, that will delete your internal memory.
Follow the Overcome guide to use Odin and restock to the GB safe rom, then go back to Overcome.
| Don't Revive Me Bro! |

GANJDROID said:
If you wiped everything then yes, that will delete your internal memory.
| Don't Revive Me Bro! |
Click to expand...
Click to collapse
Ah, my Avatar is quite fitting at this point........
Thanks. Will follow the guide again tonight

kevstv said:
Ah, my Avatar is quite fitting at this point........
Thanks. Will follow the guide again tonight
Click to expand...
Click to collapse
Haha, itbis
All youll need is:
Odin 1.7
P1_hidden.pit
GB-stocksafe.zip (i think thats what its called)
And the Obercome beta rom.
Hope it works out well for you.
| Don't Revive Me Bro! |

this also happened to my tab (because i was playing around with my system files) i just reflashed the ROM and it was fixed, dont worry about it being bricked as long as you can still access CWM and download mode
hopefully you backed up
good luck! hope you get it fixed!

Think I could be in trouble. Followed the odin steps and got a big Red fail on Completing (Write) - Fail
Now whenever i turn it on all I have is a phone icon with a broken line going to a pc icon, cant even get into recovery!

Just flash dbdata. Don't worry, it's not bricked if you can still power it on and odin recognise it.
Sent from my GT-P1000 using XDA App

kevstv said:
Think I could be in trouble. Followed the odin steps and got a big Red fail on Completing (Write) - Fail
Now whenever i turn it on all I have is a phone icon with a broken line going to a pc icon, cant even get into recovery!
Click to expand...
Click to collapse
Thats alternative download mode. Try again

DarkPal said:
Thats alternative download mode. Try again
Click to expand...
Click to collapse
Try what again? I've tried switching off and on again several times? Do you mean try the odin steps again? If so I have twice and both times ended with the same Fail. I am really starting to think there is a serious issue with my internal memory...

aibo said:
Just flash dbdata. Don't worry, it's not bricked if you can still power it on and odin recognise it.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Thanks but I'm fairly new to this, could you expand a little please. Thanks

There is a dbdata.tar file somewhere on roto rom's thread or chainfire's gingerbread rom. If it's a zip, extract it beforz. Flash it as pda.
Sent from my GT-P1000 using XDA App

I've had random reboots running a few different roms. It sucks and it does require a complete wipe. I end up going back to heimdall and reflashing all vzw images. Then I'm on a clean path to a fresh start.
Tbolt meatclaws-talkatap

Tab won't even switch on to alternative mode now other than when it's plugged into the wall socket power charger!?!?

Anyone able to offer an help? The tab will not boot unless it's plugged in charger, so when plugged into pc/laptop will not boot so I can't get to download mode..

Have managed to get it to switch on now but still getting the write failed when trying to flash the PDA. Have tried the GB Stock Safe and have tried the official samsung, both fail. This really does sound like an internal memory issue to me as everything seems to work fine until itgoes to write to the memory, does that sound feasible or am I just panicking?

One piece of advise...make sure that your battery is fully charged before you start anything....like if you plug it in will it show it charging...because if you start messing around with Odin or flashing and it dies from lack of power....then you will be SOL....I just had to send two into Samsung in the U.K. to get them flashed back to normal....but followed the Overcome rom instructions and both now have 2.3.3 android...Good luck!

1Brite1 said:
.I just had to send two into Samsung in the U.K. to get them flashed back to normal...!
Click to expand...
Click to collapse
Did this cost you?

Bricked Note :(

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

[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

so my brother brought me his semi bricked n7000 "btw i searched and googled"

so my brother brought me his semi bricked n7000 "btw i searched and googled"
well, yesterday my brother brought me his cellphone which doesn't boot anymore, he wanned to install a custom rom since he saw that i have a fast one (galaxy s I)
so when i asked him what he did , he said he followed all the steps in rootgalaxynoteDOTcom/galaxy-note-roms/kingdroid-ics-rom-v3-0-for-galaxy-note-gt-n7000-best-ics-romtouchwiz-ux/[/url]
but then, his phone didn't boot, so he wiped - reset factory setting, which i read is a BIG NO when you're flashing ICS.
so whats done is done, i am trying to get it back , i can boot in recovery mode/download mode ... i tried out many kernels like AbyssNotekernel42RedTouchCustomLogo or speedmod, and downloaded at least 4 or 5 GB stock roms.
sadly , if odin flash is successful, it stuck on (samsung galaxy note gt-n7000) black srcreen, reboots few times then stays still...
if the odin flash wasn't successful , it keeps stuck on data.img and never goes beyond that .
i did all the steps i could find, wiped data after installed stock GB rom and rebooted, nothing worked
i even used rogue_ET-recoveryonly , and i think it went along format all the way, but still nothing happened after that.
the only thing i haven't tried yet was the repartition + pit file, i couldn't find the PIT , most of the roms have pda/modem/csc ... so if anyone can help out, i would really appreciate it ..
thanks

First thing you should do is check other threads about that around here.
If you can get it into download mode, you could give flashing with Odin a try. If it doesn't get stuck at factory.fs, then you're not superbricked.
If it does get stuck, then you have 2 more hopes:
- HOPE 1
- HOPE 2
If those don't work either...I'm afraid it's off to the Samsung Service center for a shiny new motherboard.
Best of luck to you and hope you get your Note up and running as soon as possible...

thanks, no it doesn't get stuck at factoryfs at all , i did check out most of the threads here, and most of them say "go back to GB with odin and if its stuck on samsung gt-n7000 boot screen just go back with recovery mode and then wipe data / cache " but never worked, so i thought i should ask around here
i'll check out the threads you posted and see what i can come up with

weird, i used the 16gb pit - repartition (check)
and i flashed it with SGN_XX_OXA_KJ1_FACTORYFS through odin.
and its still the same, the flashing with odin was successful and everything went fine, no hanging , no delays or what so ever. after it restarts its stuck on the black samsung galaxy note gt-n7000 screen
im gonna wipe data / cache again but i doubt that would fix anything.
so any idea what could be wrong? specially when the flashing process went fine?
i've already tried like 4 stock roms ,
arabic uae , europe , saudia and the SGN_XX_OXA_KJ1_FACTORYFS
i wonder if i need to put something in boot space in odin "just a thought"
ive tried downloading roms from here [STOCK ROMS] N7000 All stock ROMs + install + Root guide All at 1place,Latest ICS LQ3
and here [STOCK ODEX PRE ROOTED ROMs] for Odin PC no counter & triangle
any ideas?

For OP:
If you are not stucking while flashing from PC Odin then you are not superbricked.
I think you got corrupted /system or other partition; I saw another thread where OP was getting this sort of hang due to filesystem corruption which can't mount.
Entropy512 gave simple dd command based solution for erasing initial 1MB of partition.
Try searching for corrupted filesystem/partition related information. I can't recall exact thread title, sorry.
I hope this will help.
I found the post/thread for you to check: http://forum.xda-developers.com/showpost.php?p=27102526&postcount=16

thanks for the reply , even think i flashed the abyss and the 4pda_kernel i still can't get anything when i do adb devices >.>
so im trying to figure out whats wrong

johar123 said:
thanks for the reply , even think i flashed the abyss and the 4pda_kernel i still can't get anything when i do adb devices >.>
so im trying to figure out whats wrong
Click to expand...
Click to collapse
Should try to install/reinstall samsung usb driver package. or try reinstall Kies also provide drivers for Note.
If driver is install properly: when connect with PC using usb cable it need to be shown under hardware management as something like "android composite adb interface" or something like that.

johar123 said:
thanks for the reply , even think i flashed the abyss and the 4pda_kernel i still can't get anything when i do adb devices >.>
so im trying to figure out whats wrong
Click to expand...
Click to collapse
Also are you trying to connect adb after booting the phone ? Means in a stuck state ? I think you can try enabling ADB thing from CWM rather than trying to boot phone fully.

hmm i can't find an option in CWM that suggests that , still searching
also im trying to find roms that i can install from CWM , are there any GB roms that can be directly installed from CWM ?
thanks.

johar123 said:
hmm i can't find an option in CWM that suggests that , still searching
also im trying to find roms that i can install from CWM , are there any GB roms that can be directly installed from CWM ?
thanks.
Click to expand...
Click to collapse
Hi: I understand he means boot the phone into CWM and then connect to PC in that environment. adb need to be run from PC while the phone is booted into CWM recovery.
Still, most of the custom roms are in the .zip format and can be install using CWM. they just now become a bit more difficult to find since dev move on to ICS/CM9 roms. Still try to find some GB roms in the forum such as: rocket GB, litening GB, xtralite GB....
This is the link for Rocket rom GB. Better try v22 than v23.
http://forum.xda-developers.com/showthread.php?t=1380284
Check rom:
http://download.checkrom.com/roms/a...oteHD_V3.zip?iframe=true&width=950&height=420
cheers,

forest1971 said:
Should try to install/reinstall samsung usb driver package. or try reinstall Kies also provide drivers for Note.
If driver is install properly: when connect with PC using usb cable it need to be shown under hardware management as something like "android composite adb interface" or something like that.
Click to expand...
Click to collapse
done that already.. everyone is saying is "get into recovery mode" >.>

johar123 said:
done that already.. everyone is saying is "get into recovery mode" >.>
Click to expand...
Click to collapse
Yes, recovery mode is in CWM. (in case you have not done it: Enter recovery by,from phone power off: pressing volumeup + home + power and release power when see samsung letter while still hole the other two buttons.)

forest1971 said:
Hi: I understand he means boot the phone into CWM and then connect to PC in that environment. adb need to be run from PC while the phone is booted into CWM recovery.
Still, most of the custom roms are in the .zip format and can be install using CWM. they just now become a bit more difficult to find since dev move on to ICS/CM9 roms. Still try to find some GB roms in the forum such as: rocket GB, litening GB, xtralite GB....
cheers,
Click to expand...
Click to collapse
thanks for the reply, i've done it many times, when im in the CWM screen, the adb devices still doesn't show anything >.> maybe im using a wrong kernel? what kernel you guys suggest?

johar123 said:
thanks for the reply, i've done it many times, when im in the CWM screen, the adb devices still doesn't show anything >.> maybe im using a wrong kernel? what kernel you guys suggest?
Click to expand...
Click to collapse
hmm. that should be still the problem with usb driver. Have you checked under hardware management if it show the device as "samsung composite adb interface" yet?
kernel should not be the problem with connecting adb. It is the problem with usb driver for Note. Sometime Win7 have problem with driver. You may want to search for another package of samsung usb driver on the web.
I did put some links of GB roms in the post in the previous page. maybe try them first if any luck.
Also try to restart computer to see if the driver issues get solved.
Got to go. Hope that you can solve the problem. GL.

forest1971 said:
hmm. that should be still the problem with usb driver. Have you checked under hardware management if it show the device as "samsung composite adb interface" yet?
kernel should not be the problem with connecting adb. It is the problem with usb driver for Note. Sometime Win7 have problem with driver. You may want to search for another package of samsung usb driver on the web.
GL.
Click to expand...
Click to collapse
thanks, i restarted my pc , reinstalled kies, and now it shows under device manager
now i connect to the phone through adb , i appreciate you pointing it out
which method you think i should go for 1st? this one
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
or unzipping a rom and then pushing it all through adb?
i think i'll go for removing and repartitioning manually, hopefully it'll work
thanks again guys , i'll post the updates here,
lol, my brother called me and he's like "if u can't fix it by the end of the night, fk it, dont bother yourself with it" but to be honest, im too stubborn, i hope i can fix it

looks like deleting and adding partitions back through parted kinda work, for the first time i was able to pass the boot screen after i installed rocketrom from CWM
however, its been 1/2 hour since im stuck on rocketrom loading screen it keeps looping and looping.. i wonder if i should wait more.. or should i try another rom?

finally got rid of the verification -.- was kinda annoying thats why i didn't bother editing posts,
anyways, rocketrom didn't work, so i decided to flash a stock rom instead , the flash through odin went fine, it was great to be able to wipe data without getting stuck , however, it keeps going though samsung animation over and over, i think im gonna leave it like this one the charger till morning, i wonder if it'll be the same
guess i have to google for "samsung loop" , i wonder why this keeps happening though -.-

-.- leaving it for 6 hours on samsung logo animation didn't do the trick , still looping when i woke up, so i guess i'll do some more search on why this is happening.

You have checked partitions and see no error that means the problem lies somewhere else, not partitions. I have no idea yet, but for me I would try some different roms. Small roms have more chance to work, that is the feedback I got from some people:
- try check rom in the link I sent
- try paranoid android which is CM9, or asylum
- extralite
cheers.

forest1971 said:
You have checked partitions and see no error that means the problem lies somewhere else, not partitions. I have no idea yet, but for me I would try some different roms. Small roms have more chance to work, that is the feedback I got from some people:
- try check rom in the link I sent
- try paranoid android which is CM9, or asylum
- extralite
cheers.
Click to expand...
Click to collapse
thanks buddy, i appreciate your help, the partition "USED" to give me error when i did the check 9 10 11 , but after removing the partition and reformatting them (and i also removed the cache partition) now its working fine "i suppose" i didn't do another check, but i might will now that you mention it.
i already tried rocket rom, didn't work, stock rom didn't work, so i'll give the others a try at least it doesn't get stuck on the boot screen, but its stuck on the animation logo which is an improvement
thanks again

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!)?