[Q] SM-G900F Baseband Unknown / IMEI Null / No Signal (For experienced users only) - Galaxy S6 Q&A, Help & Troubleshooting

Hello Guys,
I need serious superuser help.
Trying to flash a custom ROM, screwed up my IMEI and baseband.
Now I get a null IMEI and a Baseband Unknown on the phone's info.
I reflashed to 6.0.1 stock using the methodology of this thread here:
http://forum.xda-developers.com/galaxy-s6/development/g920f-android-marshmallow-6-0-1-beta-t3293941
I also flashed a few different custom ROMs without any success.
I rooted and installed Wanam Xposed and IMEI Changer, (Using this link: http://forum.xda-developers.com/galaxy-s6/development/mod-wanamlite-1-0-t3095155) but even if the IMEI is showing right this time, the baseband still shows as "unknown" and the phone won't get any signal.
Before flashing the ROM for the first time, I kept a backup of the EFS. I restored it with TWRP but still no love....
I have read countless threads over google but I haven't manged to solve it.
Can someone help?

Did you back up EFS with TWRP? Some other tool?
Sent from my SM-G920W8 using Tapatalk
---------- Post added at 08:36 ---------- Previous post was at 08:35 ----------
Any errors flashing ROMs?
Sent from my SM-G920W8 using Tapatalk

DarryDoo said:
Did you back up EFS with TWRP? Some other tool?
Click to expand...
Click to collapse
Yes, TWRP I have the efs.emmc.win and md5 file.
I tried to restore with TWRP but still no love. .

Guys ,anyone? At this point I am really prepared to try anything

Last thing I tried is getting a full Nandroid backup from a fully working G920F and restored onto my own phone.
Still no love. Factory reset, wiped cache and data from TWRP but still no love.
What could be the issue then???

have you tried smart switch ??

It gives me an error when I am trying to setup the device initialisation:
"Unable to find the serial number,model name or IMEI on the Server. Please check and try again"

Have you tried using ODIN to install the latest stock image? That did the trick for my old S5 that had an IMEI issue. I highly recommend using the SamFirm tool from this site to download stock images directly from Samsung.

Sean89us said:
Have you tried using ODIN to install the latest stock image? That did the trick for my old S5 that had an IMEI issue. I highly recommend using the SamFirm tool from this site to download stock images directly from Samsung.
Click to expand...
Click to collapse
I used SamFirm and downloaded three different stock roms for the UK and one for the nordic countries. They all pass from Odin but the phone does not boot. I get
"DM-verity verification failed" and
Need to check DRK first" and the phone won't boot up ....
Is this error because I am trying to install a wrong CSC ROM ? Or an incompatible ROM ? I can't figure it out.

I believe the dm-verity error means you've got the wrong ROM. You need to download the firmware for the device/region your phone is.

I know how to fix it

papazito2015 said:
I know how to fix it
Click to expand...
Click to collapse
Would you like to share with the class? ?
Sent from my SM-G920W8 using Tapatalk

The way of fixing DRK that I know is via box (Octoplus, Z3X, etc.), but often IMEI gets reseted in the process (at least it was in my case).
If DRK is damaged, phone won`t boot without a custom kernel (which trips knox on Android versions 5.1.1 and above), if DRK is fixed, phone can boot with stock kernel.
In SmartSwich I suppose you used IMEI from back of the phone without / right? And for model you used SM-G920F (or whatever model you have) in capital letters?

Sean89us said:
I believe the dm-verity error means you've got the wrong ROM. You need to download the firmware for the device/region your phone is.
Click to expand...
Click to collapse
At this point I am stuck...
Stuck in a ****tier place than what I started.
Last thing I tried before my phone died was trying to install the latest Stock marshmallow ROM for my device. The one I downloaded via SamFirm passed Oding but never booted.
Since then, I have tried to flash 12 other ROMS with different CSCs (yes 12) from BTU (which my phone is supposed to be) to VIR , to O2U to TEN. Nothing worked!
I had kept a nandroid backup of a ROM that was working (5.1.1 without IMEI or baseband) and even that does not boot now either.
Stuck on Samsung logo

papazito2015 said:
I know how to fix it
Click to expand...
Click to collapse
I am all ears....
brenner650 said:
The way of fixing DRK that I know is via box (Octoplus, Z3X, etc.), but often IMEI gets reseted in the process (at least it was in my case).
Click to expand...
Click to collapse
This sounds logical. Do you have a box? Where did you fix your DRK? And I don't think I really care about the IMEI at this stage, right?
brenner650 said:
If DRK is damaged, phone won`t boot without a custom kernel (which trips knox on Android versions 5.1.1 and above), if DRK is fixed, phone can boot with stock kernel.
Click to expand...
Click to collapse
Well, not necessarily I think... In one of my previous tries, I managed to install stock O2U_G920FXXU3COI9_G920FTEF2COH1 (but first I deleted the "hidden" partition from the tar). Was that a coincidence you think ? #not_sarcastic
brenner650 said:
In SmartSwich I suppose you used IMEI from back of the phone without / right? And for model you used SM-G920F (or whatever model you have) in capital letters?
Click to expand...
Click to collapse
That's right. Shouldn't I ? I can't reset the phone for the life of me!

Did you do a factory reset in recovery, immediately after flashing the correct stock ROM in Odin, and before booting into the ROM? Uncheck auto reboot in Odin, when flashing is done, power & vol- to turn phone off, then boot into recovery.
Sometimes it's the simplest things that help.
Sent from my SM-G920W8 using Tapatalk

DarryDoo said:
Did you do a factory reset in recovery, immediately after flashing the correct stock ROM in Odin, and before booting into the ROM? Uncheck auto reboot in Odin, when flashing is done, power & vol- to turn phone off, then boot into recovery.
Sometimes it's the simplest things that help.
Sent from my SM-G920W8 using Tapatalk
Click to expand...
Click to collapse
I did exactly what you described. Only issue is that as soon as the phone boots, it won't let me enter recovery immediately. Before entering, I see the Green/blueish Android screen trying to install something. It stops at about 33% and it says "erasing" and only then can I enter recovery. To which point, I can erase the cache and wipe data but the phone won't boot onto the System. It just hangs there.

Not erase cache & data, factory reset.
Sent from my SM-G920W8 using Tapatalk

DarryDoo said:
Not erase cache & data, factory reset.
Click to expand...
Click to collapse
I can't boot into the system to factory reset because I am stuck in the Samsung boot loop. Wiping data and cache from recovery is the same thing... or is there something I am missing here?

Factory reset from recovery.
Have you tried booting into safe mode?
Sent from my SM-G920W8 using Tapatalk

Related

Cannot flash Stock Recovery.img after attempt to root phone failed

Hello,
I have a Galaxy S6 Edge SM-G925W8 on firmware 5.1.1. I recently updated my firmware using Smart Switch which brought me to 5.1.1 and wiped out my root access. I attempted to re-root the phone using the same TWRP Recovery I used to root it previously, which flashed successfully according to Odin. I was however unable to enter TWRP Recovery, getting the error "recovery is not seandroid enforcing" while at the booting screen. I figured maybe the TWRP Recovery I flashed was outdated and no longer worked for firmware 5.1.1 so I am now attempting to flash the Stock Recovery.img to wipe out my now broken Recovery. The problem is when I flash the stock recovery, Odin claimed the flash failed, giving no reason as to why. I'm not sure what I should do now - return to stock recovery (which fails when I attempt) or is there perhaps a way to restore TWRP Recovery and access root privileges once again.
Thank you for your help!
"recovery is not seandroid enforcing" is not a error, it's just a warning. If it stuck at this screen, that means the TWRP you're using is not compaitable with installed bootloader.
What's your PDA number?
forumber2 said:
"recovery is not seandroid enforcing" is not a error, it's just a warning. If it stuck at this screen, that means the TWRP you're using is not compaitable with installed bootloader.
What's your PDA number?
Click to expand...
Click to collapse
I'm sorry I'm not sure what that number is. I have searched through my phone's "About Phone" and "Developer Options" but did not find anything called a PDA number. If you mean the file I used to flash the TWRP Recovery, its name is "twrp-2.8.6.0v2-zeroltetmo.tar". If that's not what you need, could you please tell me how to find it?
Thank you!
vgplayer54 said:
I'm sorry I'm not sure what that number is. I have searched through my phone's "About Phone" and "Developer Options" but did not find anything called a PDA number. If you mean the file I used to flash the TWRP Recovery, its name is "twrp-2.8.6.0v2-zeroltetmo.tar". If that's not what you need, could you please tell me how to find it?
Thank you!
Click to expand...
Click to collapse
Type *#1234# on dialer. It'll show you software version (AP), modem -baseband- version (CP) and CSC version. I'm asking for AP version.
The TWRP version that you're trying to use is pretty old. The latest official TWRP is working on latest Android 5.1.1 bootlader. Try this; (for T-Mobile variant)
https://dl.twrp.me/zeroltetmo/twrp-3.0.2-0-zeroltetmo.img.tar
Thank you for getting back to me, will that T-Mobile version work on my Canadian Sm-G925W8? It's with Rogers, not sure if that makes a difference.
vgplayer54 said:
Thank you for getting back to me, will that T-Mobile version work on my Canadian Sm-G925W8? It's with Rogers, not sure if that makes a difference.
Click to expand...
Click to collapse
Okay, thank you for getting my AP number . The AP is G925W8VLU3B0J7.
forumber2 said:
Type *#1234# on dialer. It'll show you software version (AP), modem -baseband- version (CP) and CSC version. I'm asking for AP version.
The TWRP version that you're trying to use is pretty old. The latest official TWRP is working on latest Android 5.1.1 bootlader. Try this; (for T-Mobile variant)
https://dl.twrp.me/zeroltetmo/twrp-3.0.2-0-zeroltetmo.img.tar
Click to expand...
Click to collapse
Thank you for the link, I just finished flashing that TWRP Recovery and it appears to have worked. The problem now is I booted into the Recovery, installed SuperSU2.49 to add the SuperUser permissions and now I'm stuck on an infinite boot loop. The phone doesn't make it past the boot screen. Is there a way to reverse or fix this? I am still able to boot into the TWRP Recovery however, anything I can do here to fix the problem?
vgplayer54 said:
Thank you for the link, I just finished flashing that TWRP Recovery and it appears to have worked. The problem now is I booted into the Recovery, installed SuperSU2.49 to add the SuperUser permissions and now I'm stuck on an infinite boot loop. The phone doesn't make it past the boot screen. Is there a way to reverse or fix this? I am still able to boot into the TWRP Recovery however, anything I can do here to fix the problem?
Click to expand...
Click to collapse
try cleaning the cache and daavik cache. To remove any stray bits of code left over.
vgplayer54 said:
Thank you for the link, I just finished flashing that TWRP Recovery and it appears to have worked. The problem now is I booted into the Recovery, installed SuperSU2.49 to add the SuperUser permissions and now I'm stuck on an infinite boot loop. The phone doesn't make it past the boot screen. Is there a way to reverse or fix this? I am still able to boot into the TWRP Recovery however, anything I can do here to fix the problem?
Click to expand...
Click to collapse
You flashed a whole old version of SuperSU. You need to flash latest beta;
http://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
But, you have to do it after reflash the stock firmware, because you modified the /system, which you shouldn't.
Or, just wipe everything and flash a custom ROM (I prefer this ROM )
forumber2 said:
You flashed a whole old version of SuperSU. You need to flash latest beta;
http://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
But, you have to do it after reflash the stock firmware, because you modified the /system, which you shouldn't.
Or, just wipe everything and flash a custom ROM (I prefer this ROM )
Click to expand...
Click to collapse
Thank you so much for the advice. I ended up downloading the stock firmware 5.1.1 for my phone model (AP number matched and everything) although what I didn't expect was for it to delete all my data and storage. I had no backup...as I didn't expect the root to go bad. But since it happened anyway, could you tell me a bit about these custom ROMS? The reason I never wanted to use one was due to not wanting to lose my data. But it happened anyway...so I might as well see what it's all about. I checked out the link to the one you said you prefer, is it overly beneficial to use a custom ROM? Does it already come Rooted or do I still have to do that myself?
Please let me know!

Phone boots but recovery mode does not work (after flashing TWRP)

Hi all, using S7 SM-G930F. Just got it yesterday and first thing I wanted to do was flash TWRP so I could put the new Pixel OS onto it.
Used ODIN, got the pass message as usual... phone rebooted automatically into stock OS. I turned it off and tried booting into recovery mode but it gets stuck at the splash screen. Nothing happens, not even stock recovery. I re-flashed TWRP without auto-reboot option this time but the same thing happens.
So essentially I have a phone that works but no recovery mode at all I can't find anyone else with this same problem, please help. I can't get any further without it. Ideally I want to avoid flashing the entire stock image. Thanks
OEM unlocked?
ODIN 3.12.3 or later used?
*Detection* said:
OEM unlocked?
ODIN 3.12.3 or later used?
Click to expand...
Click to collapse
Yes I did set OEM unlocked.
Ahhh, I am using ODIN 3.10.6!! Thanks, let me try 3.12 and get back to you if there's a problem. Thank you very much.
Fieldfare said:
Yes I did set OEM unlocked.
Ahhh, I am using ODIN 3.10.6!! Thanks, let me try 3.12 and get back to you if there's a problem. Thank you very much.
Click to expand...
Click to collapse
I'm afraid it hasn't worked. Exactly the same thing, just stuck on splash screen until I reboot into OS.
Double checked, OEM Unlock is definitely enabled.
Id flash stock again to fix recovery, then try TWRP with ODIN 3.12.3
*Detection* said:
Id flash stock again to fix recovery, then try TWRP with ODIN 3.12.3
Click to expand...
Click to collapse
Do you mean flash the entire stock firmware or just stock recovery? I'm attempting to extract stock recovery from firmware now... but if I have to flash the whole firmware then I guess I have to.
Just flash full stock, you won't lose anything unless you flash CSC which resets the phone after the flash
But you do know you have to wipe your phone to get TWRP installed correctly right?
*Detection* said:
Just flash full stock, you won't lose anything unless you flash CSC which resets the phone after the flash
But you do know you have to wipe your phone to get TWRP installed correctly right?
Click to expand...
Click to collapse
Nope. I didn't know. No guide I used ever states that anywhere (I'm a CWM person also, first time using TWRP).
Sounds strange to me.. How do you root your phone using TWRP then if you have to wipe it first?
Can I even use CWM for S7? Didn't think so as there are no guides for it.
Not worried about losing anything as only got the phone yesterday but really worried about the stock firmware flash not working the same way TWRP doesn't, that's why I wanted to avoid it if possible, I'll give it a go. Thanks
Fieldfare said:
Nope. I didn't know. No guide I used ever states that anywhere (I'm a CWM person also, first time using TWRP).
Sounds strange to me.. How do you root your phone using TWRP then if you have to wipe it first?
Can I even use CWM for S7? Didn't think so as there are no guides for it.
Not worried about losing anything as only got the phone yesterday but really worried about the stock firmware flash not working the same way TWRP doesn't, that's why I wanted to avoid it if possible, I'll give it a go. Thanks
Click to expand...
Click to collapse
You don't have to use TWRP to root, if you're not bothered about having custom recovery you can just flash CF-Auto Root using ODIN, that will root without the need for TWRP
Reason you have to wipe with TWRP is because of encryption the phone is using - reading the TWRP thread would be a good plan before blindly flashing stuff
Don't worry about flashing stock, I have the same G930F, flashed stock a couple times using ODIN, no issues
*Detection* said:
Id flash stock again to fix recovery, then try TWRP with ODIN 3.12.3
Click to expand...
Click to collapse
*Detection* said:
You don't have to use TWRP to root, if you're not bothered about having custom recovery you can just flash CF-Auto Root using ODIN, that will root without the need for TWRP
Reason you have to wipe with TWRP is because of encryption the phone is using - reading the TWRP thread would be a good plan before blindly flashing stuff
Don't worry about flashing stock, I have the same G930F, flashed stock a couple times using ODIN, no issues
Click to expand...
Click to collapse
I followed http://galaxys7root.com/galaxy-s7-s7-edge-root/how-to-root-galaxy-s7-s7-edge/3/
They never mentioned anything.
I just flashed stock firmware and now I can't do anything, no recovery, no download, no OS. Bootloop no matter what...
http://stockroms.net/file/GalaxyS7/6.0.1/SM-G930F/UnitedKingdom
This is what I used...
Kept trying and eventually got back into download mode (it was really hard)...
I am still lost on what to do now though.
Fieldfare said:
Kept trying and eventually got back into download mode (it was really hard)...
I am still lost on what to do now though.
Click to expand...
Click to collapse
Follow XDA guides, not random sites
OK, considering the phone is pretty much empty and new, just flash all 4 ROM parts with ODIN
AP, BL, CP and CSC, factory reset the phone and start again from scratch
This time read the TWRP thread, or the CF Auto root thread here on XDA before doing anything at all
*Detection* said:
Follow XDA guides, not random sites
OK, considering the phone is pretty much empty and new, just flash all 4 ROM parts with ODIN
AP, BL, CP and CSC, factory reset the phone and start again from scratch
This time read the TWRP thread, or the CF Auto root thread here on XDA before doing anything at all
Click to expand...
Click to collapse
Thanks! Boots now. Shame I only really found this place's guides after the one I used failed, starting again now
Did you unlock your bootloader? That is way flashing twrp works but would not boot twrp
I know the problem. Make sure "reboot automatically" is DISABLED in Odin when flashing TWRP. If you do not it will fail. I know from experience. Im assuming you already know to habe OEM unlocked etc etc
Sent from my SM-G930L using XDA-Developers mobile app

