Database Users

Bricked phone trying to downgrade from froyo 2.2

So i upgraded my phone with the leaked froyo update.zip and everything went well except for the gps. So i followed the how to "unbrick/bring back to stock" thread so i could downgrade my phone to the di18 firmware. I used odin, the s1_odin20100512.pit and the d700.zimage.stock file. I did not want to wipe out everything, i just wanted to downgrade the kernal back to stock.
When i tried flashing on odin, it failed. now when i try turning on my i get the phone icon with the exclamation mark in the triangle. I wanted to call my girlfriend after flashing my phone but now i cant . Please help me save my phone!
EDIT: Okay not bricked, but it wont load up android
Uploaded with ImageShack.us

superbraut said:
So i upgraded my phone with the leaked froyo update.zip and everything went well except for the gps. So i followed the how to "unbrick/bring back to stock" thread so i could downgrade my phone to the di18 firmware. I used odin, the s1_odin20100512.pit and the d700.zimage.stock file. I did not want to wipe out everything, i just wanted to downgrade the kernal back to stock.
When i tried flashing on odin, it failed. now when i try turning on my i get the phone icon with the exclamation mark in the triangle. I wanted to call my girlfriend after flashing my phone but now i cant . Please help me save my phone!
EDIT: Okay not bricked, but it wont load up android
Uploaded with ImageShack.us
Click to expand...
Click to collapse
Put the phone in download mode again and run odin again.
Sent from my SPH-D700 using XDA App

Thanks for the tip!

Your gonna want to flash the di18.tar in "pda" with odin and only reboot checked, no pit needed. That gets the di18 firmware back, and the only way.. kernel has nothing to do with it..
Sent from my SPH-D700 using XDA App

I am about to do this too.. and dont want to wipe the data only get back to di18 to get the gps working.. so in that case:
1. I dont need pit file at all
2. which .tar to choose? not the255 mb file?

Mine failed the first time to. I followed the directions from http://forum.xda-developers.com/showthread.php?t=773032
I tried it a second time but used the victory pit that came with odin 1.61 and it worked. I think in the instructions their using an older version of odin.
I'm not in anyway an expert and you may not even need to use a pit like another poster said. It worked for me though. When I got done the phone rebooted and it showed it having the eclair d07 build from there it updated itself to dI18.

I believe you still need the pit file. If you are going back to stock DI18, than use this:
Stock Files
The one you were trying to use was the kernel I believe.
Here is the pit file you need:
pit file
I have flashed back to stock about 14 times and I have used these two files successfully every time.

yeah ive done it te same wasy that swanysto has done it also a lot. it always works for me to. i know some sa you don't need the pit unless just doing a kernel but i always use it. just my 2 cents

pull the SD card out before you go into download mode (not just pull it out, make sure to push down and let it pop up to remove it).

[HOWTO] Fix DBDATA problems

So I tried flashing to XWJS3 in order to set my phone to PIT 803. As I understand i have to do this in order to flash it to XWJS5. After flashing with all 3 files i get this error in the recovery mode
How can I solve this?
Update: Flashing to I9000XXJPU replaced the DBDATA. The file from samfirmware.com did the trick! Thanks for a great forum
This should resolve any issues you have with the DBDATA since the I9000XXJPU-rom creates a new DBDATA.
Open Odin and select 512 .PIT, and CSC, PDA, MODEM-files. Check Re-partition and don't touch any other settings.
Turn off your phone and put it in download mode by holding VOL DOWN+MENU+POWER.
Now just flash the phone with your ROM of choice. See here for correct flashing procedures: Flash Firmware and kernels using Odin
AFAIK you should only repartition if you have a lowlevel/full rom. Make sure you use the correct PIT either way.
Click to expand...
Click to collapse
Update 2: After reading feedback from several forum members it seems like it may be wise to just stick with 512 PIT for the time being.

dbdata
nooryani84 said:
So I tried flashing to XWJS3 in order to set my phone to PIT 803. As I understand i have to do this in order to flash it to XWJS5. After flashing with all 3 files i get this error in the recovery mode
How can I solve this?
Click to expand...
Click to collapse
you need to download odin then you flash dbdata.rfs.tar in though odin to the sgs in recovery mode.files below
P.s press the thanks button =)

