Dear XDA geniuses, i could really need your help!
for the last month my battery started to run out pretty fast. Couple of days ago i noticed a weird thing, the screen started to flicker, and the phone disconnected itself from the cellular network. And then the worst has happened- the phone just shuts down itself and ever since i cant turn it on.
The only thing i can do is go into download mode, so i switched batteries and tried to install a stock firmware from sammobile with odin.
at first odin failed and told me that there is no PIT partition, i pressed reset and tried again from a different USB and then it told me "operation failed" without any reason. I tried it again and again with different version of odin, different firmware, different cable and every time the same thing- first no PIT partition and then just fail..
Please Help!
GuyTa said:
Dear XDA geniuses, i could really need your help!
for the last month my battery started to run out pretty fast. Couple of days ago i noticed a weird thing, the screen started to flicker, and the phone disconnected itself from the cellular network. And then the worst has happened- the phone just shuts down itself and ever since i cant turn it on.
The only thing i can do is go into download mode, so i switched batteries and tried to install a stock firmware from sammobile with odin.
at first odin failed and told me that there is no PIT partition, i pressed reset and tried again from a different USB and then it told me "operation failed" without any reason. I tried it again and again with different version of odin, different firmware, different cable and every time the same thing- first no PIT partition and then just fail..
Please Help!
Click to expand...
Click to collapse
You probably need to repartition your phone using a PIT file. It is very risky though so do so at your own risk.
ArkThompson said:
You probably need to repartition your phone using a PIT file. It is very risky though so do so at your own risk.
Click to expand...
Click to collapse
do you have a good guide for it? and where i can get a good .PIT file for I9305?
GuyTa said:
do you have a good guide for it? and where i can get a good .PIT file for I9305?
Click to expand...
Click to collapse
I don't think there are any guides for how to do it on the i9305. This guide is potentially applicable (just use i9305 files instead of Galaxy Duos ones) http://forum.xda-developers.com/showthread.php?t=2659635 but like I said, do so at your own risk.
This is the only PIT file I've been able to find for the i9305 http://forum.xda-developers.com/gal...fo-i9305-pit-file-flash-analysis-pit-t1950591 but I've never used it so I don't know if it works, especially on newer Android versions.
ArkThompson said:
I don't think there are any guides for how to do it on the i9305. This guide is potentially applicable (just use i9305 files instead of Galaxy Duos ones) http://forum.xda-developers.com/showthread.php?t=2659635 but like I said, do so at your own risk.
This is the only PIT file I've been able to find for the i9305 http://forum.xda-developers.com/gal...fo-i9305-pit-file-flash-analysis-pit-t1950591 but I've never used it so I don't know if it works, especially on newer Android versions.
Click to expand...
Click to collapse
Thanks for the help!
Before i try these one, does anyone has a PIT file that you tried on your I9305??
ArkThompson said:
I don't think there are any guides for how to do it on the i9305. This guide is potentially applicable (just use i9305 files instead of Galaxy Duos ones) http://forum.xda-developers.com/showthread.php?t=2659635 but like I said, do so at your own risk.
This is the only PIT file I've been able to find for the i9305 http://forum.xda-developers.com/gal...fo-i9305-pit-file-flash-analysis-pit-t1950591 but I've never used it so I don't know if it works, especially on newer Android versions.
Click to expand...
Click to collapse
Did what you offered, but odin got stuck in the "Get PIT for mapping.."
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUFNJ1_I9305XEOFNJ1_I9305XXUFNJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Click to expand...
Click to collapse
Tried to reboot my phone and PC, but still stuck. do you have an idea why?
GuyTa said:
Did what you offered, but odin got stuck in the "Get PIT for mapping.."
Tried to reboot my phone and PC, but still stuck. do you have an idea why?
Click to expand...
Click to collapse
Not sure, you could try a different Odin version maybe. I looked around online a bit and some people had luck trying it with a different cable. If that doesn't work then the PIT is probably no good. I could try dumping mine if you want but it will be the first time I've done it so don't blame me if it bricks your phone.
ArkThompson said:
Not sure, you could try a different Odin version maybe. I looked around online a bit and some people had luck trying it with a different cable. If that doesn't work then the PIT is probably no good. I could try dumping mine if you want but it will be the first time I've done it so don't blame me if it bricks your phone.
Click to expand...
Click to collapse
Tried different odin version, it doesn't stuck but says "re-partition operation failed". Tried different cable, didn't help.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUFNJ1_I9305XEOFNJ1_I9305XXUFNJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
looks like i don't have choice but to try you'r PIT file. If that won't work I'm thinking of taking it to a lab, you think they'll be able to fix it?
Thanks A lot for the help!!
GuyTa said:
Tried different odin version, it doesn't stuck but says "re-partition operation failed". Tried different cable, didn't help.
looks like i don't have choice but to try you'r PIT file. If that won't work I'm thinking of taking it to a lab, you think they'll be able to fix it?
Thanks A lot for the help!!
Click to expand...
Click to collapse
I'm starting to think that your eMMC chip is dead so it's possible that your motherboard will need replacing. Try flashing a custom recovery in Odin and seeing if you get any error messages when you boot into it. I can make the file later tonight but it's probably better to try some other things first.
ArkThompson said:
I'm starting to think that your eMMC chip is dead so it's possible that your motherboard will need replacing. Try flashing a custom recovery in Odin and seeing if you get any error messages when you boot into it. I can make the file later tonight but it's probably better to try some other things first.
Click to expand...
Click to collapse
Didn't change much. Tried to flash only the recovery and got "No PIT partition" so i added the PIT file and again "Re-Partition operation failed"
You think its a lost cause? HW problem?
GuyTa said:
Didn't change much. Tried to flash only the recovery and got "No PIT partition" so i added the PIT file and again "Re-Partition operation failed"
You think its a lost cause? HW problem?
Click to expand...
Click to collapse
It's sounding like it might be. I made the file but I haven't tested it or anything. I'll pm you the password for the .zip since I don't want random people flashing it.
ArkThompson said:
It's sounding like it might be. I made the file but I haven't tested it or anything. I'll pm you the password for the .zip since I don't want random people flashing it.
Click to expand...
Click to collapse
Thank you very much for your help but it still doesn't work.. guess its toasted..:crying:
GuyTa said:
Thank you very much for your help but it still doesn't work.. guess its toasted..:crying:
Click to expand...
Click to collapse
That sucks, it sounds like it might have been sudden death syndrome or something because of the screen flickering. The last thing you could try is ticking nand erase all as well but that could potentially completely hard brick the phone because if it still fails to write after wiping you could lose your bootloader.
---------- Post added at 12:14 AM ---------- Previous post was at 12:04 AM ----------
GuyTa said:
Thank you very much for your help but it still doesn't work.. guess its toasted..:crying:
Click to expand...
Click to collapse
I just found this thread http://forum.xda-developers.com/galaxy-s3/help/sudden-death-i9300-t2786220 . You could try doing what he did and put a custom recovery instead of a stock ROM in PDA when using the PIT file but I doubt that it would work.
ArkThompson said:
I just found this thread http://forum.xda-developers.com/galaxy-s3/help/sudden-death-i9300-t2786220 . You could try doing what he did and put a custom recovery instead of a stock ROM in PDA when using the PIT file but I doubt that it would work.
Click to expand...
Click to collapse
I tried it with the last PIT file, still didn't work..
Related
Hi everybody!
This is my first posting here, I hope it's in the right category. I've used the search function, found similar problems but no one facing the same issue. I wanted to upgrade to Android 2.3.3 (2.3.4) using Odin. I tried three different Firmware releases but none worked. This is what happens in Odin:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XWJVI_Sbl.tar.md5 is valid.
<OSM> PHONE_XXJVO.tar.md5 is valid.
<OSM> CSC_DBTJV2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> param.lfs
<ID:0/006> zImage
I tried with and without repartition. Sometimes the process stops at the SetupConnection line, sometimes at zImage when obviously the kernel should be installed. When in download mode, I see a blue progress bar starting to move across the phone screen, but soon later the whole display turns green/blue/white (it always had a different color) with no more text. Hours later Odin finally displays a FAIL message.
I tried firmware versions I9000XXJVQ and I9000XXJVR from samfirmware.com with 512 PIT file. I recognized some Kies-Thread running in the background on my Win7 machine, which I killed to prevent any problems.
In another forum I was told this issue might be related to some lagfixes installing ext4. When I read that it came to my mind that I indeed had installed the voodoo lagfix in February - I had completely forgotten about that. However, is there a chance to recover the phone? Putting it into DL mode is the only thing that works. Any help is appreciated!
Can you go in recovery mode to disable the lagfix? and when you use the 3 part file always check re-partition.
Had similar problems with Windows 7 x64, 2 in 3 flashes would fail.
Try another pc if possible with Xp.
kuribo67 said:
Can you go in recovery mode to disable the lagfix?
Click to expand...
Click to collapse
Well, I tried, but I did not succeed - (Hold Vol up + Power on) but I'll try again. Is it absolutely necessary to remove the lagfix? As mentioned before someone told me that ext4 might be causing those problems. However, I though the sd was repartitioned (when checkbox is ticked) and the firmware is a kind of disk image which is installed and thus overwrites the existing file system?
aileron79 said:
Well, I tried, but I did not succeed - (Hold Vol up + Power on) but I'll try again. Is it absolutely necessary to remove the lagfix? As mentioned before someone told me that ext4 might be causing those problems. However, I though the sd was repartitioned (when checkbox is ticked) and the firmware is a kind of disk image which is installed and thus overwrites the existing file system?
Click to expand...
Click to collapse
it's vol up + home button + power on, but don't release the button untill your are in the menu.
A stock firmware is made for RFS partition not ext4, i think it's that the problem, but i may be wrong.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XWJVI_Sbl.tar.md5 is valid.
<OSM> PHONE_XXJVO.tar.md5 is valid.
<OSM> CSC_DBTJV2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> param.lfs
<ID:0/005> zImage
<ID:0/005> boot.bin
<ID:0/005> Sbl.bin
<ID:0/005> factoryfs.rfs
Thank you all so far! Well, it almost worked - at least kind of. I tried it a couple of times, rebooted the PC, rebooted the phone, reinstalled drivers, used another USB port. After a couple of retries it stopped at "factoryfs.rfs" - which obviously contains the file system. This makes me guess that it does not matter which FS currently is installed as it gets overwritten by this factoryfs-thing. Please correct me if I am wrong!
Still, any help on this topic is gladly appreciated!
when you flash pda in odin the file system is over-written and reverts to rfs.
Try without re-partition ticked. Also after several attempts your battery may have no juice left in it: pull the battery, let it sit a couplce of minutes and then plug it in and see if it will re-charge -- may not, you might be stuck at download and odin.
Flash an older 2.2 firmware first: pda. phone and csc, don't bother with the pit file and don't bother with re-partition -- this is just to get you back and working, you can then charge the battery and update to jvr after.
Also check the thread on unbricking the phone -- most issues with flashing are recoverable, its just persistence.
lgsshedden said:
when you flash pda in odin the file system is over-written and reverts to rfs.
Try without re-partition ticked. Also after several attempts your battery may have no juice left in it: pull the battery, let it sit a couplce of minutes and then plug it in and see if it will re-charge -- may not, you might be stuck at download and odin.
Click to expand...
Click to collapse
Well, I tried to flash with and without repartition/pit-file. The download process hangs at different stages. I doubt it has to do with the battery, as the phone has been attached to the PC for almost three days now, I guess the battery is charged then...?
[/QUOTE]
Flash an older 2.2 firmware first: pda. phone and csc, don't bother with the pit file and don't bother with re-partition -- this is just to get you back and working, you can then charge the battery and update to jvr after.
Also check the thread on unbricking the phone -- most issues with flashing are recoverable, its just persistence.[/QUOTE]
To which of the thousands of unbricking threads do you refer? I read something about a tool which puts the phone into recovery mode, from where I can format the sd. However, I can't get to recovery mode by pressing vol up, home + power, i just can enter download mode. I have tried various firmwares, neither did work...
Thanks for your help so far, maybe you can give me another hint on the thread you're talking about?
Try rebooting the phone,rebooting the pc,use a different usb cable(this part made it work for me), and try again. Hope it helps man cause i've been down that road and it sucked bricked my sgs 2 times but thankfully revived it because heimdall one click un-brick oh and 1 more thing if you use 3 files check re partition
Sent from my GT-I9000 using xda premium
Mate, try a full 3 file flash and a pc with Win XP 32-bit and ODIN 1.83
Worked for me
Good luck flashing !!
Thank you all guys, it worked - even though it was none of the tips provided here. I have no clue what the problem was, I moved to another PC, it took me three tries to flash the phone.
- The second PC was Win7 64bit as well.
- I used the original cable (tried with another one as well, no difference)
- I used just the drivers without any Kies installation.
- I used a SINGLE FILE FLASH with Android 2.2.1 first (which I was then unable to boot as it stuck with the S symbol during boot)
- Flashed 2.3.4 afterwards - worked.
My phone has never ever been running so smoothly before, even with lag fixes!
Unfortunately, my external SD makes troubles, but let's see how to fix that.
My note to all of you guys facing similar problems:
Some say, use PIT and repartition, some say, don't
Just don't care - for me it finally worked without (single file flash). Try all possibilities.
Some say, install Kies, just because of the drivers, some say, install the drivers without Kies
Just don't care - try either option, it might work - for me the drivers without Kies finally worked but I have no clue if that had any impact.
Some say, use another USB cable, some say use the original one
Just don't care - try different cables if possible, in my case there was no difference.
Some say, use the USB port closest to your MB, others say, try various USB ports
Just don't care - try different ports, the behavior cannot be reproduced, each try the flashing process got stuck at another stage - independent of the USB port used.
Some say, try another computer with another OS
Good choice - that made it working in my case. Even though the other machine was nearly the same with exactly the same OS installed. Also, I have successfully flashed my phone with the first one before.
Thanks guys, you're the best! And give Android 2.3.4 a try, it's FAST and SMOOTH!
Hi everyone
My phone is ''firmware encountered an issue'' i searhing this Thread but i cant do it. Cuz i try everything.
My problem is ODIN always FAIL always
I remove drivers and no kies. I try 6 different offical roms but no different.
So, What did I do?
I use
JB leak
RocketRom JB
RocketRom v12 ICS
I use offical firmware
OJVKL1
XXLRK - N7000VD2LR1
XXLRK
My complaining is This roms is so slow i hate it. Maybe my phone is slow but it's impossible.
HARDRESET-UPDATA-ALLWIPE but always slowly. Firsday everything is good but second day is so laggy. And i think maybe i need a old rom.
GB
So i' download XXLA4 and install. Everything is great but when i XXLA4 root everything messed up.
This is root ''CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5''
and my phone is ''firmware encountered an issue'' and i think back is good ill try XXLRK again but i install mistakenly i select ''N7000_16GB_Q1_20110914-stock.pit'' file and my phone is sleeping now.
So i enter the download mode... Download mode is normal and when i install'a Kernel_JellyBeer_v3.1_STD_CWM_Flashable.zip
I see recovery menu i'll full wipe and back to instaling odin say again FAIL FAIL FAIL...
Please Help me Thank you so much
PEACE
orcunpakten said:
Hi everyone
My phone is ''firmware encountered an issue'' i searhing this Thread but i cant do it. Cuz i try everything.
My problem is ODIN always FAIL always
I remove drivers and no kies. I try 6 different offical roms but no different.
So, What did I do?
I use
JB leak
RocketRom JB
RocketRom v12 ICS
I use offical firmware
OJVKL1
XXLRK - N7000VD2LR1
XXLRK
My complaining is This roms is so slow i hate it. Maybe my phone is slow but it's impossible.
HARDRESET-UPDATA-ALLWIPE but always slowly. Firsday everything is good but second day is so laggy. And i think maybe i need a old rom.
GB
So i' download XXLA4 and install. Everything is great but when i XXLA4 root everything messed up.
This is root ''CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5''
and my phone is ''firmware encountered an issue'' and i think back is good ill try XXLRK again but i install mistakenly i select ''N7000_16GB_Q1_20110914-stock.pit'' file and my phone is sleeping now.
So i enter the download mode... Download mode is normal and when i install'a Kernel_JellyBeer_v3.1_STD_CWM_Flashable.zip
I see recovery menu i'll full wipe and back to instaling odin say again FAIL FAIL FAIL...
Please Help me Thank you so much
PEACE
Click to expand...
Click to collapse
Did you do any full wipes on ics? Where is odin failing, is it factory fs?
Sent from my GT-N7000 using xda premium
happened to me too..
That "firmware encountered an issue" is an indication that the system is corrupted to the point that it cant manage to startup..
I got that problem because of my stupidity.. Plugged my phone to the defective USB port and when I started flashing, I accidentally moved the cable and BAM! Phone is disconnected, and flash failed bigtime..
Your only fix for that if you ask me is do another flash... Try pulling out the battery for 10mins and try to boot into download mode.. That's how i was able to recover my phone from that screen..
I remember that message offering to run emergency recovery using Kies but it is totally useless.. trust me..
Make sure you're plugging in your phone to the USB port DIRECTLY on the motherboard of the computer (the ports at the back) not the ports on the front panel of the case of your computer..
If you're still encountering problems, I believe youre looking at a bricked device and seek more advanced assitance from people here..
SpyderTracks said:
Did you do any full wipes on ics? Where is odin failing, is it factory fs?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
usually factory fail.
i did every time fullwipe
Sounds like superbrick, but try flashing stock gb with pc Odin.
Sent from my GT-N7000 using xda premium
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRQ_N7000DBTLRQ_N7000XXLRK_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yep, that's superbricked. You can either repartition the emmc chip, you'll lose about 3gb of internal sd card and won't be able to run stock roms.
If you have warranty get a reply placement, just say you were updating through Kies when this happened.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Yep, that's superbricked. You can either repartition the emmc chip, you'll lose about 3gb of internal sd card and won't be able to run stock roms.
If you have warranty get a reply placement, just say you were updating through Kies when this happened.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
But i can get download mode and if i install odin ''AbyssNotekernel42CWTouchOriginalLogo'' i get recovery mode...
just once try to remove the battery for a few seconds and put the phone in download mode and flash the rom again or use a GB rom..
nokiamodeln91 said:
just once try to remove the battery for a few seconds and put the phone in download mode and flash the rom again or use a GB rom..
Click to expand...
Click to collapse
i try another laptop now... Cuz i remember what i do.
My last rom is stock XXLRK rom. And i tired slowly
i try everything HARDRESET-UPDATA-ALLWIPE but always slowly. And i think maybe i need a GB rom.
and i download XXLA4 everything is good and when i try root XXLA4.
this file: 'CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5'' stock phone.
Every time i install this way.
Wipe Data/Factory Reset
Wipe Cache Partition
Format/cache
Format/system
Format/data
Wipe Dalvik Cache
Wipe Battery Stats
Fix Permissions
This way always be good for me cuz i try this way 100 times.
I use Odin 1.85 and i use everytime u1_02_20110310_emmc_EXT4.pit (NO-RE-PARTITION)
So i think my fault is mistakenly last time i select ''N7000_16GB_Q1_20110914-stock.pit'' instal a ''CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5''
I'm tired for try.
I try another pc but result is the same. FAIL FAIL FAIL
N7000XXLA4_N7000OJVKL1_N7000XXLA4_HOME.tar
N7000XXLRL_N7000XXLRK_N7000VD2LR1_HOME.tar
N7000XXLRQ_N7000DBTLRQ_N7000XXLRK_HOME.tar
N7000XXLRT_N7000DBTLRT_N7000XXLRK_HOME.tar
N7000XXLRI_N7000OJVLR3_N7000XXLRB_HOME.tar
I'm like a sammy's storage... I try this roms but result is the same.
Where did i wrong? problem is kernel?rom?pit file? ((
where did it fail?
nokiamodeln91 said:
where did it fail?
Click to expand...
Click to collapse
Odin Fail. I think factoryfs.img fail...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRQ_N7000DBTLRQ_N7000XXLRK_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Why now is the wrong? Thing I did always right way
Done dude.. u r good to go now
Problem is solved
Thank you so much ''nokiamodeln91''
dont do any wipes as of now.. u on ICS and an unsafe kernel
dont forget the thanks button
How did you rectify this nokiamodeln91?
Sent from my GT-N7000 using xda premium
OP used an incorrect file with the PIT16GB file.. i just corrected the mistake
nokiamodeln91 said:
OP used an incorrect file with the PIT16GB file.. i just corrected the mistake
Click to expand...
Click to collapse
Nice man, well done.
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
OP used an incorrect file with the PIT16GB file.. i just corrected the mistake
Click to expand...
Click to collapse
Where can I get a copy of this PIT file? My phone is bricked and am only able to get into download mode and not recovery mode.
Hi guys and girls.
I've been frantically searching XDA for the last few hours for a definitive answer, but to no avail, so thought it's about time I just asked!
I have in my possession a Samsung Galaxy S19000, that will only go into download made.
Here's how it happened........
This morning, I was given the phone by my brother in law and asked to root it and upgrade it to a newer/better rom. When it was passed
to me, it was.....
Firmware: 2.2.1
Baseband: 19000XXJY
Kernel: 2.6.32.9
[email protected] #1
Build: FROYO.XXJPY
After a successful root and upgrade, the phone ended up like this...
Firmware: 2.3.7
Baseband: 19000XXJVK
Kernel: 2.6.35.14-g3088622
Build: CyanogenMod-7.2.0-galaxysmtd
The new Rom, as nice as it was, wasnt what he wanted, so he asked me to restore it back to it's stock state. I went into CMW and did a restore, but it failed, and now the phone will only go into download mode.
I've tried flashing a stock rom via Odin, but it got as far as the 'Nand write' stage, then hangs.
Kies doesn't show up the device in 'Emergency firmware recovery' either.
I no all is not lost, so I'm not giving up. Any help will be much appreciated.
:fingers-crossed:
Can you post the whole Odin Log?
Normally this happen when the partitions on the embedded multi media card gets corrupted for whatever reason, also known as the emmc.
Maybe it helps to flash the pit file to repartition.
To add.....
When the phone is off, it displays the 'phone and computer with an explanation mark triangle inbetween symbol', and Kies doesnt recognise it. When I enter download mode, Kies hangs at 'Connecting' for.....well..ever! So atleast I know it's recognised by my PC (ish) and it isn't completely dead :silly:
I had the same thing with the triangle a few months ago.
I just flashed a Stock Firmware with Repartition. Just be sure with Odin that you have ticked the right things Afterwards it worked.
Thankyou for you reply, and sorry for the delay posting back. God damn new user restrictions!!!
KUN1 said:
Can you post the whole Odin Log?
Click to expand...
Click to collapse
Heres what Im getting...
Code:
<ID:0/009> Added!!
<ID:0/009> Removed!!
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXDLJ4_I9300OXADLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.img
<ID:0/009> NAND Write Start!!
First try it with Repartition. If that doesn't work, you may have a look at this thread http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
KUN1 said:
First try it with Repartition.
Click to expand...
Click to collapse
You'll have to excuse me, I've never had problems problems before, so I've only had to use the PDA box till now.....
Is that the re-partition tick box, or the re-partition PIT file box??
KUN1 said:
If that doesn't work, you may have a look at this thread http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Click to expand...
Click to collapse
Christ that looks involved doesn't it! I think that be a last resort as it looks like I'll need to clear a day in my diary before I start!
For the moment you can ignore the second thread
Find a 3 File (PDA, Phone, CSC) Firmware ( maybe samifirmware.com ) , then download the 512 pit file for the GALAXY S! and the flash the Firmware with pit file and repartition.
KUN1 said:
For the moment you can ignore the second thread
Find a 3 File (PDA, Phone, CSC) Firmware ( maybe samifirmware.com ) , then download the 512 pit file for the GALAXY S! and the flash the Firmware with pit file and repartition.
Click to expand...
Click to collapse
SOLVED
I couldnt sleep, so decided to have another bash at getting this phone going again.
Many many thanks to KUN1 for hunting down and PM'ing me the necessary Odin MD5 and PIT files to use for the method he posted above.
:victory:Success:victory:
You've been a life saver sir :good:
haha no problem
Hey guys,
Last night I looked at my phone (which had been on charge for a while) and noticed that it was on the first S3 boot screen. So I assumed it had crashed and got stuck whilst rebooting, so I held the power button to reset it.
Problem is, it came back to the same screen, except this time the black background of the image was distorted - lots of red/green/blue dots on it. So I tried again, and it came back even worse... The third time, it settled on a completely distorted image and is now seemingly stuck like that.
The phone isn't booting, so far as I can tell. If I try to boot to recovery, I just see the same screen. If I boot into download mode, it actually works - the screen is no longer corrupt and it responds to button presses. (Although itnerestingly if I continue to hold Home + Vol Down + Power once the download screen appears, then it does distort).
I have tried plugging it into my PC. I don't see it as a MTP device (no suprises there), and ADB can't find it. It is however recognised by odin. I tried flashing a stock rom via odin, but it complained that there was no PIT found. (Which if I understand if something to do with the partitioning of the device.
Any ideas on how to solve this? Should I find a PIT image for my phone and flash that and the ROM together?
For background, my phone is a i9305 and was running paranoid android (4.2, IIRC).
Dont touch pit
First flash stock rom via Odin
JJEgan said:
Dont touch pit
First flash stock rom via Odin
Click to expand...
Click to collapse
When I try that, I get the following error:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305EVRALI5_I9305BVALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
That was why I was wondering about the PIT file.
I have also added some pictures (they're pretty low resolution, unfortunately). The first is what I see when I try to boot normally - lots of white and black bands (the yellow and purple you can see is just an artefact of my crappy webcam). The second image is download mode, where I continued to hold down the buttons after it loaded, causing it to reload with the corrupted image (again, this is a bit distorted by the webcam - the text and image aren't blurred).
no access to system and recovery,i doubt theonly way is download mode.just try an stock rom with pit files,agree that the issue have something to with the partition.if you have backup the whole system,even flash a new rom,youdata will be back easy and soon ,so nothing to worried and no way else to go,good luck.
Sent from my GT-I9305
As pit breaks more phones than it fixes its not recommended .
But your phone has no pit so you you have choices .
Warranty void so it would have to be a service repair .
Or you can try flashing a pit file yourself if it fails you will need to buy a new motherboard .
I´ve had the same Problem on my S1.
I Flashed a whole Package from Samsung Stock Firmware ( PIT MODEM PDA ) in Odin.
After that it worked again, i´ve needed some try´s but after that everythin was normal.
Darkangel 142
Darkangel142 said:
I´ve had the same Problem on my S1.
I Flashed a whole Package from Samsung Stock Firmware ( PIT MODEM PDA ) in Odin.
After that it worked again, i´ve needed some try´s but after that everythin was normal.
Darkangel 142
Click to expand...
Click to collapse
Do you mean specifically that you had the same error in odin, or that your S1 had the distorted screen too?
Well, I tried flashing the i9305 pit file and had no luck. The re-partitioning failed to start at all, so it didn't ruin the motherboard, at least.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305EVRALI5_I9305BVALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Back to orange/samsung it is!
Thanks for your suggestions/help, everyone.
Any joy?
Hi,
I've posted about the same problem. Completely stuck on who to deal with and can fix it How weird to have happened so close and exactly same with black screen then stuck on white, Wonder if others are out there.
Link: http://forum.xda-developers.com/showthread.php?t=2526821
stuck screen
i have the same problem with my s3 and i couldn't do the download mode. im planning to restore on stock rom but i don't know how to fix this issues.
thanks,
einjelhart said:
i have the same problem with my s3 and i couldn't do the download mode. im planning to restore on stock rom but i don't know how to fix this issues.
thanks,
Click to expand...
Click to collapse
Hi mate,
If you can't get in to Download Mode because of boot loop:
Try forcing it by holding all 3 buttons until it turns off, should come up.
Failing that, you can eBay Galaxy USB Jig that plugs in and forces Download Mode.
If you can get to Download Mode, I have written a solution to flash just the ROM.
You can read my solution by following the Link above your post
Have a great day!
-Shaz
Same problem with my s3 ,but Odin doesn't recognise my device ,please help
Debanshu bebartta said:
Same problem with my s3 ,but Odin doesn't recognise my device ,please help
Click to expand...
Click to collapse
I had these prob before; device not recognize in odin, distortion screen with colorful line, stuck at boot logo & splash screen.. I tried flash lot of thing possible to fix it but all fail. Suddenly everything working fine after changing new battery.. Lol. Or maybe im just lucky.
Sent from my GT-I9305 using XDA-Developers mobile app
Hi folks,
I friend of mine have this phone that is stuck in Odin mode. The problem is that none of the "press and hold keys" commands work and the phone just reboots into Odin every time. She has "tons" of Pictures of her first born Child on the device, without any cloud backup! :crying:
Any suggestions what to try next?
What i have done so far:
Trying all the "press and hold keys"
Letting the battery drain out and the hook up the Power to it... When connecting Power the screen turns White for 15-20 minutes and then if i reboot it, it goes back to Odin/download mode...
Is it possible that opening the phone and removing the battery could work?
Jeppe_77 said:
Hi folks,
I friend of mine have this phone that is stuck in Odin mode. The problem is that none of the "press and hold keys" commands work and the phone just reboots into Odin every time. She has "tons" of Pictures of her first born Child on the device, without any cloud backup! :crying:
Any suggestions what to try next?
What i have done so far:
Trying all the "press and hold keys"
Letting the battery drain out and the hook up the Power to it... When connecting Power the screen turns White for 15-20 minutes and then if i reboot it, it goes back to Odin/download mode...
Is it possible that opening the phone and removing the battery could work?
Click to expand...
Click to collapse
I am no expert, just going to suggest what I would try, hopefully someone may know what to do exactly.
You could try downloading stock filmware from Sammobile or updato (making sure to at least flash the same filmware build or higher, or Odin won't flash it) if you use the "home csc" csc file, it should not wipe the data on the phone, and what I hope may fix the phone not booting.
First of all you should have mentioned the model no. Second, you can try flashing the stock firmware from sammobile. Now, the tricky part is, if prior to this soft brick the phone was on a custom rom or had been rooted, then flashing the firmware alone won't bring the device back to life, a factory reset will be needed after flashing stock firmware, which doesnt seems like a favorable option considering that the data on device is important. There can be other ways to fix this without losing the data but for that illl need to know the device details.
Oh and btw, opening the device and messing with the battery won't help at all. Don't do that.
Sent from my SM-N950F using Tapatalk
Get a pit file and flash it though oden may work or not.......
yashthemw said:
First of all you should have mentioned the model no. Second, you can try flashing the stock firmware from sammobile. Now, the tricky part is, if prior to this soft brick the phone was on a custom rom or had been rooted, then flashing the firmware alone won't bring the device back to life, a factory reset will be needed after flashing stock firmware, which doesnt seems like a favorable option considering that the data on device is important. There can be other ways to fix this without losing the data but for that illl need to know the device details.
Oh and btw, opening the device and messing with the battery won't help at all. Don't do that.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Its an Galaxy Note 8 (SM-N950F)
The only thing i can see in the display is
https:// imgshare.io/image/odin-2.U7KCu
We dont know what firmware was beeing used Before this, it´s not custom or rooted tho. I assume its the latest official tho
I grabbed the latest from Sammobile, N950FXXU7DSJ1_N950FCKH7DSJ1_HTS
I could try the above suggestions but what about trying to flash the BL? Could it not be the BL that is cuppupt somehow?
I did try and flash the BL now but Odin software says:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 7 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems the partitions are gone, @stinka318. Next, where do i find PIT-files?
Found PIT file but it failed.
Also tried CSC flash but it fails (looks like Odin might not cennect to the device (ID:COM 0: [COM4])
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 179 M
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Driver related? i have the Samsung USB drivers installed….
https://zfirmware.com/download-samsung-galaxy-note-8-pit-file/
Seems like it's a kernel problem, or maybe the phone IMEI reported stolen?
Have you tried installing custom binaries? TWRP maybe?
Or messing with OEM unlock found in Developer Options?
Most of the for solving such problem, you have to flash the exact same firmware found on phone before the problem.
Try rooting using odin and then twrp and thenflashing a custom firmware..... That could help..... Just a thought.... Wipe everything except internal storage
https://mega.nz/#!Lk8RiKQR!FiH50HLQp1aijVkRARSPtBN6M6wFphShHsm7i6u23lw
Try flashing this via odin through AP.
Sent from my SM-N950F using Tapatalk