Really afraid my phone might be broken, someone please help me. (Soft Bricked)

I'm going crazy. I wanted to upgrade my Samsung Galaxy S5 SM-G900F finally from 4.4.2 to 6.01. I rooted it years ago and never cared to upgrade through OTA, since it never worked. So I found out about the FlashFire app recently, and used it to flash a 6.0.1 firmware stock zip file I downloaded. Followed all instructions, left all deselected partitions as is, only flashed boot, recovery, system, cache and preload. FlashFire started working on it, reboots into loading logo screen for a while, I start getting concerned but then it loads up a screen showing "Optimizing files" of like 250. Once that got done, it rebooted. Here is where I'm stuck since then.
My phone has been soft bricked, it's stuck on an endless Samsung logo screen, that gently flashed back and forth, and there's a blue notification light on during this. So I googled what I can do, and I tried using Volume Up + Power Button + Home button, since that would get me into recovery mode. That works, but instead of the Samsung recovery mode I get the Clockwork mod recovery screen. I had completely forgotten that I even had that. But, the same options are there too, so I wipe cache, wipe user data, wipe dalvik and factory reset. Once I did that, I selected reboot.
And the same thing happens. Endless Samsung logo screen. Stuck on it for hours. Now I honestly don't know what to do. I've done the recovery mode options 3 times, nothing changes.
Someone please help me out, I can't figure out what went wrong and how I can fix it. I can't afford a new phone...Ideally, I would like to be able to completely reset the phone entirely to factory settings. Is this possible? I appreciate any advice I can get.
Download odin and flash the whole firmware tar.md5.
4.4.2 to 6.0.1 is a big step so you'll probably need all partitions in that file.
Skickat från min SM-A310F via Tapatalk
tys0n said:
Download odin and flash the whole firmware tar.md5.
4.4.2 to 6.0.1 is a big step so you'll probably need all partitions in that file.
Skickat från min SM-A310F via Tapatalk
Click to expand...
Click to collapse
Thanks for replying. Which firmware? I don't understand what you mean by all partitions. Will this Odin method really fix my bootlooped phone?
tempest22 said:
Thanks for replying. Which firmware? I don't understand what you mean by all partitions. Will this Odin method really fix my bootlooped phone?
Click to expand...
Click to collapse
For some reason the recovery flash diden't work, and custom recoveries can't extract the csc-zip that its inside cache.img.
It could be that bootloader, modem and other partitions needs to be updated as well.
Yes. I think you'll need to flash the whole firmware with odin.
tys0n said:
For some reason the recovery flash diden't work, and custom recoveries can't extract the csc-zip that its inside cache.img.
It could be that bootloader, modem and other partitions needs to be updated as well.
Yes. I think you'll need to flash the whole firmware with odin.
Click to expand...
Click to collapse
When I googled how to properly use FlashFire when I first used it (which then lead to this soft brick) I read that you shouldn't flash the modem and other priority partitions that were unselected. So now I should do it?
Where is the best place to get firmware? And which firmware do I even get? 6.0.1? Or my old 4.4.2 to get it back to it's original state?
Help pls
tempest22 said:
When I googled how to properly use FlashFire when I first used it (which then lead to this soft brick) I read that you shouldn't flash the modem and other priority partitions that were unselected. So now I should do it?
Where is the best place to get firmware? And which firmware do I even get? 6.0.1? Or my old 4.4.2 to get it back to it's original state?
Click to expand...
Click to collapse
Either 4.4.2, 5.0 or 6.0.1 would do since you only flashed four partitions.
Use http://updato.com/firmware-archive-select-model?r=&v=&q=SM-G900F&exact=1&rpp=15
You can sort it by version, date, region etc.
tys0n said:
Either 4.4.2, 5.0 or 6.0.1 would do since you only flashed four partitions.
Use http://updato.com/firmware-archive-select-model?r=&v=&q=SM-G900F&exact=1&rpp=15
You can sort it by version, date, region etc.
Click to expand...
Click to collapse
Ok. So you're saying I download let's say the 6.0.1 from there, then I download Odin, connect my phone in download made and flash ALL partitions from that firmware? This will get my phone out of this crazy bootloop Samsung logo soft brick it's been in for 3 days?
tempest22 said:
Ok. So you're saying I download let's say the 6.0.1 from there, then I download Odin, connect my phone in download made and flash ALL partitions from that firmware? This will get my phone out of this crazy bootloop Samsung logo soft brick it's been in for 3 days?
Click to expand...
Click to collapse
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.
tys0n said:
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.
Click to expand...
Click to collapse
Ok, how exactly do I flash whole .tar.md5 package? I've been looking at how to use Odin and I don't really see how to do that.
tys0n said:
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.
Click to expand...
Click to collapse
Odin worked. Thanks!

