Database Develop

[Q] Samsung Galaxy S: Black Screen after Flash

I have a SGS with firmware I9000XWJG5 and Root. I tried to do a Speed fix, but afterwards it was slower so i tried to flash the phone with the I9000XWJG5 firmware again.
After the flash, the phone rebooted and i came to the recovery menu. There the phone wrote:
update media, please wait
and in the next lines:
E: Can't mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Now when i try do start the phone, i get a black screen after the bright S
What i have tried: Flash agein with and without re-partition and Factory Reset
Has anybody an idea what i can do?
and sorry for my bad english

bump. can anyone help with this topic..
i am having some problem..
help us guys
thanks
Fixed... use odin 512

Thread moved in Galaxy S I9000 General.

I can definately help with this one, as I worked through it last night...
I found that if you're trying to flash the JG5 rom (as mentioned in Modaco's thread) with the 513 Pit file, then you'll get the black screen of despair!! For some reason the two combination of the two don't work.
However, if you do a google search for Odin PIT 512, then download this file
You will be able to download the 512 PIT file instead. Now use this in Odin3 to flash the JG5 rom and you should have no further issues....it worked for me.
I also discovered that Samsung have just released a later firmware, so I just flashed this one on top of the JG5 one...I have a nicely running phone now.
Hope this helps...it did me!
Mike

Mine was completely knackered. Couldn't get to recovery either. Flashed Modaco's MCR R3, after the JG5 flash, using all the files in the JG5 download. Working a treat...
Cheers,
BS...

blacksoul93 said:
I have a SGS with firmware I9000XWJG5 and Root. I tried to do a Speed fix, but afterwards it was slower so i tried to flash the phone with the I9000XWJG5 firmware again.
After the flash, the phone rebooted and i came to the recovery menu. There the phone wrote:
update media, please wait
and in the next lines:
E: Can't mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Now when i try do start the phone, i get a black screen after the bright S
What i have tried: Flash agein with and without re-partition and Factory Reset
Has anybody an idea what i can do?
and sorry for my bad english
Click to expand...
Click to collapse
hello, i got the same problem. trying to reflash with I9000XXJPY 2.2.1 and the 512 pit, but still the same problem.

ash969 said:
hello, i got the same problem. trying to reflash with I9000XXJPY 2.2.1 and the 512 pit, but still the same problem.
Click to expand...
Click to collapse
Same here.
I tried JS3 and going back to JP6....and always the same result.
I'm obviously missing something. Maybe my 512.PIT is corrupted. I get the black screen and the same /dev/block.st110 errors in recovery.

