Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
you custom flashed??
what do u mean u custom flashed??
Get a rom with bootloader in it. Don t use repartition. Make sure you flash the bootloader.
Sounds like you wiped from a stock Samsung kernel, which is a big no no. The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage. If you search hard enough, you'll find a thread about it. I successfully recovered a phone I bricked way back with the first LP1 ICS kernel. It does work! You'll lose some space though.
http://forum.xda-developers.com/showthread.php?t=1667886
And there's the thread I was talking about.
tibosee said:
Get a rom with bootloader in it. Don t use repartition. Make sure you flash the bootloader.
Click to expand...
Click to collapse
Can you send me a link with a rom which has this please?
Here i had the same problem when I tried to flash my first rom. Just tried to flash on another computer and guess what... Successfully done!
Sent from my GT-I9100 using Tapatalk 2
smalmagal said:
Sounds like you wiped from a stock Samsung kernel, which is a big no no. The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage. If you search hard enough, you'll find a thread about it. I successfully recovered a phone I bricked way back with the first LP1 ICS kernel. It does work! You'll lose some space though.
http://forum.xda-developers.com/showthread.php?t=1667886
And there's the thread I was talking about.
Click to expand...
Click to collapse
Yes I factory reset a STOCK ICS ROM .. please can you assist in what I need to do.. Which PIT file and which ROM Shall I try to flash with.. please assist.. Many thanks..
Thanks for your help guys .. followed the german dudes tutorial and downloaded the .PIT file and managed to re flash stock ICS .. Now the only issue is my internal memory is showing 8.24 GB.. what happened to the other approx 8GB? I thought the Note was 16GB? Before windows used to show it as 11GB but now showing 8.24 GB is there a fix for this or is the bad or do I have to live with it.. ?
read the whole tut again it tells you why since you have to move partition tables.
Yes...it's a rather small deal anyway...there are 64gb SD card after all.
mkohman said:
Thanks for your help guys .. followed the german dudes tutorial and downloaded the .PIT file and managed to re flash stock ICS .. Now the only issue is my internal memory is showing 8.24 GB.. what happened to the other approx 8GB? I thought the Note was 16GB? Before windows used to show it as 11GB but now showing 8.24 GB is there a fix for this or is the bad or do I have to live with it.. ?
Click to expand...
Click to collapse
My advice is "live with it". Coz what the "German dudes" pit files do is avoid the "locked" sectors in your internal card. While you can try different pit files or try create new partitions via adb -- you probably wont gain much.
Or you could send it to Sammy for a warranty claim, after resetting the flash counter and then bricking it again via odin using the original pit file. Basically what you need to do is erase all evidence that u tampered with it. This is a risky option... (You can tell them phone got messed up in kies upgrade). This happened to me (on an almost new note, so i kinda did the same, except that i went a step further and deleted the boot-loader as well = hard brick. However i dont recommend it). And they replaced the phone.
I emphasize again this is risky -- and do more research before if you do this.
Problem as of now is since you've modified the pit -- and also the phone is working, you cant claim now.
nipuna said:
My advice is "live with it". Coz what the "German dudes" pit files do is avoid the "locked" sectors in your internal card. While you can try different pit files or try create new partitions via adb -- you probably wont gain much.
Or you could send it to Sammy for a warranty claim, after resetting the flash counter and then bricking it again via odin using the original pit file. Basically what you need to do is erase all evidence that u tampered with it. This is a risky option... (You can tell them phone got messed up in kies upgrade). This happened to me (on an almost new note, so i kinda did the same, except that i went a step further and deleted the boot-loader as well = hard brick. However i dont recommend it). And they replaced the phone.
I emphasize again this is risky -- and do more research before if you do this.
Problem as of now is since you've modified the pit -- and also the phone is working, you cant claim now.
Click to expand...
Click to collapse
Thanks for your assitance bro.. I will live with it. .I don't mind loosing 3 gb .. Already got 32GB SD card so no issue. Just happy its all back up and running really.. Big thanks to the German brother you the man
Its Forest1971 who first wrote this workaround and it was hg42 who rewrote the pit file and it was Dr null who proposed this way, Its all XDA members who helped you out of this brick. Not some German sites. Google throws up German results first
I am not harsh by anyway saying this. Just want to write it as it happened.
Was witnessing all the issues.
I am writing a guide for Noobies for bricks. Guess I get some help ....
prabhu1980 said:
Its Forest1971 who first wrote this workaround and it was hg42 who rewrote the pit file and it was Dr null who proposed this way, Its all XDA members who helped you out of this brick. Not some German sites. Google throws up German results first
I am not harsh by anyway saying this. Just want to write it as it happened.
Was witnessing all the issues.
I am writing a guide for Noobies for bricks. Guess I get some help ....
Click to expand...
Click to collapse
I actually followed his guide and repartioned manually and only lost about one Gbyte vs using the pit file and losing over 3 G bytes. Took a lot of trial and error though
Sent from my GT-N7000 using Tapatalk 2
RE:
mkohman said:
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
Click to expand...
Click to collapse
hi! i was in the same state as you! now, listen very carefully. Now, all you have to do is to use another PC and run ordin. Everything should work fine! My note was soft-bricked yesterday night and i had tried endless counts of tries just to get it up and running. Just earlier today,I saw someone who posted a comment in a similar forum and suggested that you should try a different PC it worked. AND IT worked for me now, just use this pit file that i had upload and download any (G-N7000)stock firmware that has (code.md5, modem.md5 and csc.md5). just place the pit file in ordin. ( do note you will lose 3gb of your internal memory) and click start hopefully it worked for you
-yours truly-
zairui from Singapore
can you contact entropy before sending your unit to samsung??
entropy is looking, if im not mistaken, for a purely stock bricked note... kindly pm him
zairui said:
hi! i was in the same state as you! now, listen very carefully. Now, all you have to do is to use another PC and run ordin. Everything should work fine! My note was soft-bricked yesterday night and i had tried endless counts of tries just to get it up and running. Just earlier today,I saw someone who posted a comment in a similar forum and suggested that you should try a different PC it worked. AND IT worked for me now, just use this pit file that i had upload and download any (G-N7000)stock firmware that has (code.md5, modem.md5 and csc.md5). just place the pit file in ordin. ( do note you will lose 3gb of your internal memory) and click start hopefully it worked for you
-yours truly-
zairui from Singapore
Click to expand...
Click to collapse
Not necessary to use the 3gb regain patch.
There's a 1gb or 2gb regain patch also. And it's enough.
WJ
Sent from xda-developers Galaxy N7000 ICS 4.0.4 LRK / CriskeloROM v.11.1 / Speedmod K3-12
---------- Post added at 11:34 PM ---------- Previous post was at 11:26 PM ----------
mkohman said:
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
Click to expand...
Click to collapse
Though so many ppl told u alrd, i just want to say, in any case, when u r in ICS alrd, it is totally prohibited to do factory reset through CWM with samsung ICS original kernel.
When u need to wipe or factory reset, make sure u r on a safe kernel like speedmod or notecore.
If u want to recover ur note, just use the pit file method. It works.
Make sure u use the correct patch of 16gb or 32gb, depends on ur note.
Always try from the smallest patch, so u won't loose so many storage.
Anyway, latest CriskeloROm with speedmod is the best for battery life nd performance.
WJ
Sent from xda-developers Galaxy N7000 ICS 4.0.4 LRK / CriskeloROM v.11.1 / Speedmod K3-12
I'm having the same issue now.
I did wipe data / factory reset with stock ICS kernel and I think, I bricked the Note.
I didn't know there were such issue.
I couldn't find a ROM with 3 files (code.md5, modem.md5 and csc.md5).
Please kindly guide me where to find such ROM.
i bricked mine last week and used the patched pit files to restore i went through a few pit files b4 i found one that worked i now have about 9 gb nand left but my phone works and has jb on it now
anubis1126 said:
i bricked mine last week and used the patched pit files to restore i went through a few pit files b4 i found one that worked i now have about 9 gb nand left but my phone works and has jb on it now
Click to expand...
Click to collapse
So we dont need 3 files ROM?
Related
hello gentlemen,
I was rooting my phone, but it seems it wasnt successful. the phone kept restarting and restarting all over again.
I had version 2.3.3 on it.
and because I am not techy enough, I thought to root it again...now the phone is not booting at all...
when I switch on the phone I get a picture of a mobile and a pc and an exclamation mark between them
I can go to the download / recovery mode...
any help on how to recover my phone...
phone is Samsung galaxy S GT i9000
First of all: your Galaxy is NOT dead.
Just flash a FW with bootloader, PIT-file and Re-Partition via Odin and it will boot again.
Sent from my GT-I9000 using XDA App
My suggestion is to go to development and find the ezbase rom, it has excellent instructions with screen shots, and offers stock froyo or gingerbread with root and recovery pre installed
GTi9000 insanity cm012/glitch
Guys, I had a similar problem with my I9000T ... I was opening a game and then from out of nowhere it freeze, and then reboot... he got a lot of time stuck on the boot screen... after some time he showed a message saying that my UID was with problems... I had the I9000T on official firmware 2.3.3 (updated via kies)
Seem to happens a lot with galaxy S models, and people allways tell to download a rom and flash it with ODIN...
The problem with is that odin didn't recognize my phone... Don't know why... I have an Windows 7 64bits , installed the samsung drivers properly, but, he never get to recognize the phone on download mode... Can someone help me, give me some clue, please, I really need your help.
Thanks a lot dudes...
Lunchbox115 said:
First of all: your Galaxy is NOT dead.
Just flash a FW with bootloader, PIT-file and Re-Partition via Odin and it will boot again.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
can you please help me with a link?? I am thankful for your reply
dany khalife said:
can you please help me with a link?? I am thankful for your reply
Click to expand...
Click to collapse
http://www.samfirmware.com/
You will need to Register to be Able to download the Firmwares.
Odin (The Tool you use to Flash) And the PIT Files are on there too.
Read http://www.samfirmware.com/SVC Android/I9000 Flashguide.pdf
Before you start messing about
slaphead20 said:
My suggestion is to go to development and find the ezbase rom, it has excellent instructions with screen shots, and offers stock froyo or gingerbread with root and recovery pre installed
GTi9000 insanity cm012/glitch
Click to expand...
Click to collapse
thank you very much for this, I recovered my phone. however, two problems appeared:
1. couldnt import the .vcf file from my external SD card to the phone contacts.
2. it doesnt support arabic
can you please advise...
thanks again for your support.
dany khalife said:
thank you very much for this, I recovered my phone. however, two problems appeared:
1. couldnt import the .vcf file from my external SD card to the phone contacts.
2. it doesnt support arabic
can you please advise...
thanks again for your support.
Click to expand...
Click to collapse
Download GB 2.3.3 JPJV6 (Arabic firmware) from here: http://forum.xda-developers.com/showthread.php?t=1102881
or here :http://forum.xda-developers.com/showthread.php?t=1011901
you don't have to register and the archives are not protected by stupid passwords.
Flash: without pit or re-partition.
To root: follow the method under 'How to root...' from the second link above.
Guys, My galaxy S is still dead, I've tryied toomany roms, nothing worked... What is odd for me is that I wipe my data, format my sdcard via recovery, but all my files are still on the sdcard, and if I delete it using the USB via PC, when I boot my phone it "recovers" all the data, back to SD... someone has some tip, info, help for me?
This Thread Is For Them Who Bricked There Phones
Don't start a new thread for your bricked phone & post here.
We will help you with every possible solutions.
Here are some quick tips :
(Here I'll use the terms like Download-Mode & Recovery-Mode, If you dont know what are they please click here. There "BOOT to RECOVERY" & "BOOT to BOOTLOADER" means how to enter into Recovery-Mode & Download-Mode respectively.)
A Bricked Phone May Have One or More (Below Problems) :
1. Booting to the ROM(Android) not possible.
2. Booting to the Recovery-Mode not possible.
3. Black screen or Bootloop(Repeated Restarting of Phone at Boot Animation or Samsung Galaxy Y Logo).
Possible Solutions :
(Remember there'll be data loss using these solutions so always try to keep a backup)
1. If you can still enter into Recovery-Mode
(a). Try to clear Data & Cache then check.
(b). Try Installing a Custom ROM using CWM(ClockWorkMod Recovery) & check.
(For Custom ROM & CWM Visit here.)
2. If Recovery-Mode didn't helped Enter into Download-Mode & flash an odin supported stock rom(using ODIN 1.84 or 1.85) from Doky73's Thread(Flashing Guide in 2nd post).
*You can inform me, if anything left out.
Note :
1. I'll be not held responsible for anything that happens to your phone.
2. Before posting try to search for similar type problems out there & try the solution, if that doesn't solve your problem then post here.
Make this a sticky.. there are many users who say that their phone is bricked
help! bricked SGY
galaxy y bricked
i bricked my sgy last 3 weeks.
here's what i did.
-installed creedsix rom.
-installed UOT kitchen Themes.
-wipe data
problem
-stuck in bootlogo
-softbricked.
-cant go to recovery mode
-flashed too many times, still stuck in bootloop
i flashed at least 20 times, with different firmwares.
but still no luck, still boot lop.
my professor said something about secondary bootloader that might help. but i had definitely no idea what it is.
i asked some techies on the mall, and they said that this phone must undergo the JTAG process. but it cost $20.
help me. thanks.
jmpotter said:
galaxy y bricked
i bricked my sgy last 3 weeks.
here's what i did.
-installed creedsix rom.
-installed UOT kitchen Themes.
-wipe data
problem
-stuck in bootlogo
-softbricked.
-cant go to recovery mode
-flashed too many times, still stuck in bootloop
i flashed at least 20 times, with different firmwares.
but still no luck, still boot lop.
my professor said something about secondary bootloader that might help. but i had definitely no idea what it is.
i asked some techies on the mall, and they said that this phone must undergo the JTAG process. but it cost $20.
help me. thanks.
Click to expand...
Click to collapse
can you go to download mode??
(try pressing volume down+ home button + power button all at the same time)
if it still can, then your SGY is still good
go to this ---> thread
and just flash your country's firmware
From where you got the firmwares.... How you flashed...
Ever tried re partitioning.... Ever flashed boot loader....
For info... Jtag or boundary-scan is used for testing & servicing high technology electronic boards...
Sent from my GT-S5360 using Tapatalk 2
Millan.SIS said:
From where you got the firmwares.... How you flashed...
Ever tried re partitioning.... Ever flashed boot loader....
For info... Jtag or boundary-scan is used for testing & servicing high technology electronic boards...
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
just for info, jtag will not fix the problem. IT IS SCANNING.. like trouble shooting.
that only means that those technicians are pretending to be well educated but the truth is that they only wanted to get some cash out of your pocket.
static28 said:
just for info, jtag will not fix the problem. IT IS SCANNING.. like trouble shooting.
that only means that those technicians are pretending to be well educated but the truth is that they only wanted to get some cash out of your pocket.
Click to expand...
Click to collapse
ya, that's what those wannabees really do..
Sent from my GT-S5360 using Tapatalk 2
this one will a little bit off topic...what is creedsix?is it a rom for SGY?
if the phone still can boot that means everything is fine. pull out the battery, wait 10 seconds, reinsert the battery, do three magic combo button, you'll enter recovery mode. don't worry about our bootloader. our bootloader is stored in different partition thus installing any custom rom won't affect our bootloader. as far as i know, there is only one person who have messed up with bootloader and got an ultimate hard brick.
kurotsugi said:
this one will a little bit off topic...what is creedsix?is it a rom for SGY?
if the phone still can boot that means everything is fine. pull out the battery, wait 10 seconds, reinsert the battery, do three magic combo button, you'll enter recovery mode. don't worry about our bootloader. our bootloader is stored in different partition thus installing any custom rom won't affect our bootloader. as far as i know, there is only one person who have messed up with bootloader and got an ultimate hard brick.
Click to expand...
Click to collapse
Really its great thread ........ Many many thanks for helping ppl ......
is it possible repair hard brick ..... what is hard brick... if device hard brick device gos life time dead ??
Sent from my GT-S6102 using xda premium
a hard brick is when our device doesn't respond to power button.
the guy that I've mentioned above is doky73. he accidentally flash a bootloader for sgs2 into his sgy. last time he said that he send his sgy to samsung service center and buy a new one. I'm not sure if samsung has revived his sgy.
edit: I didn't to offend him but I think I've mispelled doky's username. edited.
manoranjan2050 said:
Really its great thread ........ Many many thanks for helping ppl ......
is it possible repair hard brick ..... what is hard brick... if device hard brick device gos life time dead ??
Sent from my GT-S6102 using xda premium
Click to expand...
Click to collapse
whatever It may be... You should never mess up with bootloaders, if you don't actually know what's there significance...
Brief description on android starting process :
pbl(primary boot loader "boot.bin") executes first and then it executes sbl ...
Sbl(secondary boot loader "sbl.bin") is responsible for responding to combos...download mode.. Intercepting odin commands..... booting system...booting kernel.... Charging your battery while switch off... Etc etc
Harm anyone of them... And Your phone goes into lifetime hibernation, Hard-bricked.
Sent from my GT-S5360 using Tapatalk 2
thanks for the big info friend...... so hard bricl is mot repairble ......
Sent from my GT-S6102 using xda premium
my device might be bricked, can you please help me out
Hi to all, it's only my second post but i have a major problem with my samsung s-5360. it's won't boot anymore, but it can enter cmw and recovery. This is what i did wrong i believe. At first i installed morocs 1.8 kernel on creed fusion version 3.1 and it wouldn't boot anymore, so i ended up using a back-up i made before with cmw. And it worked well and phone was booting again and was on stock again. ( because back-up was made with stock-version obviously )
Then i thought: well let's try repensis noob version. And installed it and there was also an update 2 and installed it over it as well before booting the os, maybe this is what i did wrong dunno .. But afterwards it didn't boot anymore and whatever i tried, restoring one of the 3 images i made, or using one of the roms posted here like Creed fusion 3.1 rom or Aurora 2 nor Chobits didn't work.
I also tried reverting to stock with odin 1.85 but when i connected my phone via usb to the pc, odin didn't see my phone. ( after selecting the 3 tar files in odin ) Maybe i'm doing wrong something there.
What i also have to add is that when doing factory wipe in recovery it says formatted E: but unable to format E:\dev10 and dev11. clearing cache is no problem and also cleared dalvik cache. Can you please help me out ? I know, it sounds very noobish but well, i have to face it because can't do it myself without help anymore it seems ... Thanx a lot in advance.
please make sure that you've installed the driver and plug the usb to computer only on download mode when flash with odin. dev10 and dev11 are the partition for data and cache. that error means something was wrong with your recovery mode. you'll need to install a fresh stock rom with odin.
kurotsugi said:
please make sure that you've installed the driver and plug the usb to computer only on download mode when flash with odin. dev10 and dev11 are the partition for data and cache. that error means something was wrong with your recovery mode. you'll need to install a fresh stock rom with odin.
Click to expand...
Click to collapse
Thanx a lot for responding ! I only used kies for connecting my phone because i couldn't find a driver for it, and had to disconnect it, but i will search for it again now and hopefully it will work now. i have to go now and return back in three hours. i'm very curious ! i'll come back in a couple of hours and gonna tell if it worked out of course
kurotsugi said:
a hard brick is when our device doesn't respond to power button.
the guy that I've mentioned above is doky77. he accidentally flash a bootloader for sgs2 into his sgy. last time he said that he send his sgy to samsung service center and buy a new one. I'm not sure if samsung has revived his sgy.
Click to expand...
Click to collapse
to be precise: the guy was Doky73...
I was playing with different revisions of SBLs because on SGS2 some old SBL gives the possibility to reset custom bin counter via JIG. At a given point accidentally browsed SGS2 bootloader instead of SGY one...
But I did perfect job, the service center wasn't able to detect the cause of bricking, but they recovered my phone under warranty. (I think they're not reading this forum )
Doky73 said:
to be precise: the guy was Doky73...
I was playing with different revisions of SBLs because on SGS2 some old SBL gives the possibility to reset custom bin counter via JIG. At a given point accidentally browsed SGS2 bootloader instead of SGY one...
But I did perfect job, the service center wasn't able to detect the cause of bricking, but they recovered my phone under warranty. (I think they're not reading this forum )
Click to expand...
Click to collapse
Thanks friend.............
if i install some custom rom custom kernel via odin or CWN its gos to hard brick ???
in odin re-partition option for why ............ its disbl by default if i enable it wats problem........
dear friend if u have any odin full tutorial /guide /ref please provide me for learn syep by step one by one option or problem......
ops...my mistake. I guess I'm too sleepy when was typing your name. I'll edit it. sorry.
manoranjan2050 said:
Thanks friend.............
if i install some custom rom custom kernel via odin or CWN its gos to hard brick ???
in odin re-partition option for why ............ its disbl by default if i enable it wats problem........
dear friend if u have any odin full tutorial /guide /ref please provide me for learn syep by step one by one option or problem......
Click to expand...
Click to collapse
if u flash something through odin or cwm then you wouldnt hard brick ur phone.. it would be just a temporary brick which can be easily revived... i dont know abt that partioning thing
Sent from my GT-S5360 using XDA
kurotsugi said:
please make sure that you've installed the driver and plug the usb to computer only on download mode when flash with odin. dev10 and dev11 are the partition for data and cache. that error means something was wrong with your recovery mode. you'll need to install a fresh stock rom with odin.
Click to expand...
Click to collapse
Hi, there i am and sry for disturbing you again or someone else but i managed to install a non kies usb driver and i'm flashing thru odin 1.85 right now but i'm stuck at BcmCP.img for over an hour . Is it because i forgot to remove the sd card ? I only removed the sim and is it safe to stop the process and start over again or should i wait ?
---------- Post added at 02:35 AM ---------- Previous post was at 01:47 AM ----------
mickeyindahouse said:
Hi, there i am and sry for disturbing you again or someone else but i managed to install a non kies usb driver and i'm flashing thru odin 1.85 right now but i'm stuck at BcmCP.img for over an hour . Is it because i forgot to remove the sd card ? I only removed the sim and is it safe to stop the process and start over again or should i wait ?
Click to expand...
Click to collapse
Well after trying this proces for the 5th time i finally managed to go to stock rom and it only lasted a couple of minutes Of course thanx to doky73 who made all this possible ! So i unbricked it for the second time i guess
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.
Hi all,
I think I have soft bricked my S4 i337m rogers Canadian variant.
I had rooted / unlocked the bootloader with motochopper successfully.
- I am using CWM
First thing I tried to do was backup the phone onto the external SD which would not work so I just went onto the next step.
I tried flashing a ROM onto the phone after doing phone restore and clearing cache. All installed correctly (apparently) and now when I boot up the phone the Samsung logo will appear for about 5 seconds then the phone will go black and try to boot up again.
The good:
- i have access the recovery mode still
The bad:
- no recovery made for the phone
- seems to be boot looping
As a side not I have tried installing a couple other ROMs which all result in the same issue.
Is there anything that can possibly be done?
I would happily put the stock ROM back on the phone.
All help would be greatly appreciated!
Rob.
9 times out of 10 a factory reset will get you out of a boot loop. Do that in recovery and reboot.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi thanks for the reply. I have tried the factory reset and still does not fix the issue
Robby29 said:
Hi thanks for the reply. I have tried the factory reset and still does not fix the issue
Click to expand...
Click to collapse
If you are flashing a custom ROM that is not specifically for your phone, say a i9505 rom, you need to flash a Canadian kernel right after or you will bootloop. You also cannot flash any loki based roms either. As for the CWM backups, are you trying to back up to your external SD? If so, ensure the card is formatted fat32. To help get through your softbrick, just get into download mode and flash with odin
kiru said:
If you are flashing a custom ROM that is not specifically for your phone, say a i9505 rom, you need to flash a Canadian kernel right after or you will bootloop. You also cannot flash any loki based roms either. As for the CWM backups, are you trying to back up to your external SD? If so, ensure the card is formatted fat32. To help get through your softbrick, just get into download mode and flash with odin
Click to expand...
Click to collapse
Okay great I will try these. Does the kernel have to be specific to the ROM?
Robby29 said:
Okay great I will try these. Does the kernel have to be specific to the ROM?
Click to expand...
Click to collapse
The kernel is specific to your device. so you would use the i337M kernel.
So the procedure would be flash the rom of your choice, then before you boot flash YOUR i337M kernel, it will boot.
Good luck.
And make sure you do not flash a rom for the i9500 as you will hard brick
Also,
Make sure you choose the right i337m kernel. ie. a TouchWiz kernel for TW Roms and an AOSP kernel for CM10.1/AOSP Roms.
You should be able to:
remove your sdcard,
format it to fat32,
download the correct rom and kernel for you i337m to your freshly formatted sdcard,
put the card back into your phone,
boot into recovery,
install ROM zip from ext-sdcard,
install Kernel zip from ext-sdcard,
reboot.
phew....sounds like a lot of steps but not really I guess.
we good up in here....
Soft Brick S4
TheAxman said:
we good up in here....
Click to expand...
Click to collapse
Hello,
Greetings to you, I am sorry you have come to this point. I myself have bricked my phone just yesterday from flashing a bad ROM and not backing up my ROM properly. But I hope I can help you with some tips that i did to recover my phone fully. I apply some links to help you out but I recommend some patience lots of HW. ( Kies didn't work for me bugger =p.)
Unbrick S4 [Guide] -- http://forum.xda-developers.com/showthread.php?t=2265477&page=40
there is a user by the name of samersh72. you can request for a link to download your correct firmware it's best to get back to stock, ( don't forget to thank the user . )
this is someones video on youtube: http://www.youtube.com/watch?v=3a3qghhpDxg ( this helped me out as well)
I have these files/programs readied when I reverted back to stock
odin 1.3 ( i have odin 3.0 and didn't work for me reverting stock as it couldnt detect my tar.md5 file, but for some reason it worked for odin 1.3)
have your correct firmware ( I downloaded mine from http://www.sammobile.com, but for some reason I can't find yours, there is one on this site for sure just have the patience to look) make sure its for your correct carrier too.
im pretty sure you know how to do the DL mode, but just incase ill assume that you may or may not know, ill type this in anyway:
Get your S4 Download mode, [pressing up+power+home], (sometimes if i feel its not kicking in, just quick release then do it again)
open your odin 1.3, plug your phone in, tick auto-reboot, and F. reset time. PDA ticked, then find your correct firmware. hit start, then i hope from this something good will come out.
Best of wishes in your journey here in xda.
Cheers!
car154 said:
Hello,
Greetings to you, I am sorry you have come to this point. I myself have bricked my phone just yesterday from flashing a bad ROM and not backing up my ROM properly. But I hope I can help you with some tips that i did to recover my phone fully. I apply some links to help you out but I recommend some patience lots of HW. ( Kies didn't work for me bugger =p.)
Unbrick S4 [Guide] -- http://forum.xda-developers.com/showthread.php?t=2265477&page=40
there is a user by the name of samersh72. you can request for a link to download your correct firmware it's best to get back to stock, ( don't forget to thank the user . )
this is someones video on youtube: http://www.youtube.com/watch?v=3a3qghhpDxg ( this helped me out as well)
I have these files/programs readied when I reverted back to stock
odin 1.3 ( i have odin 3.0 and didn't work for me reverting stock as it couldnt detect my tar.md5 file, but for some reason it worked for odin 1.3)
have your correct firmware ( I downloaded mine from http://www.sammobile.com, but for some reason I can't find yours, there is one on this site for sure just have the patience to look) make sure its for your correct carrier too.
im pretty sure you know how to do the DL mode, but just incase ill assume that you may or may not know, ill type this in anyway:
Get your S4 Download mode, [pressing up+power+home], (sometimes if i feel its not kicking in, just quick release then do it again)
open your odin 1.3, plug your phone in, tick auto-reboot, and F. reset time. PDA ticked, then find your correct firmware. hit start, then i hope from this something good will come out.
Best of wishes in your journey here in xda.
Cheers!
Click to expand...
Click to collapse
Thanks for posting this. I hope many people read it. Anyone who flashes needs to know how to return to stock before they start flashing roms. You will need it someday!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi guys, i have some big problems with my n910f, tried to upload a pic to facebook and my phone crashed.
It simply does nothing, not booting, not charging, download and stock recovery are working.
I tried everything possible>
*flashed 3 different stock firmwares with odin
*tried a pit file repartion in odin
*wiped cache, did a few factory resets from stock revovery
*bought a new battery
*tried to root and flash a custom recovery but doesnt work
It is simply as bricked as it could be, the only information about this i have is stock recovery telling me unable to mount /data
So it seems my filesystem got corrupted as hell
The question is, how do i repair it?
Like i said pit file and bootloader flash did nothing, odin lets me flash everything without an error but it doesnt help.
I assume i could somehow repair it with adb fastboot but how?
Any help is welcome!
atilla88 said:
Hi guys,
Any help is welcome!
Click to expand...
Click to collapse
It may or may not help but I would sure try Kies. You NSFW get done errors like Kies telling you is not compatible bit but I would try the firmware initialization.
CodeNameRedNeck said:
It may or may not help but I would sure try Kies. You NSFW get done errors like Kies telling you is not compatible bit but I would try the firmware initialization.
Click to expand...
Click to collapse
Well i forgot to mention that i tried kies aswell, everyhting went good but didnt help, still nothing.
It confuses me a bit that it doesnt even charge, could a broken filesystem lead to this?
atilla88 said:
Well i forgot to mention
Click to expand...
Click to collapse
I am not sure what parts of the system need to be working for the battery to be able to charge. Good luck.
CodeNameRedNeck said:
I am not sure what parts of the system need to be working for the battery to be able to charge. Good luck.
Click to expand...
Click to collapse
did try root=> costum recovery for your variant => installing costum roms for your variant (all can be done with odin +sd card and some fils on it) but warranty is lost it may worth the try
did you try the 5 flashing fils(pit pda bl csc phone) to initial stocks with odin
ZOHUHRZED said:
did try root=> costum recovery for your variant => installing costum roms for your variant (all can be done with odin +sd card and some fils on it) but warranty is lost it may worth the try
did you try the 5 flashing fils(pit pda bl csc phone) to initial stocks with odin
Click to expand...
Click to collapse
i have the same problem, do you know where can we find the complete 5 files (pit pda bl csc phone) for flashing with odin?
its the only thing i haven't already tried.
I manage to fix the issue with storage partition, i used a pit file and the one file firmware in csc button, that made the hole data partition rewriten again so the phone is able to boot properly.
Hope you gays this may help.
Happy new year!!
heratis said:
I manage to fix the issue with storage partition, i used a pit file and the one file firmware in csc button, that made the hole data partition rewriten again so the phone is able to boot properly.
Hope you gays this may help.
Happy new year!!
Click to expand...
Click to collapse
What makes you assume we're all gay?
Sorry pal, i better watch my grammar, i ment guys.