Related
Traded my Mega for a S4 today
Love it
I rooted it, installed TWRP. I have i337m from Rogers. All was well.
I downloaded a Google Edition 4.3 Rom and went into TWRP, Wiped Cache/Dalvik/Data, and Formatted Data
I then went back, installed the Rom.zip
Wiped cache/dalvik
Rebooted.
My phone now goes directly to Odin Mood. Seems as if something partition wise happened.
UPDATE:
I attempted to flash via odin everything back to stock, it made it 1/2 way and got an error. Now I can't do anything, phone just boots to the screen attached. Odin doesnt detect phone, Kies doesn't detect phone.
Am I screwed? I can't believe this, I want to cry. Never have I had issues like this before!!!
Which TWRP version
Did you do the "Format Data" button where you had to select "Yes". If so you lost everything
Get twrp 2.5.0.2 if you get the chance
I never used Odin, so not much help there
Also, I always wipe only Data/System/Caches 2x and have no issues. I do it before flashing any rom/version update etc
I know not much help here. But, maybe an idea on what went wrong--
Good Luck
Yes - Shoot
I see the issue. I was following the guide and it states to do this with CWM, I was thinking I was reading the instructions for TWRP. I had 2.6.3.0 (whatever the newest one is)
I'm downloading the firmware now - will try Odin
You gotta use Odin to restore the firmware, but you can't use kies if you're going custom. You can also use Philz recovery for that. That's what I had and it worked great. It's based off CWM and has touch.
agent929 said:
You gotta use Odin to restore the firmware, but you can't use kies if you're going custom. You can also use Philz recovery for that. That's what I had and it worked great. It's based off CWM and has touch.
Click to expand...
Click to collapse
When attempting to flash with Odin, I'm getting the following error. Any help?
Stuck here right now if anyone has a second.
Edit
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Got it from here
http://forum.xda-developers.com/showthread.php?t=2269304
Its the Virgin Mobile Canada 4.2.2 firmware from July
My phone is Rogers but is unlocked and I'm using it with Virgin. Can I flash the virgin file rather than Rogers to avoid all the Rogers bloat?
What is the Pit error I'm getting? Did I delete a partition or anything here?
Man that stupid format is a major pain. Won't do that again. I flipped back at the guide page and read the CWM instructions by error.
agent929 said:
I don't think you're using the right firmware. You should be doing the MDL firmware.
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Click to expand...
Click to collapse
Why would he put MDL on a Canadian phone?
scott14719 said:
Why would he put MDL on a Canadian phone?
Click to expand...
Click to collapse
Oh good gosh I'm very sorry I missed that part.
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
agent929 said:
Oh good gosh I'm very sorry I missed that part.
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
Click to expand...
Click to collapse
So I attempted to flash Via Odin 3.0.7 (rogers firmware) and about 1/2 way through something Error'd and now my phone will not do anything but load the following screen attached.
Download mode or recovery does not load. Kies does not detect it. I can't get Odin to detect it either.
Did I screw myself over?
So depressed over this. I just got the phone.
That screen is another form of download mode. If you plug it into Odin at this point will Odin recognize it?
jd1639 said:
That screen is another form of download mode. If you plug it into Odin at this point will Odin recognize it?
Click to expand...
Click to collapse
I'll try again tonight after work.
Last night I could no longer get ODIN to recognize the device.
bigystyle84 said:
I'll try again tonight after work.
Last night I could no longer get ODIN to recognize the device.
Click to expand...
Click to collapse
If you are on MF3, this has worked to get me out of that screen http://forum.xda-developers.com/showthread.php?t=2360859 there is always some risk with flashing anything from Odin, so read through the thread and make sure you are comfortable with it first...
I'm on AT&T U.S. but it worked for me. You should also be able to boot in download mode (with the phone off hold vol down and home, then press power until your phone vibrates and continue holding home and vol down until you see Download mode)...
I hope this helps.
dustyhughes said:
If you are on MF3, this has worked to get me out of that screen http://forum.xda-developers.com/showthread.php?t=2360859 there is always some risk with flashing anything from Odin, so read through the thread and make sure you are comfortable with it first...
I'm on AT&T U.S. but it worked for me. You should also be able to boot in download mode (with the phone off hold vol down and home, then press power until your phone vibrates and continue holding home and vol down until you see Download mode)...
I hope this helps.
Click to expand...
Click to collapse
I have a i337M Canadian phone
And as mentioned, phone will not go into Download mode. I've tried a dozen times to get it into the regular download mode as always, does not work. It just boots to this screenshot almost instantly after hitting the power button.
I've flashed with Odin a dozen times previously with S3 and Note 2 in the past, never any issues.
How could TWRP Format Data cause all this to happen?
I just had my previous phone stolen - I bought this phone yesterday and now this happens. What a great week.
jd1639 said:
That screen is another form of download mode. If you plug it into Odin at this point will Odin recognize it?
Click to expand...
Click to collapse
jd1639 is right, I think the first line of small text says Odin, if I remember correctly.
dustyhughes said:
jd1639 is right, I think the first line of small text says Odin, if I remember correctly.
Click to expand...
Click to collapse
I couldn't get Odin to detect the phone on this screen though.
Odin detected the phone fine when I could get the to regular download mode screen before. Now I can't get to this screen, only what's attached in the screenshot, and I couldn't get Odin to detect it any longer last night.
Can a cable cause this? I am not using the Cable that came with the phone - That wasn't included when I bought it. I'm using a Sony Cable from a Xperia T I used to own.
Why did the Odin flash fail to begin with?
With did Format Data in TWRP cause all this to happen?
bigystyle84 said:
I couldn't get Odin to detect the phone on this screen though.
Odin detected the phone fine when I could get the to regular download mode screen before. Now I can't get to this screen, only what's attached in the screenshot, and I couldn't get Odin to detect it any longer last night.
Can a cable cause this? I am not using the Cable that came with the phone - That wasn't included when I bought it. I'm using a Sony Cable from a Xperia T I used to own.
Why did the Odin flash fail to begin with?
With did Format Data in TWRP cause all this to happen?
Click to expand...
Click to collapse
It's very possible it's the cable. Odin is very finicky on the cable, usb ports, and even computer you use. It works great on my lap top but I can't get it to work on my pc. Do you know anyone who has an s4 and you could borrow their cable. If you can boot into download you are not bricked and can get Odin to fix your phone. It may just take some trial and error. I've also had Odin fail a number of times and then decide to finally work for whatever reason so keep working at it.
jd1639 said:
It's very possible it's the cable. Odin is very finicky on the cable, usb ports, and even computer you use. It works great on my lap top but I can't get it to work on my pc. Do you know anyone who has an s4 and you could borrow their cable. If you can boot into download you are not bricked and can get Odin to fix your phone. It may just take some trial and error. I've also had Odin fail a number of times and then decide to finally work for whatever reason so keep working at it.
Click to expand...
Click to collapse
I'm going to get a Samsung Cable from a friend today and try it again when I get home.
jd1639 said:
It's very possible it's the cable. Odin is very finicky on the cable, usb ports, and even computer you use. It works great on my lap top but I can't get it to work on my pc. Do you know anyone who has an s4 and you could borrow their cable. If you can boot into download you are not bricked and can get Odin to fix your phone. It may just take some trial and error. I've also had Odin fail a number of times and then decide to finally work for whatever reason so keep working at it.
Click to expand...
Click to collapse
Here's some more thoughts:
I've always used firmware from sammobile.com
I've had best luck with odin ver 1.85
One other, use the usb ports in the back of your computer, not the front and no usb hub.
jd1639 said:
Here's some more thoughts:
I've always used firmware from sammobile.com
I've had best luck with odin ver 1.85
Click to expand...
Click to collapse
Cool Thanks
I downloaded the firmware from SamMobile - the latest Rogers firmware.
I will try 1.85
I have searched and searched and cannot find any fix for my issue hopefully I can get the help here like always.
Last night I flashed ktoonz kernel like I have a thousand times before and it failed in TWRP recovery, I thought nothing of it, hit reboot, and am now at a brick wall. My Gs4 acts like the Gs2 with a stuck power button, upon powering it on, it goes straight into a loop vibrating every few seconds over and over, I can't get into recovery mode and for that matter can't even get the the initial Samsung splash screen to pop up. The only thing I can do with the phone is boot into download mode, I tried restoring several times with Heimdall on my Mac and always failed when the system reached 100%, it wouldn't move past that point. I have also just finished flashing it with Odin on a friends Windows laptop which completed successfully each time but the phone is still doing the same thing. I need help, I can't afford a replacement right now and am just a little desperate!
re: official stock firmwares
lstat said:
I have searched and searched and cannot find any fix for my issue hopefully I can get the help here like always.
Last night I flashed ktoonz kernel like I have a thousand times before and it failed in TWRP recovery, I thought nothing of it, hit reboot, and am now at a brick wall. My Gs4 acts like the Gs2 with a stuck power button, upon powering it on, it goes straight into a loop vibrating every few seconds over and over, I can't get into recovery mode and for that matter can't even get the the initial Samsung splash screen to pop up. The only thing I can do with the phone is boot into download mode, I tried restoring several times with Heimdall on my Mac and always failed when the system reached 100%, it wouldn't move past that point. I have also just finished flashing it with Odin on a friends Windows laptop which completed successfully each time but the phone is still doing the same thing. I need help, I can't afford a replacement right now and am just a little desperate!
Click to expand...
Click to collapse
Odin and Heimdall don't have any options to RESTORE anything.
Both those utilities can only do one thing, they can flash firmware
TAR files. (and any other valid TAR files)
My advice to you is to simply go to SamMobile.com and download
the specific odin flash firmware for your phone model and country.
Here is an example of what you will find at SamMobile: http://www.sammobile.com/firmwares/2/
Good luck!
Misterjunky said:
Odin and Heimdall don't have any options to RESTORE anything.
Both those utilities can only do one thing, they can flash firmware
TAR files. (and any other valid TAR files)
My advice to you is to simply go to SamMobile.com and download
the specific odin flash firmware for your phone model and country.
Here is an example of what you will find at SamMobile: http://www.sammobile.com/firmwares/2/
Good luck!
Click to expand...
Click to collapse
I understand what they do, that is why I used them. I downloaded both the amdl and amdb firmware from SamMabile.com and neither of them worked, it still goes through the same process.
lstat said:
I understand what they do, that is why I used them. I downloaded both the amdl and amdb firmware from SamMabile.com and neither of them worked, it still goes through the same process.
Click to expand...
Click to collapse
I would keep trying Odin. Try different usb ports, don't use hub. Make sure you have the original usb cord. If it can get into download mode there's hope.
I tried flashing through Odin a few more times today with no luck, even tried to repartition with a .pit file and that failed. I think my phone is just screwed.
test
testtesttesttesttesttesttesttesttesttesttesttest
Actually, I had the same exact problem when I flashed KTkernel to my S4 a while back. At first I tried Odin, and it said flash was successful, but still no recovery mode or any screen.
I actually used KIES, either firmware recovery or firmware update. And that solved it. The phone boot up normally after KIES.
Kevinnme said:
Actually, I had the same exact problem when I flashed KTkernel to my S4 a while back. At first I tried Odin, and it said flash was successful, but still no recovery mode or any screen.
I actually used KIES, either firmware recovery or firmware update. And that solved it. The phone boot up normally after KIES.
Click to expand...
Click to collapse
How exactly were you able to do this? Kies doesn't recognize the phone in download mode.
Make sure your KIES is up to date, and it should recognize the phone.
Here is a thread that may be helpful,
http://forum.xda-developers.com/showthread.php?t=2261153
and
http://www.samsung.com/us/support/faq/FAQ00029015/29183
Kevinnme said:
Make sure your KIES is up to date, and it should recognize the phone.
Here is a thread that may be helpful,
http://forum.xda-developers.com/showthread.php?t=2261153
and
http://www.samsung.com/us/support/faq/FAQ00029015/29183
Click to expand...
Click to collapse
Unfortunately this doesn't seem to be working for me, either. Kies is not recognizing my phone in emergency firmware recovery on OS X or Windows.
See if you can find help making kies to recognize your device. I think you should be able to since you used Odin.
Have you tried to Odin on a windows instead of a mac.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Reinaldo33897 said:
Have you tried to Odin on a windows instead of a mac.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, on both a Windows box and through Parallels, neither have worked.
lstat said:
Yes, on both a Windows box and through Parallels, neither have worked.
Click to expand...
Click to collapse
Same problem. I tried flashing Ktweaker, install failed, and now the phone just vibrates every few seconds.
I have tried installing the PIT file, as well as the original firmware. Trying to reinstall the recovery ends with a "Fail" message.
Totally stumped.
I scheduled a repair with Samsung. Mines boxed up ready to go, just haven't sent it off yet. I gave up trying to fix it and went back to my iphone.
Sent from my iPhone using Tapatalk
lstat said:
I scheduled a repair with Samsung. Mines boxed up ready to go, just haven't sent it off yet. I gave up trying to fix it and went back to my iphone.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Did the same thing
I had no problem using QBKing77's guide to root my S3. I looked for the comparable thread when I got my S4.
I loaded up Odin but got an error saying there was no PIT partition. I put the phone into debug mode (not in the instructions?) and it seemed to work.
But then it failed half-way through. I was plugged into a USB port on the front of the computer.
Now I get the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I searched and found other threads for the S3 and other phones but would appreciate some help with the S4. Thanks.
Edit: are these the steps I need to take?
Edit #2: Uh, I guess those steps won't work since they will prompt me for a serial number and there doesn't seem to be a way to get that from a Galaxy S4 if it won't boot.
Help?
Does the phone boot into download mode? Have you tried flashing the stock firmware through ODIN?
nxtech3 said:
Does the phone boot into download mode? Have you tried flashing the stock firmware through ODIN?
Click to expand...
Click to collapse
When it boots, it goes straight to the error. If I hold volume down + Home, it *will* go into download mode.
I didn't know what to flash with ODIN.
After the fiasco with the attempted rooting, I didn't want to chance flashing the wrong thing.
Thanks for the reply.
Edit: Can someone post step-by-step directions on how to flash stock firmware through Odin? (Or the link to the thread that probably already exists)
Preferably with a link to the exact ROM/firmware that I need?
Dougmeister said:
When it boots, it goes straight to the error. If I hold volume down + Home, it *will* go into download mode.
I didn't know what to flash with ODIN.
After the fiasco with the attempted rooting, I didn't want to chance flashing the wrong thing.
Thanks for the reply.
Edit: Can someone post step-by-step directions on how to flash stock firmware through Odin? (Or the link to the thread that probably already exists)
Preferably with a link to the exact ROM/firmware that I need?
Click to expand...
Click to collapse
Look for CF-Auto-Root for jfltespr. That will get you rooted but will trip your Knox counter.
garwynn said:
Look for CF-Auto-Root for jfltespr. That will get you rooted but will trip your Knox counter.
Click to expand...
Click to collapse
I have this file already downloaded: CF-Auto-Root-jfltespr-jfltespr-sphl720
I started Odin 3.07 ("Run as administrator") and loaded the file in the PDA slot. I waited for "<OSM> Leave CS.." to appear in the "Message" box. I hooked up the Galaxy S4 but the COM port will not show up... trying different cables now... (it is plugged into the back of the computer...)
Dougmeister said:
I have this file already downloaded: CF-Auto-Root-jfltespr-jfltespr-sphl720
I guess that's it?
Click to expand...
Click to collapse
That's it. Make sure it's the current one and flash in PDA slot using Odin.
Will reboot, apply root, reboot back to stock and voila!
garwynn said:
That's it. Make sure it's the current one and flash in PDA slot using Odin.
Will reboot, apply root, reboot back to stock and voila!
Click to expand...
Click to collapse
I can't get ODIN to recognize the S4 via the USB slot ("ID:COM" port stays blank). I even re-installed the S4 drivers. Any ideas?
I've tried 3 different cables, all plugged into the back.
Dougmeister said:
I can't get ODIN to recognize the S4 via the USB slot ("ID:COM" port stays blank). I even re-installed the S4 drivers. Any ideas?
I've tried 3 different cables, all plugged into the back.
Click to expand...
Click to collapse
Not to sound silly but did you reboot into download mode?
garwynn said:
Not to sound silly but did you reboot into download mode?
Click to expand...
Click to collapse
Not a silly question at all. I've been known to do that
But no, this time I was in "download mode". For some reason, it finally worked with one of the cables using a front USB port. (?)
Thanks for everyone's help. Crisis averted.
Dougmeister said:
Not a silly question at all. I've been known to do that
But no, this time I was in "download mode". For some reason, it finally worked with one of the cables using a front USB port. (?)
Thanks for everyone's help. Crisis averted.
Click to expand...
Click to collapse
I've had dicey situations using download mode just like you've described on 2 different gs4's. I use heimdall, not odin, but same flakey results. The gs4's download mode appears to be very finicky about the quality of the usb cable and port. I never had any issue with download mode with identical hardware when I used to flash my gs2. So it's not you, it's the gs4. I finally got some reasonably reliable and consistent flashing results by using the usb ports on the back, and a high quality blackberry usb cable. In my case, the "bad" ports on the front are usb1.1, while the ports on the back are usb 2.0. So it seems to matter when flashing the gs4. So I would say avoid using usb 1.1 ports if your computer is old enough to have them.
hi all.. im a beginner at installing custom roms.. i own a Samsung Galaxy S4 i9500.. a few days ago, i updated it to CyanogenMod c-11 (kitkat 4.4.4 based) ROM, then to CyanogenMod c-12 (lollipop based) ROM, so try out its new features.. however, since yesterday, my phone is not booting up.. neither is it able to go into recovery mode.. (the boot logo displays endless).. i can only go into the download mode..
so i downloaded ODIN.. and tried flashing I9500XXUFNI2_I9500ODDFNI1_INS.zip onto it.. however, no matter what i do (removing battery, restarting PC, restarting ODIN), i cannot go past the "initialization" step.. no matter which ROM i try, it never goes past the "initialization" step.. please help..
awesim said:
hi all.. im a beginner at installing custom roms.. i own a Samsung Galaxy S4 i9500.. a few days ago, i updated it to CyanogenMod c-11 (kitkat 4.4.4 based) ROM, then to CyanogenMod c-12 (lollipop based) ROM, so try out its new features.. however, since yesterday, my phone is not booting up.. neither is it able to go into recovery mode.. (the boot logo displays endless).. i can only go into the download mode..
so i downloaded ODIN.. and tried flashing I9500XXUFNI2_I9500ODDFNI1_INS.zip onto it.. however, no matter what i do (removing battery, restarting PC, restarting ODIN), i cannot go past the "initialization" step.. no matter which ROM i try, it never goes past the "initialization" step.. please help..
Click to expand...
Click to collapse
Did you try to unzip the stock ROM to receive the .tar file for ODIN?
Joku1981 said:
Did you try to unzip the stock ROM to receive the .tar file for ODIN?
Click to expand...
Click to collapse
yes i did.. the .zip file contains two files:
- SS_DL.dll
- I9500XXUFNI2_I9500ODDFNI1_INS.tar.md5
according to instructions in different online threads, im putting this .tar.md5 in the PDA/AP slot..
awesim said:
yes i did.. the .zip file contains two files:
- SS_DL.dll
- I9500XXUFNI2_I9500ODDFNI1_INS.tar.md5
according to instructions in different online threads, im putting this .tar.md5 in the PDA/AP slot..
Click to expand...
Click to collapse
Change USB cable/port, other pc or close Kies 3 on the task bar.
It sounds more like a hardware failure.
Joku1981 said:
Change USB cable/port, other pc or close Kies 3 on the task bar.
Click to expand...
Click to collapse
Ive already tried changing USB ports.. I dont have Kies installed in the first place.. I'll try repeating the procedure on a different system though..
i certainly hope it is not a hardware failure.. i literally slept with the phone on charge and woke up to a dead phone.. the phone boots up into the bootloop.. the recovery mode ends in the bootloop as well.. only the download mode ends up in the correct "downloading.. do no turn off target" screen.. and odin detects the phone just fine.. but upgrading any firmware via odin gets stuck on the "initialization" step.. i can answer more questions if required.. at this point i dont care which ROM works for my phone.. or if i lose data.. i just wanna revive my phone..
awesim said:
i certainly hope it is not a hardware failure.. i literally slept with the phone on charge and woke up to a dead phone.. the phone boots up into the bootloop.. the recovery mode ends in the bootloop as well.. only the download mode ends up in the correct "downloading.. do no turn off target" screen.. and odin detects the phone just fine.. but upgrading any firmware via odin gets stuck on the "initialization" step.. i can answer more questions if required.. at this point i dont care which ROM works for my phone.. or if i lose data.. i just wanna revive my phone..
Click to expand...
Click to collapse
did you solve your problem?
jkamz said:
did you solve your problem?
Click to expand...
Click to collapse
I am also facing the same problem. Were you able to solve it.
no
Buy another motherboard.that solved my problem.There is no other work around
I'm also facing same issue
Bro's, gotta start somewhere, right!
The fact that you're phones are boot looping is actually a good sign - it means that they're not totally useless but salvageable.
Question: Are you able to boot into your custom recoveries, e.g. TWRP? If yes, please reply.
If no, kindly uninstall your old samsung driver, reboot pc, install new driver, put your phone into "Download mode", connect phone to pc, run Odin & hope for the best! If you can get passed this step, then it's smooth sailing...
jkamz said:
no
Click to expand...
Click to collapse
I'm having this issue with mine today, anyone able to resolve this without going true warranty?
Is the phone recognized by Odin? Post a screenshot of the Odin error or post the Odin error.
audit13 said:
Is the phone recognized by Odin? Post a screenshot of the Odin error or post the Odin error.
Click to expand...
Click to collapse
i'm facing the same problem with mine,any Fix??need help guys:crying::crying:
Odin is not working because the phone was not assigned a com port.
audit13 said:
Odin is not working because the phone was not assigned a com port.
Click to expand...
Click to collapse
He is right should be blue in com port is it latest Odin 10.7
Sent from my SM-A720F using Tapatalk
The obligatory obvious question here. Do you have the Samsung driver installed?
Just repartition the eMMC chip using .pit file with odin that it is suitable for galaxy S4 i9500.
If anyone has tried, please tell us, that it is work or not.
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Thanks!
Guys, I need a hand here, as I hit a solid brick wall and no amount of scouring the forums helped me find a suitable solution.
Hardware involved:
Galaxy Note 3 N9005 that was running 4.4.2 (bought unlocked)
iMac with Yosemite and Parallels with Ubuntu and Windows 10 with Heimdall and Odin 3.09 installed
What I set out to do: root & install clockworkmod recovery with the ultimate goal to install Linux on Android. I had my previous Note 2 and LG P990 rooted too, so I was not entirely new to the procedure.
What I "achieved": Heimdall would not work at all due to a problem that apparently affects all Samsung 4.4.2 devices. So I got Parallels on my Mac and installed Windows 10 Technical Preview to run Odin. After several attempts I finally managed to got Odin to say "PASS" on the CF Auto-Root procedure. However, the phone would not boot anymore and always return to it's ODIN state. But I also succeeded to get Clockworkmod installed.
With that I installed Cyanogen, thinking to be able to get around the booting problem. I wasn't. Now when booting Cyanogen, I get a message that encryption was unsuccesful and the device needs to be restored.
I would like to comply and downloaded the stock files for restoring through Odin, but now even with the device in the proper ODIN download state, the phone is no longer recognized by the Software. Tried about a hundred times now with reboot etc. and nothing seems to work. Even KIES does note recognize the phone anymore.
I can enter CWM and Odin modes just fine. I just can't boot and I can't get it recognized by my Mac anymore. My best guess is I unintentionally screwed up the partition table / PIT file and now I can't restore it anymore.
I am at the end of the rope here and getting desperate, any suggestions (preferably step by step) would be most welcome!
psearcher said:
Guys, I need a hand here, as I hit a solid brick wall and no amount of scouring the forums helped me find a suitable solution.
Click to expand...
Click to collapse
It's very weird that in Download Mode Odin don't recognize your device. Remember that you need Kies 3 for android 4.4.2 and Kies 3 has to be completely closed for use ODIN.
Joku1981 said:
It's very weird that in Download Mode Odin don't recognize your device. Remember that you need Kies 3 for android 4.4.2 and Kies 3 has to be completely closed for use ODIN.
Click to expand...
Click to collapse
Ok, I tried on my Win Laptop from work now and Odin can recognize the Smartphone there. I will take it home on the weekend to go further.
However, a hasty try to flash the stock rom (Vodafone NL Lollipop) resulted in the same "encryption failed" error I had before. Any ideas what I am doing wrong?
psearcher said:
Ok, I tried on my Win Laptop from work now and Odin can recognize the Smartphone there. I will take it home on the weekend to go further.
However, a hasty try to flash the stock rom (Vodafone NL Lollipop) resulted in the same "encryption failed" error I had before. Any ideas what I am doing wrong?
Click to expand...
Click to collapse
Your phone is unlocked. You had to try the POLAND Lollipop firmware or wait till future udpates.
Joku1981 said:
Your phone is unlocked. You had to try the POLAND Lollipop firmware or wait till future udpates.
Click to expand...
Click to collapse
Hi there Joku!
Just tried the Polish Lollipop Firmware and it still keeps displaying the "Encryption failed" error. It looks like it does not matter which file I flash, it will keep showing the same error.
Like I said, I believe I somehow broke the PIT file of the phone. Any ideas how to fix this?
Regards,
Rene
Try this pit file.
https://meocloud.pt/link/4ebb315a-867c-4469-bfdf-c234ca9f4d1e/PIT-File-DBT VFG-UK-MSM8974.zip/
Put it on pit field. Set repartition on and auto reboot. If all goes well then try to flash the Vodafone NL 4.4.2 rom (it's the one I use so I know that this pit file works with it).
Sent from my SM-N9005
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
If it doesn't work try to go in TWRP and wipe the /data partition and then reflash the stock rom.
Sent from my SM-N9005
Question solved!
DeuXGod said:
Try this pit file.
Put it on pit field. Set repartition on and auto reboot. If all goes well then try to flash the Vodafone NL 4.4.2 rom (it's the one I use so I know that this pit file works with it).
Sent from my SM-N9005
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
If it doesn't work try to go in TWRP and wipe the /data partition and then reflash the stock rom.
Sent from my SM-N9005
Click to expand...
Click to collapse
Thanks DeuXGod, but by now I more or less stumbled on the solution by trial and error. I'll post it here, hoping that somebody may benefit from my endeavours in the future. As a n00b I can't post links though. Sorry for that.
I do not know if all the steps are necessary or correct, but in the end they did lead me back to a working device. :fingers-crossed:
After trying a few PIT files here in the forums, the problems did not go away. Some of them would lead to a phone that just got stuck at the "Samsung" screen and would not fully boot up.
So I got the idea to flash back the "old" Dutch 4.4.2 ROM, which I downloaded from Sammobile and flashed in ODIN. After booting it showed a bit of a different error message, saying the file system was corrupted
I googled for this and stumbled on a small ZIP file that is supposed to fix "cannot mount DATA / EFS errors". I loaded this on my SDXC.
Flashed aforementioned ZIP file through the recovery from the SDXC.
After rebooting it still showed the same error, so I got back to recovery, did a factory reset and a cache wipe.
Another reboot and much to my surprise (and great relief) the phone booted up normally again!
From there I thought that if this worked, the Polish 5.0 should work too. I flashed it. Flashed CF Auto Root after that and everything seems to be working fine!
I set everything up and the phone is now restoring the apps etc. So far looking very good!