Related
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!
Basically, in all of my wonderful wisdom, decided to try and root my Galaxy S thinking it would be a similar process as to that of the HTC Desire on the ground that I was sick of the way Orange have changed the phone.
Several methods here didn't work so I decided to play about with Odin. I ended up in a boot loop and have now managed to install a US T-moblie OS for a Vibrant handset. Does anyone have any idea how to rectify this horrific balls up? Or where I can get a UK OS from to put back on it? Also I have failed to root the phone.
now seems to be good time to install gb with cfroot kenrel
I know I'm a complete novice and I'm sorry for that, but could you/show or link me to a tutorial of that at all please?
Dave Dave Dave Dave Dave. What have you done?
Don't worry mate, check out the ezbase thread in development section. Full instructions and downloads included. Should sort you right out.
Happy flashing.
Sent from my GT-I9000 using XDA Premium App
So far so good, just lacking the room as I have no idea what I should download.
Any idea?
Dave759 said:
So far so good, just lacking the room as I have no idea what I should download.
Any idea?
Click to expand...
Click to collapse
Probably best to go for rom kitchen jvh - stable, customisable and great help from the users in the thread. Once you've a bit more experience with sgs flashing, then insanity all the way.
Hope it all goes well mate.
Edit: dave, have you flashed the gingerbread base rom from the ezbase thread yet?
Sent from my GT-I9000 using XDA Premium App
I couldn't tell you where I'm at. All I've done is follow the steps, downloaded EZOdin V1.70 and this;
Repartition is not mandatory, but it does not hurt to repartition the phone.
Start Phone in Download Mode (No Cable Attached)
Open EZOdin.
- Check Re-Partition
- Select EZbase.pit as PIT
- Select EZbase-PDA-XWJS3.tar.md5 as PDA
- Select EZbase-PHONE-XXJVE.tar.md5 as PHONE
- Select EZbase-CSC-XXJV1.tar.md5 as CSC
checked everything it says and pressed start. The message box is up to;
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
and has been that way for a good 10 minutes.
this is very strange,anyway
1- did u install kies as its important for the sake of the drivers
2- did u check/tick the 3 boxes in odin
3- if the 2 above are checked try changing the usb port or the computer
keep me informed m8
I think that's the froyo 2.2.1 ezbase base. On the first page, there should be a jvb (I think) ezbase download.
10 minutes is too long, pull battery, disconnect usb, close ezodin, reopen, re-add files, go to dl mode on phone, connect usb, wait for yellow light in ezodin, press start.
Sent from my GT-I9000 using XDA Premium App
Dave, if you want to pm me your home number, i can call you to talk you through it.
Worst case scenario is a flash of eclair jm9 - will sort 99% of snags.
Sent from my GT-I9000 using XDA Premium App
Do you have 3 button combo?
If so...
Download STOCK JVH gingerbread with bootloaders.
Follow instructions on JVH thread in the first post.
I would go into recovery, factory reset and format internal sd card before flashing.
Use 512.pit and repartition and use odin.
http://forum.xda-developers.com/showthread.php?t=1011901
Download this...
http://www.multiupload.com/INQRN37ODA
You can get odin and 512 pit from samfirmware.com
Then when you have a working phone you can root with cf-root.
http://forum.xda-developers.com/showthread.php?t=788108
And maybe install the screen off animation with battery percentage...
http://forum.xda-developers.com/showthread.php?t=1055979
This is the link to $omator's file for JVH...
http://forum.xda-developers.com/attachment.php?attachmentid=591847&d=1305015870
In my opinion, just get a stock JVH ROM from Ramad
Get it here
Run the .exe and the 3 files will be unpacked.
Try using Odin 1.3 to flash. I had problems with the phone not booting when I used 1.7
I'm using a 513 Pit so that's what I recommend. 513 was made a day after 512 so it makes me think it may correct some problems as no one knows the full theory behind Partition Information Tables (PIT) files.
When the phone boots for the first time, go into the phone dialler and put in the code below to factory reset the phone. This seems to cure issues that may occur if you just start using the phone as normal.
*2767*3855#
Good luck and post back if you have problems.
goodluck dave
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]
[SOLVED] Read on to find out how.
For this to work you must be able to access "Download mode" and make sure that your phone is recognized by the computer.
Here's what happened:
Phone was running CM7.2 and Glitch 13.1 and I wanted Slim ICS 4.2 so what I did was: wipe user data, cache and devik cache then installed Slim ICS 4.2 through CWM and it worked.
But when the phone was trying to do the initial install after it had rebooted from flashing Slim in recovery it just restarts and loops, always about to do the initial install.
Got fed up with this and sort of rage flashed back to stock loosely following THESE instructions, but I didn't follow the instructions like I should have. What I did instead was flash my stock JVC gingerbread firmware (Orange of the UK branded) TAR file as PDA with the 20100512 PIT file in Odin3 1.87. And yes I did check "Repartition" in Odin, because the instructions I had for Hemidall said to have repartition "CHECKED".
This is the result, from 3e recovery.
--Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: getprop("ro.product.device") == "GT-P1000" ||
getprop("re.build.product") == "GT-P1000" ||
getprop("ro.product.device") == "GT-i9000" ||
getprop("re.build.product") == "GT-i9000"
E:Error in /cache/recovery/sec_csc.zip (Status 7)
Installation aborted.
So then some poo came out... but I thought if I followed the instructions EXACTLY as they were writtin these problems would all go away and I can go back to not crapping myself
I followed the instructions perfectly and I still get the same screen as written above, in 3e recovery.
So now too scared to touch the phone without some brief guidance, can someone please please help as I'd really like to be able to start testing and benchmarking ICS roms.
Thank you again XDA
You can try flashing with my recovery kit, worth trying, just download it, unzip and read the .txt first, pictorial instructions included
http://db.tt/MOGZx01S
Sent from my GT-I9300 using xda premium
Thank you slaphead20
My only question is: What have I done, and why will ezbase recovery kit for gb fix it?
Before trying ezbase (which is downloading now and will take 22 minutes) should I try flashing to stock like I normally would with Odin where by I just flash the one TAR file in PDA? But if you don't think it will help then I wont touch it until recovery kit gets here :/
Odin can't see the phone, but Hemidall works perfectly... do I have to somehow revert the drivers in Device Manager for Odin to see my phone again?
As you know Hemidall comes with that "Zadig" drivers thing and it was after using this that Odin stopped seeing my phone
mod2max said:
Odin can't see the phone, but Hemidall works perfectly... do I have to somehow revert the drivers in Device Manager for Odin to see my phone again?
As you know Hemidall comes with that "Zadig" drivers thing and it was after using this that Odin stopped seeing my phone
Click to expand...
Click to collapse
You may need to reinstall driver s,, not sure as I don't use heimdall, the kit I sent you is an Odin based kit, will give you a stripped down gb Rom called ezbase, there is a pit file included, and also a cf root kernel, so you should be able to use heimdall
Sent from my GT-I9300 using xda premium
slaphead20 said:
You may need to reinstall driver s,, not sure as I don't use heimdall, the kit I sent you is an Odin based kit, will give you a stripped down gb Rom called ezbase, there is a pit file included, and also a cf root kernel, so you should be able to use heimdall
Click to expand...
Click to collapse
Well it's 2:00AM Sunday morning here in the UK, got home a few moments ago and had a brainwave "Why not use a virtual machine to install the phone's drivers and test Odin" so I did and it works fine I will flash the recovery kit in the morning (even though it is morning... ) and let you know how it goes.
Thought I'd reinstall the drviers on my PC since it worked on the virtual machine, got Odin back
However, I set up the flash as described in EZOdin and it got to HERE and then it got stuck... been stuck for about 20 minutes now.
In the white "Connection" status box in Odin it says "Set Partition"
Phone is still plugged in, haven't seen any progress bars on the phone or any change in Odin, is it safe to remove the phone (Hemidall would say "Hemidall crashed" but is safe to remove the phone)?
UPDATE
Ok so got the phone removed, safely I think...
It's gone a bit funny like it did when Hemidall crashed... so no boot logo or kernel splash etc, just a white picture of a phone and dotted line connection to a pc. But I fixed that by flashing again with exact set up from the instructions for Hemidall, it got logos back and recovery etc.
But can still access download mode and and Odin sees the phone, hope is not lost
Is it worth trying to flash the files in normal Odin3? I have version 1.87. It might be a one off crash (like Hemidall's was) but I crap my self when stuff like this happens and would rather it didn't do it again
mod2max said:
is it safe to remove the phone (Hemidall would say "Hemidall crashed" but is safe to remove the phone)?
Click to expand...
Click to collapse
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again
xsenman said:
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again
Click to expand...
Click to collapse
Ahhh that must be what it is, upgrade mode :/
Well I got the phone out and download mode still works and Odin can still see the phone, so I'm pretty safe atm (I think.....) battery has already been removed etc.
But while download mode and Odin work I'm not doing more to the phone now, if I carry on I will actually have heart failure. So I will pick this up again later on this afternoon.
xsenman said:
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again
Click to expand...
Click to collapse
Could you please explain what you mean by "using Pit first"? I thought pit files go in it's space in Odin at the same time as flashing everything else (when you use Pits of course).
My current plan is, install the usb drivers on a machine that has never been touched by me, Odin or anything else. So maybe this will determine whether it is EZOdin playing up on the latest version of Windows 7... if it's not either of those then I guess that means I am no longer able to flash PIT files and am screwed.
But I will find out, fingered crossed!
Slaphead20, I've taken the PDA, PHONE and CSC files you gave me and would like to flash them in Odin3. I've stripped the files of their ".md5" extensions and now they are just ".tar" but I was wondering if this would have any bad effects while flashing? Does Odin3 take ".md5" files like EZOdin does? Is it safer to leave the files in their ".md5" format?
How it was solved:
I took the "ezbase recovery kit" that was kindly made available to me from Slaphead20 and unpacked the "PDA", "PHONE" and "CSC" .md5 files, I first removed the ".md5" extensions from the end of each file name and then used WinRAR to unload the contents of each ".tar" folder into a normal uncompressed folder for use with Hemidall.
**I did find that while unpacking these files there was two "cache.rfs" files, they are both the same but we just use one when using Hemidall.**
The reason I used Hemidall instead of EZOdin (which is supplied with the recovery kit) or Odin3 is because firstly when I tried to use the recovery kit in EZOdin, it crashed and I had to unplug the phone unwillingly (that caused "Upgrade mode"). And the reason for not using Odin3 was fear of the same.
The process:
**Make sure your handset has plenty of juice cause the last thing you want is a bad flash and then not being able to charge the batter without an external charger.**
Firstly, get your phone into "Download Mode" with the USB cable unplugged from the computer
Set up Hemidall like so...
**Make sure "Repartition" is checked and "No Reboot" is unchecked for this bit!**
Partition ID______Partitions (Files)
____0___________IBL+PBL = boot.bin
____3___________SBL = Sbl.bin
____6___________KERNEL = zImage
____11__________MODEM = modem.bin
____21__________PARAM = param.lfs
____22__________FACTORYFS = factoryfs.rfs
____23__________DBDATAFS = dbdata.rfs
____24__________CACHE = cache.rfs
After the flash is complete the phone will reboot, the first ever boot of the OS is a long one so just be patent and it will eventually (fingers crossed) load.
Q: What is it doesn't load?
A: Flash the above again until it does, or your doing something wrong -_-"
Once the phone has loaded, shut it down and then go back into "Download Mode" with the USB cable unplugged. Now, with Hemidall select the same pit file as before but make sure that "Repartition" and "No Reboot" are both unchecked, then click "Add" and select "Kernel" for the "Partition Name", browse to the "zImage" file in the "CF -Root for EZbase" folder (or similar). Plug the USB cable into the phone, click "Start" and wait for the phone to reboot, then you will have Root (+ SU) and CWM.
**If any flash you make with Hemidall stalls (fails) after you click "Start" and you have to unplug the phone it will now be stuck in "Upgrade Mode" but get into "Download Mode" and follow this guide from the start.**
Thank you Slaphead20 for this one
hi, thx for such an informative insight here...
there should be a sticky thread for such kind of issues and which would get everyone going in quick !
not sure if mods are listening to this
anyways thanks again
Sent from my GT-I9000 using xda app-developers app
Just as a heads up, all credits to
Nitr8 for the ez components
Chainfire for cf kernel
Samsung for pit file
Link to recovery kit, unzip and read.txt
http://db.tt/MOGZx01S
Sent from my GT-I9300 using xda premium
dude, ive had similar problems, due to this thread i was able to fix, and get my phone running. now ive got one small problem left. cwm wont flash. im stuck on 3e recovery, when i try to flash update.zip, it fails, and obviously i cant update to different rom with that. any hints on how to get cwm on it? and how do u generally get cwm when using that recovery pack?
banana_plug said:
dude, ive had similar problems, due to this thread i was able to fix, and get my phone running. now ive got one small problem left. cwm wont flash. im stuck on 3e recovery, when i try to flash update.zip, it fails, and obviously i cant update to different rom with that. any hints on how to get cwm on it? and how do u generally get cwm when using that recovery pack?
Click to expand...
Click to collapse
flash the cf kernel as pda in Odin, no repartition....for crying out loud there's a pictorial guide with screen shots of Odin loaded up....:banghead::banghead::banghead::banghead:
Sent from my GT-I9300 using xda premium
slaphead20 said:
flash the cf kernel as pda in Odin, no repartition....for crying out loud there's a pictorial guide with screen shots of Odin loaded up....:banghead::banghead::banghead::banghead:
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
now guess what? i did flashed CF kernel. guess does it load CWM afterwards? no. 3e recovery loads up instead. it actually failed for the first time (when flashing in ezodin as pda) the second time it was flashed right. but no CWM. was following tutorial step by step. im sure i was doing exactly whats stated in it. any ideas my dear ?
banana_plug said:
now guess what? i did flashed CF kernel. guess does it load CWM afterwards? no. 3e recovery loads up instead. it actually failed for the first time (when flashing in ezodin as pda) the second time it was flashed right. but no CWM. was following tutorial step by step. im sure i was doing exactly whats stated in it. any ideas my dear ?
Click to expand...
Click to collapse
did you flash as a separate step from the ez base flash?
Sent from my GT-I9300 using xda premium
slaphead20 said:
did you flash as a separate step from the ez base flash?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
dude, youre absolutely right. as a separate step. been through google for hours, untill now its unsolved for me. 3e recovery stays in.
banana_plug said:
dude, youre absolutely right. as a separate step. been through google for hours, untill now its unsolved for me. 3e recovery stays in.
Click to expand...
Click to collapse
try a new download of the kit, no one, and I mean no one, has ever had that before
Sent from my GT-I9300 using xda premium
slaphead20 said:
try a new download of the kit, no one, and I mean no one, has ever had that before
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
yes. you probably understand why im actually posting here. i nearly never post, not because im a techie, im a total noob, its just that im good at research, and i dont like to bother others. but at this point im pretty tired. will go thru the procedure again (third time) and see what happens. ****ing 3e recovery!
p.s correct me, replacing the kernel with CFROOT one from the pack, should automatically flash CWM? if thats the case, i might go and find another kernel with such capabilities, am i on a right path? p.s when i get rich, ill donate to you a beer ;D
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!