i need help FRP unlocking my Galaxy S7 SM-G930W8

Hello i have a Galaxy S7 SM-G930W8 thats frp locked and i have been looking to unlock it for the past 4 days but could not find any solution on how to please help,thanks
Kemako121 said:
Hello i have a Galaxy S7 SM-G930W8 thats frp locked and i have been looking to unlock it for the past 4 days but could not find any solution on how to please help,thanks
Click to expand...
Click to collapse
Flash stock then log in with your Google credentials
*Detection* said:
Flash stock then log in with your Google credentials
Click to expand...
Click to collapse
well could you please link me the stock of my phone because i cannot find it myself.... i was looking for a while and tried some but now my phone is just stuck on the boot screen..
Stock sm-g930w8 firmware is here: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/
This post may be helpful: https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
audit13 said:
Stock sm-g930w8 firmware is here: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/
This post may be helpful: https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
Click to expand...
Click to collapse
thank you a lot but i have another question after i ran a boot.tar from firmware.obi my phone is stuck on the boot logo what can i do to move on and is it safe if i boot the files u sent me with the current state of my phone? also the download will be ages since the speed for non premium is 15kb/sec
To return the phone to a stock condition, you flash the ROM using Odin which will overwrite everything with the possible exception of the data partition.
If the phone is stuck at the boot logo, have you tried a factory reset from stock recovery?
You can try this link: http://samsung-updates.com/device/?id=SM-G930W8 or https://updato.com/firmware-archive-select-model?exact=1&q=SM-G930W8
I don't know about download speeds for the above-two links as I have never used them before but other XDA members have.
audit13 said:
To return the phone to a stock condition, you flash the ROM using Odin which will overwrite everything with the possible exception of the data partition.
If the phone is stuck at the boot logo, have you tried a factory reset from stock recovery?
You can try this link: http://samsung-updates.com/device/?id=SM-G930W8 or https://updato.com/firmware-archive-select-model?exact=1&q=SM-G930W8
I don't know about download speeds for the above-two links as I have never used them before but other XDA members have.
Click to expand...
Click to collapse
i have tried going into the boot menu for factory reset but no luck the phone just resets,im starting the odin method right now with the thing you provided, also do i fill all the blanks (like the csc,ap and cp?) in odin?
After downloading the file from sammobile.com, unzip the file once (I use 7zip) to yield the necessary files. Each file will be preceded by the blank or slot location.
Difference between CSC and Home CSC: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835 or https://forum.xda-developers.com/galaxy-s7/help/question-using-ap-bl-csc-instead-home-t3562545
audit13 said:
After downloading the file from sammobile.com, unzip the file once (I use 7zip) to yield the necessary files. Each file will be preceded by the blank or slot location.
Difference between CSC and Home CSC: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835 or https://forum.xda-developers.com/galaxy-s7/help/question-using-ap-bl-csc-instead-home-t3562545
Click to expand...
Click to collapse
help when i put in all the things it says: SW REV. CHECK FAIL DEVICE:2 BINARY:1
Odin recognizes the phone? Are you seeing the message in download mode?
audit13 said:
Odin recognizes the phone? Are you seeing the message in download mode?
Click to expand...
Click to collapse
so i managed to get this phone back to its original state when it was frp locked by downloading software from sammobile but it still remembers the google account... i will try to download a older version of android and run that to hopefully get the phone to 6.0.1 or whatever the original version was and try some older ways to frp unlock my phone because the older version will have less security patches. hopefully this works! thanks for the help so far .:good:
I'm not sure that you can downgrade once the phone has been updated.
Good luck.
same here, stuck without solutions. tried pretty much everything found on the internet carefully and taking the time to do it.. but still...
i still need help can someone find a way to unlock my phone?
One way to remove frp lock is to flash a custom recovery (like TWRP) for your phone and then use the wipe -> format data (and type 'yes' when asked, without the quotes). Restart the phone and let the system boot. After it boots you can procede to flash the stock rom
* P.S. 1: flashing a custom recovery will trigger KNOX so say bye bye to S Health if you are not planning to root the phone (so as to be able to edit the build prop and enable SHealth again) after flashing the stock rom again. Do not attemp to flash the stock recovery image on its own or your phone will be soft bricked and the dm-verity error will give you nightmares (happened twice to me, took me 6 hours to recover my phone). To get back the stock recovery you need to flash the stock rom again.
* P.S. 2: If your phone has the bootloader locked you will not be able to flash a custom recovery. In that case you can try to downgrade to 6.0 but there are not guarantees that it will work ok.
Sent from my SM-G930F using Tapatalk
coto39 said:
One way to remove frp lock is to flash a custom recovery (like TWRP) for your phone and then use the wipe -> format data (and type 'yes' when asked, without the quotes). Restart the phone and let the system boot. After it boots you can procede to flash the stock rom
* P.S. 1: flashing a custom recovery will trigger KNOX so say bye bye to S Health if you are not planning to root the phone (so as to be able to edit the build prop and enable SHealth again) after flashing the stock rom again. Do not attemp to flash the stock recovery image on its own or your phone will be soft bricked and the dm-verity error will give you nightmares (happened twice to me, took me 6 hours to recover my phone). To get back the stock recovery you need to flash the stock rom again.
* P.S. 2: If your phone has the bootloader locked you will not be able to flash a custom recovery. In that case you can try to downgrade to 6.0 but there are not guarantees that it will work ok.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
hi could you please link the stuff i need to download in order to to this my phone is SM-G930W8

