Database Users

Safe way to load Froyo on i9000m Bell Mobility Galaxy's

Okay, so after corrupting my SD card over 12 times and replacing my phone twice I think I have found the answer.
I strongly believe that the reason we get faced with the SD corruption (The ones where it is fixable by a software reset at the service center) on our i9000m's is because we repart while flashing.
The 512,513,903 pit files might be okay on international models, but I suspect that the Canadian version uses some other partition structure.
So to keep it short here is a successful method to install froyo on the i9000m. I have flashed to froyo using this method and have been using it for over 20 days now without issues.
Make sure you get a brand new phone before flashing. If you have reparted using odin this might be useless.
Installation Steps:
1. Make sure your phone is rooted (You can root via OCLF in the market)
2. Download Rom manager and install Clockworkmod recovery (Instructions can be found here - http://forum.xda-developers.com/showthread.php?t=734166&highlight=clockwork)
3. Install Doc's froyo rom from here ( http://forum.xda-developers.com/showthread.php?t=817703)
Once flashed it should work fine. When the phone starts make sure you first see the I9000M screen and then it switches to the I9000 screen and then the Galaxy and then into Froyo.
I have not tried just flashing froyo using ODIN without re-parting (Maintaining factory partitions). In theory it should work, if anyone tries it let us know.
P.S. I use Doc's rom as it allows to flash via clockwork. I am not endorsing this in any way.

I have personally flashed dozens of things through Odin with 512 and 803 pit, as well as tons of things through zip's like Doc's, with absolutely no problems on my Bell I9000M 16GB.
**Knocks on wood**

Do you lose your 850 Band doing it by this method. Please check by Activating WiFi while in your service menu (*#*#0011#*#*). You will see when you switch over from WiFi to 3G you Band should drop down to 850 from 1900.

Woolios said:
Do you lose your 850 Band doing it by this method. Please check by Activating WiFi while in your service menu (*#*#0011#*#*). You will see when you switch over from WiFi to 3G you Band should drop down to 850 from 1900.
Click to expand...
Click to collapse
WelCOME HOME OCRF's, Happy Flashing. http://forum.xda-developers.com/showthread.php?t=823702

rumy said:
I have not tried just flashing froyo using ODIN without re-parting (Maintaining factory partitions). In theory it should work, if anyone tries it let us know.
Click to expand...
Click to collapse
I've tried this one.. Never repartitioned yet still had a corrupt sd in the end.

cloudrainstar said:
I've tried this one.. Never repartitioned yet still had a corrupt sd in the end.
Click to expand...
Click to collapse
Can you give more information on what happened.
Original ROM?
Froyo Version tried to flash to?
Which SGS ei (gt-i9000m or gt-i9000)?

I've re-partitioned in ODIN by flashing back to JH2 (2.1), then use Doc's ROM to 2.2. What should I do to enable 850Mhz? I already added WCDMA850 in *#2263#

Woolios said:
Can you give more information on what happened.
Original ROM?
Froyo Version tried to flash to?
Which SGS ei (gt-i9000m or gt-i9000)?
Click to expand...
Click to collapse
1. UGJH2
2. I believe the one that it died on was XXJPM, after about 3 days. I've flashed XXJPH and XXJPK before that on that phone as well for a few days each, no pit/re-partition every time I flashed
3. GT-I9000M

killer23d said:
I've re-partitioned in ODIN by flashing back to JH2 (2.1), then use Doc's ROM to 2.2. What should I do to enable 850Mhz? I already added WCDMA850 in *#2263#
Click to expand...
Click to collapse
Does 850Mhz Band work for you? Could you check with the above method

Woolios said:
Can you give more information on what happened.
Original ROM?
Froyo Version tried to flash to?
Which SGS ei (gt-i9000m or gt-i9000)?
Click to expand...
Click to collapse
I am an Indian & have an Asian 16GB SGS. Every time & have this urge to FLASH, I just pick the pit file, nothing else, check re-partition, let the phone reboot, remove battery, re-insert, go back to download & re flash.

Me n 2 friends bought it together from same bell store 3 months ago.
Friend 1 :
On his 2nd sgs.
Got it replaced because internal sd got corrupted.
He was on jpk w/ repartition done
Friend 2 :
Still on his original sgs.
Stock + voodoo (aka never used odin)
Me:
On my 3rd sgs (if u count replacing the pcb as a new phone)
First one was stock + voodoo (stock was flashed using repartition through odin)
Second one was jpk w/ repartition
Third one im running with stock + voodoo (aka following friend #2's approach)
Hope tht helps :\

rumy said:
Okay, so after corrupting my SD card over 12 times and replacing my phone twice I think I have found the answer.
Click to expand...
Click to collapse
That's dedication right there.

ragin said:
I am an Indian & have an Asian 16GB SGS. Every time & have this urge to FLASH, I just pick the pit file, nothing else, check re-partition, let the phone reboot, remove battery, re-insert, go back to download & re flash.
Click to expand...
Click to collapse
Most of the time what I do is use Odin 1.3 Use an 803 PIT re-partition not checked at the same time select the PDA Phone and CSC since your 900MHz you should not have a problem using the GT-i9000-CSC-Multi-XXXXX.tar.md5 for CSC and the MODEM_i9000XXJPK.tar.md5 for Phone and your PDA will be JPM/JP6 or whatever rom you wish to install

cloudrainstar said:
1. UGJH2
2. I believe the one that it died on was XXJPM, after about 3 days. I've flashed XXJPH and XXJPK before that on that phone as well for a few days each, no pit/re-partition every time I flashed
3. GT-I9000M
Click to expand...
Click to collapse
Funny thing is I'm on 3rd SGS now too my first one I went crazy on Flashing everything as I had no problems with anything I did to it until JPM/JP6 I bought another SGS while I sent in the other one as a replacement for mine and as a gift for my wife after I get my SGS back from bell. The one I got for my wife died within 6 hours of flashing ROM's I use to have the 850MHz band on my original SGS throughout the whole flashing process but I couldn't repeat it with my wife's SGS. Now since I've buggered hers once already I'm now scared to do anything with this one. Although I still have the DOA warranty on it. I'm I crazy??? Probably more confused as I spent a lot of time reading on these forums and don't have an answer to what went wrong...

I have the Captivate and my girl has the I9000M. I am definitely not new in flashing, just find it very interesting that after flashing Doc's V6, the Bell APN still remained and the boot screen still has I9000M.
Did Bell do something to the phone to prevent people modding it?
So far, my gf didn't complain about corrupting SD. She got hers like 3 weeks ago and the battery production date is Oct 2010. The phone even has 3 button download mode working out of the box.

Okay so with all the excitement and multiple upgrades of docs rom I made a boo boo.
I flashed a wrong kernel (BLN) using CWM and the phone would not start and could not get into CWM. So I did a flash to UGJG8 and then restored to dock.
Things would work fine for a few hours and then I would get errors, my internal SD card was intact, however my internal available memory was 0. I repeated this process with the same issue, finally got fedup and reparteed with the 512 and it all worked for a few hours and then internal and external all said unavailable.
Now when I boot It goes to the 19000 screen and then shuts off.
However, when I load UGJG8 with my external SD it boots to android and none of the SD cards are available, but internal available says 1.85.
I am trying different things as I want to try and figure out whats going on, any suggestions?
P.S. I strongly believe it has something to do with odin and/or pit files, i.e. software fix.

rumy said:
Now when I boot It goes to the 19000 screen and then shuts off.
However, when I load UGJG8 with my external SD it boots to android and none of the SD cards are available, but internal available says 1.85.
Click to expand...
Click to collapse
Aren't those 2 the "Internal Sdcard Corruption" indicators ?
Boot into recovery. What do u see ?

Yup, I know it is the internal SD card corruption.
Ohh well.... back to the bell store
P.S. I want to highlight that all of this started once I used odin, till then I was using froyo for over a month without any issues. now it might be a coincidence but I dont think so!

I won't use odin if I don't have to. Il use cw instead
Sent from my GT-I9000m

I've flashed JPK for Phone, CSD and the other one. 512 Pit.
I did it on 2 i9000M and never had problem.
I used mine exclusively with 3G Data only though. No Calling plan attached.

Bell Internal SD Card Solution

My internal SD failed about 5 minutes after the latest update and so I started trying to flash new roms/pit combinations like a madman. This led me to the Q&A subforum, where I found this thread:
http://forum.xda-developers.com/showthread.php?t=892534
Where:
Encrypted1024 said:
WOW! I am back up and running. This appears to be a data partition issue.
Can't say exactly what I did but here it goes. I may have done these things more than once today so you may have to run through this procedure a couple of times.
- Flashed JH2 with repartition and pit 512. (Stuck in bootloop)
- Flashed JL2 with Repartition and pit 512. (Boot to S Screen now)
- Flashed with SpeedMod 12
- Boot to recovery mode
- Format every partition
- Flash to JH2 with repartion and 512 pit. (Back to boot loop)
**** Heres where it was different***
- Flash to JL2 without repartion or pit
Booted up and working.
I know, sounds sketchy, but I must have reflashed my phone with 10 different firmwares today.
After I got it booted up I flashed it with Darky's 7.6 ROM. It gave an error at first about the data parittion but it repaired itself after running lagfix and changing to ext partition.
I may recomend to flash with Darky 7.6 and apply lagfix to rebuild the partitions and see if it fixes this issue right away.
Click to expand...
Click to collapse
I did this and followed every instruction, it works perfectly. My phone went from the DBdata recovery error and unable to mount filesystem -> Darky's Rom 7.7 with all the working bands.
I urge everyone with a failed bell phone to try this, it's amazing.
Also, thanks so much to Encrypted1024 for finding this.

Why didn't you just send it back to Bell and get your new phone + $100?
I have a launch Bell i9000m that refuses to die. I've flashed via CWM and Odin many times, but it's still fine. I'd actually be happy if it died so I can get the $100 credit and a new phone....

sr3yas said:
My phone went from the DBdata recovery error and unable to mount filesystem -> Darky's Rom 7.7 with all the working bands.
I urge everyone with a failed bell phone to try this, it's amazing.
Click to expand...
Click to collapse
sorry, but dbdata errors in recovery are not the major sdcard issue that is not recoverable from. dbdata errors are recoverable via flashing, same with st10/11.
unless someone with an mmcblk0p1 issue wants to try this, i highly doubt it will work.

wang1chung said:
sorry, but dbdata errors in recovery are not the major sdcard issue that is not recoverable from. dbdata errors are recoverable via flashing, same with st10/11.
unless someone with an mmcblk0p1 issue wants to try this, i highly doubt it will work.
Click to expand...
Click to collapse
I just tried it with my mmcblk0p1 error, and it doesn't work.

jentech said:
I just tried it with my mmcblk0p1 error, and it doesn't work.
Click to expand...
Click to collapse
Agreed. I just hit my second phone with that error and haven't seen any solution to recover from it. Dead = dead.
We need to get very clear on this board between what is a truly dead phone due to sd card issues vs what is recoverable (no comment on how sucky it is to experience a recoverable issue tho).

Vibrant partitions are borked please help

My vibrant has an error of can't mount mmcblk0p1 and I can't use my external sd or install apps in recovery I can still access my external sd for some odd reason I installed a rom and then flashed voodoo and it wouldn't with after a great while so I battery pulled and used odin trio get to eugene froyo that cannot brick and my partitions aren't being read I can fix thus all if I can change the voodoo/enable-lagfix file to disable it can someone please suggest how to fix this issue I'm almost literally in a panic over this please help it'd be much obliged

I haven't had a need to but you can try to ODIN back to stock and start over again
If there's a better solution someone will post it soon here

Well thats the solution right there... Your probably gonna need eugenes froyo that doesnt brick and either JK2 or JFD .tar and ODIN back to get your phone restored to a stock version.

z0phi3l said:
I haven't had a need to but you can try to ODIN back to stock and start over again
If there's a better solution someone will post it soon here
Click to expand...
Click to collapse
I tried it won't help I'm current on the eugene that doesn't brick I just need a solution I've fixed this kind of problem before but only cuz I could access my internal sd when I boot up I can only access it through recovery now

jmcghee1973 said:
Well thats the solution right there... Your probably gonna need eugenes froyo that doesnt brick and either JK2 or JFD .tar and ODIN back to get your phone restored to a stock version.
Click to expand...
Click to collapse
I'm on eugenes froyo with no brick and I've flashed back to jfd and I get a black screen

Yea... eugenes froyo is just a step in the process. Its not a daily driver rom..You have to go back into D/L mode and ODIN JFD.tar without Repartition checked

[Q] Fascinate stuck on SAMSUNG logo, no idea what to do

So I was never into rooting phones I never really cared that much and my friend said it was really awesome so he rooted my phone then never told me anything to do with it so I seriously didn't change a single thing. I also guess he didn't mention you can't reset factory settings which is what I did and it is stuck on the samsung logo. I searched for this and read the "flash odin" that means zero to me. I absolutely have no idea what any of that is, can anyone help me? Thanks in advance!

Alas, I don't have any links to give you, but hopefully I can clarify what you need to do.
Odin is simply a program that is used for flashing software to your phone. All you do is download said program, as well as a recovery file and a PIT file (which is what is used to repartition the phone's internal memory). Your safest bet is to download the DL09 package, which will get you back to the stock android 2.1 that your phone came with. From there you can run your phone's system update to upgrade to the current version. There are instructions on how to flash through Odin, so I won't go into that. What you'll want to look for, though, is a full odin package, which means that it includes EVERYTHING, and you won't have to flash the system, radio, modem, etc. separately.
Hopefully that clears things up a bit. I was in the same boat as you recently.
EDIT: The most important thing to do is relax. I know it's scary to get such a bad error on your first crack into rooting, but Odin makes it REALLY hard to brick this phone. It's a little intimidating at first, but once you start flashing through Odin, no android issue will phase you.
http://forum.xda-developers.com/showthread.php?t=1026746 This is the thread I used when I screwed up my Fascinate. May it serve you well.

Ok, you will definitely be able to get out of this situation. Try this link https://docs.google.com/document/d/1cZAF3hzDIHSMEkf0QcFs2cLLrF5PmOUEXcM268FoIzk/edit?hl=en&authkey=CKqWypcP for some basic info. Look through these forums/internet and download ODIN (any version should do). Find a link to the DL09, ED01, or ED04 odin files for the full rom and a link for the atlas_v2.2.pit file. Make sure the samsung usb drivers are installed on your PC for your phone. Pull the battery. Open up ODIN. plug in the usb to your computer and phone. Hold down the "volume down" button until a yellow android comes up for your phone that says "downloading". At this point ODIN should turn yellow in the first box. Click "Pit" and select the atlas_v2.2.pit file. Click PDA!!! and select the rom that you downloaded. Hit "Start" and wait about 5 minutes until ODIN turns green and tells you "success". Disconnect the USB. Put battery back in. Boot up and hopefully you should have a stock phone back. All of your settings will be gone and you may have to OTA upgrade to the latest ROM through verizon, but all your data on the SD card will still be there. Good luck!

Mikes30000 said:
Find a link to the DL09, ED01, or ED04 odin files for the full rom
Click to expand...
Click to collapse
I would recommend against the ED01. That's a leaked ROM, and if you ever need to send your phone in for Warranty, they'll know you were up to no good. DL09 and OTA update is usually the safest bet.

seraphls said:
I would recommend against the ED01. That's a leaked ROM, and if you ever need to send your phone in for Warranty, they'll know you were up to no good. DL09 and OTA update is usually the safest bet.
Click to expand...
Click to collapse
EB01 was the leaked Froyo ROM. ED01 was the first official Froyo build released from verizon/samsung. Since then there has been official upgrade builds of ED03 and ED04. The newest, ED05 is a leak. So no problem flashing ED01. I personally prefer to flash DL09 then let the phone OTA to ED04.

landshark68 said:
EB01 was the leaked Froyo ROM. ED01 was the first official Froyo build released from verizon/samsung. Since then there has been official upgrade builds of ED03 and ED04. The newest, ED05 is a leak. So no problem flashing ED01. I personally prefer to flash DL09 then let the phone OTA to ED04.
Click to expand...
Click to collapse
And that, kids, is why you don't post on XDA before your morning tea - you forget how to read! My bad - I stand corrected.

Pc Odin Stuck on Factoryfs.img! Please Help!

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?