Hey guys I have an Indian Galaxy pop aka galaxy mini running 2.2.1 .
I wanted to flash CM7 on it so I first flashed the CWM recovery from tj_styles thread via odin .. it flashed successfully and the phone booted but now I can't get into recovery mode ...
Tried home + power, terminal emulator, qtadb .. it just gives a black screen or gets stuck on the Samsung screen...
Anyone knows what the problem is? Any help would be appreciated
Upgrade to GB first then flash cwm.
CWM only work in gingerbread..
Sent from my GT-S5570 using Tapatalk
Yp first search how to upgrade to gb...then recovery mode..then ll b able to flash cm7 ..
Sent from my GT-S5570 using XDA App
Okay ... thanks for the replies
roofrider said:
Upgrade to GB first then flash cwm.
Click to expand...
Click to collapse
I had android 2.2.2 on galaxy pop cdma.but i installed ROM manager.infact i also installed cwm.but when i clicked backup current ROM.Phone got blacked out..and doesnt start..Now the problem is how to i enter recovery mode..i tried all possible combinations ..dosent wrk ...plz help
rak_688 said:
I had android 2.2.2 on galaxy pop cdma.but i installed ROM manager.infact i also installed cwm.but when i clicked backup current ROM.Phone got blacked out..and doesnt start..Now the problem is how to i enter recovery mode..i tried all possible combinations ..dosent wrk ...plz help
Click to expand...
Click to collapse
Rom manager is not compatible with our device and you have hard bricked (broken bootloader) and now you must give to samsung service for repair.
Sent with my Evil GT-S5570 from Hell
EVIL THOR said:
Rom manager is not compatible with our device and you have hard bricked (broken bootloader) and now you must give to samsung service for repair.
Sent with my Evil GT-S5570 from Hell
Click to expand...
Click to collapse
thats sad...but as a developer cant we fix it ourselves..i mean generally what is generally done in these situations.reflashing bootloader with some tools ?
rak_688 said:
thats sad...but as a developer cant we fix it ourselves..i mean generally what is generally done in these situations.reflashing bootloader with some tools ?
Click to expand...
Click to collapse
Actually, ROM Manager is capable of bricking the Motherboard, and this situation is termed as "Hard Brick" ie, the phone is completely dead. You can't enter recovery/download mode or boot up.
So, only the Samsung Service guys can replace the motherboard in order for the phone to function properly.
On the other hand, if the bootloader is bricked, it is also a case of Hard brick, but some devices can recover from this stage, but no idea about Galaxy Mini. I guess only locked bootloader is dangerous more than unlocked bootloader, and Galaxy Mini's is unlocked. Normally every Samsung's bootloader is unlocked I guess.
coolsandie said:
So, only the Samsung Service guys can replace the motherboard in order for the phone to function properly.
Click to expand...
Click to collapse
Phone doesn't need motherboard replacement. It could be fixed with JTAG like RiffBox in any better service. I have RiffBox and several GT-S5570 phones were fixed with JTAG method.
It isn't simple but is possible. Phone should be disassembled, eight wires soldered to the motherboard and through JTAG access rewrite boot loader to the OneNAND memory. After resurrection finished, it's possible to switch phone to the download mode and continue flashing with Odin.
try install your stock rom via odin, and later install cmw, later of this you can flash what you wants, i recomend cmw touch updated
And what was the need of reviving a 1 year old thread
Want 10 posts then post something useful in current topics
dheeraj (dhlalit11) said:
And what was the need of reviving a 1 year old thread
Click to expand...
Click to collapse
A good post of course.
dbunic said:
Phone doesn't need motherboard replacement. It could be fixed with JTAG like RiffBox in any better service. I have RiffBox and several GT-S5570 phones were fixed with JTAG method.
It isn't simple but is possible. Phone should be disassembled, eight wires soldered to the motherboard and through JTAG access rewrite boot loader to the OneNAND memory. After resurrection finished, it's possible to switch phone to the download mode and continue flashing with Odin.
Click to expand...
Click to collapse
Related
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
i was having stock version of galaxy ace in my mobile, wanted to install any custom firmware. But the problem was volume buttons in the mobiles were not working due to some hardware prob, but still i manage to find a way to connect it to download mode by an app and installed cwm through odin, and then using cwm manager app i tried installing miui rom on my mobile, but i don't know what is the problem it is keep getting restarted in the boot screen, now i neither have app to connect download mode, nor the volume keys to recovery mode.I almost think that my mobile s dead now, can any one give me a hope to get my mobile back working again?
Samsung service center?
Don't be a noob. Be a newbie..!!
Details here.
shaaan said:
Samsung service center?
Don't be a noob. Be a newbie..!!
Details here.
Click to expand...
Click to collapse
i tried everything, i didn't got any help when i posted help for the recovery mode without volume keys, i figured it out my self but now i'm totally confused what to do.i don't have any idea...
Prawesome said:
Touch Recovery or not,its still a risk.I had recommend fixing your phone first.Why? Because in case you encounter some sort a problem with the kernel you flashed and your touchscreen becomes unresponsive,then your only way out would be Odin.
Click to expand...
Click to collapse
TechNoJerky said:
Don't install, first you'll have to fix your device. i had this problem and i ended up to samsung service center cuz of fully bricked device.
Click to expand...
Click to collapse
This is what happens when you dont listen to good people.
Anyway,I suggest flash stock recovery if u can boot in CWM and then take it to service center.Say I was updating using kies and now my phone wont start..!act all noob..this works most of the time
Best of luck!!
I got my Galaxy Note today, I was on 4.0.4 and I rooted it. Then I went to recovery mode and flashed teh recovery there is on clockworkmod webpage for Galaxy Note N7000. After that wipe factory and flashed PA 3.94, and it got stopped and reppently it turn off and I am not able to turn on the phone.... please need some help
the recovery for N7000 is in the kernel so the clockworkmod website flash of CWM doesnot stick.. boot into download mode and flash a stock rom ( preferably JB) and start again
I cannot access download mode I think....
Was it Cwm.zip by any chance?
Sent from my GT-N7000 using XDA Premium 4 mobile app
IDk how is called. I got it from clockworkmod recovery page.
herna said:
IDk how is called. I got it from clockworkmod recovery page.
Click to expand...
Click to collapse
As an ex-N7000 owner (I still browse these forums from time to time), I can tell you the Temp (non-touch) CWM you flashed is safe for for wipes and formats (hence no problem when you did factory reset with it). HOWEVER it is is not safe to flash ROMs where the zip file contains an updater script with format commands coupled with an update binary which does not suppress "secure erase" commands (Running on top of On ICS kernel - subsequently fixed by Samsung on JB kernels).
With CM.10.* ROMs there is no problem, but some ROMs still use bad update binary (probably from Android kitchen). I feel PA is the culprit in this case.
So it would now seem you are 'Superbricked". Only solution is repartition or new MOBO.
Edit: J-Tag won't work unfortunately.
Will try repartition, if not will try JTAG and if it doesn´t work will send it to service centre. But how to repartition if I cannot access Download Mode?
Download Mode is essential in order to flash required modified PIT file for repartitioning. I assume you can't enter recovery mode either right? That being the case service center is the way to go. J-Tag can't fix bricked areas, but may be also able to re-partition.
Good luck :fingers-crossed:
shoey63 said:
Download Mode is essential in order to flash required modified PIT file for repartitioning. I assume you can't enter recovery mode either right? That being the case service center is the way to go. J-Tag can't fix bricked areas, but may be also able to re-partition.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
I mean I cannot access download mode, or maybe idk how to do well, but if I cannot access download mode that maybe means I am hardbrick and not SuperBrick, and Hardbrick can be fixed via JTAG or at least it says here http://forum.xda-developers.com/showthread.php?t=1656635
I just tried adb devices, not found. I connected Odin, not found. I try access recovery mode, impossible and I tried download mode(maybe idk how to ) impossible.
Also I have not battery signal when I connect phone for charging...
I think you may be both hardbricked and superbricked at the same time (Same as what happened to me). That is the worst case scenario Practice download mode more to see if you can get into it, and, if successful, flash stock GB with PC Odin. Otherwise try repartitioned PIT file from @hg42.
shoey63 said:
I think you may be both hardbricked and superbricked at the same time (Same as what happened to me). That is the worst case scenario Practice download mode more to see if you can get into it, and, if successful, flash stock GB with PC Odin. Otherwise try repartitioned PIT file from @hg42.
Click to expand...
Click to collapse
Okey, will try, about JTAG or JIG I think maybe it can get "alive" the phone and let me boot into download mode, idk if is like that There is a sequence for download mode? Try with or without batter? idk so much about Samsung, is my first Samsung Phone, and about you, what you did with it? Did you change your Note? Can I have what the guide call Died Brick?
I got a refund and put it towards Sony Xperia Z. J-Tag may fix bootloaders and bring download mode back, but bricked areas will never be recoverable. Download mode is 3 finger "salute". Forget the combo ATM. Don't have the device
Sent from my C6603 using xda app-developers app
shoey63 said:
I got a refund and put it towards Sony Xperia Z. J-Tag may fix bootloaders and bring download mode back, but bricked areas will never be recoverable. Download mode is 3 finger "salute". Forget the combo ATM. Don't have the device
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
And if I get download mode via JTAG and then repartition? I mean the only solution to bricked areas go good is via repartition,no? And for repartition I need download mode...
I AM STILL THINKING OF THIS, BUT NO SURE
There are three types of bricks for N7000
a) Soft Brick - Stuck at Samsung Logo [Added BootLoop here]
b) Super Brick - Stuck at flashing Factoryfs.IMG in ODIN . Also called as EMMC Bug....
c) Hard Brick - Sorry Unrecoverable by this guide. Try THIS
d) Dead Brick - No charging battery sign also - Mostly = Hard Brick ; But there is a window of possibility by a JIG.
If that guide is good, my device is on d) , but idk what JIG do
I mean if I JTAG will I can use my device? What problems will it have? And if I use JIG, what problems I will have? WIll it work good?
I have just see this video http://www.youtube.com/watch?v=d0SX3iDuIZc
Do that video says I have to JTAG, then use the JIG for going on download mode and then, repartition or install JB ROM from Odin? Please just say me, I can try today
OKey have just commented with some DEVs. Jtag will repartition all for get it booting, so I am gonna try the JIG for see if I can get download mode. If I cannot I will make JTAG(will repartition) and then I will use the JIG for get into download mode(I also can make with hands), so if JTAG work I just need to flash JB via ODIN, my question is, can somebody send me a guide or link for JB to N7000 via ODIN? THANKS!!1 THANK YOU ALSO @shoey63
Follow Dr Ketan's thread in stickies of original android development.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Thank you man Will use the pit for partition 16 GB version, and then flash JB via ODIN! Thanks, one question, when I get JB, how to install PA or any Custom ROM without problems? What recovery to use? Please help me
Just read the instructions on the rom threads, they give you all the guidance you need.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Thank you , I just asked for do not have problems like this again, but I have just check all JB ROMs, even stock one has secure kernel and I will can make it good, just really so much THANK YOU! And is really incredible how is easy is to get brick on samsung phones WOW! I am DEV for Huawei u8800pro, I made so much things and stupid things to my phone and never got bricked, never(also huawei has pink screen feature) but never, will take more care since tomorrow
I THINK DEV MUST PUT A GUIDE LINKED ON THEM ROMs THREADS, FOR PEOPLE READ IT BEFORE INSTALL
The guides are already there in the stickies, people just don't read before flashing.
Sent from my GT-N7000 using XDA Premium 4 mobile app