I inherited a Galaxy S7 from my brother after he recently passed away. He was with T-Mobile, so it's a G930T (I have the original box, too, which has come in handy). I brought it back home with me... to France. I figured I'd have it unlocked and replace my old smartphone with this newer one.
Since I didn't know what his pin was, I did a factory reset... and found myself stuck in FRP!
At that point I called T-Mobile and was able to have myself added as an authorized user on my brother's account. They gave me the pin (too late! gah!) and unlocked the phone on their end, as it had been fully paid for. But as far as the FRP thing they were unable to help.
After a lot of googling, I found a bunch of how-to videos explaining how to bypass FRP, I thought I was in luck... except none of them worked for me. Then I came across a comment stating that flashing the device might do the trick. So I decided to try that... but now I'm locked in a boot loop (on the Samsung Galaxy S7 screen that keeps flashing on and off).
Here's what I did, step by step:
1) I installed Odin 3.13.1 from samsungodin.com
2) I downloaded & unpacked a stock ROM from sammobile.com, more specifically this one:
G930TUVS8CRJ1 - GALAXY S7 SM-G930T TMB USA (T-MOBILE)
3) I connected the phone to the laptop
4) I ran Odin and selected (with the AP button) the AP_GS30T* file & hit "start"
Odin said PASS! and I thought all was good... except it wasn't.
So I went googling some more and found a great page... which I am not allowed to link to yet, apparently, but it's on thedroidguy's website.
Only problem is that I can NOT get into the Recovery Menu. When I try the procedure (Home+Volume Up+Power) all I get is "recovery booting" in a bright blue font and THAT starts flashing on and off instead of the Galaxy S7 screen. If I redo the same button sequence, it just switches back to the other screen.
The ONLY other screen I can get to (unless there's another trick I haven't heard of yet) is the blue 'Warning' screen from which you can install ROM's (Home+Volume Down+Power).
So I tried to reinstall that same ROM two other times. First because I wasn't sure if I'd ran Odin as an administrator the first time around, figured that might be the issue, but that didn't change anything. Then I gave it another shot, this time using the phone's original USB cable (I had initially used mine), hoping that would make a difference... but of course, it did not.
So... is there anything I can do at this stage? Did I maybe go for the wrong ROM? Is there another one I can try?
I just hope it's not permanently bricked :-o
So I managed to unbrick my device, yay me! It took me some time to figure it out, but the solution was quite simple. Up until that point I had only been flashing the AP file alone. What fixed my problem was to also flash the bootloader (BL) file. This got me out of that boot loop.
I still haven't managed to bypass that annoying FRP lock, though. Every technique I've tried has failed.
On the plus side, I'm becoming an expert at flashing :-o
I just came across a method that, I think, could work: flash the factory combination file, enable usb debugging, then flash the regular firmware (with all files except CP).
My problem is that I can only find ONE combination file for the G930T but it doesn't match ANY of the firmwares available on sammobile... is this a problem?
The filename is similar to the v6 firmwares, only the last 4 characters don't match.
The other issue is that none of the v6 firmwares will flash on my device (they all fail pretty quickly while going through the AP file)... will using the combination file fix this?
Any thoughts or suggestions would be greatly appreciated.
Related
Hi all..or anyone out there
I have had the seemingly strange bootloop problem on my stock note N8010...which stuck on the dreaded "samsung galaxy note 10.1" and only has odin feature working. (and no factory reset options because I think the poor old tab is crammed to bursting with apps, files and cache and so had a meltdown) poor thing.
so anyway I check these sites of techie wonder and wisdom and followed every logical option..starting with the simple ones
first ran power down and tried to boot up (x3) with no joy, then take apart the tablet to disconnect / reconnect the battery and boot up (x3) still no change.
So went and got the firmware from samwares (both jelly bean and kitkat) to then flash through odin....tried and failed first because of dodgy cable, but the then got a new one...and joy of joys (at first) odin recognised my tab and the firmware flashed across with pass..but then auto rebooted straight back into the dreaded samsung 10.1 again....so tried different versions of odins... and tried other global n8010 firmware...but funnily and frustratingly then all fully download and pass in odin (and the andoid logo and green download status bar on the tablet seems to shown that downloading is and has fully taken place.... but the darn thing still wont boot up past the samsung galaxy note 10.1
Sadly coming to the ends of my tether (of so many nearly there false hopes, high and lows) and very little cash to send it to the Sami tech bods doesnt help matter....I then read and tried the (supposed) last resort pit file/firmware option...first with kitkat (as apparently that worked for someone somewhere) and then tried with jelly bean..again each time itAlways passes in odin.... but auto reboots into the dreaded bootloop logo .... to haunt and torment me.. Aaaaagh!!!!.....I would not mind if it said action failed (for once) like some others seem to experiencet...but it always passes in ODIN????
So.....have come to the semi ignorant conclusion it is either the bootloader section of the tablet or the original software that is messed up or some internal hardware component has a fault.
but was wondering if there is anthing left to try...or would it potentially be possible or worth trying to root a tablet in this condition?
As although I have not ventured into the wild worlds of rooting.....I am now pretty confident of messing with this tablets mind..and have little to lose...so any further ideas and help would be great.
Exact same here. Never flashed, totally stock N8010. My wife hadn't used it for a couple of weeks. So she grabs it again and it was off. booted to nothing but the boot logo. Nothing worked except Download mode.
Flashing stock roms has Odin reporting success, but it still won't boot up. Trying re-Partition does give a fail as soon as I press start.
And we aren't alone. It appears there are quite a few of these cases. I have no idea how to solve this.
I have done a bit of rom flashing on my old galaxy S (the first one) and bootloaders and such usually were included in a ROM. Rooting was done with Recovery or an app and I think it was also possible with adb, IIRC (it's been a while).
It's my wife's Note and she's starting to scope out mini iPads...
Same problem with GT-N8010
I am also having the same problem.
I tried to upload a new ROM via ODIN. All was successful from the ODIN app (PASSED). but stuck on the boot screen. Power and Vol up does not work (it appears to but then crashes out to the boot screen again) so no way to do a hard factory reset.
Volume down/power does work and allows you to get to Odin mode. but as above, uploading a new ROM does not seem to work.
This is an un-rooted GT-N8010 with the stock ROM when I purchased it back in 2013 I believe.
Come on guys, give us some ideas.
Thanks
Gene
Sounds like wrong model firmware flashed as that's the usual bootloop problem .
Try Odin firmware flash wait to passed then remove battery for a short while and replace and try recovery mode .
In my case there is no incompatible firmware issue... The tablet just stopped working one morning and that was that.
Can't comment on the other posters though.
Sent from my GT-I9305 using XDA Free mobile app
Gene_uk said:
In my case there is no incompatible firmware issue... The tablet just stopped working one morning and that was that.
Can't comment on the other posters though.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
My wife's the same. Never done anything to it. No idea how to remove the battery. I let the battery run down once, then recharged it, made no difference.
That was before trying to flash the new firmware. My Note says N8010 on the back, it says so in the download mode. I got a firmware from SamMobile for the N8010. Don't know what else I can do.
Widdly said:
My wife's the same. Never done anything to it. No idea how to remove the battery. I let the battery run down once, then recharged it, made no difference.
That was before trying to flash the new firmware. My Note says N8010 on the back, it says so in the download mode. I got a firmware from SamMobile for the N8010. Don't know what else I can do.
Click to expand...
Click to collapse
Having same problem here ... tried flashing different firmwares along with PIT file - still no luck ..
stuck on samsung galaxy note screen .. cannot get recovery mode
Any help guys?
hi guys, i did the qualcomm root technique via http s:/ /ww w.yout ube.co m/watch?v=GNInTlCpv8E (remove the spaces) on my Galaxy S7 (NOT edge) and it's been nothing but a headache since doing it. I couldn't get Xposed Framework installed( probably my own fault from inexperience ) so therefore I could do nothing fun.
So at some point I got stuck in a boot loop, wiped all the data and it started back but I lost all the SU stuff, but it ran fine so I didn't bother doing anything more to the phone, left as is. only difference is the the unlock symbol still appeared when turning the phone on.
Anyway today, a week or so later all my apps one by one crash, I restart the phone, lo and behold another boot loop. Soooo I wiped the phone (lost a couple new guitar riffs damn it) and now I just want to restore to the factory rom. I *thought* I found the correct one, but ODIN keeps saying FAILED after I put in the ap/bl/cp/csc
for one I have a HOME_CSC and a CSC but odin only lets u use one CSC....ODIN implies I should use Home_CSC but neither one is working, everything I do ends in FAILED(similar to my life )
Can anybody link me to the correct stock rom for a SMG930T and give me some proper directions on what I should be doing?
Yes it's very clear that i'm in over my head, a newb, please take it easy on me!!!
http://www.sammobile.com/firmwares/database/SM-G930T/
Or you try Smart Switch with Emergency Mode
I bought a G930F from Amazon for use with my T-Mobile service, rooted it, and flashed a custom ROM (not sure exactly which one, but I have a folder named "CF-Auto-Root-herolte-heroltexx-smg930f") to it almost a year ago and everything was working just fine until this.
I was trying to get FRep (android macro/automation) working. It uses a setup tool on a PC that requires a connection and USB debugging enabled on the phone. When trying to run the setup I was getting errors about the socket/address already being in use so I'm not sure if it ever managed to do anything, but I saw a suggestion of rebooting my phone to fix the errors. In doing that I held down the power button, for my ROM's power options, chose reboot, went to the next reboot screen (maybe TWRP?) and chose the default reboot there.
When my phone tried to boot I got the Samsung Galaxy S7 logo with small red text of "Custom binary blocked by FRP lock". I'm still not entire sure what causes this (seems like a mismatch between having a custom ROM and some other setting). I'm wondering if the FRep setup tool somehow switched from OEM firmware protection flag. I booted into the download mode and tried to just reflash my old ROM, but even in the download mode I'm seeing "Custom binary (RECOVERY) blocked by FRP lock" with "NAND Write Start!!" then "Complete(Write) operation failed." in Odin3 logs.
I'm giving as much detail as I can because I'm not exactly sure which pieces are which. I've actually tried flashing the "CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5" and "twrp-3.0.2-2-herolte.img.tar" files in the "AP" slot in Odin3 as I don't remember which file is for what, but both give errors on writing. I'm wondering if I shouldn't do custom ROMs in the future as I don't follow the scene long enough to learn all that I should in order to not mess things up.
Any help will be appreciated!
edit: I'm downloading a stock S7 ROM from sammobile, but I don't think Odin3 will be able to flash it anyways. Is there any way to use the PIT settings or something else to change the OEM protection piece?
edit2: After downloading a stock ROM I was able to flash it all with Odin3. I think only part of it would have been necessary (maybe just needed a new bootloader, not entirely sure about AP/CP/CSC fields in Odin3.) Got the phone working again, but now I've gotta remove some popup inducing malware that I think I got when downloading a stock ROM the link in the instructions here: https://forum.xda-developers.com/galaxy-s7/help/frp-boot-fix-sm-g930f-t3350149
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
philipp-h said:
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
Click to expand...
Click to collapse
Philip, it helps if you let us know what country your in.
Anyway the solution to your problem is pretty straight forward, you just need to flash the latest firmware for your region with Odin. No need to mess about with TWRP at this point.
Official firmware will contain a copy of the stock kernal which will also be installed when you flash with Odin 99% of the time. If for some reason the kernal is not flashed (it happens) and you continue to get the reboot issue then you will need to flash the kernal seperately first with Odin then the firmware afterwards.
The issue with the FRP lock will remain after this but should allow you to unlock with google email and password.
So we're talking, downlaod mode, flash official fimrware and go from there.
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
philipp-h said:
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
Click to expand...
Click to collapse
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
cooltt said:
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
Click to expand...
Click to collapse
Hi cooltt and thanks for your help!
Unfortunately the BTU-ROM did not solve the freeze-reboot-problem but led to another: After flashing the phone gets stuck with a blue screen "Erasing". After several hours I force rebooted and now it is showing a similar screen with "Error!" and a percentage which is increasing to a random number from 0% to 12% on each boot. On first boot it shows the boot screen ("Galaxy S7"), then "Installing system update" shortly and then "Erasing". After force-reboot it shows boot screen, "Erasing" then "Installing system update", both for a very short time (sometimes misses "Installing...")
As suggested I used SamFirm to download the newest BTU-ROM (SM-G930F_1_20191218140415_dgobhw6g3v_fac; G930FXXS7ESL5/G930FOXA7ESL5/G930FXXS7ESL5/G930FXXS7ESL5). I just ticked F. Reset Time and Reboot. Re-Partitioning did not change anything. Using Odin v3.13.1 does not make a difference. The other ROMs, like SM-G930F_1_20191226131628_8ds2p6kf0v (G930FXXS7ESL9/G930FDBT7ESL9/G930FXXS7ESLA/G930FXXS7ESL9) which I downloaded with Frija (should do the same: download enc4-files from Samsung and decrypt) make the phone going to the initial setup fine, but with the reboot-problem. Tried also with Odin 3B patched.
At this point I was going to write, that I could not access the recovery mode with the BTU-ROM but just now I started it unintentionally when looking for the sequence of screens showed on boot. So I used my chance, made a full wipe and screenshot. After this the phone booted until the glowing "Samsung"-logo appeared. Then rebooted and went to initial setup (after "Androi"Installing applications") in German. The freeze-reboot-issue appears as with all the other ROMs.
The phone is certainly an original SM-930F as it was bought directly from a big, trustworthy dealer and then just used by my aunt. The only one touching it when problems appeared was me. There is SM-G930F printed on the backside and showed in download mode.
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
philipp-h said:
Hi cooltt and thanks for your help!
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
Click to expand...
Click to collapse
Hi Phill
The only options checked in Odin should be F-Reset and Auto reboot. Don't check any others.
The blue screen erasing and updating is normal after a flash with Odin, the phone will restart a couple of times, just leave it do it's thing for a bout 10 minutes or so. If it's any longer than that as you have mentioned then it's stuck as you've said.
So we're going to start from the begining again but do something slightly different.
1. Place the phone into download mode
2. Run Odin but uncheck "Auto Reboot" so the only option checked is F-Reset Time.
3. Use whatever firmware you want, BTU or DBT the latest version. Make sure files are in the correct boxes.
4. Connect phone and flash with Odin, wait until Odin says "succeed 1" and "dissconnected" . It may even say "pass" in green, not important but "succeed 1" is important.
5. Your phone will show the bar and do not disconnect. So....disconnect from laptop / PC. The screen should remain "do not disconnect".
6. Hold volume down+home+power (in that sequence).
7. As soon as the screen goes black move your finger to volume up, while still holding down home + power. You are trying to get the phone into Recovery mode as you said earlier.
8. The option to choose in the recovery menu is "wipe cache partition" NOT "wipe/factory reset". I can see from your pictures that this option has failed because the FRP lock is still on!!
9. When you've chosen "wipe cache partition" then choose "reboot system now"
The phone should go through it's normal set up routine, erasing, update, installing apps etc, just leave it do this and hopefully the phone will boot then ask for the Google email and password which was used on the phone.
There are very few reasons for the phone to get stuck on boot....
1. Incorrect firmware,
2. Water damage
3. The phone has been Rooted with FRP lock on. It is very rare to be a hardware issue.
You should always turn FRP lock off and enable OEM unlock in settings before flashing to a phone. I know it's a little late for that but something to remember.
To check for water damage.
1. Remove SIM card and holder
2. Shine a light in the hole, you will see a WHITE sticker which turns PINK if water has ever got inside the phone.
Thanks a lot again for your great efforts!
I tried as you wrote but did not manage to start recovery immediately after flashing (tried >10 times). But after some while the BTU-ROM started and now keeps doing so even after new flash without wiping cache afterwards. Wiping data worked for me in past when I sometimes had enough time to enter Wi-Fi-password. It was saved even after reboot and away when I did data wipe in recovery. With the newest ROMs I never got beyond typing Wi-Fi credentials.
I cannot see a water damage. A root was never tried before (and OEM-lock and FRP were always on because stock, which is very bad now ). Would be absolutely no problem if this !#@*#% stock ROMs would work... TWRP installation was directly blocked when I tried my luck as last resort. I did not try other images.
Thanks nevertheless for your time and patience!
Hi. I'm looking for some help after exhausting every suggestion I can find on the web.
Background to the problem (this goes back to last September so my recollections might be a bit vague):
1. My SM-G930F (with custom ROM) started overheating.
2. I took it to my local Samsung store (first mistake) who ran diagnostics and said the battery need to be replaced.
3. I paid to have the battery replaced and collected the handset from the store where everything appeared to be working.
4. 100 yards from the store, the handset rebooted. This continued every few minutes.
5. Returned to the store who said "Nothing to do with us mate, it was working when you left".
6. After many escalated communications with Samsung support, they collected the handset, ran some other diagnostics, and returned the handset stating that the main board had failed and would cost hundreds of pounds to replace.
7. I decided to spend my money on a heat gun and a second hand main board (from a well known auction site). Replacement went well and everything was working fine. It was a UK Stock ROM, but I can't remember which.
8. I then made my second mistake, I installed TWRP and performed a full restore (including the EFS partition) from the backup I'd taken of the previous main board. The handset booted into my custom ROM OK but the IMEI was blank and the SIM no longer worked.
9. I then made my third mistake, I used ODIN to install the latest stock ROM at the time (PDA G930FXXS6ESGD / CSC G930FXEU6ESGD from sammobile.com) which updated the bootloader. The installation completed successfully but somehow triggered the FRP lock and boot loops.
Current status:
1. Stock ROM boot loops. I just get the yellow triangle containing an exclamation mark and the message "Error!" (I don't get the "No Command" message).
2. I can't install any custom recovery / ROMs / etc. due to FRP.
3. All I can really do is boot the handset into "Download Mode". Can't get into "Recovery Mode". Smart Switch reports "Unrecognized device".
I believe my only option is a U6 combination ROM to clear the FRP and repair the IMEI, but it looks like this has yet to be released.
Questions:
1. I'm not sure what "Error!" means. I can't find anyone else reporting it. Does anyone know?
2. As it's been a year since the U6 bootloader was released, is a U6 combination ROM likely to ever be released?
3. Is anyone aware of any free options to resolve my problem without a combination ROM?
4. I've spent hours and hours trying different tools / methods to fix the handset, all to no avail. Do I just bite the bullet and buy another main board?
Many thanks in advance for any advice. Much appreciated.
tibbsbrookside said:
Hi. I'm looking for some help after exhausting every suggestion I can find on the web.
Current status:
1. Stock ROM boot loops. I just get the yellow triangle containing an exclamation mark and the message "Error!" (I don't get the "No Command" message).
2. I can't install any custom recovery / ROMs / etc. due to FRP.
3. All I can really do is boot the handset into "Download Mode". Can't get into "Recovery Mode". Smart Switch reports "Unrecognized device".
I believe my only option is a U6 combination ROM to clear the FRP and repair the IMEI, but it looks like this has yet to be released.
Questions:
1. I'm not sure what "Error!" means. I can't find anyone else reporting it. Does anyone know?
2. As it's been a year since the U6 bootloader was released, is a U6 combination ROM likely to ever be released?
3. Is anyone aware of any free options to resolve my problem without a combination ROM?
4. I've spent hours and hours trying different tools / methods to fix the handset, all to no avail. Do I just bite the bullet and buy another main board?
Many thanks in advance for any advice. Much appreciated.
Click to expand...
Click to collapse
The original problem was the battery which is common now as they don't last forever. The solution is to change the battery as you did but the main board was already damaged at that point. Repair versus cost in this case is too high hence them telling you to go away and buy a new phone.
Buying a new board is great but you have to ensure the connected Google account has been signed out of for that device.
You tried to overwight the EFS with your data, that's when it got into a real mess as the FRP lock prevents this.
Which brings me to the yellow exclamation mark, it means the bootloader file is missing or corrupt and thus the firmware cannot start. This would make sense because now the EFS partition is also corrupt from earlier.
There isn't going to be a new release of the combination ROM as the S7 is an old device and the devs have moved on from it.
Solution (but no gurantees)
Nand erase whole device, all partitions including EFS.
Flash stock fimrware, if phone boots the IMEI will be blank
Flash TWRP
With TWRP flash your EFS back up from original mainboard which was damaged
Pray that it works, if not then i'm sorry but the phone is now with the angels.
Thanks for the response.
You are referring to the "Nand Erase" option in Odin, yeah?
Will flashing the stock firmware re-create the partitions, or would I have to re-create them first using a PIT file?
tibbsbrookside said:
Thanks for the response.
You are referring to the "Nand Erase" option in Odin, yeah?
Will flashing the stock firmware re-create the partitions, or would I have to re-create them first using a PIT file?
Click to expand...
Click to collapse
Hello, yes nand erase in Odin.
PIT file is included in the firmware no need to extract and falsh seperately
Tried flashing various stock ROMs with the "Nand Erase" option checked.
Although the phone spends a long time "erasing" after the flash completes successfully, it still eventually just boot loops with the same "Error!" message.
Thanks for the advice anyway.
I will be performing the last rights on the handset later