Thanks for the tip though as I find little documentation on that fix I think I'll flash to I9000XXJPU then XWJS3 with 803 => then XWJS5.... or can I skip the second step?
hehe sorry, I'm pretty new at this and have been reading a ton.

This is a fairly common issue. If you repartition your device (ie. run repartition with a new .PIT file) you change the partition sizes and therefore some of the old partitions become unavailable. In this case the partition that holds dbdata would have been changed and the old dbdata data was unavailable to the system. The fix is (a) flash a full ROM that contains all the components needed eg. JPU in this case, or (b) flash just the component you need eg. dbdata.rfs in this case. Either way would resolve the problem.

Hi,
i have the same Problem. After an unsuccessful flash (including a brain fart) with the JS5.
Flashing the I9000XXJPU with 512 pit and repart fixed the issue, i could start my phone again.
However, after that i flashed the JPY-PDA with 512 pit + repart i have the same "Can't mount DBDATA" error again :/
When i do a factory reset + reboot in this state, i get the Bootscreen with the Samsung S Logo, but then the screen just turns black and nothing happens.
Any suggestions how to fix this?

i had the same problem i would flash JPU with Repart and 512 all fixed then i would flash JS3 with repart and 803 and i get the same error then i went back to JPU then fixed then JS5 or JS3 i get the error back again. I do see dbdata.rfs being flashed as the last thing but still the error.
The only way i could get it to boot was when it showed the error i would scroll down the recovery console to wipe/clear data and then reboot and it worked fine booted to JS5. Hopefully thats works for you.
So in summary i flashed JS5 fine but had to do a wipe/clear data then reboot in the console but i dont know if it means there is still a problem but so far its working fine. My only issue is that i still have the old market and i cant see all the samsung apps like video editor etc.

Well, that is what i already tried. It starts into the samsung bootscreen after that but then it just force closes and i have to pull the battery.
I just flashed JPU again, the phone is in a working state atm. But i would like to upgrade it to the JPY, without the error obviously
//EDIT
Just tried it again, here is what i have done:
1. Flashed JPU with repart and 512 pit
2. Confirmed it was working.
3. Rebooted into recovery, did a factory reset + a wipe data
4. Rebooted again, confirmed its working
5. Flashed the JPY with repart and 512 pit
---> DBDATA error again :/
6. Factory reset + wipe cache
But after a reboot i only get force closes and a black screen.
Any suggestions?
Do i need to flash the JPY in a different way after i have successfully flashed the JPU?
//EDIT²
Well, after i did start to actually use my brain it did work
I did flashed with JPU(3 Files), repart and a pit file.
So there is no actual reason to flash the JPY and AGAIN use a pit file + repart.
Its what i did when i flashed the JPY the first time (i came from 2.2 back then).
My phone is booting without any issues now, and i have JPY-JPY-JPY again

which pit file did you use ofr JPU to work with repart?

i think we are in the same boat we both have been on pit 512 and need to somehow get to pit 803

Copacaba said:
//EDIT²
Well, after i did start to actually use my brain it did work
I did flashed with JPU(3 Files), repart and a pit file.
So there is no actual reason to flash the JPY and AGAIN use a pit file + repart.
Its what i did when i flashed the JPY the first time (i came from 2.2 back then).
My phone is booting without any issues now, and i have JPY-JPY-JPY again
Click to expand...
Click to collapse
I forgot to mention that I did NOT use flash it with another PIT-file after the initial JPU flash + PIT. When I tried that appoach i got the same DBDATA-error. However I plan on flashing it with this I9000_XEN_I9000XWJS5 which includes all 3 files.
Download I9000_XEN_I9000XWJS5, see first post.
I'm interested to know if anyone has success with this method. Are there any benefits of changing the PIT file?

I was stuck at DBData error! Wiped the Cache/User data. But only after seeing this thread I came to know that there is no necessity for that
So for the people who are reading this thread with the dbdata problem. Here's my experience NO NEED TO WIPE USER DATA FOR DBDATA PROBLEM. To solve the dbData problem, I went to Darky resurrection and now I'm in Darky 9.2, though its good, I'm far more comfortable with stock rom for some reason.
Now I'm Totally confused on how to flash to JS5.
What should I do now?
Flash XEN JS5(3 files) + 803pit + repart ?

