Hi
I was stupid and bricked my phone after trying to flash N7000XXKJ1 firmware. I guess PIT file was wrong..
Kias don't see it now and ODIN is failing to flash any KJ4 firmware, and also there is no pit in them.. any ideas or just throw it away?
Thanks!
dont throw it away you just need the correct pit file.
If you would like you can send it to me instead of throwing it away.
Hmmm I've never used PIT files when flasing on Galaxy S2 and Note. Why do you use them?
Maybe you need a jig to solve the problem.
Some update: I used borrowed jig and it is worked, sort of..
I am getting into boot loader I guess which says - can't download. battery too low.
However phone doesn't charge in current state. Is it common problem? Any ideas how to charge it before I am start looking for another Note with charged battery =)
kromosto said:
dont throw it away you just need the correct pit file.
Click to expand...
Click to collapse
all stock firmwares comes without pit file, except one I used.. is it maybe possible to extract pit info from working phone?
just to update, managed to fix by flashing N7000XXKJ4_N7000XEOKJ1_N7000XXKJ4_HOME.tar.md5 w/o pit. Had to buy universal external battery charger for $20 since stupid phone wont charge batter in recovery mode.
So i guess my advice is not to flash KJ1 with PIT =)
vvs said:
just to update, managed to fix by flashing N7000XXKJ4_N7000XEOKJ1_N7000XXKJ4_HOME.tar.md5 w/o pit. Had to buy universal external battery charger for $20 since stupid phone wont charge batter in recovery mode.
So i guess my advice is not to flash KJ1 with PIT =)
Click to expand...
Click to collapse
Glad you got it working, would have been very sad if it would have been totally bricked.
Happy days with your new Galaxy Note!
Sent from my GT-I9000 using xda premium
Ok, I don't have a note, but this thread came up with search. I have the problem that I flashed a pit for a galaxy 1900 on my galaxy player. It gives me red errors about "E:failed mount /dbdata (invalid argument)" E:failed mount /cache (invalid argument). I have tried flashing .md5 stock rom via odin, but it doesn't help. I basically need to know how to extract a pit file so that I can tell someone else how to that has my device.
when i flash firmware on galaxy A8(sm-a810f)
odin display set partition
Related
Hi all,
I was wondering with the internal SD card issues with this particular phone, is anyone having this or any other issues with the SD card dying in the I9000 International version?
My SD card died on me about a week ago. I've had the phone since Oct. 2010. I called Bell and had a replacement phone sent out and it arrived on Monday. I was very sceptical that the new phone would be ok. It's a 10.11 hardware version. By this afternoon the phone died. The menu button and the back button don't light up or work plus when in recovery mode there's an error about dbdata or something like that. It's a little hard to see. So now I have to wait till the phone I sent Bell shows up and that work order is closed before I can put in for another replacement. I really love this phone, but I'm really hating it as well.
Chevy
I believe your phone still recoverable if its showing dbdata.
Have you tryed factory resetting or flashing jl2 with odin?
Sent from my I9000m using XDA's app.
When the internal SD Card dies, you'll get an error about mmcblk0. To fix the dbdata error, you can flash with a firmware that has a dbdata.rfs file in it. If I'm correct, the only Bell firmware available having dbdata is JH2. You could try to either flash only dbdata with a customize tar file with Odin or the extracted dbdata.rfs with Heimdal. Based on my experience, both should work. Note that I've never personally try to only flash dbdata.rfs so I cannot guarantee that it will work or would not mess things up. Anyone else done it?
Note that if you are on JL2, you can have some issues flashing earlier firmwares due to the updated sbl...
Good luck, but don't worry, you can recover from that error...
I believe your phone still recoverable if its showing dbdata.
Have you tryed factory resetting or flashing jl2 with odin?
Click to expand...
Click to collapse
Yes I've tried factory reset and multiple time flashing JL2 with odin 1.3. I even flashed speedmod kernel thinking that with more options something might work.
When the internal SD Card dies, you'll get an error about mmcblk0. To fix the dbdata error, you can flash with a firmware that has a dbdata.rfs file in it. If I'm correct, the only Bell firmware available having dbdata is JH2. You could try to either flash only dbdata with a customize tar file with Odin or the extracted dbdata.rfs with Heimdal. Based on my experience, both should work. Note that I've never personally try to only flash dbdata.rfs so I cannot guarantee that it will work or would not mess things up. Anyone else done it?
Note that if you are on JL2, you can have some issues flashing earlier firmwares due to the updated sbl...
Good luck, but don't worry, you can recover from that error...
Click to expand...
Click to collapse
Ok, so heres what my phone says when in recovery screen:
update media, please wait.
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA
your storage not prepared yet, please use UI menu for format or reboot actions.
copy default media content failed.
How would I flash a custom tar file? I guess I should say, who do I make the custom tar file?
I did try and flash JH2 and part way through the flash the phones screen turned light blue. Odin did not finish the flash. Perhaps that's when the SD card got corrupted. After that I tried going back to JL2 and after many times flashing I finally got JL2 to take.
Is Heimdal easy to use?
Chevy
I just wanted to let everyone know that I was able to recover my and get back working.
Thanks to all,
Chevy
chevy2410 said:
I just wanted to let everyone know that I was able to recover my and get back working.
Thanks to all,
Chevy
Click to expand...
Click to collapse
Good to hear! I was sure it was recoverable ....
A friend of mine is on a T-Mobile UK Samsung Galaxy S. He's stuck on a non-simlocked and non-netlocked 2.2 (JP3), T-Mobile UK aren't releasing 2.2.1 any time soon, and hence he wants to upgrade to an unbranded 2.2.1. He doesn't want to root it... he just wants to be on the same or similar firmware as I'm on (i.e. a stock, stable, UK, unrooted, no "lagfix", etc, 2.2.1).
He has Odin. He has the Windows drivers installed. But I have some questions.
I'm on JPY which has been perfect for me. Zero problems. Is there much advantage with JS5? What has changed/added between JPY and JS5?
Best place to get the European firmware is here? http://forum.xda-developers.com/showthread.php?t=846913
Does he need just a pit file, or other files (e.g. tar) too?
extorian said:
A friend of mine is on a T-Mobile UK Samsung Galaxy S. He's stuck on a non-simlocked and non-netlocked 2.2 (JP3), T-Mobile UK aren't releasing 2.2.1 any time soon, and hence he wants to upgrade to an unbranded 2.2.1. He doesn't want to root it... he just wants to be on the same or similar firmware as I'm on (i.e. a stock, stable, UK, unrooted, no "lagfix", etc, 2.2.1).
He has Odin. He has the Windows drivers installed. But I have some questions.
I'm on JPY which has been perfect for me. Zero problems. Is there much advantage with JS5? What has changed/added between JPY and JS5?
Best place to get the European firmware is here? http://forum.xda-developers.com/showthread.php?t=846913
Does he need just a pit file, or other files (e.g. tar) too?
Click to expand...
Click to collapse
JPY is the lastest UK rom pointless using anything else until its out for the UK
People here just love new numbers and letters.
if he is going from branded would be best to use a pit file. ( pit 512)
then flash the 3 JPY files.
I tend to debrand phones when I get them in as I don't think its fair being stuck on older versions.
So... download Odin + PIT from the top of that page I linked. Flash the 512 PIT using Odin with repartition. Download the JPY firmware from the same page. Flash the 3 files in there. Reboot. Done?
What about clearing cache? Factory reset?
Anything else?
Flashing with Odin will do the factory reset.
Sent from my GTI-9000 Using that XDA app thingy
We've hit a problem
He's been trying the files on this thread: http://forum.xda-developers.com/showthread.php?t=846913
He selected repartition, and flashed the PIT file + JPY_JPY_JPY.tar at the same time (although I believe we've tried one at a time too).
Now when he reboots his phone it doesn't boot - it just vibrates.
He's tried going into recovery and clearing the cache, user data, factory reset, etc.
He can still get into download mode and recovery.
Any suggestions?
extorian said:
We've hit a problem
He's been trying the files on this thread: http://forum.xda-developers.com/showthread.php?t=846913
He selected repartition, and flashed the PIT file + JPY_JPY_JPY.tar at the same time (although I believe we've tried one at a time too).
Now when he reboots his phone it doesn't boot - it just vibrates.
He's tried going into recovery and clearing the cache, user data, factory reset, etc.
He can still get into download mode and recovery.
Any suggestions?
Click to expand...
Click to collapse
Flash pit with repartition selected.
Wait till you see a green box with pass
Unplug phone take battery out.
Then put it back on download
Click reset it Odin
Untick repartition
Select all three jpy files.
Plug in phone. Click start.
Leave till you see green pass.
Sent from my GTI-9000 Using that XDA app thingy
All three files? Should they have come with the firmware download? That only contained a 300MB file JPY_JPY_JPY.tar.
extorian said:
All three files? Should they have come with the firmware download? That only contained a 300MB file JPY_JPY_JPY.tar.
Click to expand...
Click to collapse
Different to how I get them direct for Samsung. So wouldn't know sorry.
Sent from my GTI-9000 Using that XDA app thingy
Can we get the JPY firmware direct from Samsung?
No, but samfirmware.com has all those firmwares.
Yeah they have JPY. However it's just a 512 PIT file. Is that all he needs?
Thats what i flash JPY with .
Error solving with a rom install i usually wipe everything flash back to eclair with 512 pit and repartition . That works i then flash to Froyo no repartition .
jje
Still no joy
OK, so as per the instructions above (I think), we made sure the SIM and SD card are removed. Connected the phone. With Odin, ticked Repartition, and then flashed the 512 .pit file. Waited until we saw the green box in Odin with Pass on it. Unplugged the phone and took the battery out. Put battery back in and booted the phone into download mode. Clicked Reset in Odin. Made sure re-partition was unticked. Made sure the pit file is no longer selected. Added the JPY_JPY_JPY.tar to the PDA section. Plugged in phone. Clicked start. Left it until we saw green pass. On restarting the phone, it to boots past the Galaxy S splash screen and tune then there's a single vibrate followed by a double, which then repeats.
Did we do something wrong? We noticed in Recovery there is an error displayed:
E:can't mount /dev/block/st110 (invalid arguement)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed
What else can we try to get to JPY?
The firmware from samfirmware.com and the firmware linked from the firmwares post on XDA (mentioned earlier) both give an identical JPY_JPY_JPY.tar. We've been unable to find any firmwares with the three JPY files in it. Anyone have a link? Or any other things we can try?
extorian said:
Still no joy
OK, so as per the instructions above (I think), we made sure the SIM and SD card are removed. Connected the phone. With Odin, ticked Repartition, and then flashed the 512 .pit file. Waited until we saw the green box in Odin with Pass on it. Unplugged the phone and took the battery out. Put battery back in and booted the phone into download mode. Clicked Reset in Odin. Made sure re-partition was unticked. Made sure the pit file is no longer selected. Added the JPY_JPY_JPY.tar to the PDA section. Plugged in phone. Clicked start. Left it until we saw green pass. On restarting the phone, it to boots past the Galaxy S splash screen and tune then there's a single vibrate followed by a double, which then repeats.
Did we do something wrong? We noticed in Recovery there is an error displayed:
E:can't mount /dev/block/st110 (invalid arguement)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed
What else can we try to get to JPY?
The firmware from samfirmware.com and the firmware linked from the firmwares post on XDA (mentioned earlier) both give an identical JPY_JPY_JPY.tar. We've been unable to find any firmwares with the three JPY files in it. Anyone have a link? Or any other things we can try?
Click to expand...
Click to collapse
You only use the PIT file and choose re-partition when you have the 3 separate flashing files.
When you have the singe JPY tar file you do not select re-partition and do not use the PIT file - do the following:
put phone into download mode
open Odin
choose your single JPY file as the PDA
make sure "re-partition" is UNTICKED
DO NOT select your PIT file
connect your phone to PC via USB
Odin will detect your phone - click start
let Odin do its stuff until your phone restarts
you are now on 2.2.1 stock
I always do an immediate factory reset.....it seems to sort out any lags or issues that you occasionally get after flashing
good luck!
When he tries to just the .tar without repartition or .pit, Odin fails.
When he tries to format the internal SD card from Recovery it says:
E:can't mount /dev/block/st110 (invalid arguement)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed
It could be that repartitioning previously has messed stuff up? Maybe the wrong PIT (we used 512)? I've read in a few places that Clockwork recovery can fix this. Thoughts?
Or is there a 3 file JPY option we can use?
So, according to this thread http://forum.xda-developers.com/showthread.php?t=784958#8180949 it seems we messed up the partitions by using the pit file originally with repartition. If JPY isn't a full firmware we'll need to flash back to a full firmware to fix it. For example he says "The reason for this screwup is because the JH7 tar package does not contain params or dbdata files, it's not meant to be a full installer- it's meant to be an upgrade. When you partitioned you deleted your existing dbdata and params partitions on your phone, so when JH7 tried to set them up they didn't exist."
We're going to try JPU (somewhere said that's a full update) with 512 pit + repartition, then if that boots update to JPY (no pit, no repartition).
FIXED!!!
After putting the three-file JPU on it from samfirmware.com with 512 pit and repartition, it booted up into 2.2.1 fine. We then flashed the JPY tar (no pit, no repartition), and it's working.
Thanks for the help guys.
Thats great news. X
Sent from my GT-I9000 using XDA App
Hi I am the friend that has caused the headache throughout this thread, I'd just like to say a big thank you to extorian and everyone else that provided input and solutions to getting the rom installed on my phone.
I'm over the moon with the update, phone runs better than ever. Thanks again.
Sent from my GT-I9000 using XDA App
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the <3e> recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Best option for bell users is darkys rom. For further info check darky's rom info
Lyon huntington said:
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the <3e> recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Lyon huntington said:
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Click to expand...
Click to collapse
Flash the stock JL2 firmware with Odin the use super one click to root your phone then flash a new kernel with SGS Kernal flasher from the market... then u will have clockwork recovery then wipe and flash seeArms! Its a great rom but not as fast as darkys
Get the stock firmware from samfirmware.com u can get the .pit file from there to
Sent from my bell GT-I9000m using XDA App
repartition yes? .pit universal?
Jason123420 said:
Flash the stock JL2 firmware with Odin the use super one click to root your phone then flash a new kernel with SGS Kernal flasher from the market... then u will have clockwork recovery then wipe and flash seeArms! Its a great rom but not as fast as darkys
Get the stock firmware from samfirmware.com u can get the .pit file from there to
Sent from my bell GT-I9000m using XDA App
Click to expand...
Click to collapse
So the stock JL2 that I have is a .tar and .dll
I have a 512.pit from a beta 2.2 , are they different?
Did I mention boot problems too? Hanging @ Samsung, no splash ani.
I guess the .pit means yes on repartition?
Thanks
Just use the stock firmware and .pit from samfirmware.com and when Odin is open do not tick off repartirion... just put the .pit in it's spot and the tar in th's PDA part and flash
Sent from my GT-I9000 using XDA App
Now I'm no pro... I just flashed a rom once and got stuck in a boot loop and this is what worked for me
Sent from my GT-I9000 using XDA App
Recovery back but can't mount /dev/block/stl10
Decided to try Darkys v9.2 Resurrection.. no go.
Flashed JL2 and got recovery back but crash after animation.
3e recovery shows me Can't mount /dev/block/stl10.
some threads say dead, others make ref. to old builds.
any current ideas?
thanks
Sorry man like I said I'm no pro... ide flash stock jl2 back and send it back to Samsung for repair maybe they will do something for your warranty
Sent from my GT-I9000 using XDA App
Lyon huntington said:
Decided to try Darkys v9.2 Resurrection.. no go.
Flashed JL2 and got recovery back but crash after animation.
3e recovery shows me Can't mount /dev/block/stl10.
some threads say dead, others make ref. to old builds.
any current ideas?
thanks
Click to expand...
Click to collapse
Download a full firmware for your model and locale (with dbdata in it) and flash it with repartition with the pit proposed (samfirmware.com) then, I believe, you will have a full functioning phone. If everything is ok, then flash ... whatever.
It's Alive! - Can't mount /dev/block/stl10 fixed.
Hey All,
Got it all working again.
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) flash w/repartition.
Flashed w/repartition - I9000XXJP2.7p. (the only FULL firmware I had on-hand)
on reboot the system does a media check and was successful in reformatting and mounting the internal SD.
Phone didn't like the ROM and still logo of death, but..
A quick Jig into Download Mode..
Flashed I9000UGJL2_homebinary_add_param.tar with no repartition
(can't remember if I used .pit).
And Success!! my phone is alive and running 2.2
Thanks for the help, and hopefully this thread can help others.
Everyone should build/get a jig
There is nothing more awesome than being able to force download your non-booting phone.
I could not have done this repair without one.
http://forum.xda-developers.com/showthread.php?t=819551.
The only problem now is it's back to stock...
oh phone, how can I crash you next?
thanks again everybody!
tsinc said:
Download a full firmware for your model and locale (with dbdata in it) and flash it with repartition with the pit proposed (samfirmware.com) then, I believe, you will have a full functioning phone. If everything is ok, then flash ... whatever.
Click to expand...
Click to collapse
Yes, do this. For repartition to work the .tar has to have dbdata.rfs, otherwise it won't work.
Then flash a speedmod kernel with odin for root/cwm and flash you're favourite custom rom
unlock&root owngrade or speedmod kernel? suggestions?
Forgot to mention that all this started after I got the phone back from Bell service after SD card failure.
I know mod methods changed with the latest firmware, as I had used the update.zip method that is now unavailable.
My phone went in unlocked and rooted
the phone came back re-locked (old code doesn't work? wtf?),
and it was unrooted w/3e recovery
Can the phone unlock code change?
Will downgrading to 2.1 make unlocking easier?
or is unlocking just as simple after a speedmod kernel with odin for root/cwm
Which is better?
downgrade the firmware to 2.1 and root using the old update.zip method or speedmod kernel?
Which kernel? (link please )
cheers
Lyon huntington said:
Hey All,
Got it all working again.
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) flash w/repartition.
Flashed w/repartition - I9000XXJP2.7p. (the only FULL firmware I had on-hand)
on reboot the system does a media check and was successful in reformatting and mounting the internal SD.
Phone didn't like the ROM and still logo of death, but..
A quick Jig into Download Mode..
Flashed I9000UGJL2_homebinary_add_param.tar with no repartition
(can't remember if I used .pit).
And Success!! my phone is alive and running 2.2
Thanks for the help, and hopefully this thread can help others.
Everyone should build/get a jig
There is nothing more awesome than being able to force download your non-booting phone.
I could not have done this repair without one.
http://forum.xda-developers.com/showthread.php?t=819551.
The only problem now is it's back to stock...
oh phone, how can I crash you next?
thanks again everybody!
Click to expand...
Click to collapse
All you did was flash UGJL2 with no repartition and it brought your phone back?
Kops said:
All you did was flash UGJL2 with no repartition and it brought your phone back?
Click to expand...
Click to collapse
You know what....I've been trying various combinations of CSC/MODEM/PIT and everything to get this phone running again.
All I did was select a FULL UGJL2, and thats IT. NO pit, NO repartition, and it worked
The best way to revive your I9000m is to first flash JPC (a three file ROM) with 512 PIT and repartition ticked. The phone will still be in a boot loop. Then flash the JL2 PDA without repartition or PIT. The best way to go back to stock! Has always worked for me. I9000m's are not the same as other I9000's and do not flash repartition and the PDA in the same flash! Good luck!
Hi guys for the last 2 days I've been trying to debrick my software bricked gt-i9000.
I've trawled the site and most of the links for what I need are now dead.
I really need a trust worth 512.pit file and I can not find one. Its driving me up the wall
Google is a labyrinth of shaddy looking poo, and the xda threads are mostly months old and out of date (aka the links are dead).
Basically I'm having the /dbdata invalid argument issue. I can't flash to a standard 2.3.3 and as far as I can understand I need to repartition and use a legit 512.pit file with a 2.2.1 build or something similarly old.
I tried to put cyanogen 7.1 on one of my galaxy s phones, the other has ICS on it and is working great, but I buggered this one up :/
Help me oh lords of the interwebs you are my only hope.
Here you are .
Ah ****e.
I think I used a screwy 512.pit file
My phone is hanging in download mode now and odin has been saying "DO NOT TURN OFF TARGET" for about 15-20min.
Thanks man, now to try and flash this thing again.
Sadly, it didn't work.
I still get the red writing and the install fails and boot loops. I'll have to take it to some one that knows more than I because I can't damn well figure it out :/
Cheers for the help
dangah said:
Sadly, it didn't work.
I still get the red writing and the install fails and boot loops. I'll have to take it to some one that knows more than I because I can't damn well figure it out :/
Cheers for the help
Click to expand...
Click to collapse
maybe you can post your setting in odin here?
The usually way to unbrick terminal with download mode working is to flash a full gb firmware without repartition if you wasn't on cm like firmware or with repartition if you had cm or other rom with mtd partition system.
Inviato dal mio GT-I9000 usando Tapatalk
Try flashing just a kernel...
Sent from my GT-I9000 using XDA
From ics/CM7/miui to stock GB: Use 512.PIT, tick re-partition in Odin.
All links in Ramads thread are valid mediafire downloads. http://forum.xda-developers.com/showthread.php?p=14273101
Follow instructions in same thread how to put PDA, MODEM and CSC in Odin.
Important: Click 'Start' 5 - 10 sec. after you have connected USB cable. Odin will timeout looking for phone if you wait too long.
Sent from my GT-I9000
Have you tried Heimdall & a Heimdall packaged firmware?
Worked for me when I was attempting to go back to stock & Odin screwed up mid flash. I find Odin a pain & I blame it for screwing it up (& maybe partly my own fault)
Let me know if you need the files - the firmware is named as XWJVZ.
Hello guys!
My friend gave his Galaxy Note for me to get a brick fix. He said that he flashed the German ICS STOCK ROM and wiped using CWM. He said that he entered in a bootloop. Then he tried to flash using ODIN, but it stopped at factoryfs, as known at the eMMC bug. In the bug, he disconnected the USB cable and he is seeing a message which says to connect to Kies and select recovery. But he said that didn't worked and Kies didn't recognized the phone. Even with ODIN, loaded with PIT and PDA, the phone wasn't able to receive factoryfs, the same file from the 1st error. I followed a lot of tutorials here on XDA and used the search to find a similar thread. He needs help, since recovery mode, charging mode and normal mode are blocked by the message. I need a ROM which contains the PDA, the CSC and the MODEM files. I already have the PIT, so I need those 3 files to try again.
--PHONE DETAILS--
Samsung Galaxy Note N7000
16GB Storage
LAST Firmware completelly flashed: XXLRQ (I think that is the firmware which you can't wipe)
ICS Stock
Thanks!
EDIT: I tried with another GB firmware and with an ICS firmware. Still NOT WORKING.
EDIT #2: The phone still have Download mode open!
BIGGEST EDIT:
All of the methods in this thread are NOT WORKING. Still stops at factoryfs and CWM says "Installation Aborted". SO, WHAT I CAN DO? He is desperated, I'm desperated. PLEASE ANSWER FAST !!
Mr.Indigo said:
Hello guys!
My friend gave his Galaxy Note for me to get a brick fix. He said that he flashed the German ICS STOCK ROM and wiped using CWM. He said that he entered in a bootloop. Then he tried to flash using ODIN, but it stopped at factoryfs, as known at the eMMC bug. In the bug, he disconnected the USB cable and he is seeing a message which says to connect to Kies and select recovery. But he said that didn't worked and Kies didn't recognized the phone. Even with ODIN, loaded with PIT and PDA, the phone wasn't able to receive factoryfs, the same file from the 1st error. I followed a lot of tutorials here on XDA and used the search to find a similar thread. He needs help, since recovery mode, charging mode and normal mode are blocked by the message. I need a ROM which contains the PDA, the CSC and the MODEM files. I already have the PIT, so I need those 3 files to try again.
--PHONE DETAILS--
Samsung Galaxy Note N7000
16GB Storage
LAST Firmware completelly flashed: XXLRQ (I think that is the firmware which you can't wipe)
ICS Stock
Thanks!
EDIT: I tried with another GB firmware and with an ICS firmware. Still NOT WORKING.
Click to expand...
Click to collapse
He did successfully bricked his devices.. If you are not able to enter into download mode you have a paperweight in your hands... If he has warranty try to get it replaced.. If he doesn't then try the pit file method on the general forum..
You don't need any 3 files.. It's the same or at least the effect its the same with 1 or 3 files
Tapatalking on my n7000
msedek said:
He did successfully bricked his devices.. If you are not able to enter into download mode you have a paperweight in your hands... If he has warranty try to get it replaced.. If he doesn't then try the pit file method on the general forum..
You don't need any 3 files.. It's the same or at least the effect its the same with 1 or 3 files
Tapatalking on my n7000
Click to expand...
Click to collapse
He is able to enter into DL mode. Even PIT doesn't work.
Mr.Indigo said:
He is able to enter into DL mode. Even PIT doesn't work.
Click to expand...
Click to collapse
Well then your only option its the warranty or pay samsung either for a new phone or a mother board replacement...
That pit file method its only a partial solution to help you get your device partially working maybe a couple of months.. When the emmc bug happens it does damage the Emmc chip so the hardware its fried and there's no software that can repair it..
The pit method could work for someone but not for others.. Depends on the damage
Tapatalking on my n7000
Here I think you may find a solution for your problem.
If you think you need to flash the 3 files with odin try flashing an old GB ROM, you can find it here, some (NOT ALL) of the ROM in this post has PDA, CSC and PHONE part.
Good luck!
andreaonelove said:
Here I think you may find a solution for your problem.
If you think you need to flash the 3 files with odin try flashing an old GB ROM, you can find it here, some (NOT ALL) of the ROM in this post has PDA, CSC and PHONE part.
Good luck!
Click to expand...
Click to collapse
I tried it, but didn't work. This solution is too much dangerous?
andreaonelove said:
Here I think you may find a solution for your problem.
If you think you need to flash the 3 files with odin try flashing an old GB ROM, you can find it here, some (NOT ALL) of the ROM in this post has PDA, CSC and PHONE part.
Good luck!
Click to expand...
Click to collapse
It's doesn't matter if it's 1 or 3 files.. The pit file just repartition the emmc in order to reacomodate the memory and so you can flash the rom.. Flashing separately phone csc and PDA won't make any difference..
Tapatalking on my n7000
Have you tryed to flash a GB ROM with three files?
And the solution proposed here?
andreaonelove said:
Have you tryed to flash a GB ROM with three files?
And the solution proposed here?
Click to expand...
Click to collapse
Mr.Indigo said:
Hello guys!
My friend gave his Galaxy Note for me to get a brick fix. He said that he flashed the German ICS STOCK ROM and wiped using CWM. He said that he entered in a bootloop. Then he tried to flash using ODIN, but it stopped at factoryfs, as known at the eMMC bug. In the bug, he disconnected the USB cable and he is seeing a message which says to connect to Kies and select recovery. But he said that didn't worked and Kies didn't recognized the phone. Even with ODIN, loaded with PIT and PDA, the phone wasn't able to receive factoryfs, the same file from the 1st error. I followed a lot of tutorials here on XDA and used the search to find a similar thread. He needs help, since recovery mode, charging mode and normal mode are blocked by the message. I need a ROM which contains the PDA, the CSC and the MODEM files. I already have the PIT, so I need those 3 files to try again.
--PHONE DETAILS--
Samsung Galaxy Note N7000
16GB Storage
LAST Firmware completelly flashed: XXLRQ (I think that is the firmware which you can't wipe)
ICS Stock
Thanks!
EDIT: I tried with another GB firmware and with an ICS firmware. Still NOT WORKING.
EDIT #2: The phone still have Download mode open!
Click to expand...
Click to collapse
I have the same problem!!!
I'm desperated, since it's my main phone!
I will try the last solutions!!!
andreaonelove said:
Have you tryed to flash a GB ROM with three files?
And the solution proposed here?
Click to expand...
Click to collapse
That's what I need.... I didn't found the 3 files. I will try!
andreaonelove said:
Have you tryed to flash a GB ROM with three files?
And the solution proposed here?
Click to expand...
Click to collapse
This solution is based on a GB kernel. I'm in the same situation as Mr.Indigo, with the same ROM and the same problems. I need to use CM9 kernel to use with ICS, right? Or I can use GB kernel?
Aldenucci said:
This solution is based on a GB kernel. I'm in the same situation as Mr.Indigo, with the same ROM and the same problems. I need to use CM9 kernel to use with ICS, right? Or I can use GB kernel?
Click to expand...
Click to collapse
IDK, you must do it at your own risk.
andreaonelove said:
Here I think you may find a solution for your problem.
If you think you need to flash the 3 files with odin try flashing an old GB ROM, you can find it here, some (NOT ALL) of the ROM in this post has PDA, CSC and PHONE part.
Good luck!
Click to expand...
Click to collapse
I tried this solution. The cellphone starts to make strange noises and a lot of characters entered in ADB command. Any other solution??
Mr.Indigo said:
I tried this solution. The cellphone starts to make strange noises and a lot of characters entered in ADB command. Any other solution??
Click to expand...
Click to collapse
Yeah already told you.. Walk to the nearest samsung center and claim the warranty or pay for a replacement
Tapatalking on my n7000
unfortunately sound like a brick to me. failed flashing via pc odin and stuck at factoryfs has something to do with your root. so i heard.. the best way is to send it to SSC for repair while you still have the warranty
msedek said:
Yeah already told you.. Walk to the nearest samsung center and claim the warranty or pay for a replacement
Tapatalking on my n7000
Click to expand...
Click to collapse
He didn't have warranty. I'm trying to flash any PIT which owns factoryfs. He said that fails to wipe into some minutes and I have 88 factoryfs PITs. So I have to flash ALL of them to know. BTW I can flash a kernel using ODIN!
mistajoe83 said:
unfortunately sound like a brick to me. failed flashing via pc odin and stuck at factoryfs has something to do with your root. so i heard.. the best way is to send it to SSC for repair while you still have the warranty
Click to expand...
Click to collapse
My problem is SOLVED!
I found 88 PITs, whick it was intended for factoryfs. I tried the first ten PITs, and the 7th WORKED!
It was 17xx MB. Now the phone is working! THANKS FOR ALL OF YOUR GUYS HELP!