Hello,
Unfortunately, I have Cyanogenmod on my Galaxy S4 GT-I9505 (in UK on O2). I want to unlock the phone, which apparently involves going back to a stock ROM.
After much searching around, I've eventually managed to download a stock ROM that wasn't corrupt, and Odin, and USB drivers. But when I try to do the firmware upgrade thing, it fails. I now seem to have a brick. How I hate Cyanogenmod!
Here's what happens in Odin:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
...and all I get on the screen of my phone is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". Except I can't use Kies (or Smartswitch) because it's a stupid Cyanogenmod phone so Kies (or Smartswitch) doesn't recognise its existence! GRRRRR!
So, do I have a brick that is completely useless? I've only had this phone a month or so (I bought it, tragically, with cyanogenmod on it).
Any suggestions/help/sympathy would be GREATLY appreciated! (please!)
- Paul
hellopaul said:
Hello,
Unfortunately, I have Cyanogenmod on my Galaxy S4 GT-I9505 (in UK on O2). I want to unlock the phone, which apparently involves going back to a stock ROM.
After much searching around, I've eventually managed to download a stock ROM that wasn't corrupt, and Odin, and USB drivers. But when I try to do the firmware upgrade thing, it fails. I now seem to have a brick. How I hate Cyanogenmod!
Here's what happens in Odin:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
...and all I get on the screen of my phone is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". Except I can't use Kies (or Smartswitch) because it's a stupid Cyanogenmod phone so Kies (or Smartswitch) doesn't recognise its existence! GRRRRR!
So, do I have a brick that is completely useless? I've only had this phone a month or so (I bought it, tragically, with cyanogenmod on it).
Any suggestions/help/sympathy would be GREATLY appreciated! (please!)
- Paul
Click to expand...
Click to collapse
It has nothing to do with Cyanogenmod all your problems. You are putting the blame in the wrong corner. Kies not recognizing, the failure of the flash, not being sim-unlock has nothing to do with Cyanogenmod. But with you not reading enough.
You want to flash a 4.2.2 rom and you can only do that if you are not on a knox bootloader. What is the text when you boot in download mode?
And btw, as far as I know you don't need to downgrade your FIRMWARE, but only your MODEM.
Thanks for your quick reply!
Lennyz1988 said:
You want to flash a 4.2.2 rom and you can only do that if you are not on a knox bootloader. What is the text when you boot in download mode?
Click to expand...
Click to collapse
Here's the text:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
And btw, as far as I know you don't need to downgrade your FIRMWARE, but only your MODEM.
Click to expand...
Click to collapse
Is that an easier process?
I was using Android 5.0.2 with Cyanagenmod. I'm not sure what version the ROM I downloaded was - it actually downloaded and wasn't a corrupt .zip file, which seems to be a very very rare thing. Might attempting to install a 4.x.x firmware over a 5.x.x cause problems? Is there anywhere I can reliably download a 5.x.x ROM that actually works? I've wasted several days searching for a UK O2 ROM. I can recommend plenty of sites that CLAIM to have it, but it's corrupted or just doesn't download due to any number of errors.
hellopaul said:
Thanks for your quick reply!
Here's the text:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
Is that an easier process?
I was using Android 5.0.2 with Cyanagenmod. I'm not sure what version the ROM I downloaded was - it actually downloaded and wasn't a corrupt .zip file, which seems to be a very very rare thing. Might attempting to install a 4.x.x firmware over a 5.x.x cause problems? Is there anywhere I can reliably download a 5.x.x ROM that actually works? I've wasted several days searching for a UK O2 ROM. I can recommend plenty of sites that CLAIM to have it, but it's corrupted or just doesn't download due to any number of errors.
Click to expand...
Click to collapse
Here an whole post with firmwares.
http://forum.xda-developers.com/showpost.php?p=41072392&postcount=2
Try flashing a 4.4.2. firmware. If flash is succesfull, then downgrade modem to 4.2.2.
If it's not, then pick an 5.0.1 firmware and downgrade modem to 4.2.2.
4.2.2 modem:
http://d-h.st/CXx
When you are done with what you want to do ( I assume something with region away). Flash AGAIN the 4.4.2 firmware or 5.01. You cannot stay on the 4.2.2 modem.
Thank you for your help with this!
I managed to un-brick my phone (hooray!) using 'Philz Touch' and some of the advice here: http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
I just re-downloaded that firmware from the site you suggested - that's where I managed to download the (exact same) firmware before. I've just tried installing it again, but got exactly the same error in Odin. I've currently got another ROM downloading from one of the dodgy 'teenage-hacker' sites (Rapidgator.net). I assume that it won't even unzip, but it will be tomorrow before it's completed the download.
I'm guessing that I need to download firmware that's UK and O2 (I'm in the UK and my phone's locked to O2). This rather limits my options - there only seem to be a couple of places on the net with this ROM (neither of which work). If I installed, say, a Vodafone ROM, then unlocked the phone, should that (in theory) then work with my O2 (or any other) SIM? I plan to switch to BT Mobile (running on the EE network) shortly - hence wanting to unlock the phone.
hellopaul said:
Thank you for your help with this!
I managed to un-brick my phone (hooray!) using 'Philz Touch' and some of the advice here: http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
I just re-downloaded that firmware from the site you suggested - that's where I managed to download the (exact same) firmware before. I've just tried installing it again, but got exactly the same error in Odin. I've currently got another ROM downloading from one of the dodgy 'teenage-hacker' sites (Rapidgator.net). I assume that it won't even unzip, but it will be tomorrow before it's completed the download.
I'm guessing that I need to download firmware that's UK and O2 (I'm in the UK and my phone's locked to O2). This rather limits my options - there only seem to be a couple of places on the net with this ROM (neither of which work). If I installed, say, a Vodafone ROM, then unlocked the phone, should that (in theory) then work with my O2 (or any other) SIM? I plan to switch to BT Mobile (running on the EE network) shortly - hence wanting to unlock the phone.
Click to expand...
Click to collapse
You are not reading what I wrote. You CANNOT flash the firmware you tried before. It's impossible because that version is to old. You are downloading a 4.2.2 and you need need 4.4.2 minimal (possible even 5.0.1 minimum).
I have no way of telling which version that firmware was - it was listed under United Kingdom and had O2 in the filename. No version number.
So - back to my previous question - should I be able to use, say, a Vodafone 4.4.2 firmware without risk of bricking my phone? Or maybe the BTU 5.0.1 version? And then be able to do the standard Samsung S4 process to unlock it? I guess I'll just try it and see if it works.
No. You need to download the latest ROM for your carrier, here. Once you have installed that firmware, you must install through Odin a 4.2.2 modem found at the link Lennyz1988 provided. Only then can you use the service menu method or RegionLock Away to unlock the S4. After that, extract the modem from the firmware package you downloaded and flash it through Odin.
Honestly, spend the money and unlock the phone, if O2 won't do it. An unlock code is virtually guaranteed to work, unlike the unlock methods in the forums.
Unfortunately that firmware you linked to is one of the many corrupt .zip files out there, and will not decompress at all.
I've got another firmware downloading (very very slowly) from Rapidgator. It will probably also be corrupt.
I've called a couple of local phone unlocking shops, and they don't have a clue what Cyanagenmod is, and whether it will affect the unlockability of the phone. I'll just pay an ebayer to give me an unlock code, in the hope that it might unlock it, despite what I've read. Most people say I must go back to a stock ROM before unlocking.
Ugh. Awful Cyanogenmod.
hellopaul said:
Unfortunately that firmware you linked to is one of the many corrupt .zip files out there, and will not decompress at all.
I've got another firmware downloading (very very slowly) from Rapidgator. It will probably also be corrupt.
I've called a couple of local phone unlocking shops, and they don't have a clue what Cyanagenmod is, and whether it will affect the unlockability of the phone. I'll just pay an ebayer to give me an unlock code, in the hope that it might unlock it, despite what I've read. Most people say I must go back to a stock ROM before unlocking.
Ugh. Awful Cyanogenmod.
Click to expand...
Click to collapse
The archives are not corrupt. Something is wrong at your end.
And again, CM has nothing to do with your issues. If you were on the stock rom you would just have had the same problem.
If I was on a stock ROM I wouldn't have to go through all this, and could presumably just unlock my phone very easily, as outlined on many sites, such as giffgaff (I cannot post links in this forum yet).
I cannot get that ROM to unzip, using 7-zip, WinRAR, Mac OS X Finder, Mac OS X Terminal. I've downloaded it at least 3 times, and it's always corrupt. Mac OS X Terminal reports "bad zipfile offset (local header sig): 0".
Uh?? Update: I've just tried 7-zip again...and it's decompressed it! How utterly bizarre.
I just tried it with Odin and it did not work - the usual result:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I have to turn off the phone, and use Philz Touch to bring it back to life.
hellopaul said:
If I was on a stock ROM I wouldn't have to go through all this, and could presumably just unlock my phone very easily, as outlined on many sites, such as giffgaff (I cannot post links in this forum yet).
I cannot get that ROM to unzip, using 7-zip, WinRAR, Mac OS X Finder, Mac OS X Terminal. I've downloaded it at least 3 times, and it's always corrupt. Mac OS X Terminal reports "bad zipfile offset (local header sig): 0".
Uh?? Update: I've just tried 7-zip again...and it's decompressed it! How utterly bizarre.
I just tried it with Odin and it did not work - the usual result:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I have to turn off the phone, and use Philz Touch to bring it back to life.
Click to expand...
Click to collapse
Yes ofcourse it fails. You are not following my instructions.
You are flashing a 4.3 rom which is IMPOSSIBLE for you. Your bootloader is at least a 4.4.2 version, probably even a 5.0.1 version. So you can only flash those stock roms.
Lennyz1988 said:
Yes ofcourse it fails. You are not following my instructions.
You are flashing a 4.3 rom which is IMPOSSIBLE for you. Your bootloader is at least a 4.4.2 version, probably even a 5.0.1 version. So you can only flash those stock roms.
Click to expand...
Click to collapse
Sorry if I'm not following you. How can you tell what version the firmware file is? The site I downloaded it from claimed it was 5.0.1.
My phone's Android version is 5.0.2
I've been putting the firmware file into Odin's AP slot.
I haven't done anything with the BL (presumably bootloader) slot.
Isn't there a way I can completely wipe the phone, then install whatever firmware I want, regardless of what was previously installed?
alright let's try something else.
Flash this rom with Philz. Perform a full wipe first form within the recovery.
http://forum.xda-developers.com/showthread.php?t=2283194
It's a 4.4.2.
Then flash a 4.2.2. modem and then try the things you want to do.
So I guessed that I should copy the .zip file of that WanamLite Rom onto the SD card, which I did.
I then did:
Recovery mode reboot, and booted into the Philz thing.
Wipe Data/Factory Reset.
Install Zip > Choose zip from /storage/sdcard1, and located the .zip file...
Installing...
Finding update package...
Installing update...
Welcom to WanamLite XXUGNH7 3.1
Formatting system...
System mounted!
data mounted!
Cleaning cache...
Installing system...
Symlinking...
Setting permissions...
set_metadata: some changes failed
E:Error in /storage/sdcard1/GT-I9505_WanamLite.XXUGNH7.V3.1.NO-WIPE.zip
(Status 7)
Installation aborted.
press any key to continue.
So now I'm wondering how to get around a Status 7 error. Searching that forum thread about Wanamlite gives no help - at least not in a language a human can understand. Someone suggested:
"after spending several hours on this ... i made it
How to flash this ROM on old NON-Knox bootloader:
1. flash XXUEMJ5 modem via odin to prevent lags and call problems
2. flash a TWRP recovery to bypass the "status code 7"-error while flashing this ROM
3. flash this ROM
4. install your prefered recovery"
I have absolutely no idea what any of that that means.
I have rebooted the phone, and it will only boot into the Philz thing - presumably because there is no operational firmware installed at all.
Partial success:
I followed the instructions given here: https://www.youtube.com/watch?v=np_nlFALMbQ
...to install firmware via PhilZ Touch, and I can successfully install Cyanogenmod (argh!) or WanamLite (yeah!). But I still cannot access the service menu in WanamLite. At least typing *#0011# does get some kind of menu up, but not the ServiceMode main menu.
And at least I now have a fully operational phone (with WanamLite), but still locked to O2.
Lennyz1988 suggested I "flash a 4.2.2. modem" - might doing that unlock the ServiceMode menu? Are those at all related? To flash the modem (presumably using Odin) which slot do I put it in? CSC?
I tried installing the O2 UK firmware using the exact same technique, using both the ROMs I downloaded, but neither would work. It failed at the very start, saying [bad]. I then reinstalled WanamLite successfully.
It wasn't just Lenny who mentioned flashing the 4.2.2 modem. I mentioned it as well. In fact, in the thread on the topic - which you really should be reading - the last few pages are peppered with posts from me telling people that you have to downgrade the modem (at minimum) before you can use either unlock method. For the record, I know downgrading works, because I had to do it myself after losing a SIM unlock that was done through the service menu. I ended up using RegionLock Away and couldn't be happier.
With that said, you cannot use a custom ROM of any kind to perform the unlock. I tried accessing the service menu on Imperium ROM, which is based on stock, and failed. You must be completely stock, which means you need to install a stock ROM to your device, using Odin. Download a new copy of the ROM, and if necessary use a totally different computer. Just one question however. If flashing the ROM through Odin doesn't work this time, will you then blame WanamLite for it?
Thank you for all your help with this, Strephon and Lennyz1988.
So, I tried flashing the modem (I put this file: I9505ZHUFNB3_MODEM.tar into Odin's CP slot - it seemed to work). I rebooted and tried to get to the service menu, but as Strephon predicted, there was no service menu.
So, again using Odin, I tried to put this firmware (I think it might be 4.2.2) on the phone:
I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5
...and, predictably, it failed.
So then I tried doing them both at the same time, with the modem file in the CP and the firmware in the AP slot. But it failed again:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried to re-install the various other stock ROMs I'd downloaded (and re-downloaded, on a different computer), with no success.
So, I got back in touch with O2 - they'd previously said they wouldn't unlock the phone because they say the phone and number need to have been used together for 12 months. I only bought the phone about 6 weeks ago. But after much pleading (and £15) they've agreed to send me an unlock code! So when this arrives, I'll try it out (the phone is currently still running WanamLite) and see if it works. If not, to save my sanity, I'll just cut my losses and sell/give away the bloody phone as "locked (forever) to O2, with WanamLite or Cyanogenmod".
And no - I don't blame WanamLite (or Cyanogenmod now) for the stock ROM installations working - I can only assume that there's a problem with the ROMs. I can install WanamLite and Cyanogenmod fine, and it just so happens that they're not downloaded from some dark, dodgy server, unlike most of the supposedly stock ROMs. It's just really annoying that the phone's previous owner thought it was a good idea to install Cyanogenmod in the first place, without first unlocking the phone.
It's only annoying because the phone wasn't unlocked beforehand, meaning you have to put the stock ROM on the device in the first place to be able to unlock it using those methods. I can understand that. However, you still have the issue of why Odin keeps on failing when you try running it. That's one that perplexes me as I've had no issues with Odin whatsoever.
Well, my problems are over! O2 have already emailed me an unlocking code which WORKED! I now have an unlocked phone. I'm still interested in tweaking it, so may well install a more interesting firmware in future.
Thanks for your help and suggestions!
Evening fellas!
I hope i can get some help over because i am freaking out!
Let me start with what i wanted to achieve. I wanted to go and use Stuff on my phone which wasnt usable due to the SafetyNet API, because i got a custom firmware and root Access. I tried to flash Magisk but it doesnt worked, neither did my SuperSU proberly.
My idea was to unroot and then simply flash the stock firmware via Odin on my phone. 1st couple of tries it didnt work. However, it also didnt affect my phone at all. So i then went into my recovery (TWRP) and did factory reset. Just to clean things up. I tried again to flash and yeah, he actually did it! Just with the minor exception that the flasing failed like 3% before its completion and now i got basiclly a white brick. I ve tried numerous times to flash that firmware again, get some other firmware running - I also tried to flash the Stock Rom completly (which also was able to start the flashing just before it failed in the middle).
I dont find any help on the internet, or at least not help that helps me in my specific situation. I honestly dont know what to do else... I do appreciate any help!
Please help me xda-users, you re my last hope!
Did you try using the original USB cable? Tried different USB ports?
audit13 said:
Did you try using the original USB cable? Tried different USB ports?
Click to expand...
Click to collapse
Yes, i just did. I ve used several USB Ports of my Computer (Haven't tried another computer yet, but that will come too). I also used two different cables. One Original and one third-party cable from amazon, which worked just fine for normal file copying and moving, on the S4 before its brick and the Samsung Grand Prime as well (as i use that in the mean time).
As from yesterday at some random points i was still able to get to flash something for just a second or so, the only messages i get from odin today are these:
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
I dont find any helpful information on that error message either, which is the worst part of it all.
Is Odin assigning a COM port to the phone?
audit13 said:
Is Odin assigning a COM port to the phone?
Click to expand...
Click to collapse
Yes, everything is detected. Odin is detecting the Samsung Grand Prime just as well as the Galaxy S4. I've also tried different version of Odin. v3.12.3 and v3.13.1. They both give me the same output.
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Thread moved to Help & Troubleshooting.
audit13 said:
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Click to expand...
Click to collapse
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
vM44tze said:
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Okay, i don't know whats wrong now - but now i cant even flash back the stock firmware that worked before with odin v3.07. Odin now says:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: Its not even being detected anymore.
There is no need to split the tar.md5 into 4 parts. In Odin 3.07, you can flash it as a single file in PDA.
You're flashing the latest stock ROM? Is it possible the USB port on the phone is damaged?