emmarbee said:
I was stuck at DBData error! Wiped the Cache/User data. But only after seeing this thread I came to know that there is no necessity for that
So for the people who are reading this thread with the dbdata problem. Here's my experience NO NEED TO WIPE USER DATA FOR DBDATA PROBLEM. To solve the dbData problem, I went to Darky resurrection and now I'm in Darky 9.2, though its good, I'm far more comfortable with stock rom for some reason.
Now I'm Totally confused on how to flash to JS5.
What should I do now?
Flash XEN JS5(3 files) + 803pit + repart ?
Click to expand...
Click to collapse
If you follow the instructions in the first post you will have to re-partition with a full stock rom such as JPU. This will erase all your user data/cache. Afterwards you can flash JS5 with just the PDA.
You may be able to flash/re-partition JS5 with 3 files and 803 pit, though I can't confirm if this is a full rom like JPU. If it is a full rom then I think you may be able to skip flashing JPU all together.
Someone more knowledgable than me would have to confirm this before I can recommend it though. To be on the safe side just flash JPU(3files)+512 PIT w/re-part first, then JS5(1 file) without re-part.

well stop using pit 803.
use 512 or 513.
samfirmware have a love for pit 803 but its most useless of them.
this has been up for discussion 100+ times and the fact is that pit 803 really sucks.
**DamianGTO Steam kernel. 350MB Ram. 500HZ. all ext2. Steam Rom. Js5**

Really Damian? Because on some threads people are saying the opposite.. In truth, I haven't seen any evidence that anyone has actually analysed the PIT files well enough (except maybe the Heimdell developer), to know whats going on, and I don't really recall him saying what was going on.

Have a look at this :
http://forum.xda-developers.com/showthread.php?t=816449
The basic difference is the partition size of system and dbdata.

Auzy said:
Really Damian? Because on some threads people are saying the opposite.. In truth, I haven't seen any evidence that anyone has actually analysed the PIT files well enough (except maybe the Heimdell developer), to know whats going on, and I don't really recall him saying what was going on.
Click to expand...
Click to collapse
well i know it well. its looked into how it works.
the main thing is the different size of the partition. but many has different problem when using pit803.
it always works with pit 512, accept for one firmware. that need pit 513.
that's for the firmware is to big for pit 512.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**

UFFF!
I can confirmed method on first post working, and very important is what write on gray:
If you're upgrading to a newer rom with 803 you must NOT re-partition again or you will end up with the same problem.
Thanks and Regards

miro666 said:
UFFF!
I can confirmed method on first post working, and very important is what write on gray:
If you're upgrading to a newer rom with 803 you must NOT re-partition again or you will end up with the same problem.
Thanks and Regards
Click to expand...
Click to collapse
Thanks for the feedback, I´ve updated the post. This problem annoyed the hell out of me, so I hope it saves people some of the frustration.

TechKidTarek said:
you need to download odin then you flash dbdata.rfs.tar in though odin to the sgs in recovery mode.files below
P.s press the thanks button =)
Click to expand...
Click to collapse
This unbricked my phone. Thank you sir.

The dbdata File was flashed in Recovery Mode? Not in Downloadmode?

Boot files problem.. how to flash roms ?? (URGENT)