i beleive you need to have a CSC file also for the odin flash.
i sorted mine like this:
Downloaded some JP2 odin files [used this as this was the only one on Samsung-firmwares that had all 3 PDA, Modem and CSC Files. flashed this using a .512 pit in odin. - this allowed the phone to boot normally.
connected to Kies and using reg hack [set to XEU] managed to update to JPY.
the following the Darky guide, flashed the CF Root kernel, installed the ROM Manager from the market, using the recovery mode installed the update.zip file for clockworkMod.
Formatted everything in ClockworkMod
Factory Reset in ClockworkMod
Installed Darky ROM V8.0 Wipe

thanks for your find !
Rumble6059 said:
i beleive you need to have a CSC file also for the odin flash.
i sorted mine like this:
Downloaded some JP2 odin files [used this as this was the only one on Samsung-firmwares that had all 3 PDA, Modem and CSC Files. flashed this using a .512 pit in odin. - this allowed the phone to boot normally.
connected to Kies and using reg hack [set to XEU] managed to update to JPY.
the following the Darky guide, flashed the CF Root kernel, installed the ROM Manager from the market, using the recovery mode installed the update.zip file for clockworkMod.
Formatted everything in ClockworkMod
Factory Reset in ClockworkMod
Installed Darky ROM V8.0 Wipe
Click to expand...
Click to collapse
thanks mate ! after a huge scare sorted mine with this firmware as well, this after I tried several other newer firmware packages from samfirmware and was ,slowly but surely ,starting to lose hope ...
for some reason this particular firmware JP2 seems to fix this problem
cheers and thanks again for your find !

fix for black screen after flash with no recover or download mode working.
Hey All.
So like the subject says, you flash and then your phone restarts or whatever, and then you get the normal galaxy s startup, with the sound and the visuals, but then that's it. Henceforth you are greeted with the two lights (if its a Bell Vibrant) from your options and back keys.
To fix it use the attached file. Its called ADB or something - I just know it works. It was a fix for the galaxy s phones that didnt have the recovery/download mode stock.
so here is how it goes:
1. download adb to your desktop and unpack it (if its in winrar or zip or whatever) to a file folder named adb.
2. open a command prompt.
3. type "cd" and then the address of the "adb" folder. so for example it should be in C:\Users\your user name\Desktop\adb. where "your user name" is your user name a duh.
4. plug in your galaxy s via usb.
5. type "adb reboot download" in the command prompt. copy it using your mouse as well.
6. turn on your phone.
7. press enter in the command prompt, then keep copying and pasting and pressing enter until you see the download screen on your phone. each time you press enter it says device not connected or something but just keep trying.
the article i read:
can't post it but the thread is called "How to get the 3 button recovery mode working"
Credit to Goots from samsung galaxy s forums. Go Goots!

[Q] I9000 soft bricked

I need some help... Please!
I have a I9000T galaxy S phone and I soft bricked it. This is the story:
I flashed my phone using Odin with ROM JPY_JPY_JPY (downloaded form samfirmware, only file: PDA), and then flashed supermod-kernel-k13d-500hz...then I uploaded Modem UGJL2 for Froyo as an update.zip file (to get band 850 mhz for my country) and applied successfully!
My phone worked as a charm. No bricking.
Then I realized that there was a newer ROM: I9000XWJS5 with the XEN thing.
Since the ROM has the 3 files (MODEM, CSC, and PDA) and I read that it needed a different PIT, I flashed with the re-partition checkbox checked and with the 803 pit file.
It didn't get through. It got stuck at flashing sbl.bin
I had to unplug it after several minutes and I realized that it was soft bricked. It didn't work but download.
I tried to go back to JPY. After many tries and errors (changing PIT to 512 and repartitioning), finally I could flash back to JPY ROM. At the end of the process it reboots and the system get into Android system recovery <3e>. I can read at the bottom the following signs:
E: Can't mount /dev/block/stl10 (invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
If I reboot the system, it boots and I see the splash "S" moving theme, and it seems that it is booting but then it stops and it starts vibrating from time to time... then the screen goes black and nothing happens (but vibrating from time to time). It never appeared the "login screen"
Reading here and there, some advised to flash first the speedmod-kernel with the PIT 512 file and re-partitioning. I did so, and then, after boot I was able to get into Clockworkmod recovery screen. The menu is green and the version is 2.5.1.0
Someone suggested to flash to JPU ROM (that way it fixed a similar problem) but when I did so, it takes me to the beginning (the process hung at sbl.bin)...
I've been flashing and reflashing with different options these 3 ROMs (JPU, JPY, JS5) the only one that completes the flashing successfully is JPY, and eventhough it tries to boot, it fails to present the logon screen (dots for password)... JPU and JS5 hang at sbl.bin and after that, no boot... freeze. I have to flash back to JPY.
I have read tons of forums, I have learned a lot, but I believe I need deeper advices.
Thanks in advance!

Some further information. JPU, JPY, JS5 are ROMs that were downloaded from samfirmware.com... I guess that is what you mean when you advice to flash any stock ROM. Am I right?

Guessing you have a I9000m. If yes, Flash JPC with 512 PIT and repartition ticked. You will still be in a boot loop. Take out battery and then load JL2 into PDA of ODIN and flash. You could try it even if you do not have an i9000m but at your own risk! Advice is free, phone isn't!

droilfade said:
Guessing you have a I9000m. If yes, Flash JPC with 512 PIT and repartition ticked. You will still be in a boot loop. Take out battery and then load JL2 into PDA of ODIN and flash. You could try it even if you do not have an i9000m but at your own risk! Advice is free, phone isn't!
Click to expand...
Click to collapse
No... I don't have a I9000m, I do have a I9000T
When I flashed the JPY it turned a I9000, but I applied the Modem UGJL2 which adds the 850mhz band (which is the only difference between the I9000T and I9000.
Someone suggested going to JM8 (Eclair 2.1), but I have read that in some cases it produces hardbrick... what do you think?

Oh, been there! I can give you some advice... First, i will recommend heimdall for flashing, it allows a little bit more of control with the files you want to flash. Then, i had this problem with the dbdata... i think it's becacause of the repartition thing, honestly i'm not sure but do not worry, if you can enter download mode it's recoverable.
So, let's try something. Download heimdall, install it, install your drivers and then download the rom in this post (it's and old build of Darky's Rom), the thing here is that you <<have>> to flash this with the command line client, so you can specify the order of the files to flash leaving at the very end the Sbl.bin and modem.bin (Both files can't be flashed neither with heimdall nor Odin in my Galaxy i9000T). Obviulsy the heimdall flash will fail with the Sbl.bin file, so you just pull out your battery and power up your phone. That should do it... it have failed a couple of time for me, so if it fails for you (It gives you a boot loop) tell me so i can share my other method. If this works you should be able to enter CWM and flash a custom ROM or be able to flash another stock rom but be careful, do not flash bootloaders, modems or do a repartition (That's why i prefer Heimdall over Odin).
I hope you could have your phone back.

froysm said:
Oh, been there! I can give you some advice... First, i will recommend heimdall for flashing, it allows a little bit more of control with the files you want to flash. Then, i had this problem with the dbdata... i think it's becacause of the repartition thing, honestly i'm not sure but do not worry, if you can enter download mode it's recoverable.
So, let's try something. Download heimdall, install it, install your drivers and then download the rom in this post (it's and old build of Darky's Rom), the thing here is that you <<have>> to flash this with the command line client, so you can specify the order of the files to flash leaving at the very end the Sbl.bin and modem.bin (Both files can't be flashed neither with heimdall nor Odin in my Galaxy i9000T). Obviulsy the heimdall flash will fail with the Sbl.bin file, so you just pull out your battery and power up your phone. That should do it... it have failed a couple of time for me, so if it fails for you (It gives you a boot loop) tell me so i can share my other method. If this works you should be able to enter CWM and flash a custom ROM or be able to flash another stock rom but be careful, do not flash bootloaders, modems or do a repartition (That's why i prefer Heimdall over Odin).
I hope you could have your phone back.
Click to expand...
Click to collapse
Thank you froysm... What I see in your post is that we are going to try to flash a Darky's ROM in order to have CWM so we can flash a custom rom?
If that is so... I already have CWM... It is version 2.5.1.0 with its menu in green.
What is custom rom? are they the roms from samfirmware? I tried JPU and JS5 and they hang at slb.bin... the only one that flashes successfully is JPY, and eventhough it "runs", somehow it is not working.

In regard heimdall... Do I have to have ubuntu in order to install it? Is there a heimdall for windows?

Well, if you have CWM try one of the roms of the world famous romkitchen Cook a rom, download it, enter recovery mode, go to mounts & storage (and connect your phone to the computer) and select mount USB storage, put the donwloaded zip file in your phone. Then unmount, go bak to the main CWM menu, select install zip from sdcard, the choose zip from sdcard, find your rom and flash it! However... as far as i can remember i could never mount my phone with CWM 2.x so may need to flash Darky's Rom just to be able to mount your phone, put the zip file there and then reflash with the new ROM viw CWM...

jdelagarza said:
In regard heimdall... Do I have to have ubuntu in order to install it? Is there a heimdall for windows?
Click to expand...
Click to collapse
Yes, heimdall is available for Windows here It's pretty straight forward, just put your phone in Download mode, select the files you want to flash and hit start.

froysm said:
Yes, heimdall is available for Windows here It's pretty straight forward, just put your phone in Download mode, select the files you want to flash and hit start.
Click to expand...
Click to collapse
Thank you... believe it or not you poured some light into my darkness.
I have 3 issues and I hope you can clarify...
How would you order flash methods, in order of importance? Odin, CMW, heimdall? Which one is better, which one is worse?
I'm able to flash speedmod-kernel-k13d-500hz... that is what brings me the CMW v2.5.1.0.... should I try to install a newer version of CMW? or should I stick with heimdall option?
Flashing ROMs such as Darky's rom can be potentially harmfull? I mean, can my phone end with a hardbrick?

jdelagarza said:
Thank you... believe it or not you poured some light into my darkness.
I have 3 issues and I hope you can clarify...
How would you order flash methods, in order of importance? Odin, CMW, heimdall? Which one is better, which one is worse?
I'm able to flash speedmod-kernel-k13d-500hz... that is what brings me the CMW v2.5.1.0.... should I try to install a newer version of CMW? or should I stick with heimdall option?
Flashing ROMs such as Darky's rom can be potentially harmfull? I mean, can my phone end with a hardbrick?
Click to expand...
Click to collapse
Don't worry, that is exactly why we are here to learn from other people experience and share what we have learned.
About your issues,
I only have access to my Linux machine and heimdall says this when i ask for help (with the command
Code:
heimdall help
Usage: heimdall <action> <arguments> [--verbose] [--delay <ms>]
action: flash
arguments:
--repartition --pit <filename> --factoryfs <filename>
--cache <filename> --dbdata <filename> --primary-boot <filename>
--secondary-boot <filename> --param <filename> --kernel <filename>
--modem <filename>
So, what you have to do is navigate to the location of your files and write something like this
Code:
heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --dbdata dbdata.rfs --cache cache.rfs --param param.lfs --kernel zImage --primary-boot boot.bin --secondary-boot Sbl.bin --modem modem.bin
See how i reordered the files to flash leaving at the very end Sbl.bin and modem.bin?
As i told you before this will fail because of the last files, but it will allow to flash everything else. Remove your battery, put it again and try to boot your phone.
I forgot to tell you something really important!! Since the flash in going to fail it will give you the <<scary>> "Connect phone to PC" screen, but don't worry, heimdall can take care of that. Again, asking heimdall for help in the command line says something like this:
action: close-pc-screen
description: Attempts to get rid off the "connect phone to PC" screen.
And that is exactly the next step to take, write down in your command line (with the pone connected to the pc and in download mode)
Code:
heimdall close-pc-screen
And that's it, wait for the phone to boot.
This method is the one i advise when you just can enter Download Mode or when you really need to repartition.
Better? Worse? Nah, they are just really different approaches, Odin is the Samsung standard, Heimdall came to the game because it's OS X and Linux compatibility and CWM allows you to control your phone, custom kernel settings, flash updates packages with modems, boot animations , even whole roms without the need of a cable to connect your phone to a PC and other really cool stuff. Generally, since i've been in custom roms (like darky's, romkitchen, ultimate, etc) since i got this phone, i only use CWM, and when i have a big problem or i need a stock rom i use Heimdall (because i'm on Linux).
The CWM version is just fine, not all the roms are compatible with CWM 3 at the moment, so just make sure you can mount your phone in your pc with CWM. Try first the CWM option, if you can't mount it or it just don't works try the heimdall option.
The last question, I'm not saying it's 100% safe because it is not, but not only custom roms, this also can happen flashing a rom with Odin or Heimdall. Honestly i haven't heard of someone who bricked a phone in the whole thread of the romkitchen or darky's rom. I mean, it could happen, even with a perfectly stable stock rom. but it's not so common, at most, the worst thing you will encounter in your custom rom experience is a lot of Force Closes in applications (if you mix data and apps from incompatible versions) maybe a couple of boot loops, but nothing to be really scared about, just make sure you can enter Download Mode and everything will be fine.
Phew! The longest post if ever written in any forum. I hope i made everything clear, if you happen to have any other question i'll be happy to answer it (But it will have to wait for tomorrow... you know, it's midnight).

Thanks...
I'm downloading darky_heimdall.zip. As soon as it is downloaded, I will try it.
Just for your information, with CMW I tried to mount the USB and it worked!
So, now I am at a dilemma... Should I flash darky with CMW or heimdall?
Oh, if you wanted to know how I managed to install a WORKING STOCK ROM with froyo... here is the tutorial that I followed:
http://neosystm.com/2010/12/actuali...000t-a-froyo-2-2-1-xxjpy-de-forma-no-oficial/
It worked as a charm... I had Froyo 2.2.1 with JPY ROM.
The problem began when I tried to update it to JS5 ROM.
Cheers!

I just finished downloading darky's rom...
I noticed that it has 3 .bin files: boot.bin, modem.ini and slb.bin
I was curious about the content of my previous working ROM (JPY) and the not working ROMs (JPU and JS5).
I found that JPY has only the modem.bin file.
and JPU & JS5 have boot.bin and slb.bin (but no modem.bin).
Question: Since you advised to install darky's rom and but the sbl.bin file at the end, so my phone can get flashed with everything but slb.bin, can I do the same with the JS5 ROM?
I look forward to your response...

OK... I tried to flash darky's rom with CMW... it said:
"Installing: SDCARD: darky_heimdall.zip
Finding update package...
Opening update package...
Installing update..."
And it hung... I guess this was expected due the slb.bin...
I'm gonna try the heimdall method.
So, what do you think? Should I try it with JS5 or with darky's rom?
Cheers

Ok... I flashed with heimdall.
This is the result:
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading PIT file
PIT file upload successful
Uploading factory filesytem
100%
Factory filesytem upload successful
Uploading cache
100%
Cache upload successful
Uploading data database
100%
Data database upload successful
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading secondary bootloader
100%
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
The last two sentences appeared when I unplugged the phone after a 10-minute wait.
I removed the battery, and put it back again. Turned my phone on, and I've got the picture of the cell phone - computer hazard. I'm able to enter download.
What's next?

Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?

jdelagarza said:
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
Click to expand...
Click to collapse
I've found a thread that says that they fixed it going back to JM8 ROM, and then moving back to Froyo 2.2.
Does anyone know any potential damage of such flashing?
I read this post http://forum.xda-developers.com/showthread.php?t=780867
And it seems that downgrading can lead to corruption and hard bricking.
Does anyone know?

Hey, sorry i didn't answer sooner, let's see...
jdelagarza said:
I just finished downloading darky's rom...
I noticed that it has 3 .bin files: boot.bin, modem.ini and slb.bin
I was curious about the content of my previous working ROM (JPY) and the not working ROMs (JPU and JS5).
I found that JPY has only the modem.bin file.
and JPU & JS5 have boot.bin and slb.bin (but no modem.bin).
Question: Since you advised to install darky's rom and but the sbl.bin file at the end, so my phone can get flashed with everything but slb.bin, can I do the same with the JS5 ROM?
I look forward to your response...
Click to expand...
Click to collapse
Yes, you can.
jdelagarza said:
OK... I tried to flash darky's rom with CMW... it said:
"Installing: SDCARD: darky_heimdall.zip
Finding update package...
Opening update package...
Installing update..."
And it hung... I guess this was expected due the slb.bin...
I'm gonna try the heimdall method.
So, what do you think? Should I try it with JS5 or with darky's rom?
Cheers
Click to expand...
Click to collapse
That specific version of Darky's rom is intended only for heimdall, so it will obviously fail. You'll see, some files can just be flashed via CWM and some can just be flashed with Odin and Heimdall, be careful and read with which tool can be flashed.
jdelagarza said:
Ok... I flashed with heimdall.
This is the result:
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading PIT file
PIT file upload successful
Uploading factory filesytem
100%
Factory filesytem upload successful
Uploading cache
100%
Cache upload successful
Uploading data database
100%
Data database upload successful
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading secondary bootloader
100%
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
The last two sentences appeared when I unplugged the phone after a 10-minute wait.
I removed the battery, and put it back again. Turned my phone on, and I've got the picture of the cell phone - computer hazard. I'm able to enter download.
What's next?
Click to expand...
Click to collapse
As I told you on my last post, heimdall can take care of that. Just put your phone in Download Mode and write heimdall close-pc-screen. That should solve your problem.
jdelagarza said:
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
Click to expand...
Click to collapse
Nope, i've never found it (actually i've never needed it).
jdelagarza said:
I've found a thread that says that they fixed it going back to JM8 ROM, and then moving back to Froyo 2.2.
Does anyone know any potential damage of such flashing?
I read this post http://forum.xda-developers.com/showthread.php?t=780867
And it seems that downgrading can lead to corruption and hard bricking.
Does anyone know?
Click to expand...
Click to collapse
Try my methods first, I've tested them a lot and never had a real problem. If you want to try this, go ahead. As i told you before it's very rare to hear a phone really bricked, most of the times it's recoverable.

Oh, I forgot the heimdall close-pc-screen.
Ok... I tried it twice.
The first time my command prompt was busy trying to upload sbl.bin, so I opened another command prompt and I threw the command. The result: "Failed to access device. Error: -3"
The second time I waited until the flashing ended with error, and then I threw the command (within the same command prompt). The result: "Failed to retrieve config descriptor"
Hmmm... what was the other method that you mentioned in your first post?
In the other hand, can you read the following post, and could you go through all the comments after the post. Pay special attention to Jedi and GSCATIL...
http://foro.neosystm.com/f19/androi...00xxjvk-%96-beta-para-el-samsung-galaxy-s-69/
Jedi describes my exact problem (about the phone vibrating), and GSCASTIL is from Puebla, so he is with Telcel as well...
My problem didn't happen updating to gingerbread... It happened updating to JS5 (Froyo).
Hope this helps... what do you think?

jdelagarza said:
Oh, I forgot the heimdall close-pc-screen.
Ok... I tried it twice.
The first time my command prompt was busy trying to upload sbl.bin, so I opened another command prompt and I threw the command. The result: "Failed to access device. Error: -3"
The second time I waited until the flashing ended with error, and then I threw the command (within the same command prompt). The result: "Failed to retrieve config descriptor"
Hmmm... what was the other method that you mentioned in your first post?
In the other hand, can you read the following post, and could you go through all the comments after the post. Pay special attention to Jedi and GSCATIL...
http://foro.neosystm.com/f19/androi...00xxjvk-%96-beta-para-el-samsung-galaxy-s-69/
Jedi describes my exact problem (about the phone vibrating), and GSCASTIL is from Puebla, so he is with Telcel as well...
My problem didn't happen updating to gingerbread... It happened updating to JS5 (Froyo).
Hope this helps... what do you think?
Click to expand...
Click to collapse
Always, after any task completed successfully or unsuccessfully either with Heimdall or Odin, unplug your phone, reboot it, put it again in download mode and connect it. So do that again, flash, wait for the fail, unplug, reboot, download mode again, connect again and try to remove the error screen with heimdall.
I will read that post and see what i can find (I can't read it right now, sorry).

Soft bricked N7000. How to?

Tried everything I could with Odin and phone still stuck in a start loop.
I was downgrading from checkROM to official firmware ZSLA2 with CWM (I wanted to keep ROOT, so I selected "Keep CF-Root kernel") due to stability issues, after restarting the phone got into the start loop.
I flashed with Odin official ZSLA2 with the same result (looped start). I flashed XXKKA (again looped start). During the flashing process, Odin says the flashing was successful. By the way, both ROMS are tar.md5 files.
I tried to remove the battery for over 30 minutes and charge it for 2 hours, tried re-partition in Odin (it's my understanding that with a stock rom, it creates a clean installation), but Odin fails to start the process.
What else can I do?
I am sorry if this has previously asked, but I've been searching for over 2 hours and nothing similar came. Somebody mentioned to use a PIT file in addition, but the other person who got his phone soft bricked didn't solve the problem either. As downloading a ROM is time consuming and I've got many problems with upload sites in china (cannot access to most of them), I would thank any help in regards this issue.

Sounds like your kernel isn't talking properly to your ROM.
A fresh start is your best bet. Flash a stock rom and kernel from Odin and reroot it with CF-Root.
What files are you putting into Odin? There should be a total of 4.
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)

I am using official ROM N7000ZSLA2_N7000ZSLA2_N7000XLA4_HOME.tar.md5 into PDA and also tried ROM N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5, which I used successfully in the past to make root into my phone.
Does it really make a difference to flash 4 separate files instead of a full pack? Where can I find an official ROM with pda radio and kernel separated? Just untar the ROM?

btyork said:
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
Click to expand...
Click to collapse
Oh, they do come into the Note; I flashed the Beta ICS, and one of the things they mention is to use the PIT file for the 16GB version, instead of the 32GB that comes with the leaked ROM. Unfortunately I deleted that ROM, and donwloading it is painfully slow and also wouldn't necessarily solve my problem as I couldn't even make a phone call.

True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.

Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.

btyork said:
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Click to expand...
Click to collapse
This are the files I am flashing:
Sorry, I am new user and still cannot post screen captures. I do have more than the 5 files.
In XXKKA I have:
Boot
Cache
Factoryfs
Hidden
Modem
param.lfs
Sbl
zImage
In ZSLA2:
Cache
Factoryfs
Hidden
Modem
zImage
btyork said:
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
Click to expand...
Click to collapse
I can only enter into Download mode, not recovery mode.
Odin is full wipe, right? What the hell am I doing wrong?

N7000xxla1_n7000oxala1_oxa
http://hotfile.com/dl/141060546/b0c7420/N7000XXLA1_N7000OXALA1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han

choihan06 said:
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you

mrfan said:
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
Click to expand...
Click to collapse
I have just recently dowloaded and installed the rom without problem. What do you mean by corrupted rom?
Sent from my GT-N7000 using xda premium

I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

Fix The problem
I had the same problem, the device got into start loop. JUST DO A FULL WIPE..! and the device should start normally. I worked for me.... :good:
Sent from my GT-N7000 using xda premium[/QUOTE]

[Q] Flashing stock rom using odin

Hello,
I will start with saying that Ive already checked every tutorial in every android website.
here is what I did.
I had Miui (Not the ICS one) I have tried to flash CM9 with the existing recovery. than something somewhere on the flash procedure go wrong and the phone just rebooted and putted in loop with no recovery option but download option. so I tried to flash the stock rom using odin 1.85, and the phone just looping on the image of the mobile operator. I did this procedure with the odin for more stock roms I found.
thanks in advance really I need your help...

http://www.theandroidsoul.com/xxjvu/
maybe you forget ‘Re-Partition’checkbox, it's important.

Hmmm.. perhaps, you have to make sure all the files are properly placed (depending on the ROM you are installing). Also, I'd recommend using a pit file (and don't forget to click on "Re-Partition".. So far, it worked for me. ^.~

[SOLVED] downgrade from stock ics to stock gb -> stuck at bootscreen

hello,
i bought a fresh n7000 with stock ics firmware on it. i wanted to go to paranoid android.
1. i rooted the stock ics
2. found out that i need gingerbread to flash custom firmware
3. installed sdk, driver on ubuntu
4. installed heimdall, as its the odin for linux
5. downloaded N7000XXKJ4 from samfirmware.com
6. extracted it to have the single images to flash with heimdall 1.3.1
7. booted in download mode, attached the phone to usb and hitted detect device in heimdall
8. device was found
9. started flashing, first without repartition
boot.img as BOOT
param.lfs as PARAM
factoryfs.img as FACTORYFS
cache.img as CACHE
zImage as KERNEL
Sbl.bin as SBL1
hidden.img as HIDDEN
modem.bin as MODEM
10. flashing went all thru, the phones screen showed the progress also
11. phone did a reboot, after all flashing was done
12. stuck at bootscreen
13. found in the web that its normal and i should do a factory reset in the recovery (its not cwm)
14. stuck at bootscreen
15. repeated step 9. with pit file and repartition
16. same bootscreen
i know the phone is not dead, just not booting, but i have absolutely no chance to find out what to flash exactly and how to do it.

hm could i now just flash the abyss kernel and cwm recovery.bin or so and install a custom rom?

if you are now on GB then flash a kernel, either in CWM or odin and do a full factory reset along with all caches and dalvik cache.
i wouldnt recommend flashing a custom ROM until the stock rom is booting, you dont want to be covering up any underlying errors.
Also, Why did you re-partition ? Did you re-partition using a 3 file firmware (PDA, CSC, Phone) or just a single firmware - PDA ??

hm i dont know on what i am, because it doesnt boot.
i thought i eventually had to repartition because i changed from 4.0 to 2.3.5 ... i used the n7000 16gb pit file.

Well what did ODIN say ? Did it complete or did it get stuck and fail ?
You can flash a kernel in ODIN which should allow you to enter CWM and do a wipe, However you might get issues if you flash a GB kernel over ICS Firmware and vice versa

heimdall ran complete through, said its all fine and the phone rebooted at the end of flashing as it should be. seems all perfect.
the issues i get can not be worse?! if i would now flash a gb kernel, even if there is ics under the hood, the phone would also just not boot?!

I dont know really, Ive never tried, nor do i intend to lol.
But i imagine GB is now on your phone considering it all passed without fail So i guess you should try to flash a kernel and then do a full wipe and see if it boots then
chances are there are some ICS files left on the system preventing it from booting.

and following the guides on xda im not allowed to flash the other kernel with heimdall/odin.
i should use the cf-kernel for my firmware and flash it with the bat-script, is this correct?

Just flash this in ODIN and you will be fine
https://dl.dropbox.com/u/69014495/GingerBread-speedmod-kernel-n7000-k2-12-Odin.tar
boot into recovery, do a factory reset, then clear cache partition, then go to advanced and clear dalvik cache, then reboot
then report back

ok. now i have the yellow triangle. i wanted to avoid this.
BUT it looks very promising. clockword mod is starting. did the wipes. and when i reboot it boots directly in cwm. i think this is good atm.
i have to leave at work now. tomorrow morning i can flash a rom with cwm right? and if i flash an ics rom, then i have to flash a ics kernel, too?!

Dont worry about the triangle, Use this app to remove it https://dl.dropbox.com/u/69014495/eu.chainfire.triangleaway-47fe5bbd55070e4eddce741c0ef13110.apk
Like i said above, Make sure the phone boots before flashing any other ROMs. If you want to upgrade to ICS you will need to flash ICS in ODIN, Unless you want to use a CM9 / AOSP based ROM like Paranoid Android, In this case you will stay on GB, Just full wipe and flash ROM in CWM
EDIT: I mis read your post, Your phone is not booting, But only booting into CWM, In this case, try a custom ROM, Nothing to extreme just a simple GB ROM and see if it boots properly then

thanks so much!
flashed checkrom notehd via cwm. boots clean and nicely up.
i flashed/rooted some phones before htc hero, hd2, zte blade. but none of them, even the hd2 with its windows conversion was as unclear as the n7000. i think because in former times the developers wherent as many as actual, and there were much less guides/tuts/howtos which made an user less unsecure.
nevertheless, your support is gorgeous: friendly, fast and ultracompetent.
edit: can i change the title in solved anyhow?

xmaskx said:
thanks so much!
flashed checkrom notehd via cwm. boots clean and nicely up.
i flashed/rooted some phones before htc hero, hd2, zte blade. but none of them, even the hd2 with its windows conversion was as unclear as the n7000. i think because in former times the developers wherent as many as actual, and there were much less guides/tuts/howtos which made an user less unsecure.
nevertheless, your support is gorgeous: friendly, fast and ultracompetent.
edit: can i change the title in solved anyhow?
Click to expand...
Click to collapse
Your welcome!
Glad to see you're up and running again
Oh and if you go to your very first post on this thread, Click edit then you should be able to put [Solved] in the title bar

Buddy start from crap...and one advice..u never know the depth of an ocean unless u dive into it..be brave...just follow cursed4eva tutorials on youtube.u will know everything...and only u can teach uraelf no one else..what i did when i was a boy,i mean when i was new to note,i followed this guy and he saved my daymy recommendations is to use odin...flash a 3file rom whose links are provided in cursed4eva's video..and flash it...u will be on stock gb..
Sent from my GT-N7000 using xda app-developers app