Ok guys I seem to have a problem
I tried to flash the new firmware through Odin, and it went through ok. Restarted back into Android, then went to flash a custom recovery.
When I tried flashing the recovery, it said there was a PIT error, so I got the i9505 PIT and tried to flash it with the firmware in Odin.
It won't flash at all, everytime I get to NAND Write Start, it says right after Complete(Write) Operation Failed.
Am I pretty much screwed here?
Also it says Write Protection Enabled in the Odin Mode.
Any help would be great!
I can still get in Download Mode, but when I try to turn on, it mentions Firmware Problem and connect to Kies
try to restore it using kies, if that works.
I think I've brought my phone back from the clutches of death.
I've managed to re-partition using a .pit file, and flash back to AME3. Recovery flashed fine too. It seems I can't flash the MEA, it just corrupts my PIT every time I try and flash it... So I think i'll stick with AME3
interesting, something like this should never happen
I have the feeling it was something else, not the ROM itself...
okty2k said:
interesting, something like this should never happen
I have the feeling it was something else, not the ROM itself...
Click to expand...
Click to collapse
I was thinking that myself.
I've never had problems flashing with Odin3 before, but saying that, i'm currently using my girlfriends Windows 8 x64 machine until I get a new laptop. To recover it, I used my dads Windows Vista laptop, and all flashed fine. Very strange.
Also does CSC matter? I'm in the UK, but Kies says my CSC is TGY, which is Hong Kong?
Brownie2k said:
I was thinking that myself.
I've never had problems flashing with Odin3 before, but saying that, i'm currently using my girlfriends Windows 8 x64 machine until I get a new laptop. To recover it, I used my dads Windows Vista laptop, and all flashed fine. Very strange.
Also does CSC matter? I'm in the UK, but Kies says my CSC is TGY, which is Hong Kong?
Click to expand...
Click to collapse
No for the CSC (as far as I know, at least).
It might have been the USB port you used. Also, if any Kies instance was still running, that can also lead to problems.
From what you wrote I think it was a problem with ODIN detecting the phone the right way...
okty2k said:
No for the CSC (as far as I know, at least).
It might have been the USB port you used. Also, if any Kies instance was still running, that can also lead to problems.
From what you wrote I think it was a problem with ODIN detecting the phone the right way...
Click to expand...
Click to collapse
I'm giving it another go on the Vista Machine.
Thing was, the MEA actually installed ok on this computer, but there was no WiFi, so I was going to install Philz CWM and clear data/cache etc. When I went to install the recovery, I got the error No PIT Information Found or something along them lines. From there, my problems really started. I can't understand why.
If it all works out well on the Vista machine, then I think it's safe to say that I won't be using Windows 8 to update my phone anymore.
I'll report back with any info.
Ok final update on this whole situation.
Using the Windows Vista laptop, I reflashed the pre-rooted MEA firmware. It all installed ok, no NAND Write Error, no fails.
Booted into Android, all seems fine. Wifi was working as expected.
Rebooted back into Download Mode, flashed Philz CWM Touch, failed first time, ran Odin3 as administrator and tried again.
Recovery flashed fine, no problems, no errors.
Rebooted into recovery, cleared cache, data.
Rebooted again into Android, finally setting up now.
All seems fine now, running MEA firmware, custom recovery
Related
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
Searched but and found similar posts but with different phones or different firmware, so the file references were of no help.
Basically I had safestrap working, had flashed google play edition ROM and it was working great with the exception of the play store not wanting to connect. I was in the process of messing with that and read (here) that I needed 4.3 edition of that app, I checked and I had 4.2, so I loaded 4.3 to the Sdcard and installed it..
Phone rebooted and just stays on the samsung custom splash screen indefinitely . I can get to ODIN on the phone, soI tried using https://builds.casual-dev.com/jodin3/ to get access and see what I could do, but it keeps telling me to unplug and plug in the phone, and gives an error that it cant mount the device.
So, im kinda stuck, I didn't use ODIN to do anything previously, But considering its the only thing I currently have access to, I guess its my only hope.
Been fighting this a few hours and getting pretty dejected, I had almost everything PERFECT.. and now back to WORSE than where I started.
Wingnutt said:
Searched but and found similar posts but with different phones or different firmware, so the file references were of no help.
Basically I had safestrap working, had flashed google play edition ROM and it was working great with the exception of the play store not wanting to connect. I was in the process of messing with that and read (here) that I needed 4.3 edition of that app, I checked and I had 4.2, so I loaded 4.3 to the Sdcard and installed it..
Phone rebooted and just stays on the samsung custom splash screen indefinitely . I can get to ODIN on the phone, soI tried using https://builds.casual-dev.com/jodin3/ to get access and see what I could do, but it keeps telling me to unplug and plug in the phone, and gives an error that it cant mount the device.
So, im kinda stuck, I didn't use ODIN to do anything previously, But considering its the only thing I currently have access to, I guess its my only hope.
Been fighting this a few hours and getting pretty dejected, I had almost everything PERFECT.. and now back to WORSE than where I started.
Click to expand...
Click to collapse
The 4.3 edition of SS doesn't work on 4.2. Does it stay on the splash or does it go to the actual boot animation? Also, you don't need to boot into the phone to use odin, it's a PC program. You can google "mf3 tar files" and you'll find the thread with the ODIN files, use them to get back to stock.
DeadlySin9 said:
The 4.3 edition of SS doesn't work on 4.2. Does it stay on the splash or does it go to the actual boot animation? Also, you don't need to boot into the phone to use odin, it's a PC program. You can google "mf3 tar files" and you'll find the thread with the ODIN files, use them to get back to stock.
Click to expand...
Click to collapse
It sits on the Samsung custom screen, that's it.
And how do I use the ODIN files.. When the ODIN program won't do anything except tell me over and over to in plug and plug in the phone?
How do I "use the Odin files" ??
Wingnutt said:
It sits on the Samsung custom screen, that's it.
And how do I use the ODIN files.. When the ODIN program won't do anything except tell me over and over to in plug and plug in the phone?
How do I "use the Odin files" ??
Click to expand...
Click to collapse
Did you install the Samsung USB Drivers? Google that and install them, then plug in the phone and run the program.
DeadlySin9 said:
Did you install the Samsung USB Drivers? Google that and install them, then plug in the phone and run the program.
Click to expand...
Click to collapse
I *think* I already have installed them but I'll double check just in case, I have android file transfer installed, it does the same, I'll try it under windows in instead of Mac as well.
Ok, ODIN sees the phone, under windows, Downloading a MF3 TAR file as seen here http://forum.xda-developers.com/showthread.php?t=2504311
(1.5gb?!) once thats done Ill see what we have![/QUOTE]
Well, im a little stuck
I downloaded a the MF3 TAR file from here:http://forum.xda-developers.com/show....php?t=2504311
Flashed the bootloader: BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.mp5
That went through properly, the phone rebooted..
No change..
what am i supposed to do next?
I flashed the CSC file: CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
That went through as well, after reboot no change.
Tried flashing the phone file: PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
but nothing happens, no error message... it just doesent do anything :silly:
a little help?
Wingnutt said:
Well, im a little stuck
I downloaded a the MF3 TAR file from here:http://forum.xda-developers.com/show....php?t=2504311
Flashed the bootloader: BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.mp5
That went through properly, the phone rebooted..
No change..
what am i supposed to do next?
I flashed the CSC file: CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
That went through as well, after reboot no change.
Tried flashing the phone file: PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
but nothing happens, no error message... it just doesent do anything :silly:
a little help?
Click to expand...
Click to collapse
You put platform tar in the PDA slot right? Also, you might have to restart between flashes or just load them in all at once.
There's a picture on this post with what options you should have: http://forum.xda-developers.com/showpost.php?p=46955352&postcount=7
DeadlySin9 said:
You put platform tar in the PDA slot right? Also, you might have to restart between flashes or just load them in all at once.
There's a picture on this post with what options you should have: http://forum.xda-developers.com/showpost.php?p=46955352&postcount=7
Click to expand...
Click to collapse
Yep, ive read that thread stem to stern, everything is in the correct slots, I can flash everything EXCEPT the platform file
have tried it by itself, and as added with the rest, either way it same result.
Wingnutt said:
Yep, ive read that thread stem to stern, everything is in the correct slots, I can flash everything EXCEPT the platform file
have tried it by itself, and as added with the rest, either way it same result.
Click to expand...
Click to collapse
Make sure the file you download was full and that it extracted the whole platform file. Other than that i'm not sure why it wouldn't work..
DeadlySin9 said:
Make sure the file you download was full and that it extracted the whole platform file. Other than that i'm not sure why it wouldn't work..
Click to expand...
Click to collapse
Ive downloaded it twice, Ive tried flashing it under windows 7 and OSX. Same result.
I would be happy to try a different platform file, but I cant find any others.
One oddity, the ONLY Odin program that can see the phone is Jodin3, the web based version.
Ive downloaded 1.85 and 3.07 (windows) have updated the samsung USB drivers, have updated the heimdall software... they cant see it.
Wingnutt said:
Ive downloaded it twice, Ive tried flashing it under windows 7 and OSX. Same result.
I would be happy to try a different platform file, but I cant find any others.
One oddity, the ONLY Odin program that can see the phone is Jodin3, the web based version.
Ive downloaded 1.85 and 3.07 (windows) have updated the samsung USB drivers, have updated the heimdall software... they cant see it.
Click to expand...
Click to collapse
Seems like it's not installing the drivers right. I'd try installing again: http://forum.xda-developers.com/showthread.php?t=2038555 or just manually go into device manager and point it to where you installed the drivers. Also, you might have to wait a while on any version of ODIN (even the we version) for it to finish checking the file.
OHHHH ****!
You were right, it was the USB drivers, I had to do it via method 3, I.E. manually select them.. for some odd reason the installer DID install the drivers but the device showed up as someting totally different than when doing it manually.
flashing now... will see what happens:laugh:
ITS ALLLLIIIVVVEEEE!!!!!!!
Ok. so, now I cant start over lol!
Thanks for all your help, everyone!!
I’m having a problem flashing via ODIN or anything else… I have a Sprint SPH-L720 MF9 everything. I am using a mac with VMware fusion and windows xp and 7. I have also tried everything below on a native windows 7 machine.
I started with MF9 and had rooted and ran TriForce 3.1 for a long time. Everything was working fine, so I never updated. I didn’t want to get tangled up in the knox mess. I decided to go ahead and update last night and I went through using unknownforce’s instructions and downloads. I tried to flash NAE modem only, but odin failed. Now it won’t boot, just goes to the download mode page. (the one that says to recover using kies) it also allows me to enter download mode (power+volume \/)
I’ve tried:
Odin full MF9 firmware (as my phone started with this, and I’ve never flashed anything knox)
Odin MF9/NAE modem
Full MF9 odin restore (there’s a thread that has the whole exe that does everything)
All of these with adding a pit file.
Every time, odin fails. It seems to be failing at the modem.bin, but who knows. It doesn't seem to transfer for very long, perhaps 2 minutes.
I’ve gotten to the “screw it” stage and loaded Kies (tried both mac and windows xp and 7) and tried to do a recovery there. It won’t recognize the phone right now though. It just sits there, basically. EDIT: It sees the phone and sits there trying to connect, but eventually times out.
Odin can see the phone and attempts to flash, but again, runs into the problems above. I can’t download the firmware through kies due to being a sprint phone and no S/N. I'd prefer to avoid knox, but if I have to, I'm fine with going that route. If I'm not out of warranty yet, it will be soon. As long as that's the only big ramification, I don't really care.
Anyone have any ideas? Need more information?
Update: I was able to get part of the NAE update to work. The Knox bootloader. That's it. It's not tripped, but it's now showing in download mode. Still can't get any further, however.
Sent from my Nexus 7 using Tapatalk
Maybe try this: http://forum.xda-developers.com/showthread.php?t=2277480. I always use Run as Administrator for Odin and used 3.07 Odin to flash MF9 and NAE. If you try, follow every step to the T. Sorry if I didn't help.
.
2WhiteWolves said:
Maybe try this: http://forum.xda-developers.com/showthread.php?t=2277480. I always use Run as Administrator for Odin and used 3.07 Odin to flash MF9 and NAE. If you try, follow every step to the T. Sorry if I didn't help.
.
Click to expand...
Click to collapse
The linked page for unknownforce is actually the page I was using to update the first time. The problem is, odin fails no matter what I do... I appreciate the suggestion though.
Try different usb cable and usb port. Someone mentioned to uninstall kies it will cause issues with odin. You can try that or uninstall drivers an install it again. Or try different versions of odin. I use 1.85 and some versions thats starts with 3. Since you already flashed NAE tar. You can not flash any version before NAE. Hope it helps.
Sent from my Nexus 5 using Tapatalk
Called sprint who transferred me to Samsung, they couldn't talk me through it. The phone wouldn't show up in kies for them. They did mention, to my great relief, to steer clear of the sprint store. They instructed me to head to best buy and go to the Samsung store inside. Apparently they supposedly have a tool to reflash the phone there... We'll see later today. I'll post back with my results. I have 28 days left in my warranty. Just in time, it seems.
I didn't try using 1.85, but had tried 3.07 and 09. Kies came later. I originally used the drivers recommended in other threads. I only have two ports on my main machine, but did try another machine without success. Cords as well. Actually I did a backup with one of the cords right before trying the flash. Who knows.
Now that the warranty is nearly gone and I'm surely knoxed now.. Is there anything I need to watch out for? Does it make it much different to flash or is it just the flag for my soon to be nonexistent warranty?
Sent from my Nexus 7 using Tapatalk
Update:I took the phone to Samsung inside Best Buy. They hooked it up to a laptop and got it working within 20 minutes. They flashed 4.4.2 onto the phone, and to my surprise, everything was as I left it, minus root, and with Sprint ID added. Somehow, through everything, my data partition was untouched. Even more interesting, all of my apps and everything work. I was on TriForce ROM 3.1... Only thing I've noticed is that my data connection isn't consistent. It will drop out, and stay out until I toggle airplane mode. Still says I have signal, and can make calls.. I think a full restore may be in order.
Moral of the story? The SWAS (Store Within A Store) Samsung is running in Best Buys is pretty decent. They took no time at all, in the grand scheme of things. Unfortunately, I wasn't able to see the software they used. He tried Kies at first, but moved on quickly.
Hi,
I just tried to flash the baseband "I9505XXUGNG2-MODEM" with MobilOdin to the S4 (i9505) with installed CyanogenMod 11 (last nightly). After reboot the phone displays the Samsung S4 logo and after this a black screen with a fast flashing very smal pink triangle in the center of the screen which moves from left to right and start over.
What is this and how can i get the phone to work again?
Thanks
I have the exact same problem. Bought Mobile Odin and tried to flash with it, and this happened. I dont know about you but for me it wont even go into recovery mode. The only thing seemingly working here is download mode, but Odin cant find my i9505, even tho its able to find my old Galaxy S(1).
Are we having the same problem? Is there anyone that can help?
Odin worked for me in the download mode so I had luck to find a solution.
I flashed TWRP with ODIN. After this I could enter TWRP on the S4 again. But the normal boot still didn't worked. So I flashed the last nightly CM11 (the zip was still on the phone) from within TWRP. After this the S4 booted fine again without any data loss
That's because you can't use MobileOdin to flash a modem if you have the new bootloader.
I am glad u found a solution hitziflitzi.
However im not as fortunate at this moment. Anyone got any idea what i can do? Im in the same spot as he was, except Odin for PC wont recognize my phone, even tho it recognized my old phone just fine.
Help would be much appreciated
Bump
Do i need do buy a new phone? Any thoughts?
DarioG87 said:
Bump
Do i need do buy a new phone? Any thoughts?
Click to expand...
Click to collapse
hi mate
what odin are you using , did you see what @Lennyz1988 said?
Hi there
On pc i have tried these versions of Odin:
1.83
1.85
3.04
3.06
3.07
3.10
They all find my galaxy S1 but non of them can find my S4 :\
When i connect my S4 to the computer it says "usb device not recognized"
As for MobileOdin i used the newest at that time, fresh off play store.
At the time i flashed i was not aware that i couldnt use MobileOdin as Lennyz1988 said, it all seemed to be safe and easy when i used the app.
Help is much appreciated
DarioG87 said:
Hi there
On pc i have tried these versions of Odin:
1.83
1.85
3.04
3.06
3.07
3.10
They all find my galaxy S1 but non of them can find my S4 :\
When i connect my S4 to the computer it says "usb device not recognized"
As for MobileOdin i used the newest at that time, fresh off play store.
At the time i flashed i was not aware that i couldnt use MobileOdin as Lennyz1988 said, it all seemed to be safe and easy when i used the app.
Help is much appreciated
Click to expand...
Click to collapse
Hi mate
Did you try this:
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
http://forum.xda-developers.com/showthread.php?t=2265477
If all that fail , try this:
https://www.youtube.com/watch?v=YO7TVY2UXEY
See if it works, reflash stok rom again , backup first , EFS too
I have tried all that unfortunately.
I dont know what to do when my pc finds my old phone(s1), but not my new one (s4). It found my s4 all fine before i flashed with mobile odin, but after that i cant boot or go into recovery, only put it into download mode.
Is my phone dead? Do i have to buy a new one? :\
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!