Need help with Odin, cannot return to stock :(

Hi,
Using latest Odin I am trying to return to my phone to stock but cannot 
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
GODSPD said:
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot 
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
Click to expand...
Click to collapse
You flashed the wrong firmware and corrupted your device.
You should flash the newest available firmware for your specific model number. You might have to flash the PIT file for your model number along with the firmware with the "re-partition" option checked in Odin when you flash it.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You flashed the wrong firmware and corrupted your device.
You should flash the newest available firmware for your specific model number. You might have to flash the PIT file for your model number along with the firmware with the "re-partition" option checked in Odin when you flash it.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I need to keep v3 bootloader, i am very sure that latest firmware will work but i am trying to avoid it, and i never flashed the wrong firmware, i have tried aroud 6 different v3 and none will stick, can you suggest where i can find the PIT files and possible guide? without the pit file the repartition option fails each time...
GODSPD said:
I need to keep v3 bootloader, i am very sure that latest firmware will work but i am trying to avoid it, and i never flashed the wrong firmware, i have tried aroud 6 different v3 and none will stick, can you suggest where i can find the PIT files and possible guide? without the pit file the repartition option fails each time...
Click to expand...
Click to collapse
If you didn't flash the firmware then how did it show up as a different device "from a previous ROM", as you said?
They might have been V3 firmware, but was it for the same model number of V3 as yours? Are the model numbers different? Is V3 the model number? Or is it the device branded name?
Sent from my LGL84VL using Tapatalk
Droidriven said:
If you didn't flash the firmware then how did it show up as a different device "from a previous ROM", as you said?
Thanks for the feedback.
They might have been V3 firmware, but was it for the same model number of V3 as yours? Are the model numbers different? Is V3 the model number? Or is it the device branded name?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback, several months ago i flashed G935FXXS3ERHD_G935FXEO3ERG2_XEO on the S7 Edge International, so firmware is correct, i flashed a custom ROM - Glamour ROM a S9+ Ported ROM for the S7E, everything worked fine until i tried to revert back to stock, every other V3 firmware apart from the one mentioned above wont flash correctly, either fails or boot loops, has no stock recovery, and system status is still showing CUSTOM, when i plug the device in it will come up as Galaxy S9+ ... for some reason i cannot do a proper flash on it,
I am almost certain i can do a proper flash with the latest firmware but i am trying to avoid that...
GODSPD said:
Thanks for the feedback, several months ago i flashed G935FXXS3ERHD_G935FXEO3ERG2_XEO on the S7 Edge International, so firmware is correct, i flashed a custom ROM - Glamour ROM a S9+ Ported ROM for the S7E, everything worked fine until i tried to revert back to stock, every other V3 firmware apart from the one mentioned above wont flash correctly, either fails or boot loops, has no stock recovery, and system status is still showing CUSTOM, when i plug the device in it will come up as Galaxy S9+ ... for some reason i cannot do a proper flash on it,
I am almost certain i can do a proper flash with the latest firmware but i am trying to avoid that...
Click to expand...
Click to collapse
Have you tried factory resetting the device then try flashing via Odin? Sometimes there is conflicting data that prevents from flashing the firmware.
You might not have a choice of which firmware to flash to repair your device.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you tried factory resetting the device then try flashing via Odin? Sometimes there is conflicting data that prevents from flashing the firmware.
You might not have a choice of which firmware to flash to repair your device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
more than you can imagine, every possible wipe and combination has been done with no luck at all
GODSPD said:
more than you can imagine, every possible wipe and combination has been done with no luck at all
Click to expand...
Click to collapse
Well then, suck it up and flash the newest firmware, you are out of options.
Your device probably doesn't allow downgrading, in this case, you can only flash exactly what was on the device before you caused the issue or a newer firmware, you can't go backwards to an older firmware.
If you're trying to flash an older firmware in an effort to get past a locked bootloader, you are probably wasting your time, that doesn't work out most of the time.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Well then, suck it up and flash the newest firmware, you are out of options.
Your device probably doesn't allow downgrading, in this case, you can only flash exactly what was on the device before you caused the issue or a newer firmware, you can't go backwards to an older firmware.
If you're trying to flash an older firmware in an effort to get past a locked bootloader, you are probably wasting your time, that doesn't work out most of the time.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
That definitely makes sense that i cannot downgrade but i am flashing either the same firmware or slightly newer staying on the same bootloader version.

Categories

Resources