Related
BRICKED USERS GUIDE.......
First you need to know that this guide is trying to help you..
I cannot take any responsibility for your brick getting harder ....
.....IGNORE ALL WHO SAID NOT TO WASTE THEIR TIME .....
....... The poll was for a different post related to emmc bug where i suggested a workaround for the emmc bug , which I edited several times....
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.
e) OTA Brick - A rare kind of Soft Brick which people have encountered due to updating OTA on a rooted Stock ROM.
f) CM12 Brick - A Brick I and another XDA Mate encountered when CM12 encountered a /data write error. Worst is ODIN Flashing Fails .....
CM12 Brick
CM12 Brick
Error Details : Flashing JB Kernel in ODIN Fails ...
Received Response from LOKE FLashing Failed ....
a) Download the PIT file
b) Flash in Odin
c) After SUCESSFULLY Flashing Pit File
d) Flash ICS KERNEL (SPEEDMOD KERNEL) USING ODIN
e) Now go to Recovery and Flash your Favorite Philz Kernel
SOFT BRICKS
I will try to describe ways to get Soft Bricked so that you can compare.....
You have messed with the system file. Remember the Blue Screen of windows.
==> 1. Deleting any system file .odex
==> 2. Moving from GB or ICS to CM/AOSP/AOKP Roms without following instructions or vice versa
==> 3. Flashing incomplete ROMS (did not check MD5 - Google it How to check)
==> 4. Flashing an incompetent kernel (oh I didnt read instructions)
==> 5. Many other methods
==> 6. JB BootLoop
Now you have to return to normal state. But beware there is a emmc bug which is going to interfere our correction process. Oops ! It hurts. There is no safe way as on date for ICS except there are Safe Kernels Claimed.
Pray to your favorite god or luck or better pray even if you are an atheist.
RECOVERY STYLE 1 : [ODIN]
GINGERBREAD VERSION
1) Use ODIN
2) Uninstall Samsung KIES. It interferes with the ODIN flashing.
You should have the ADB/USB Drivers
Just in case you don't have them, here are the Samsung USB drivers
3) Download the AbyssKernel 4.2 for ODIN.
Incase it fails u can use 3.9 version too.
4) Wipe Data/Cache/Dalvik.
5) FLASH THE ROOTED KJ4 kernel From PC ODIN - Kernel Link
TRY FLASHING THE STOCK ROM in PDA Try the Oldest Stock ROM - KJ4 click me
Remember to Run ODIN in Admin mode (Right Click and Run even if you are an Admin)
6) Head to Dr Ketan Thread for Rooting...
ICS VERSION
1) Use ODIN
2) Uninstall Samsung KIES. It interferes with the ODIN flashing.
You should have the ADB/USB Drivers
Just in case you don't have them, here are the Samsung USB drivers
3) Download the AbyssKernel 4.2 for ODIN.
Incase it fails u can use 3.9 version too.
4) Wipe Data/Cache/Dalvik
5) FLASH ANY ics rooted rom in Abyss Recovery which has a safe kernel
Remember to Run ODIN in Admin mode (Right Click and Run even if you are an Admin)
RECOVERY STYLE 2 : [CWM]
ICS and GINGERBREAD USERS
a) Go to CWM
b) Flash Abyss Kernel 3.9 or 4.2 [Touch version] or Hydracore latest version.
c) Do data/ factory reset.
d) Flash with your favorite ICS / GB /AOSP/ AOKP/PA/CM9/CM10
[BOOTLOOP JB Leak / Official]
ODIN Version
a) Download Stock JB from Dr Ketans Thread
b) Install Tar file via ODIN in PDA
c) Reboot
d) Root as in Dr Ketans Guide
e) Install Custom ROM from CWM if you need
CWM Version
Understanding the issue now. So Prefer ODIN version now.
END SOFT BRICK
SUPER BRICKS
Hmm ... I understand your despair. My friend forest has written a wonderful guide to retrieve you out.
If you are confirmed that you are a Super Brick
Head to this thread ......
But .... Just before heading to Mr Forests Thread May be you are not a Super brick ...
There are few who had the same symptoms of a Super Brick but successfully recovered without the Forest1971 workaround.
RECOVERY STYLE 1 : START HERE
IMPORTANT NOTE : Remove your SD Card and SIM CARD Please
Run ODIN IN ADMIN Mode
a) Now you have to repartition your Note
b) Download the following (Importantly the .pit file)
PIT: Q1_20110914_16GB.pit (Only for users with 16GB Internal SDCard) 32 GB users Please Google ur file.
PDA: CODE_N7000xxxxx_CL627135_REV02_user_low_ship.tar.m d5
PHONE: MODEM_N7000xxxxx_REV_05_CL1067428.tar.md5
CSC: GT-N7000-MULTI-CSC-Oxxxxx.tar.md5
Thanks PrinceOMI & DuckBoot for the download links (PIT Files)
Stock ROM & Pit File Flashing Thread
c) Check these options: Re-Partition, Auto Reboot, and F. Reset Time.
d) Flash thru PC Odin (All the files, particularly the PIT file)
SUCCESS .... GOOD FOR YOU .... Only 2% reported success using this style (I ask you not to Thank me but to write here in this thread if you are successful. Many users do not care..)
RECOVERY STYLE 2 : START HERE
Working on it .... Not able to proceed. Ideas dropped.
END :angel: SUPER BRICK :angel:
:cyclops: OTA BRICKS :cyclops:
I will try to describe ways to get OTA Bricked (very rare)
a) Installed the OTA for ICS ROM Indian Version LPA on a rooted ROM.
Some thing has messed up with your .odex files and you get force closes or Stuck at Samsung LOGO
1) ODIN Method
a) go to Download Mode (Power Button + Vol down + Home)
b) Flash the ICS ROM posted in Dr.Ketan Thread in the PDA
Remember that options are ticked according to this image.
Donot tick repartition.
You can root it by Heading to Dr Ketans thread.
2) CWM Method (Custom Firmware - Closest to LPA ROM)
a) go to Download Mode (Power Button + Vol up + Home)
b) Flash the ROM close to LPA without any Reset or Wiping.
This will endup with a custom ROM Clea Note (LPA Rooted)
END :highfive: SUPER BRICK :highfive:
Dude, that's really sad. You should've gotten your girl her presents before repairing. It's not her fault you flashed custom ROMs.
Sent from my superior GT-N7000 using Tapatalk
Sure I will gift her my Samsung Galaxy Tab ( which I got it repaired due to water entry; She poured water on it )
She Loves Playing with my Tab.
sorry, i don't mean to criticize your method but...
if your eMMC is already dead or corrupted, how is this method gonna revive the note??
I got my Note connected to PC Odin (when it was superbricked) once which I could not replicate again.
Since I got it connected anybody else would by the above procedure.
I always believe that Software Problems can be solved by tweaking Softwares; not by replacing the motherboard; I did it once but I missed How I did it.
prabhu1980 said:
b) Download the following (Importantly the .pit file)
PIT: Q1_20110914_16GB.pit
Click to expand...
Click to collapse
I had a feeling that the partitions are messed up by the kernel and restoring it by pit would help, as it worked for a few people. Anyway here are the pit files
I like optimists, but I hate to see them when they fail
superbrick is when the portion to which ROM gets written is fried due to the bug.
AND, JTAG JIG is different from micro USB JIG.
While I appreciate your gesture to trying help others, wrong information is unwelcome. Also, even if you are able to connect to PC odin after everything, this method does not tell how to make it flash the ROM.
Thanks anyway.
From a bricked user who tried everything to resurrect the note but failed.
Corrected My Post about JTAG (I am not a perfectionist and please allow unintented mistakes)
But I got connected once to PC Odin.
Were you able to connect it ??
Did you try the method posted above while using the JIG ?
You are right !! This method will be OK till PC Odin.
But once you are able to connect; lets try Step 2 and Step 3 (added after some research)
Lets get it connected first.
Getting Fried
Click to expand...
Click to collapse
- Does Flashing Fry your ROM ? Comeon Man Its a Software BUG and it should be possible to recover.
How many times we have fried Windows and Linux and played with Boot Partitions for Multiple OS.
Something should be possible. Please throw some light and help the Superbrick users. Donot demotivate.
Find Ways to Come out of this bugging bug.
I am not a software developer but ur comments will drive me to become one Thanks !!!
While I appreciate your gesture to trying help others, wrong information is unwelcome.
Click to expand...
Click to collapse
Boss !! What I am doing here is just a try before replacing your motherboard ! Hope it will harm no one.
prabhu1980 said:
Did you try the method posted above while using the JIG ?
Click to expand...
Click to collapse
I did when my Note got bricked, and it didn't help one little bit.
I wrote this because I got connected to PC Odin after the Black Screen.
Did you got connected and still unable to recover ??
We should somehow be able to connect it to PC.
Any alternate suggestions Chasmodo .
We have to find a way out of this Brick Issue.
Please help !! (I dont think I can brick to find a way out
If required please make a bounty for the developers to revive from this situation.
My Feeling is "Whatëver bad happened to me should never occur to anyone else"
prabhu1980 said:
I wrote this because I got connected to PC Odin after the Black Screen.
Click to expand...
Click to collapse
I understand your intenstions, but eMMC is fried (i/o bug which might allow excess voltage while wiping or corrupting NAND) no one knows what the reason is yet, but all we know is the partition where the ROM gets written to get corrupted and hence you cannot flash any ROM onto it, no matter what you do!
eMMC Bug which will allow excess voltage damaging the ROM . Thats Frying ....
Thats Poor Hardware right ??
But we dont know what's the BUG. Coz had we known we could have corrected it.
Were you able to connect to PC Odin when you had a blackscreen ??
prabhu1980 said:
I wrote this because I got connected to PC Odin after the Black Screen.
Did you got connected and still unable to recover ??
We should somehow be able to connect it to PC.
Any alternate suggestions Chasmodo .
We have to find a way out of this Brick Issue.
Please help !! (I dont think I can brick to find a way out
If required please make a bounty for the developers to revive from this situation.
My Feeling is "Whatëver bad happened to me should never occur to anyone else"
Click to expand...
Click to collapse
You found your way out of a situation caused by the Repack Rom, not by the LPY one.
LPY bricks seem to do physical damage to your EMMC chip, so connecting your
Note to the PC will do no good. PC Odin flash will fail because of the damaged EMMC blocks.
There's a lot of bricked users who can get into Download and/or Recovery mode,
but ALL their flashes still fail. See this: http://forum.xda-developers.com/showthread.php?t=1653290
I fear the Note community will be remembering this LPY debacle for a long, long time. There's no known cure for now.
LPY bricks seem to do physical damage to your EMMC chip
Click to expand...
Click to collapse
It seems or Is it confirmed damage ??
Please dont think I am pulling too hard. May be if Emmc is getting damaged why not replace Emmc chip instead of the whole motherboard. I got my Motherboard replaced..
If Partitions are getting fried then Why cant we re partition it ?
anilisanil said:
I understand your intenstions, but eMMC is fried (i/o bug which might allow excess voltage while wiping or corrupting NAND) no one knows what the reason is yet, but all we know is the partition where the ROM gets written to get corrupted and hence you cannot flash any ROM onto it, no matter what you do!
Click to expand...
Click to collapse
Did you re-partition your ROM ??
If you had done it. Can we have a re partition (modified PIT) for LPY to overcome the area corrupted ??
There are ways to repartition . Included Step 3 in my post.
You may be right !! But I am just looking for a solution like you ....
But since you are using words like MIGHT and MAY I m still guessing solutions may exist.
Please read this Thread http://forum.xda-developers.com/showthread.php?p=26167317#post26167317
anyone tested yet?
Sent from my GT-N7000 using XDA Premium HD app
Looks like there is one success case jpturibio
Please look into this. Try Try until u succeed.
prabhu1980 said:
Looks like there is one success case jpturibio
Please look into this. Try Try until u succeed.
Click to expand...
Click to collapse
I really have no idea. Samsung service guys even tried JTAG my device, but the whole thing conked off while JTAG and they replaced my device under warranty.
So if a JTAG could not restore my phone, how would I know if flashing repetitively would help. Anyway, I am glad it worked for someone, and I get a feeling that we would soon be finding some solution to this plague!
Please watch this thread and Post your success / parted snapshots here.
Please look into this !! Factory.RFS users.
Dont get demotivated. Many have gone past this in several forums (Google it and See)
Many have success cases.
We have to evolve a method , so please post to help me solve this issue.
My S4 can't turn on (the first screen of the model is starting and then nothing, downloading and recovery mods are working), its all happend after i did something wrong when I have tryed to root the phone, i puted the .tar file in the bootloader line in odin insted of the PDA line, I also tryed to flash stock rom to it and it's always fail. is there any solution or is it lost?
burik1994 said:
My S4 can't turn on (the first screen of the model is starting and then nothing, downloading and recovery mods are working), its all happend after i did something wrong when I have tryed to root the phone, i puted the .tar file in the bootloader line in odin insted of the PDA line, I also tryed to flash stock rom to it and it's always fail. is there any solution or is it lost?
Click to expand...
Click to collapse
Well you did something horribly wrong my friend. Did you not refer any tutorials?
Mindless efforts.
Always flash via PDA.
Try changing the cable and the usb port and flash the latest updated 4.4.2 firmware for your phone using the PDA tab and revert.
@MAX 404
"If someone helps, never forget to hit thanks ? "
Hi
the story is I had a Hong Kong version galaxy s5 G900F model and i wanted to install googles apps and stuffs on it so i tried to root it and as i was NOOB it got a odin failled message. after that phone vibrated and turned on but there were no picture, while it was trying to boot with the blue light on the top it has the samsung booting sound played only half the way and would stay in booting for ever. still no picture ! no physical damage to the phone its only 6days only.
it boots to download mode. even goes to CWM but still no picture. I have z3x box and I have flashed the phone with 4 files still no luck! no picture
Restored the latest firmware with re partitioning enabled, still no luck! the only thing i have not tried is jTag.
I have even tried two different brandnew screens on the phone still no luck! I have tried custom kernel no luck!
I have a repairer friend he said the display driver may have been erased? is there anything like that? is there any way to fix?
I hope someone here can help me !
shamid202 said:
Hi
the story is I had a Hong Kong version galaxy s5 G900F model and i wanted to install googles apps and stuffs on it so i tried to root it and as i was NOOB it got a odin failled message. after that phone vibrated and turned on but there were no picture, while it was trying to boot with the blue light on the top it has the samsung booting sound played only half the way and would stay in booting for ever. still no picture ! no physical damage to the phone its only 6days only.
it boots to download mode. even goes to CWM but still no picture. I have z3x box and I have flashed the phone with 4 files still no luck! no picture
Restored the latest firmware with re partitioning enabled, still no luck! the only thing i have not tried is jTag.
I have even tried two different brandnew screens on the phone still no luck! I have tried custom kernel no luck!
I have a repairer friend he said the display driver may have been erased? is there anything like that? is there any way to fix?
I hope someone here can help me !
Click to expand...
Click to collapse
Shouldn't have ticked the re-partition box without a PIT file
You'll need the stock firmware from sammobile dot com and ODIN, and the PIT file from here
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file and ROM to ODIN together, boot to download mode on the phone, hit start
It will flash the PIT file, then it will flash the ROM, all being well, it should boot back up normally
*Detection* said:
Shouldn't have ticked the re-partition box without a PIT file
You'll need the stock firmware from sammobile dot com and ODIN, and the PIT file from here
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file and ROM to ODIN together, boot to download mode on the phone, hit start
It will flash the PIT file, then it will flash the ROM, all being well, it should boot back up normally
Click to expand...
Click to collapse
as i already have explained i already have done it with PIT file ! it seems turning on but no picture !
Nowhere in your post did you mention a PIT file
common man im looking to solve the problem. its obvious if i click on re partition i have to use .pit file.
Not at all, you managed to brick it, that tells me you don't really know what you're doing, so fairly likely you could have ticked it without knowing you had to use a PIT file
Anyway, if you've successfully flashed a stock ROM using PIT, and it still has no display, it sounds like a hardware fault, there's not much else you can do software wise other than what you've already done
EFS Partition in tact? I know that contains some fairly important data, including IMEI and radios, not sure if it has anything to do with display, but if you lost that, you can't fix it by reflashing ROMs
How do you know it's in download mode if there is no display?
well it can be detected via odin and samsung tool when i press down the volume down power and home and after that volume up.
as i said its just 6days old and had no issues before i start this process.
anyyone ?!
z3x box ?
You tried flashing it connected directly to a native PC ?
Phone > USB > PC
did everything no luck!
Hey guys..in fact I originally had one problem/question, but since I managed to brick my phone, I now have 2 questions. Hope you can help me with at least the one I need to unbrick the phone and later on, after bringing my phone back to life (I hope), I´ll ask the less important one. If you dont want to read it all, please go to the last paragraph to see the final problem and question.
So here´s what happened. As I was trying out different kernels on a Note7 ROM for my 910F, I managed to brick my phone. Originally the phone would not boot into recovery and gives me the message that there is a problem with firmware..as I tried to boot in download mode to flash stock ROM and get back to it, Odin gives me the message FAIL in red colour. I tried flashing again and then another stock ROM and again the problem persisted. It came to the point where the phone would now say that it couldnt read mmc (non-partition message in ODIN). After several hours (still counting) of searching both here at XDA and outside I finally managed to understand how to create a image recovery into a sd card and so I did it.
I used Win32DiskImager to write this image ( mega:///#F!QIMmFRIT!Ns3AM-n0FUoMqOOWUif9ng ) into my sd card. With phone off I inserted battery and then card and booted into download mode...SUCCESS...no more mmc message at the top left of screen, but still I cant manage to flash any stock ROM and FAIL message keeps coming. One time it said PIT not recognized and I used a SM-N910F_32GB.pit and it said PASS, but if I try and flash with ROM still fails. In the instructions it says I need to flash at the same time the SM-N910F_32GB.pit, a BL,a AP and a CP, but I cant find any BL and CP to any specific AP. Is this the solution or I am missing something here? Please help..my phone is bricked and my s4 cant manage to be my daily driver no more.
Thanks everyone
Have you referred this thread:
https://forum.xda-developers.com/showthread.php?t=3488114
Reporting Via N910G
yashthemw said:
Have you referred this thread:
https://forum.xda-developers.com/showthread.php?t=3488114
Reporting Via N910G
Click to expand...
Click to collapse
Hello friend and thank you for your reply. I don´t know how I missed that thread, but I´m glad you told me about it cause it had exactly the missing components I needed to solve my problem. But a new one just emerged with it.
I´ll be posting there from now on. Thanks again
Hi folks!!!
I know is very annoying this question....
But already look in a lot of forums in XDA, but without luck....
So I first start with my background about restoring and flashing devices.....
MY first flashing device was a Galaxy S1 with Cyanogenmod.
Later a flash 1 Galaxy Young, and after I fixed a different and default random soft bricked Galaxy Young.
My last flashed device was a S5 with LineageOS 3/4 months ago....
Im did so installing CWM when was possible, using Odin , or ADB....from Linux and W$.....
Until I get lost my last phone Galaxy S5...
So I had to buy a 2° hand phone quickly....he was working OK... for a while ....the time has passed and become more and more slowly....so I decided to make a reset factory .......very BAD IDEA... I didn't take build information....just the model...GT-I9500....
The same info appears in the Odin download Mode....
But there is no tag with SN, and IMEI neither on the back... :'-(
So I get stuck in the Download mode ...but there IS NOT TAG about ODIN mode in this screen.....at least if
unplug the battery, and restart the phone holding PWR+HOME+VOL. DOWN .
[ EDIT ]
Trying to flash stock firmware with Kies ( who request a valid SN, what I take from web ) in the next models
GT-I9505
GT-I9500
give me this message ( in spanish =) ) ==> "este modelo no admite la inicializaciòn" , which means " this model cannot be initialized" .
[ end EDIT ]
I also tried smash (softly...covering with a canvas ) the power button...but without luck...
Seems like the phone is factory locked..... what I had read may be by AT&T or Verizon....any way to know which dealer?
Any idea or recomendation where to start ???
Its ( maybe ) JTAG cable the ONLY way/solution to fix this, or even this is NOT a solution...?
I will waiting for your answers....
TIA
PS: sorry if I made some mistakes with the english
Odin doesn't recognize the phone?
Rhoban said:
Odin doesn't recognize the phone?
Click to expand...
Click to collapse
Hello Rhoban, and thanks for your reply!!!!
and YES, Odin recognize the phone, the flash result is PASS, but the phone continues stucked on the same "Download" screen...
Because I dont have SN and IMEI neither, I dont know which ROM to flash..
After tryed to reset factory whithout luck, I tried to flash lineage, without any result.
Also because I cant unlock bootloader, I supposed to the phone was from Verizon or AT&T.
I tried to flash this ROMS's , setting the image on AP field from Odin
Verizon
I545VRUAME7_I545VZWAME7_I545VRUAME7_HOME.tar.md5
I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_HOME.tar.md5
From doidview ==> I545VRUGOC1_I545VZWGOC1_I545VRUGOC1_HOME.tar.md5
also i tried to flash the next PIT files and same result...nothing changed
SCH-I545.pit
SGS-I337_16GB.pit
adonis.pit
an this bootchain and bootloaders setting up on BL tab:
I545_OC1_Stock_Kernel.tar.md5
NB1-Boot.tar.md5
VRALEC.bootchain.tar.md5
From droidviews.com ==>
I545_NC5_Stock_Kernel.tar.md5
I545_NG6_Stock_Kernel.tar.md5
I know all above is a mess , but the list is the most detailed I can :silly:
thanks again!!!!
PS: I want to put the source link where I take the kernel images and ROM's , but because I'm newbie
( --- ALL new users prevented from posting outside links in their messages. ----), I can't
X00D45 said:
Hello Rhoban, and thanks for your reply!!!!
and YES, Odin recognize the phone, the flash result is PASS, but the phone continues stucked on the same "Download" screen...
Because I dont have SN and IMEI neither, I dont know which ROM to flash.
Click to expand...
Click to collapse
Hi, the same download screen before you started flashing? Do you have "no reboot" ticked? (Heimdall user sorry) After pass just restart the phone and wait 10 min or so.
Also because I cant unlock bootloader, I supposed to the phone was from Verizon or AT&T.
Click to expand...
Click to collapse
Never read into this, but resources are there( Seen some topic titles), there is hope for Verizon and AT&T users.
also i tried to flash the next PIT files and same result...nothing changed
SCH-I545.pit
SGS-I337_16GB.pit
adonis.pit
Click to expand...
Click to collapse
Did you have a backup? Flashing the wrong pit file might hardbrick your phone. I guess the above where blocked bij Odin (Lucky you).
In short:
Connect your phone in download mode> open Odin> click PDA or AP > Select the stock firmware > start.
You mentioned your device being a GT-I9500, but the ROMs you said you have downloaded are for I545 and I337, both of which are Snapdragon models. The GT-I9500 is the Exynos model.
So that may be your problem.
Thanks LexHimself for your advices! I had backed up already the contacts and pics.
and thanks Rhoban ....for you suggest I have to start again from the beggining, looking for the rigth ROM for my device... so thanks for put spot on the processor model !!!!
So I gonna start again, looking for the right ROMS...
I will post as soon has news about flashing Exynos rom´s....
thanks guys!!!
[SOLVED] !!!!
Hello guys!!!!
As Rhoban point me, I have to look for the right recover image ,and ROM for my phone GT-I9500, with Exynos processor, who has code JA3G, so with that code I can address well .
So I download this recovery image "philz_touch_6.12.8-i9500.tar.md5", and after install, I download and install the right LineageOS ROM for my system.....
but this would not have happened, if I would started for look for the processor model as FIRST STEP...
so THANKS SO MUCH RHOBAN, and thanks LexHimself for your advices!!!!
??????
Cheers!!!!