Related
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!
Hello all,
Problem: my S5 SM-G900F has ''Reactivation Lock'' enabled.
ROM: XtreStoLite 2.2 (touchwiz based)
I tried to get into my recovery and it gave me Custom binary blocked by Reactivation Lock instead. It seems Reactivation Lock is enabled. This happened to me after (not directly) I had flashed XtreStoLite 2.2 ROM. The thing is that I don't remember enabling anything, and I can't find the option to disable it in this ROM either. Also I never made a Samsung account in order to enable this lock. And it looks like I need a Samsung account to disable it again. So how can I disable it if I don't have a Samsung account in the first place?
I tried to flash recovery via Odin, but that just failed. I also tried to do a factory reset from the settings menu but then settings app just crashed and nothing happens.
I really hope someone can help me... Thanks in advance!
Flash a stock Kitkat ROM with ODIN from sammobile dot com, instructions under the download
Log into all accounts you have, disable reactivation lock
--
Can a mod make these instructions a MASSIVE red sticky? The number of people not reading threads and asking the same question day after day is ridiculous
Flash a stock Kitkat ROM with ODIN from sammobile dot com, instructions under the download
Log into all accounts you have, disable reactivation lock
Click to expand...
Click to collapse
Thanks for your reply!
I had already flashed a lollipop version via the same way. But I see you say KitKat, and probably for a reason...
Now with the Stock Lollipop ROM which I flashed:
-In download mode I can see Reactivation Lock is ON.
-It shows a Samsung icon to add an account in account settings. But selecting it results in nothing.
-Factory reset doesn't work. Results in endless loop <next> <next>....
-In settings>security Reactivation Lock can't be disabled. It just turns itself on automatically.
I'm downloading a KitKat version now. Hope that solves the problem.
Lollipop doesn't work, needs to be KitKat
*Detection* said:
Lollipop doesn't work, needs to be KitKat
Click to expand...
Click to collapse
Downloading took forever (200kb/s)... But I've the file now. Tried to flash it via Odin. All great, but near the end it fails to complete...
I tried twice. This phone is from Germany, but I live in the Netherlands. I bought it with Lollipop on it, didn't need to update from KitKat first. Is there any problem in that when going to a KitKat firmware? The firmware I downloaded is one for the Netherlands, not Germany.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANH6_G900FPHN1ANH1_G900FXXU1ANG8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
-edit-
Seems I need a PIT file or something (for re-partitioning phone). Will try finding one...
All good now. Thanks for your help
For the ones that might have same problem as I had:
Download KitKat firmware and flash it using Odin. If you get an error (because downgrade from L to KK) get yourself the right .PIT file for re-partitioning your phone. I got mine from here : http://forum.xda-developers.com/showthread.php?t=2737448 and flasht it after the fail. Then did a factory reset via stock recovery and booted phone. On some point got the Samsung lock thing which wanted me to log in. Just made a Samsung account and logged in. Now it's all working fine and Reactivation Lock is disabled via the settings.
Disabling reactivation lock - another solution
Darkmond said:
All good now. Thanks for your help
For the ones that might have same problem as I had:
Download KitKat firmware and flash it using Odin. If you get an error (because downgrade from L to KK) get yourself the right .PIT file for re-partitioning your phone. I got mine from here : http://forum.xda-developers.com/showthread.php?t=2737448 and flasht it after the fail. Then did a factory reset via stock recovery and booted phone. On some point got the Samsung lock thing which wanted me to log in. Just made a Samsung account and logged in. Now it's all working fine and Reactivation Lock is disabled via the settings.
Click to expand...
Click to collapse
I encountered the same problem with the reactivation lock after flashing xtresolite (lollipop) onto my g900f. I followed the steps to download the stock KK rom, flash from Odin and reboot. At this point I got stuck on the boot screen (not boot-loop) indefinitely (until 2% battery). After flashing KK, removing battery and reinserting it I was then able to boot into the stock recovery. I did a factory reset and wiped the cache and rebooted. The phone now boots normally into stock KK rom and I was able to deactivate the reactivation lock using my samsung account. Hope this helps anyone with a similar issue.
please help me with my s6 g920a, I can't find any kitkat firmware.
/
Darkmond said:
All good now. Thanks for your help
For the ones that might have same problem as I had:
Download KitKat firmware and flash it using Odin. If you get an error (because downgrade from L to KK) get yourself the right .PIT file for re-partitioning your phone. I got mine from here : http://forum.xda-developers.com/showthread.php?t=2737448 and flasht it after the fail. Then did a factory reset via stock recovery and booted phone. On some point got the Samsung lock thing which wanted me to log in. Just made a Samsung account and logged in. Now it's all working fine and Reactivation Lock is disabled via the settings.
Click to expand...
Click to collapse
Another easy solution can be found here:
[Guide] Unlock FRP / Deactivate Reactivation lock, Root and recovery for Samsung
Hi, How can i downgrade from APDC firmware to APB7? Within Odin there's no way to do that beacuse it doesn't allow to replace or install firmware older than the one you have on your phone (unlocking OEM from developer menu doesn't work).
Now the only thing i was able to do is to install TWRP recovery and root the phone but i need to find a way to get back the best working APB7
thanks , bye
jantellaz said:
Hi, How can i downgrade from APDC firmware to APB7? Within Odin there's no way to do that beacuse it doesn't allow to replace or install firmware older than the one you have on your phone (unlocking OEM from developer menu doesn't work).
Now the only thing i was able to do is to install TWRP recovery and root the phone but i need to find a way to get back the best working APB7
thanks , bye
Click to expand...
Click to collapse
Here : http://www.theandroidsoul.com/download-a3-2016-stock-firmware-88226/
there is latest MM and older LP firmwares..
jantellaz said:
Hi, How can i downgrade from APDC firmware to APB7? Within Odin there's no way to do that beacuse it doesn't allow to replace or install firmware older than the one you have on your phone (unlocking OEM from developer menu doesn't work).
Now the only thing i was able to do is to install TWRP recovery and root the phone but i need to find a way to get back the best working APB7
thanks , bye
Click to expand...
Click to collapse
Download firmware linked by @XDADEVX .
I think you may need one of these, too.
Then open odin go to pit button and select the pit file and in AP select the firmware. You also need to check "Repartition" box in odin.
Now click start and wait .
Downgrading firmware is very dangerous, bla, bla, bla.
Before choosing read this
Samsung usually prevent downgrading via odin for a reason.
If the firmware has had a revision update then down grading can make bad things happen.
ashyx said:
Samsung usually prevent downgrading via odin for a reason.
If the firmware has had a revision update then down grading can make bad things happen.
Click to expand...
Click to collapse
So? Which would be the way for downgrading this phone from MM to LP? I'm still on stock LP. But I'd like to try MM only if I'm sure I'll be able to go back. Usually, in most phones I've tried, is flashing the older ROM and then do a data wipe from recovery. I haven't tried with this A3 yet.
---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------
jantellaz said:
Hi, How can i downgrade from APDC firmware to APB7? Within Odin there's no way to do that beacuse it doesn't allow to replace or install firmware older than the one you have on your phone (unlocking OEM from developer menu doesn't work).
Now the only thing i was able to do is to install TWRP recovery and root the phone but i need to find a way to get back the best working APB7
thanks , bye
Click to expand...
Click to collapse
You've created a user just to ask this but didn't bother to come back and tell what happened or how did you fix it, if you did.
Please don't be selfish. Don't just ask. Help others too, leave an update.
downgrade
Hello Everyone,!
Someone help me please!
I have a telekom hungary samsung galaxy a3 2016sm-a310 phone, and i want to downgrade from android 7.0 nougat to android marshmallow 6.0.1
I downloaded the correct firmware file, but odin has stopped updating firmware.
Odyn log is here:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> A310FXXU2BQB6_A310FTMH2BQB6_A310FXXU2BQA6_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)What i'm dong wrong?
Thanks, Zolee
---------- Post added at 02:59 PM ---------- Previous post was at 02:49 PM ----------
Hi everyone! I have same problem! Odin has stops the update process, the sboot.bin file complete writing failed, nothing doesn't happened.
Hello all, recently I rooted using SamFAIL method it worked but I wanted to revert back to Stock so I downloaded my firmware and tried going back to stock as the instructions on the thread were. I couldn't get the AP file to pass so my dumb self gave up and tried going back to root by just putting the BL and CSC again as if I finished Part 1 of the SamFAIL method anyways now my device is in a boot-loop currently, the AP file worked but now it says this.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My device is a G950U model on Sprint. Im just worried I made a huge mistake and that my device is useless now if anyone can help me it'd mean alot. Sorry if this post is hard to understand.
Edit: Another question as well when I rooted I noticed it changed my model to G950U1 and my base to AQH3 should I download that firmware and see if it will flash it and see if it works?
Edit 2: i dont know what happened but I was going off to sleep and i looked at my device and it booted up on itself it still has root unsure why this hapended perhaps was it my low battery? when the device booted it was at 10% anyways how do i close this thread!
(This post is intended for people that legally own the S8+).
OK so in short I bought an S8+ online and couldn't login after it had been wiped.
"unauthorized factory reset" error.
This method worked for me (Samsung S8+ 64GB) running Android 8.0
To flash I am using Odin 3.12.1
Firstly we need the combination rom which you can download here:
Combination Rom V7/V8
Put your phone into download mode. Connect it to your PC and flash the combination rom.
(In odin click AP and add it there.)
After you have flashed, boot up your phone. Go into settings (Swipe down from the top) and perform a factory reset from inside the rom.
Let the phone reboot. Now power it off and enter download mode again.
Next we want to flash our firmware. I am using (G955FXXU2CRED) this worked for me, I am unsure of others.
Flash: AP - BL - HOME_CSC
After this has finished the phone will reboot and totally bypass the Google setup, you will have full access.
Now go into settings, Reset > Factory data reset. (While I was there I also turned off OEM and enabled USB debugging).
Now reboot once more and you will be faced with the Google setup, now you can enter your Gmail.
Enjoy.
Hello and thank you for this guide but i have a problem.
I have followed all the steps in your guide up to the point where i need to flash my device with stock firmware. When i flash my samsung s8 plus g955f with stock firmware odin says pass, then my device reboots back to factory binary with firmware g955fxxu2are1 although i flashed with stock firmware g955fxxu2cred. Any idea why this might be happening and how i can fix this?
Note: my device was on g955fxxu2cred before starting this process in your guide.
I can only assume you have flashed the wrong firmware, otherwise you would not have a different firmware version.
Try and start by flashing the "RED" firmware to start with, then follow the guide from step 1.
Sorry for sounding like a noob but what is "RED". I have checked again to make sure i flashed with stock firmware g955fxxu2cred and i can confirm this was the stock firmware i used. I downloaded this firmware from sammobile so it cant be the wrong one.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Also when i access settings from rom after flashing factory binary i do not have the option for oem unlock. I pressed 7 times on build to access the develepor options and there still isnt an oem unlock option.
No the OEM unlock is after you have bypassed the gmail login screen.
Where are you getting the firmware from? Sorry when I say "Red" I mean "G955FOXM2CRED"
Maybe some bad firmware? I got the G955FOXM2CRED firmware from updato.
nitec0re said:
(This post is intended for people that legally own the S8+).
OK so in short I bought an S8+ online and couldn't login after it had been wiped.
"unauthorized factory reset" error.
This method worked for me (Samsung S8+ 64GB) running Android 8.0
To flash I am using Odin 3.12.1
Firstly we need the combination rom which you can download here:
Combination Rom V7/V8
Put your phone into download mode. Connect it to your PC and flash the combination rom.
(In odin click AP and add it there.)
After you have flashed, boot up your phone. Go into settings (Swipe down from the top) and perform a factory reset from inside the rom.
Let the phone reboot. Now power it off and enter download mode again.
Next we want to flash our firmware. I am using (G955FXXU2CRED) this worked for me, I am unsure of others.
Flash: AP - BL - HOME_CSC
After this has finished the phone will reboot and totally bypass the Google setup, you will have full access.
Now go into settings, Reset > Factory data reset. (While I was there I also turned off OEM and enabled USB debugging).
Now reboot once more and you will be faced with the Google setup, now you can enter your Gmail.
Enjoy.
Click to expand...
Click to collapse
I have a regular S8 (950U), most FRP bypass for these devices require the ADB FRP.bat to be run between the combination firmware and the normal firmware are installed, at which part is the FRP actually being removed/bypassed here?
I m trying also the same. I installed the combination. The frp is off now but i can't find the right stock rom. The phone has bootloader level 4. From where you got the stock rom? Whatever i tried i got an error binary 4>1.
I have the G955U AT&T.
If this process works smothly, it sure beats the method of http://www.techoxygen DOT COM /bypass-factory-reset-protection-on-samsung-galaxy-phone/
I found, for me with the above process, an easier method to get onto the internet by using a Bose headphone with a mic, and when at the initial login/setup page, which FRP then requires you knowing the login info, pressing a Bose headphone button brought up a prompt for voice command, and at that point say chrome or google and you are on the internet to get the two files you will need in the solution. After setting up the several apps, then you are able to enter the (your Google email) 'login', and on re-boot the FRP will be gone, using your initial 'login'. Done
The flashing method is more direct and less hassle.
SUCCESS on g930f. Thank you so much. By the way... I had the newest fw with september patch installed.
Flashed the G930FXXS3ERHD
Flashed Combination file COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship
Let Boot up.
Perform a factory reset in Settings.
Flash G930FXXS3ERHD (AP, BL, CP) (got fail message after trying to flash CSC or HOME_CSC)
Worked like a charm. Thank you so much.
spittfire said:
SUCCESS on g930f. Thank you so much. By the way... I had the newest fw with september patch installed.
Flashed the G930FXXS3ERHD
Flashed Combination file COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship
Let Boot up.
Perform a factory reset in Settings.
Flash G930FXXS3ERHD (AP, BL, CP) (got fail message after trying to flash CSC or HOME_CSC)
Worked like a charm. Thank you so much.
Click to expand...
Click to collapse
So which did you flash, the regular CSC or home CSC?
Just the AP, BL and CP.
After booting in Oreo i entered my gmail account, Flashed another time with AP, BL, CP, and CSC, made a cache wipe and a factory Reset.
spittfire said:
SUCCESS on g930f. Thank you so much. By the way... I had the newest fw with september patch installed.
Flashed the G930FXXS3ERHD
Flashed Combination file COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship
Let Boot up.
Perform a factory reset in Settings.
Flash G930FXXS3ERHD (AP, BL, CP) (got fail message after trying to flash CSC or HOME_CSC)
Worked like a charm. Thank you so much.
Click to expand...
Click to collapse
Can you make a step-by-step howto for G930F?
I've flashed PHN-G930FXXS3ERHD completely, Oreo boots up
Then what?
When i set the COMBINATION file in AP and flash it. It shows a FAIL in Odin and (BOOTLOADER) on the S7 screen.
When i set the COMBINATION file in AP, the G930FXXS3ERHD BL and CP files it also shows a FAIL in Odin and (BOOTLOADER) on the S7 screen.
spittfire said:
SUCCESS on g930f. Thank you so much. By the way... I had the newest fw with september patch installed.
Flashed the G930FXXS3ERHD
Flashed Combination file COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship
Let Boot up.
Perform a factory reset in Settings.
Flash G930FXXS3ERHD (AP, BL, CP) (got fail message after trying to flash CSC or HOME_CSC)
Worked like a charm. Thank you so much.
Click to expand...
Click to collapse
Hi
could you provide link for these files?
FAIL
When I try to flash the combo it just fails after sboot.bin
Any ideas?
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 2011 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any news how to remove frp with g950fxxu4arl1??
Hi, It works with g955w?
no
LXY7Q89J2K said:
When I try to flash the combo it just fails after sboot.bin
Any ideas?
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 2011 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
do you use the right combination? you have to flash thse same ''u'' exmple u2 u3 u4 only
FAIL! (Auth) pit
G955U ATT
giorgosperi said:
i m trying also the same. I installed the combination. The frp is off now but i can't find the right stock rom. The phone has bootloader level 4. From where you got the stock rom? Whatever i tried i got an error binary 4>1.
I have the g955u at&t.
Click to expand...
Click to collapse
i have a bootloader 5 8.0.0/r16nw/g955usqu5crk1 can anyone please help me find combo files i will donate $! Thank you! Galaxy s8 plus
charter3554 said:
I have a regular S8 (950U), most FRP bypass for these devices require the ADB FRP.bat to be run between the combination firmware and the normal firmware are installed, at which part is the FRP actually being removed/bypassed here?
Click to expand...
Click to collapse
Usually, the part where the frp reset go to OFF is when you make the factory reset operation from inside the combination firmware.
Later that, you flash the stock rom and u get frp protection removed.
---------- Post added at 12:17 AM ---------- Previous post was at 12:15 AM ----------
Stryker2u said:
i have a bootloader 5 8.0.0/r16nw/g955usqu5crk1 can anyone please help me find combo files i will donate $! Thank you! Galaxy s8 plus
Click to expand...
Click to collapse
Have u solved ur problem??
If not, post here to help u. I know by experience how tricky gets to have the appropriate combination in advance bootloader firmwares.