Related
Long story short. I'm helping out my colleague who got her phone locked. We ended up factory resetting it, but she's not the most technical, so it seems that every time she's gotten a new phone over the years, she's just created a new gmail-account and forgotten about it.
Then FRP kicked in. Shouldn't be a problem if she just knew her account.. We've found out that she's got at least three accounts, but none of them works. I figure she's got another one, but not one that she could remember. So I have to bypass FRP somehow, otherwise this phone will be an expensive useless brick. :/
It seems it's on build MMB29K.G930FXXU1BPJE.
It's recently updated, so any bypass I've found seems to have been patched. It's usually a good thing, but in this case (she can blame herself, though..) it's a bit sad.
I've tried to downgrade using Odin, but for some reason it fails. I've haven't been able to enable OEM-unlock or enable Developer options.
Any help is appreciated!
She should have some record of which account she used, creating a Google account should ask for a backup email address for recovery, so one of her accounts should have the details of the one she's forgotten
Otherwise unfortunately this could just as easily be "I stole a phone and want to know how to bypass FRP"
Octoplus box and your problem is solved.
*Detection* said:
She should have some record of which account she used, creating a Google account should ask for a backup email address for recovery, so one of her accounts should have the details of the one she's forgotten
Otherwise unfortunately this could just as easily be "I stole a phone and want to know how to bypass FRP"
Click to expand...
Click to collapse
I know. At first she couldn't remember the gmail, and after we checked against her phone no. we found two accounts. Checking against her work e-mail, I found another. Unfortunately it was none of them.
vatvedt said:
I know. At first she couldn't remember the gmail, and after we checked against her phone no. we found two accounts. Checking against her work e-mail, I found another. Unfortunately it was none of them.
Click to expand...
Click to collapse
All I can suggest is look for tutorials on YT for bypassing FRP for whichever security update that phone was on / downgrade with ODIN to one that has a tutorial (Try leaving out the BL part of the flash if it's failing, and use CSC, not HOME_CSC)
You should definitely be able to downgrade a G930F, I just did with mine from 7.0 Nougat back to 6.0.1 using ODIN 3.12.3
You don't need OEM Unlock or Dev Options / USB debugging for flashing stock with ODIN
*Detection* said:
All I can suggest is look for tutorials on YT for bypassing FRP for whichever security update that phone was on / downgrade with ODIN to one that has a tutorial (Try leaving out the BL part of the flash if it's failing, and use CSC, not HOME_CSC)
You should definitely be able to downgrade a G930F, I just did with mine from 7.0 Nougat back to 6.0.1 using ODIN 3.12.3
You don't need OEM Unlock or Dev Options / USB debugging for flashing stock with ODIN
Click to expand...
Click to collapse
Thanks, I'll give it another try later tonight.
Following this video (https://www.youtube.com/watch?v=KRUp09bXnDA&feature=youtu.be) I didn't have to downgrade anything other than the account manager on 6.0.1 through an .apk. That way I could bypass FRP on the October security patch. She was so happy, and I told her to keep it to this one @gmail-account.
So, problem solved! Thanks for the replies!
Nice one :good:
My Fried gave this phone to me (SM-N915G) which is stuck at Powered by Android, and told me to fix it.
He said that when he update to MM from LP without KIES or Odin, the phone suddenly restarted and stuck there getting HOT
He had no experiece to repair it so he asked me to fix it.
So for 3 days lately, i have tried many ways to fix it but wihout any progress, as follow :
1. Flashing Official MM wby using Odin -> still stuck
2. Downgrading Flash Official LP using Odin -> still stuck
3. Installed TWRP, and flasing CFW Micky387_MM_V3.0 for 915F/FY/G (flashing Bootloader and modem as required) -> still stuck with set warranty bit : kernel
4. After Flashing Micky CFW and Failde, i try to flash Emotion Kernel -> still stuck with Kernel is Seandroid Enforcing
5. Redoing Flash Micky CFW with other CSC -> Still Stuck (even i tried with 915F and 915FY as in the aroma installer)
6. Never failed during flash procedure with Odin or TWRP, everything is smooth
7. When stuck, the device is getting Hot slowly but and when left as long as 15 minutes, the HH is getting HOT (TWRP read 72 degree at most)
**Update
8. Tried using Official SmartSwitch sucessfully but the result is still the same -> Still Stuck and getting hot as usual T.T
Last Download Mode status is :
Odin Mode (High Speed)
Product name: SM-N915G
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox warranty void: 0x1 (2)
Quallcomm secureboot : Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
I am now thinking, should i flash another Kernel or PIT or Bootloader? but i still cant decide what to do next to revive this Phone
Please help, any suggestion is greatly appreciated, thank you.
Please give some help, thank you.
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
wingz17 said:
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
Click to expand...
Click to collapse
Have you tried a reinstall using KIES?
The Radius Kid said:
Have you tried a reinstall using KIES?
Click to expand...
Click to collapse
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
wingz17 said:
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
Click to expand...
Click to collapse
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Thank you for the suggestion,
I will try that one out and let you know.
wingz17 said:
Thank you for the suggestion,
I will try that one out and let you know.
Click to expand...
Click to collapse
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
wingz17 said:
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
Click to expand...
Click to collapse
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
The Radius Kid said:
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
Click to expand...
Click to collapse
Thank you for the response,
I was using KIES 2.64 that downloaded from Samsung website to fix the phone as your suggestion (tools->firmware upgrade and initialisation) but still fail to fix it.
Nope, the antivirus still active when KIES download the FW and Flash it into the phone, but it is new to me that antivirus will intercept ongoing dowloaded files, if so i think the antivirus will give some notification or warning about the content of the file that being downloaded and in my case, my antivirus is still cool and no notification whatsoever.
The bad thing is i do not have any cwm backup and since this is my friend phone and not mine, well... we dont have any backup for this phone.
Regarding the battery, i admit that i havent try other battery, since i dont see any connecton between it, in my opinion, the phone works well, the charging animation working, and no sign of weak battery... but i will try to do it if i can get some other battery
I have surfed many forums and websites, but almost 90% can be fixed with simple flashing from odin or just by clearing up cache and data from recovery.
Other that that, wither, no one respond to the problem, or just some discussion without conclusion, really frustrating.
I even go further to read about android booting sequence to identify whats wrong with the boot sequence, but still confused...
But i have some question if you would to answer :
1 . Stuck at Android logo, bootloader or kernel problem?
2 . Is it possible that one of the mainboard chip that have some part in booting process is malfunctioning? But if so, the phone will be dead bricked right?
3. How about the booting process is halted due some hardware failure? ex : some chip (other than chip that have part in booting process) is bad and so the bootloader init is halted
4. The Worst guess, is it possible that the phone is fake? (the serial number behind the baterry is accepted by kies though)
Thank you very much, you are the only one who still response to my problem. :good:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Bordo_Bereli51 said:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Click to expand...
Click to collapse
Thank you for the Response,
First, his phone is N915G (according to the box and the information in the battery compartment)
(Really sorry for the mistake i made at the thread title)
And regarding bootloader, that is also my concern at first, i think maybe i was flasing wrong region and bootloader, and so i search the way to find out the real version of the phone, but after trying many ways described on the net (by imei or serial number) , i still cannot found out the way.
But one instance when i try using KIES, and KIES asked for the version and serial number when device upgrade and initialisation, i entered the exact version and serial number that is found behind the phone in battery compartment. KIES immediately confirms that the version and serial number is valid, (i still wonder though, is KIES check it online at Samsung server or there are some serial number database embedded in the KIES) and continue to run trough the official fw download and installation by KIES but at the end still no success.
Is it possible that the version and serial number is wrong ? if so, how to determine the correct one?
and is it safe to try flasing another bootloader?
Thank you very much
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Bordo_Bereli51 said:
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Click to expand...
Click to collapse
Thanks for the reply!
Although there is no bootloader related to serial number, but if we put the serial number in KIES, it will identify what CSC and region, which can be use as a guide to choose the correct FW or let KIES do the Flashing according to the inputted serial number, and as long as the serial number is correct one, that is my opinion but please CMIIW.
When flashing MM, if i use the MM that has been downloaded, the bootloader and baseband is included in the MM image right? or shouuld i flash it separately?
i have tried your suggestion but with no sucess, i have dowloaded the PIT and the FW, flash it trough odin which was sucess, but still stuck.
I do not tick auto restart at Odin, so i manually restart the phone, but i encounter an event which at 20% installing system update (below the greed droid guy) the progress bar is vanished and replaced with erasing, and after that the phone stuck again at the same spot.
Do you have any idea why?
Thank you very much.
Just thinking, should i erase the NAND in ODIN?
If so, how to restore it?
I think that if i backup the NAND using custom recovery and restore it later, it just bring back the same problem, if the NAND causing all this.
Do anyone have some NAND backup that i could use? or any other suggestion?
Thank you
Can you boot to recovery? if yes, try to wipe data and cache.
If it still not working, try to backup your efs with a custom recovery (ex. TWRP), or better the entire System like data, system, boot, efs, modem and save it to your computer.
After saving the backup, try to flash the firmware with pit file while checked NAND erase all.
When its finished and your device boots up, you can flash back your custom recovery and recover only the efs-partition.
If its not working, then there is maybe problems with your eMMC. But be aware using nand erase all. It is the last riskfully option left after trying several things.
I have a backup of my resurrection rom. If you want it I can upload it.
Hi
Please can someone help. I have just got a Samsung galaxy s7 and was trying to get back some pictures I accidentally deleted using a program called Dr Fone. I followed the instructions and didn't realise I was possibly rooting my phone
The phone is on Status custom and I just want to restore it to how it was originally. I have reset to factory settings but this hasn't corrected it. I am constantly getting a security notice about unauthorised actions
I am not very technical so if anyone could help please give the exact links for where I can download a program to repair this - I have read about a program called Odin but not sure exactly where or how to find this. Does this need to be installed on a computer or phone?
Some more information on the phone is that it's a UK phone. Firmware CSC code is BTU if that helps. It's an S7 SM-G930F
As I said I am not very technical so please can anyone help and if possible provide a step by step guide for what to do that would be amazing
Thank you, David
Odin is a desktop application, it is uses to flash firmware onto your phone. By flashing stock firmware you'd get your device back to stock (excluding KNOX and FRP)
Here's a detailed guide on what Odin is and how to use it https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
You can use that site to get the firmware for your device by region and carrier.
Ok great thanks
Please can you tell.me what excluding KNOX and FRP means?
I will give this a go. Have started the download for step 3. This download seems to be taking a couple of hours. Do you know roughly how long it takes to put everything on the phone once the download if complete?
I may have to leave the actual installation until tomorrow if it takes a long time.
Thanks again for all you help
KNOX is a way for Samsung to check if you have altered the firmware. Flashing custom firmware and/or rooting trips the KNOX counter, and will void warranty and disable some Samsung apps.
FRP is factory reset protection, if prevents someone from being able to steal your phone and get access by factory resetting. Even after a factory reset, FRP is intact and will require the original google account to do the device setup. So make sure you know your credentials, or delink your account before flashing.
Both are part of the firmware that can't be modified or reverted.
Updato can be quite slow to download, sammobile.com is another site but also slow in my experience. The flashing process takes about 15 minutes on your PC, but the phone can sit on the Samsung splash screen for 15 or so minutes as well.
Beanvee7 said:
KNOX is a way for Samsung to check if you have altered the firmware. Flashing custom firmware and/or rooting trips the KNOX counter, and will void warranty and disable some Samsung apps.
FRP is factory reset protection, if prevents someone from being able to steal your phone and get access by factory resetting. Even after a factory reset, FRP is intact and will require the original google account to do the device setup. So make sure you know your credentials, or delink your account before flashing.
Both are part of the firmware that can't be modified or reverted.
Updato can be quite slow to download, sammobile.com is another site but also slow in my experience. The flashing process takes about 15 minutes on your PC, but the phone can sit on the Samsung splash screen for 15 or so minutes as well.
Click to expand...
Click to collapse
Great thanks for all your help so far. I have completed the ODIN update and got the green pass. The phone is trying to boot up and is saying it is encrypted for security and asking for a password. When I put what I thought was the password in it doesnt seem to accept it, is there any way around this?
I read on another message to try the password default_password but this hasnt worked
I have realised that when I flashed the AP download to the phone that there were 4 other files that were downloaded after I unzipped it. Do I put these into ODIN too?
Thanks again
Davifgmmm678 said:
Great thanks for all your help so far. I have completed the ODIN update and got the green pass. The phone is trying to boot up and is saying it is encrypted for security and asking for a password. When I put what I thought was the password in it doesnt seem to accept it, is there any way around this?
I read on another message to try the password default_password but this hasnt worked
I have realised that when I flashed the AP download to the phone that there were 4 other files that were downloaded after I unzipped it. Do I put these into ODIN too?
Thanks again
Click to expand...
Click to collapse
There are 5 files. You have to flash 4 BL, AP, CP, CSC (not home-csc !) Keep in mind if you previously had firmware from January 2018 and up you can only flash equal or newer firmware.
Domino5 said:
There are 5 files. You have to flash 4 BL, AP, CP, CSC (not home-csc !) Keep in mind if you previously had firmware from January 2018 and up you can only flash equal or newer firmware.
Click to expand...
Click to collapse
ah great thanks, I think that was the mistake I made. I have an S7 and originally downloaded version 7.0 am now downloading version 6.0.1 which I think is correct for an S7?
Davifgmmm678 said:
ah great thanks, I think that was the mistake I made. I have an S7 and originally downloaded version 7.0 am now downloading version 6.0.1 which I think is correct for an S7?
Click to expand...
Click to collapse
6.0.1 is old Android Marshmallow better do not downgrade. There is latest 7.0 Nougat for GB BTU https://updato.com/firmware-archive-select-model?record=CE58E60E0EEF11E89F15FA163EE8F90B
Domino5 said:
6.0.1 is old Android Marshmallow better do not downgrade. There is latest 7.0 Nougat for GB BTU https://updato.com/firmware-archive-select-model?record=CE58E60E0EEF11E89F15FA163EE8F90B
Click to expand...
Click to collapse
thanks thats the one I downloaded earlier - will try again with all 4 BL, AP, CP, CSC on ODIN
Thanks so much for continuing to reply - I know I'm useless but im worried I cant use my new phone again!
Hello wise people of XDA,
This is my first post.
I currently use an S6 G920F United Kindom unlocked as my phone and i have been using this phone for a long time. Now its past its warranty I decided to root the phone and see what i can do with it and get rid of the bloatware. Normally i either use KingoRoot or KingRoot but both failed so I searched around on the internet and came across CF Auto Root. After seeing it was successful for others i jumped on the bandwagon. I rooted it and everything was golden until i came across a problem, it would randomly turn off. This was random and infrequent. but not it happens like 5 times a day so i decided to flash a stock rom. For some strange reason Sam mobile wont let me download a stock Rom so after poking around the internet i have download a few stock roms however they always fail in Odin. Now my phone wont even boot as it says "error occured while updating use smart switch emergency recovery feature" so i go onto the Smart switch PC app and then it doesnt recognise. After 2 days of trying i haven't had any luck so I don't know what to so. Every time I try flashing something, when it fails i get some red text on the phone which I don't understand.
Someone please help me as I cant just buy a new phone and this is the only phone i have got. Any help would be very grateful and please don't hesitate to ask any questions.
Edit:
It says on the Download Screen:
Odin Mode
Product Name: SM-G920F
Current Binary: Custom
System Status: Custom
Reactivation Lock: Off
Secure Download: Enabled
Knox Warranty Woid : 1 (0x0500)
RP SWREV: B:6 K:2 S:2
(When it fails it says) SW REV. Check Fail. Device:6 . Binary: 5
Hopefully that helped.
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Bryan48765 said:
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Click to expand...
Click to collapse
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
wasim.1.wt said:
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
Click to expand...
Click to collapse
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Bryan48765 said:
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Click to expand...
Click to collapse
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
wasim.1.wt said:
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
Click to expand...
Click to collapse
U6/S6, "Device:6" is in the odin log so it's already 6 and won't return to 5.
Hello, My Sprint S7 was frp locked and I wanted to sim unlock it. I downloaded odin v3.12. ADB does not see the phone. I flashed with a firmware file. It is now in a boot loop where it says system install. At one time it came up and said it failed and to use Smart Switch emergency repair. I downloaded smart switch and it says unsupported device. I can put the phone in download mode. I have searched and gotten firmware. Everything I try fails in odin. Is it bricked for good or is there a way to fix it? Are there reputable companies that can unbrick it for a small fee? This site is tough to navigate and everytime I search it seems I come up with another place. One had a link to download firmware to flash and fix bricked phone but when I tried to open it my antivirus said it was full of adware. The phone is SM-G930P running 7.0. I was going to flash to a universal one or at&t. I can try odin and screenshot the results if I need to. I am willing to try about anything. Thanks in advance for any help. I have another one (they came as a pair) it is not frp locked but is simlocked. Not blacklistedd but it does show an unpaid balance. I cannot get a hold of the person I bought them from. I know what to check now though. Lesson learned.
KeithSherley said:
Hello, My Sprint S7 was frp locked and I wanted to sim unlock it. I downloaded odin v3.12. ADB does not see the phone. I flashed with a firmware file. It is now in a boot loop where it says system install. At one time it came up and said it failed and to use Smart Switch emergency repair. I downloaded smart switch and it says unsupported device. I can put the phone in download mode. I have searched and gotten firmware. Everything I try fails in odin. Is it bricked for good or is there a way to fix it? Are there reputable companies that can unbrick it for a small fee? This site is tough to navigate and everytime I search it seems I come up with another place. One had a link to download firmware to flash and fix bricked phone but when I tried to open it my antivirus said it was full of adware. The phone is SM-G930P running 7.0. I was going to flash to a universal one or at&t. I can try odin and screenshot the results if I need to. I am willing to try about anything. Thanks in advance for any help. I have another one (they came as a pair) it is not frp locked but is simlocked. Not blacklistedd but it does show an unpaid balance. I cannot get a hold of the person I bought them from. I know what to check now though. Lesson learned.
Click to expand...
Click to collapse
If its stopping on sboot.bin install samfirm and download latest firmware then flash again
kpwnApps said:
If its stopping on sboot.bin install samfirm and download latest firmware then flash again
Click to expand...
Click to collapse
Hey. Thanks for responding. I downloaded samfirm. It says device not supported. I have been searching around to make sure I try to flash the correct software. At this point I am not as concerned about sim unlocking as just getting it to boot up again. Is it possible I tried to go further back and an older bootloader bricked it? Thanks
KeithSherley said:
Hey. Thanks for responding. I downloaded samfirm. It says device not supported. I have been searching around to make sure I try to flash the correct software. At this point I am not as concerned about sim unlocking as just getting it to boot up again. Is it possible I tried to go further back and an older bootloader bricked it? Thanks
Click to expand...
Click to collapse
Install firmware from updato.com and try again
kpwnApps said:
Install firmware from updato.com and try again
Click to expand...
Click to collapse
Hey. I have been trying to download from updato. I guess the free download is not very good. It says 2 days and keeps disconnecting. Fianlly aborted when about halfway through. I have found another site to give a shot. Maybe I just did not have the correct file the first time. Thanks for checking in. I appreciate any input or ideas.
Btw, the other s7 I have is working. It is sim locked from Sprint. It is not listed as stolen or lost. To flash to Sprint would I just use the latest download? Thanks
KeithSherley said:
Hey. I have been trying to download from updato. I guess the free download is not very good. It says 2 days and keeps disconnecting. Fianlly aborted when about halfway through. I have found another site to give a shot. Maybe I just did not have the correct file the first time. Thanks for checking in. I appreciate any input or ideas.
Btw, the other s7 I have is working. It is sim locked from Sprint. It is not listed as stolen or lost. To flash to Sprint would I just use the latest download? Thanks
Click to expand...
Click to collapse
The saga continues. I did download stock firmware. It still failed when trying to flash with Odin. I can get it to load the recovery menu and the download menu now. Before the recovery menu would not load. on the log the last two things say
xbl.elf
FAIL! (Auth)
I tried Kies and Switch, neither support the device. I am currently downloading a stock rom from SamFirm, once I figured out the exact way to type on model and region code. I will try that in a little while and search for odin auth fials for the s7.
Thanks again for the help. I have learned quite a bit and it is fascinating. Any thoughts on the fail would be greatly appreciated. I hope after I get the stock rom back I can find the correct process to unlock it.