Related
So... Like a fool, having successfully rooted my phone a couple of days ago on the I9505XXUBMGA firmware, I saw this appear in Kies when I plugged my phone into Kies this morning. I thought (yeah you know where this is heading) "Oooh shiny new update, must download".
So although I had root I didn't think it would be a problem I'd just re-root afterwards. And hey if it didn't work I'd just downgrade the firmware and repeat the original process.
Trouble is I now have a message saying "SuperSU has been forced to stop for an unauthorized attempt to access system in your device. It may be solved by the policy update service. It may be safe to delete an application obtained from an unauthorized route. Check now?". I then have the option to not show for 30 days and then Cancel, Update or OK. Trouble is now when I attempt to revert the firmware back to an earlier version.
So now when I go into Download mode I see:
Code:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
If I try and Odin a new (stock) firmware on I get a write error from Odin and on the I9505 I get the following below the above text:
Code:
START [224, 1440]
SW REV. CHECK FAIL : fused: 2, Binary : 1
Odin shows:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
So, kind of stuck now. If the phone tries to restart I get the message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". For a while I couldn't get the phone to boot, and Kies doesn't see the phone, but oddly re-partitioning via Odin using the PIT file means the phone will boot. From there I still get the SuperSU message but can switch it off and get into recovery mode, does that mean there is a chance I can re-flash things via adb / fastboot?
Yep I'm an idiot for trying and being the Guinea pig, but as I don't know how to proceed if anyone wants to help out and see if we can get it back and un "Knoxed" (which I think might be the issue) I'm more than happy to help.
Limitations currently are that I am running Windows XP 32-bit via Parallels virtual machine. The unbricking steps seem to indicate needing a 64-bit machine? I could probably do that but would have to get hold of and install 64-bit Windows 7 as a VM.
In terms of Android hacking I'm a noob, but can follow instructions, and am comfortable with a Unix/Linux command line if that's any help to anyone who wants to take pity on me...
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Boolean = True said:
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Click to expand...
Click to collapse
So, assuming you are stuck at the "there was a problem stage" you need to turn off the phone and get it into download mode (hold volume down, home + power - I guess you know this but just in case). I found this a bit fiddly I think because the phone is auto-rebooting, so try pressing power off and just holding the volume down and home buttons.
Then in Odin I used the PIT file listed in this thread. In the 'Re-partition' section and the boxes for Auto Reboot, Re-Partition, and F. Reset Time were all checked. I left all the other boxes empty (including the Files section). Click start and then after a while the phone reboots. It take a minute or two but if you see the Samsung logo it should boot.
Hope that helps... now to find a way around the MH1 firmware... oh and glad it wasn't just me that was daft enough to go and try it.
No, not just you mate. I had a hell of a time last night. Flash pre-rooted MGG firmware via odin, which bootlooped. I couldn't flash MGA firmware again.
So I flashed Stock MGG which booted but the security measures implemented have stopped me from changing my font using ifont.
I have now flashed MH8 over the top and it's working better than MGG, but still can't use some apps due to the new security measures.
I was able to flash Omega V10 from TWRP and it booted fine, but no wifi and I'm unable to flash LTE modem to correct it.
Looks like I'm stuck unrooted on MH8 for the time being.
There are some instructions on this thread on how to root this firmware, they're a bit lengthy tho.
http://forum.xda-developers.com/showthread.php?p=45283966
Sent from my GT-I9505 using Tapatalk 4
Bugger.
To add insult to injury it appears that WiFi is now no longer working either.
I'll look into the post you linked too, but I can't see how it will update that all, i.e. it says to use Odin which currently fails for me.
Odin doesn't fail for me when flashing kernels or recoveries, just when I try and flash full firmware earlier than MGG which includes the bootloader.
Flash full MH8 firmware from samfirmware, I have no issues except for the security problems.
Sent from my GT-I9505 using Tapatalk 4
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
jd1639 said:
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
Click to expand...
Click to collapse
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
shrubz said:
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I hadn't realised that flashing the same or newer would work (it does). But WiFi is still borked... any ideas?
Tiny amount of progress, more out of hope I tried to flash a pre-rooted ROM - obviously this didn't work, but when I reflashed MH8 again I noticed the device made the start up sound (which it hadn't been) and WiFi is now working.
As a bonus if I go into Device Status it is now showing as Official, which is nice!
I think I'll leave it there for now, but will keep an eye out for progress, hopefully the bootloader will be "fixed" in due course.
Chainfire is working on a fix for CF-Root. So hopefully all will be good soon.
Sent from my GT-I9505 using Tapatalk 4
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!
Hi,
I managed to be brick free since I started reading XDA Developers & modifying my devices starting with my XDA Mini in 2008. Now 6 devices later I finally managed to - hopefully just soft - brick my Note 3 (hlte)
I bet if I search long enough I could try to recover it on my own, and i did so the lasst 15 years, but I am a bit scared now, I really fear to loose the last thread this phone is hanging on, so please hear me out and maybe its an easy problem for the more expiereinced users out there.
Situation before the update:
* rooted
* cwm recovery - latest version
* cm11 latest snapshot
* Encryption enabled
The update:
- Used adb sideload method to load cm12.1 latest nightly
- Phone booted fine, just was completely misconfigured (Xposed not working, root apps lost root access, etc.)
- Wanted to go to recovery, but recovery stopped working. Phone just showed shortly it goes to recovery, then black screen
- So I factory resetted the phone via normal CM settings.
- Everything was fine, I started to install apps and was happy.
- Phone is currenlty NOT encrypted anymore
- I totally forgot to fix the not working recovery mode *DOUH*
- Then I changed the DPI settings in build.prop to 320 as it was under cm11
- Phone never rebooted.
The situation now:
- Phone does not boot normally, shows black screen right after boot mode details in top left corner. No boot logo and such
- Phone can't enter recovery, same as with normal boot
- ADB can not see the device in either normal boot/recovery/download mode
- Download mode seems to be still working *HOPE*
So what to do now?
Can I somehow just fix the build.props?
Can I flash a new recovery using ODIN, and then format/wipe/reinstall?
Can I simply reflash CM12.1 using ODIN?
Or do I have to, as some howto suggested, flash a stock samsung rom? And which one for that matter?
Hope someone can help me,
CySlider
Update: Solved by pushing the right stock rom to the device using ODIN.
Interesting part I learned: You can flash multiple times with ODIN without rebooting the device if flashing fails. You just have to unplug and replug the cable (quickly if Battery is nearly dead). Messages on Screen might get messy with errors that the loading bar got wrong values, but it works.
Flash stock Samsung rom via Odin .
Can I somehow just fix the build.props? YES if you can see it on your phone.
JJEgan said:
Flash stock Samsung rom via Odin .
Can I somehow just fix the build.props? YES if you can see it on your phone.
Click to expand...
Click to collapse
Ok, which one, Lolipop? or Kitkat? Last stock that was installed before going to Cyanogenmod was Kitkat or even older.
Also will I loose root access this way?
Cy_the_Slider said:
Ok, which one, Lolipop? or Kitkat? Last stock that was installed before going to Cyanogenmod was Kitkat or even older.
Also will I loose root access this way?
Click to expand...
Click to collapse
If you just want a cm rom just flash a kit kat official rom.
Anyway try to go into download mode. When it asks to cancel or continue choose cancel. I saw several members mentioned the phone managed to boot that way.
And off course no root.
Sent from my SM-N920C
Rosli59564 said:
If you just want a cm rom just flash a kit kat official rom.
Anyway try to go into download mode. When it asks to cancel or continue choose cancel. I saw several members mentioned the phone managed to boot that way.
And off course no root.
Sent from my SM-N920C
Click to expand...
Click to collapse
Ok, thank you. About the tip with Cancel. unfortunately it did not help. I geuss the problem is an invalid DPI setting in the build.props and it will not changed by going to download mode first :/
Ok I will try to locate a stock rom with Kitkat.
Thank you.
No success it seams:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/012> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:1/012> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:1/012> File analysis..
<ID:0/007> SetupConnection..
<ID:1/012> SetupConnection..
<ID:1/012> Initialzation..
<ID:1/012> Get PIT for mapping..
<ID:1/012> Firmware update start..
<ID:1/012> SingleDownload.
<ID:1/012> sbl1.mbn
<ID:1/012> NAND Write Start!!
<ID:1/012> aboot.mbn
<ID:1/012> rpm.mbn
<ID:1/012> tz.mbn
<ID:1/012> sdi.mbn
<ID:1/012> NON-HLOS.bin
<ID:1/012> boot.img
<ID:1/012> recovery.img
<ID:1/012> system.img.ext4
<ID:0/007> Can't open the serial(COM) port.
<ID:1/012> modem.bin
<ID:1/012> cache.img.ext4
<ID:1/012> hidden.img.ext4
<ID:1/012> FAIL! (Size)
<ID:1/012>
<ID:1/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 2)
I used: N9005XXUGNG1_N9005DBTGNG1_N9005XXUGNG1_HOME.tar.md5 and set it to AP setting in ODIN 3.10.7
CAN I leave Download mode to test, if something changed? Or should I better stay in download mode to try again?
Ok, after realizing that I can not flash again without reentering the doanload mode anyway, I restarted.
It showed a new download mode with the message:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I searched and found that I should use the right PIT file. I found a combination that seemed to match my device here: (german)
http://www.pocketpc.ch/samsung-gala...1800-anleitung-flashen-dbt-fw-eu-geraete.html
I did hold my breath, and...: Failed again:
<ID:0/012> Added!!
<ID:0/012> Removed!!
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOE9_N9005DBTGBOF1_N9005XXUGBOD3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> boot.img
<ID:0/012> cache.img.ext4
<ID:0/012> hidden.img.ext4
<ID:0/012> FAIL! (Size)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So, did I finally manage to hard brick? ((
I'm still in this special mode scraed frozen about powering off as I saw messages saying this is the last shot I had. COME ON!!
What I don't get is. After updating to CM12.1 didn't I got Lolipop bootloader with it? Maybe trying to put on 4.4.2 was wrong after all, b/c of downgrade?
Rop left in download mode is this info:
Product Name: SM-N9005
Current Binary: Custom
System Status: Custom
Reactivation Lock(KK): Off
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enabled
UDC START
anyone?
Cy_the_Slider said:
What I don't get is. After updating to CM12.1 didn't I got Lolipop bootloader with it? Maybe trying to put on 4.4.2 was wrong after all, b/c of downgrade?
Rop left in download mode is this info:
Product Name: SM-N9005
Current Binary: Custom
System Status: Custom
Reactivation Lock(KK): Off
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enabled
UDC START
anyone?
Click to expand...
Click to collapse
Try non DBT firmware. So you can still enter download mod?.
Sent from my SM-N920C
Rosli59564 said:
Try non DBT firmware. So you can still enter download mod?.
Click to expand...
Click to collapse
I don't know. Luckily, if I unplug and replug the USB Cable quickly, I seem to be able to flash again without the need to find out, if it will boot again.
I am currently downloading the UK version as I think to remember it was an english phone. (Got it as a present)
I just don't understand why the PIT did not fix this issue. it should have resizeed the partition anyway...
Damn I feel stressed...
Cy_the_Slider said:
I don't know. Luckily, if I unplug and replug the USB Cable quickly, I seem to be able to flash again without the need to find out, if it will boot again.
I am currently downloading the UK version as I think to remember it was an english phone. (Got it as a present)
I just don't understand why the PIT did not fix this issue. it should have resizeed the partition anyway...
Damn I feel stressed...
Click to expand...
Click to collapse
Can't you just flash a twrp and flash a CM from there?
Sent from my SM-N920C
If you tell me how to flash a twrp via odin. Sure I would try. Is this possible?
The UK Rom download finished. Lets see if htis works.
Ok, Flashing the UK BTU rom worked in the sense that ODIN did not show any errors.
When I try to start it, it starts until it asks for a password?!? then it crashes.
I can enter recovery, but when I factory reset, it does not start at all and recovery is also gone again. Only Downloadmode is luckily still available.
Have I messed up the factory reset feature by applying the PIT file for the german rom maybe?
Update: Seems I made it. The last problem now was the Batery being completely dead as it seems to not be loading while in this broken state. And the USB PC connection was not delivering enough power to survive the phone fully booting. Now its on the loginscreen and charging.
Hopefully I can put a Solved behind this topic soon. Thanks for all input!
Hello everyone,
I have a customer that managed to forget his account. He came to me to bypass the frp. He said he has the latest update of Nougat so I knew the only bypass I could posssibly use was probably the bluetooth headset one (if lucky). So I tried to revert the phone to an earlier Nougat version so I can use an easy bypass (hence I don't have any bluetooth headset). I've used Odin to flash one of the earliest Marshmallow versions for G935F (a vodafone, Uk one as the user said he bought the phone from there). Problem is Odin failed to flash the BL file and I've read somewhere on this forum a user said just uncheck that and I'll be fine. Well I've done that and the phone remained soft bricked (probably because the BL the phone still had was made for Nougat). Then I've downloaded a Nougat rom for the phone and the same problem (SW_RW verification for the BL file) so I bypassed the BL again and I've flashed the other files via Odin. All good, now the phone boots, installs the apps but it doesn't see the Sim anymore (I know that because the customer had a sim pin lock, wich the phone doesn't ask for anymore). Well, also the phone of course is still FRP locked but now I have two problems: It doesn't detect the Sim card anymore and it's still FRP locked. I am planning to flash the latest Oreo Rom as I am thinking that the bootloader will accept it and this way the phone will detect the sim again and at least I will be able to return it to my cutsomer in the same state as it was before.. but I am afraid I will not be able to bypass the FRP at all afterwards if I flash to the latest security patch. What should I do, is there any possiblity to fix both of my problems ? If yes can anyone here help me ?
EDIT:
First of all, the title is wrong - the phone ain't soft bricked anymore., it just doesn't detect the sim anymore and it's frp locked. And regarding to what I've wrote, I've also tried to flash like 3 Nougat versions for the G935F and same result everytime: BL check failed. Two of the roms were taken from threads from here, one of them had "untouched in its name" so I thought the bootloader will accept it but it didn't. Maybe the client thought he had Nougat on the phone when he had Oreo and maybe that's why the Bootloader won't accept to be flashed with any bootloader from Nougat roms. I must specify at least, I didn't try flashing the latest Nougat version yet. I can access download mode and recovery mode and I can turn on the phone but it won't let me pass the frp of course. I am waiting for some answers in here before trying to flash latest Nougat version and latest Oreo versionl.
Any help would be greatly apreciated, thank you very much!
Edit 2: Managed to flash the latest Nougat patch with succes (the Bootloader passed the verification, the Rom I flashed it's called: "G935FXXS2DRDI_Germany.zip".
Now the problem with the sim is solved, but I still have the FRP lock activated. If anyone knows how can I bypass it please help! Maybe I can dowgrade the phone somehow or anything else.
Edit 3: Planning to use a combination method shown in this video: youtube.com/watch?v=5v1oN4WFuqA
Edit 4: The combination ROM used in that tutorial won't get past the verification in Odin, wich results in a SW_RW flash fail. Trying a newer one from May, 2018 (COMBINATION_FA60_G935FXXU2ARA1).
Edit 5: This one failed as well..
=====================================================
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<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> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
===================================
EDIT 6: The second combination ROM actually worked! I forgot to switch to my other folder in odin so I thought it's not working. Now I am in the rom, on developer settings but I only see the usb debugging option. I can't see anything about OEM unlock. Could I directly flash the 6.0.1 Marshmallow now ? Hmm I will try exacly that!
Edit 7: Looks like the verification in Odin still fails if I try flashing the 6.0.1. I'm out of ideas.
EDIT 8: FInal Edit - I managed to unlock it by making an update and a downgrade from a specific x version to a specific y version. But.. I am afraid it is forbidden to give the exact details here so I guess that's it. SOLVED!
We don't allow discussion of FRP bypassing here because it could be used by thieves. The main purpose of FRP locks is to prevent that.
BrainwashedUser said:
Hello everyone,
I have a customer that managed to forget his account. He came to me to bypass the frp. He said he has the latest update of Nougat so I knew the only bypass I could posssibly use was probably the bluetooth headset one (if lucky). So I tried to revert the phone to an earlier Nougat version so I can use an easy bypass (hence I don't have any bluetooth headset). I've used Odin to flash one of the earliest Marshmallow versions for G935F (a vodafone, Uk one as the user said he bought the phone from there). Problem is Odin failed to flash the BL file and I've read somewhere on this forum a user said just uncheck that and I'll be fine. Well I've done that and the phone remained soft bricked (probably because the BL the phone still had was made for Nougat). Then I've downloaded a Nougat rom for the phone and the same problem (SW_RW verification for the BL file) so I bypassed the BL again and I've flashed the other files via Odin. All good, now the phone boots, installs the apps but it doesn't see the Sim anymore (I know that because the customer had a sim pin lock, wich the phone doesn't ask for anymore). Well, also the phone of course is still FRP locked but now I have two problems: It doesn't detect the Sim card anymore and it's still FRP locked. I am planning to flash the latest Oreo Rom as I am thinking that the bootloader will accept it and this way the phone will detect the sim again and at least I will be able to return it to my cutsomer in the same state as it was before.. but I am afraid I will not be able to bypass the FRP at all afterwards if I flash to the latest security patch. What should I do, is there any possiblity to fix both of my problems ? If yes can anyone here help me ?
EDIT:
First of all, the title is wrong - the phone ain't soft bricked anymore., it just doesn't detect the sim anymore and it's frp locked. And regarding to what I've wrote, I've also tried to flash like 3 Nougat versions for the G935F and same result everytime: BL check failed. Two of the roms were taken from threads from here, one of them had "untouched in its name" so I thought the bootloader will accept it but it didn't. Maybe the client thought he had Nougat on the phone when he had Oreo and maybe that's why the Bootloader won't accept to be flashed with any bootloader from Nougat roms. I must specify at least, I didn't try flashing the latest Nougat version yet. I can access download mode and recovery mode and I can turn on the phone but it won't let me pass the frp of course. I am waiting for some answers in here before trying to flash latest Nougat version and latest Oreo versionl.
Any help would be greatly apreciated, thank you very much!
Edit 2: Managed to flash the latest Nougat patch with succes (the Bootloader passed the verification, the Rom I flashed it's called: "G935FXXS2DRDI_Germany.zip".
Now the problem with the sim is solved, but I still have the FRP lock activated. If anyone knows how can I bypass it please help! Maybe I can dowgrade the phone somehow or anything else.
Edit 3: Planning to use a combination method shown in this video: youtube.com/watch?v=5v1oN4WFuqA
Edit 4: The combination ROM used in that tutorial won't get past the verification in Odin, wich results in a SW_RW flash fail. Trying a newer one from May, 2018 (COMBINATION_FA60_G935FXXU2ARA1).
Edit 5: This one failed as well..
=====================================================
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<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> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
===================================
EDIT 6: The second combination ROM actually worked! I forgot to switch to my other folder in odin so I thought it's not working. Now I am in the rom, on developer settings but I only see the usb debugging option. I can't see anything about OEM unlock. Could I directly flash the 6.0.1 Marshmallow now ? Hmm I will try exacly that!
Edit 7: Looks like the verification in Odin still fails if I try flashing the 6.0.1. I'm out of ideas.
Click to expand...
Click to collapse
Sent from my GT-I9300 using Tapatalk
(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.