Since nobody gave me a good answer (i asked in samfirmware and other androidforums) and im not the only one having this problem, i decided to post in development section.
It seems that GT-I5800 black edition Teos users have a problem with the ROMS that come without the Sbl.bin, boot.bin and logo.png.... we cant flash ROMS that are missing these files, always get this error message.
--Appling Multi-CSC...
E:Can't mount /dev/block/st17 (Invalid argument)
E:main:Can't mount DATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
Click to expand...
Click to collapse
Ive looked inside every ROM .tar and i found out that JPF, JPM, and custom ROMS based on this stock roms are missing those files, and we cant flash those.
Inside JP8, JP9 and JPB those 3 files are included and i managed to flash all 3 of them, but we want to be able to flash a custom rom or update to JPM of XWJPD.
I need to know if its safe to add the 3 missing files inside JPM.tar and then flash it.
(I know you will tell me its not safe to flash with the boot files.. BUT.. we cant FLASH any ROM stock or custom that dont have those ROMS everytime i hit same error message (E: Cant Mount DATA
Please DO NOT answer if you're not 100% sure what are you talking about.

pflorin said:
Since nobody gave me a good answer (i asked in samfirmware and other androidforums) and im not the only one having this problem, i decided to post in development section.
It seems that GT-I5800 black edition Teos users have a problem with the ROMS that come without the Sbl.bin, boot.bin and logo.png.... we cant flash ROMS that are missing these files, always get this error message.
Ive looked inside every ROM .tar and i found out that JPF, JPM, and custom ROMS based on this stock roms are missing those files, and we cant flash those.
Inside JP8, JP9 and JPB those 3 files are included and i managed to flash all 3 of them, but we want to be able to flash a custom rom or update to JPM of XWJPD.
I need to know if its safe to add the 3 missing files inside JPM.tar and then flash it.
(I know you will tell me its not safe to flash with the boot files.. BUT.. we cant FLASH any ROM stock or custom that dont have those ROMS everytime i hit same error message (E: Cant Mount DATA
Please DO NOT answer if you're not 100% sure what are you talking about.
Click to expand...
Click to collapse
I dont know! But you should have read this before you post in dev!!!!! http://forum.xda-developers.com/showthread.php?t=857760

pflorin said:
Since nobody gave me a good answer (i asked in samfirmware and other androidforums) and im not the only one having this problem, i decided to post in development section.
It seems that GT-I5800 black edition Teos users have a problem with the ROMS that come without the Sbl.bin, boot.bin and logo.png.... we cant flash ROMS that are missing these files, always get this error message.
Ive looked inside every ROM .tar and i found out that JPF, JPM, and custom ROMS based on this stock roms are missing those files, and we cant flash those.
Inside JP8, JP9 and JPB those 3 files are included and i managed to flash all 3 of them, but we want to be able to flash a custom rom or update to JPM of XWJPD.
I need to know if its safe to add the 3 missing files inside JPM.tar and then flash it.
(I know you will tell me its not safe to flash with the boot files.. BUT.. we cant FLASH any ROM stock or custom that dont have those ROMS everytime i hit same error message (E: Cant Mount DATA
Please DO NOT answer if you're not 100% sure what are you talking about.
Click to expand...
Click to collapse
I have the exact same phone. No problems. Flash the entire Lestatious branch (not trying to get you to use it) and see if the problem remains.
And no. Never flash those files. It's just a horrid idea.
And this isn't even development!

sadly your question will be left "un solved" because i dont see any problem in what you say...maybe you need to learn how to flash...because you seems to confuse yourself in mixing up stuff...And posting in dev section was a bad idea...This will soon be closed..
Hope you learn how to flash with success in near future..
Happy Flashing in Advance
PeACE

im on jpb but i dont know how to flash, right !!!!!!!
did you ever tried to flash a teos i5800 black??

Sir,if you flash bootloader ,it may do harm to your phone.And Bl isnn't an necessary thing for flash.Use odin to flash those tar files is easy and fast without any problems.
Sent from my GT-I5800 using XDA Premium App

Maybe u should wipe cache&data partitions
Sent from my GT-I5800 using XDA Premium App

Alo try to remove sd card and sim ard, i had problems flashing if i had those cards inserted, firsto of all try to flash a stock firmware, like jpd or jpm, look in samfirmware for your you phone's location, if you can flash with no problems a stock firmware, try with a custom one

[Q] Am looking 4 stock "PHONE" file 4 Vibrant T959

Hello,
Do you know where I can get a PHONE file for Vibrant T959 to use with ODIN?? Please help...
A while back, in the process of installing a 2.3.3 ROM on my Vibrant T959, I used a Galaxy 9000 PHONE file (and PIT and PDA) via ODIN. Since then, at boot, splash says i9000 then 2nd splansh says Vibrant.
Phone works ok, but there are times when it thinks phone is an i9000 not an Vibrant - like using ROM Manager and downloading recovery.
I have looked everywhere but not found a stock PHONE file for Vibrant (only found 512 PIT and PDA files).
Please email or point me to one, if you have or know where.
Much appreciated

http://forum.xda-developers.com/showthread.php?t=1047087
You'll find the Tar and Pit under Step 2.

eggnoodle said:
http://forum.xda-developers.com/showthread.php?t=1047087
You'll find the Tar and Pit under Step 2.
Click to expand...
Click to collapse
Hi eggnoodle,
I do not see PHONE file in the package..., only the PIT and PDA files.
Will this fix the GT i9000 splash screen and other issue? Let me know..
thx

Perhaps you misunderstood, but I was not looking for the TAR and PIT files. I am looking for the PHONE file.
Thx

If you're looking for stock rom then you can find it here
http://forum.xda-developers.com/showthread.php?t=848737&highlight=T959UVJFD
hopefully someone else with more experience can chime in...as I'm a newbie myself.

Thx anyway, but I am looking for the specific PHONE file to use with ODIN...

Im at work at the moment but go to the dev page and look for tge aoi toolbox that has tge stuff you need to flash back to stock
Sent from my GT-I9000 using XDA App

seedofchaos said:
Im at work at the moment but go to the dev page and look for tge aoi toolbox that has tge stuff you need to flash back to stock
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Hi seedofchaos,
I have flashed back to stock many a time, to install ROMS, etc. but this has not restored the Vibrant initial splashscreen. This first splash only changed after I used a GT i9000 PHONE file with ODIN.
If you can direct me to a PHONE file to use with ODIN, I would appreciate it.
I have read about the aoi toolbox but it is more than I was looking for at moment. I just need the PHONE file for the Vibrant T959, please.

Flashing the Samsung Vibrant to stock firmware does not require a PHONE file to be selected in Odin.
You might have heard that for some other phone, but for this phone all that is required is a .tar file and a .pit file which has already been linked to.
Edit: Seems like you might just have to flash a vibrant kernel. Look into flashing that.

ferhanmm said:
Flashing the Samsung Vibrant to stock firmware does not require a PHONE file to be selected in Odin.
You might have heard that for some other phone, but for this phone all that is required is a .tar file and a .pit file which has already been linked to.
Edit: Seems like you might just have to flash a vibrant kernel. Look into flashing that.
Click to expand...
Click to collapse
No sir, I am not trying to flash back to stock. I am not trying to flash to stock. I know how to do that with TAR and PIT, but that is not what I am trying to do.
I need the PHONE file to restore the initial boot splash and to get the phone to stop identifying as a GT i9000 in some apps, which it does. This behavior started when I used a GT i9000 PHONE file in ODIN.
Sorry for the confusion this is causing, but if anyone has it, I need a PHONE file for Vibrant T959.
thanks

peaceful1 said:
No sir, I am not trying to flash back to stock. I am not trying to flash to stock. I know how to do that with TAR and PIT, but that is not what I am trying to do.
I need the PHONE file to restore the initial boot splash and to get the phone to stop identifying as a GT i9000 in some apps, which it does. This behavior started when I used a GT i9000 PHONE file in ODIN.
Sorry for the confusion this is causing, but if anyone has it, I need a PHONE file for Vibrant T959.
thanks
Click to expand...
Click to collapse
We understand what you are trying to do. You want to get the old boot splash back the only way to do that is to flash a stock rom. Jfd will do the trick. Otherwise you'll need to have a custom kernel like overstock flashed through clockworkmod.
+10char

Well, I have flashed JFD twice using ODIN, but no cigar.
I did so in the process of installing a new ROM.
Is there something I am missing? Current ROM is Simply Galaxy 3 rc2 based on 2.3.3
Thanks for all help

I think you need vibrant sbl.bin/boot.bin. Look here....
http://forum.xda-developers.com/showthread.php?t=756832&page=2
You can ask Jellette for bootloader.

It sounds to me like you flashed the i900 sbl and boot.bin in other words your phone has the i900 boot loader. You'll need to find the files to flash the t959 boot loader however be VERY VERY careful doing so as you have about a 50/50 chance of hard bricking your phone when doing so. The files aren't available on xda for that reason. You're only shot is finding a dev who has said files and is willing to help you out. Good luck!
Sent from my SGH-T959 using XDA App

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?