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
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!
Recently I used ODIN 3.0.7 to try and root my Samsung Galaxy S3 (Telia) 4G with a so-called "CF-Root-SGS3-v6.4".
It is the 16 GB, 2 GB RAM 4G/LTE version, and it was running at Android 4.1.2 when I tried to do the root.
The phone booted up fine and ODIN claimed it was a success, I immediately noticed that the phone had stopped recognizing my SIM card, and the Root Checker also stated that something was wrong and it wasn't rooted. so I download a stock ROM and try to install that, however when I choose the SD card to try and install it, it says no files are found.I had made it to the CWM Recovery tool on the phone, and I could start the phone that way ("Reboot Phone Now", but it still didn't recognize my stuff, so I tried following the stock ROM instructions I was given, and I wiped all data, cache and stuff after backing it up on my PC in the CWM recovery tool.
Now, at this point, the phone is stuck at "Downloading - Do not turn off target!". When I try turning it off, the screen goes black for 2 seconds, and then the screen appears again. If I am quick, I can get into the "ODIN" mode, where I can once again try and root it. It fails again, but now I get to the CWM Recovery Tool again, but no files are found at all, and if I reboot the phone, it just goes back to the Downloading screen (I left it on overnight and it stayed on that screen, by the way. I doubt it is ACTUALLY downloading anything).
I do not know the Kernel or ROM version. The phone was bought in the start of February, though, so I could imagine it's rather new.
What do I do now? I just wish to get my phone back to normal Android, normal everything even if it means a factory reset.
You need to goto the NV backup sticky thread in the dev section that I put together, look near the bottom.
Download the param binary and flash with odin to revive your device.
Sent from my GT-I9305 using Tapatalk 2
Hello, I followed the guide and flashed the phone with the param with ODIN, however, the phone is still stuck on its "Downloading - Do Not Turn Off Target!" screen (though it is not showing the ODIN mode at the corner anymore.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Param_Bin_I9305.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> param.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... *0*
<OSM> All threads completed. (succeed 1 / failed 0)
The box is green and says "PASS!", but the phone is unresponsive.
Did I do something wrong?
Right now you need to read then run this via odin from you PC...
http://forum.xda-developers.com/showthread.php?t=1942150
You probably corrupted your efs partition by flashing a CF Root not intended for your phone. The CF Root is for SGS3 not I9305 LTE.
Sent from my GT-I9305 using XDA Premium HD app
Raistlin1158 said:
Right now you need to read then run this via odin from you PC...
http://forum.xda-developers.com/showthread.php?t=1942150
Click to expand...
Click to collapse
This did it, thank you!
Time to reinstall a lot of apps, and be more careful with the root I pick.. ;_;
You already have root with this rom
Hello again, sorry for sort of necroing.
So I got it running again, there is one nasty problem, though - The phone won't recognize my SIM card, meaning that it simply doesn't register that there is one.
I'd guess the phone warranty is void at this point, so what do I do? Is there any DIY fix?
Azortharion said:
Hello again, sorry for sort of necroing.
So I got it running again, there is one nasty problem, though - The phone won't recognize my SIM card, meaning that it simply doesn't register that there is one.
I'd guess the phone warranty is void at this point, so what do I do? Is there any DIY fix?
Click to expand...
Click to collapse
Did you check your IMEI??? After messing with your phone you could simply lost it.
Sent from my GT-I9305 using xda app-developers app
How do you check IMEAI
DjeMBeY said:
Did you check your IMEI??? After messing with your phone you could simply lost it.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
hard bricked galaxy sIII I9305
guys i got a much worse situation, my device is a galaxy I9305, and i turned my phone off during the flash of a firmware where it was saying "FAIL" for a long time. I'm desperate at the moment and i'm not finding out any way how to debrick it, any help would be greately appreciated! My device is stuck on "Downloading... Do not turn off target!!" it's only this text in the center, with nothing more
UPDATE: Up until yesterday, my phone was stuck on the Samsung logo. I used Odin to flash the original Carphone Warehouse Gingerbread Rom. The phone then became stuck in a loop of unresponsive processes and wouldn't boot up. I decided that this was due to the Google Apps on the phone being a newer version than the O/S (I have not factory reset). Kies would not connect to the device in this state, so i used Odin again to flash the stock UK Jellybean Vodafone Rom. My phone now boots, and most settings/apps appear to have been kept. However, some system apps, i.e. messaging, force close. I think this may be because the APN's etc are now on Voda settings. Unfortunately, 'settings' is also a process which force closes!
Basically, at the minute, I'm looking for a way to a) stop the force closes to manually change settings, or b) flash the UK unlocked JB Rom - I can't find this Rom anywhere.
Hi all. Hope somebody can help me.
I have an unlocked Galaxy Note, which has always run stock, up-to-date, Samsung firmware. Yesterday, I was attempting to use the satnav, and had the phone plugged in via car charger. The battery was low, and the satnav wouldn't connect to GPS. In the end, it became unresponsive, and I reset it. Now, the phone will only boot as far as the Samsung logo. Additionally, when it is charging, it doesn't show the bar climbing the battery - only the status (currently over half full).
I can get into recovery and download modes, but I'm really wanting to avoid a full reset/wipe, as I have some texts which have great sentimental value (yes, I know, I should have backed these up).
Other threads which are similar seem to point to Odin and an earlier stock ROM - I've downloaded the original ROM my phone would have had and Odin, but want to know 1) is this the best way to go and 2) what do I do next?
Thanks.
Flash the stock ROM again with ODIN.
fact fbarro
Varad297 said:
Flash the stock ROM again with ODIN.
Click to expand...
Click to collapse
Have now tried this. Odin reports a fail...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> boot.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response form LOKE
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
...and now, when I have rebooted, I get a yellow triangle with 'Firmware upgrade encountered an issue...'
Have retried Odin and received a pass.
Now, the phone is trying to run setup wizard, but is crashing/force closing a number of processes. Might this be because the stock Rom is too old?
fivegoldstars said:
Have retried Odin and received a pass.
Now, the phone is trying to run setup wizard, but is crashing/force closing a number of processes. Might this be because the stock Rom is too old?
Click to expand...
Click to collapse
Further update. I have reflashed again, this time with the JB Vodafone Rom. Previously I was on the unlocked UK Rom, but I can't find this anywhere. I'm now able to get into the phone, and the majority of things work, but some functionality is missing. I've tried to force an OTA update, but now the phone says its running the most up to date software. Any ideas how I can go back to the proper Rom for this phone?
This is the proper ROM mate, may not be the one you got with your phone but still the stock ROM. Or else you can search for the ROM you need on sammobile.com
Do hit thanks if this helps!
Varad297 said:
This is the proper ROM mate, may not be the one you got with your phone but still the stock ROM. Or else you can search for the ROM you need on sammobile.com
Do hit thanks if this helps!
Click to expand...
Click to collapse
Well, as per update in O/P, I'm back in the majority of things, but certain system processes force close when I open. The phone registers on the network, and will make voice calls, but I can't access messaging (force closes) or APN's (force closes). So cannot text or connect to mobile internet. Have tried wiping cache, but I'm now running out of ideas.
Did you check sammobile.com? Or dr.ketan's thread in the original Android Development forum? Try flashing some other stock after a full wipe..
I used the only UK JB Rom in Dr Ketans thread. Have not checked sammobile yet - need to do this later.
I'm not wanting to do a full wipe until I can access and backup my texts - trying to install without wiping first.
fivegoldstars said:
I used the only UK JB Rom in Dr Ketans thread. Have not checked sammobile yet - need to do this later.
I'm not wanting to do a full wipe until I can access and backup my texts - trying to install without wiping first.
Click to expand...
Click to collapse
Good news/bad news.
Firstly, the original problem of my phone stuck on the Samsung logo is fixed. My full sequence of events was 1) flash stock Gingerbread rom using Odin. This gave me a phone which would not boot due to Google processes force closing. 2) flash stock JB rom from Dr Ketans thread. This gave me a phone which booted, but could not access APNs/messaging, although all other settings/apps/files were still intact 3) flash stock JB rom from Sammobile (CPW). This gave the same problem. 4) Perform full factory reset and reflash JB CPW rom. Phone now has full functionality, but has lost all files, messages, apps etc.
Thanks for everyone's input - thread can be closed.
A full wipe mostly does it. And always backup the important stuff. If you're gonna root, Titanium backup is the best. And mate do click the 'Thanks' button if i helped!
Don't forget. do a backup of your current rom! if ever there might be a problem at least you can still jump back to it!!!
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..
I recently screwed up my S5 active and am desperate for help.
I only ever really occasionally screw with the OS, and I did a poor job of documenting what I did with this phone, so I will do my best to recollect exactly the state.
The phone is an AT&T Samsung Galaxy S5 active, model G870A
The recovery was some kind of robot icon that would show for maybe ~10 seconds at the start of boot (not a regular android, more square). I've tried searching for it to, as yet, no avail.
I'm fairly certain that the image I put on the device was KoolKit_S5_Active_V1.1.0.
I cannot recall if I used safestrap, towelroot, twrp, or some combination of these in order to get the above on the device. I have copies of each sitting in a folder I created for the phone.
The other day, SuperSU said it needed the binary updated. Me, being dumb, wanting the notification to go away, decided to appease it. It asked if I wanted to do so using recovery. I figured this would be easier, so I clicked "yes". And then my life got a lot more stressful.
When the phone boots now, it goes into ODIN mode and displays the message "android could not do normal boot. ODIN MODE".
I cannot get it to any other screen. Recovery, download mode, whatever. (I'm pretty sure this is download mode, but I cannot initiate any mode, it just goes into this).
I've been poking around on these forums. The first suggestion I thought might work was to use ODIN to (re?) flash towelroot. Or TWRP. I forget which one I tried, but it wound up resulting in a failure in ODIN, and a message on the screen stating something along the lines of "sys rev check fail no version".
I am very confused about what I need to be flashing using ODIN, but I have managed to cobble together that it has to be through ODIN.
I don't necessarily need links, I can find those, and I may already have the files. I'd really like to know which files it is that I need.
Do I need a firmware? What is the file format for that? tar.md5? etc.
Ideally I'd just like to get back to a regular run mode where my worst problem was a wonky USB port. I would deeply appreciate it if anyone could get me in that direction.
Thank you
It's working.
I plugged it in, tried to flash a PIT file. That failed. Apparently one does not flash those alone.
The screen said something like "check failed : PIT" ...
I went here:
http://forum.xda-developers.com/showthread.php?t=2799754
Followed the instructions. Got a failure. (This was, stupidly and fortunately, without restarting phone after pit failure).
Phone rebooted like nothing was ever wrong.
ODIN log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
P.S.: Previously unidentified robot was safestrap:
http://img.wonderhowto.com/img/96/6...hwiz-launcher-your-samsung-galaxy-s5.w654.jpg
Im glad you could fix it.
I also have a problem with a AT&T S5 active, the phone has horrible screen lag (even the booting screen is slow)
I tried doing a factory reset and also doing a downgrade to kit-kat using Odin, but the problem persists