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!
Related
Hi All,
I have a Note Edge 915FY. Tried to upgrade it to stock 5.0.1 via sammobile.com
It is now stuck. It just shows the Samsung Galaxy Note Edge screen and then flashes to "Recovery Booting" and just stays stuck there! For hours!
I have also tried to download 4.4.4 from sammobile.com and flash that but same thing happens. I cannot go into recovery, only into download mode.
I also tried to root it using CF-Autoroot but that failed.
Furthermore, I have tried flashing CWM and TWRP but both do nothing.
I am absolutely stuck! And I really need help!
PS: The phone has no warranty now, so I have no fallback! Please HELP!!!!!
I didn't have any luck flashing CF-AutoRoot when I was on Lollipop, I used CWM and it worked fine.
If your'e stuck go into ODIN mode (Power, Home + Down Vol) and then click up when prompted,
make sure your pc has samsung drivers installed
Download the stock 5.0.1 BOC2 ROM from this XDA page
http://forum.xda-developers.com/note-edge/development/rom-stock-tw-lollipop-t3019721
(You can easily up to BOC6 or a hacked rom later)
Make sure to set Odin as shown in the picture from that same url above
http://dl-1.va.us.xda-developers.com/3/1/4/6/2/6/9/odin.PNG?key=DHp6BTdAsBVpoENIbV4DMw&ts=1431888807
This should work without any issues, I spent some cycles getting bootloops via cf-auto root and some funny ROM behaviour, I was always able to
use this to get me back to stock, root using cwm method then deploy whichever debloated rom you like !
G
iqsoft said:
Hi All,
I have a Note Edge 915FY. Tried to upgrade it to stock 5.0.1 via sammobile.com
It is now stuck. It just shows the Samsung Galaxy Note Edge screen and then flashes to "Recovery Booting" and just stays stuck there! For hours!
I have also tried to download 4.4.4 from sammobile.com and flash that but same thing happens. I cannot go into recovery, only into download mode.
I also tried to root it using CF-Autoroot but that failed.
Furthermore, I have tried flashing CWM and TWRP but both do nothing.
I am absolutely stuck! And I really need help!
PS: The phone has no warranty now, so I have no fallback! Please HELP!!!!!
Click to expand...
Click to collapse
iqsoft said:
Hi All,
I have a Note Edge 915FY. Tried to upgrade it to stock 5.0.1 via sammobile.com
It is now stuck. It just shows the Samsung Galaxy Note Edge screen and then flashes to "Recovery Booting" and just stays stuck there! For hours!
I have also tried to download 4.4.4 from sammobile.com and flash that but same thing happens. I cannot go into recovery, only into download mode.
I also tried to root it using CF-Autoroot but that failed.
Furthermore, I have tried flashing CWM and TWRP but both do nothing.
I am absolutely stuck! And I really need help!
PS: The phone has no warranty now, so I have no fallback! Please HELP!!!!!
Click to expand...
Click to collapse
Did you solve?
Try this (It works for me when my Note Edge was bricked):
On samsung kies 3 select "Tools --> Firmware Upgrade and Initialization" and follow the instructions.
It will ask for phone model (SM-N915FY or other) and for Serial Number S/N, this number is indicated under the battery (make attention to insert the number near S/N not near SSN).
After this It will ask to connect the phone in Download Mode and after it will start to download the firmware (more than 1GB) and will start the installation.
Boot into recovery , power + button + sound UP and clear cache and all reset.
Re do lollipop and you should be fine.
Happened to me but i worked it out after the panic stage....
lucarp78 said:
Did you solve?
Try this (It works for me when my Note Edge was bricked):
On samsung kies 3 select "Tools --> Firmware Upgrade and Initialization" and follow the instructions.
It will ask for phone model (SM-N915FY or other) and for Serial Number S/N, this number is indicated under the battery (make attention to insert the number near S/N not near SSN).
After this It will ask to connect the phone in Download Mode and after it will start to download the firmware (more than 1GB) and will start the installation.
Click to expand...
Click to collapse
I have tried this but weird enough for me, after I input the model number followed by the S/N number in Kies, I got a message "Initialization is not supported for SM-N915FY"
Its kind of fishy since the S/N input only appears after I gave Kies the Model number. If N915FY was not supported, why would they make me open up the back cover and look up for the S/N, make me type it letter by letter and then tell me 'Ok, no luck for you!'.
Any explanation and/or solution for me please? I only have 14 days of extensive researching experience, still left with a 'baseband unknown and null imei" note edge with no prior efs backup .
I think we got the same problems bro, i was very proud note edge user till two days a go, when sudden problems start to happen like restart, slowdown, loop, freeze and shoot of, later no more reboot from system menu that it just shoots of, and then latter hard to start, i had to take out battery and push start + home + volume down buttons about one minute and put back battery just to bring in to download mode and then volume down to start the in to system, and after screen is off it shots down again and again, and last time i put in to freeze to start it to see any missed calls or messages, but sens last night no way i can start any more!
I used to update apps from google and samsung store, and i em curious at this latest update, overnight was lot of data use, even in settings it was setup not to sync any data and not to use any data in background, only Viber app, so i assume there most have been sent to our phones some malware update to brick our old lovely phones, it is very possible.
Now, all i can do is to go to market to find broken screen note edge to purchase and replace motherboard, and i hope i find one not sim-locked.
So try to use Odin v3.07, and download the firmware from here https://www.sammobile.com/samsung/galaxy-note-edge/firmware/#SM-N915FY ans flash it, hope you get back your phone, and if you need to root it, use TWRP v3.02.tar flash with odin to...so the rest of procedure i guess you know!
Today i found on local phone shop+ service one note edge with a bit broken screen, but it did start and stack on kind of "recovery booting", i realized the service or the owner did try to flash sort of room on it but not completed, i bought the phone sm-n915FY model for 30.euro, and now i just transferred the motherboard to my own phone and flashed the TWRP v3.02.tar successfully and let it charge first, bcz there was only 05% battery, and later i will see if i can restore the twrp backup, and i will be careful with this update apps from google and Samsung store the gmail, androidwebsecurity**, maps and browser.
Well, my phone works now, it's just the TWRP backup is not working correct, even i modified folder of the backup, i had pssword in backup and now when i restore seek pasword, i type correct, but the phone did encrypt it. so i have to start with new room setup.
Help Help Help :
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got TWRP cant install.Because. OEM locked.
It flashed. Great. But now IT STILL DOESNT BOOT. I'm stuck at NO COMMAND, it keeps restarting after 20-30 seconds of showing no command. and it's looping all over.*
i flashed stock firmware.It is flashed.Then reboot.Then install system update.Then Erasing.Then rebooting.Then NO COMMAND.Then reboot itselve recovery mode.Then i wiped factoory and cache.Then press rwboot to system.Then Samsung Galaxy S8 Plus.Then install system update.Erasing.No Command. etc. Keeps rebooting. its on NO command screen. It just restarts. Doesnt boot. I want to enable OEM Unlock. I installed combination binary. But not appear in Developer Mode.
i flash atock with Kies emergency.I flash different stock firmware from updato.com. But nothing happend.
I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?
JeffDC said:
I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?
Click to expand...
Click to collapse
KIES says that. (THR) Stock. i downloaded it and flashed with Odin. Then reboot. Then system install update. Then Erasing. Then reboot and No Command! 30 seconds keeps rebooting itself 30 seconds interval Random.
I did factory format, cache clear. then the same problem. i want to install twrp recovery with oden. It says Oem Lock. Not allowed. But i flashed Combinary file. I can get into system and i to developer mode but dosnt seem OEM UNLOCK that ll do enable it.
Ok mate, but if you press Vol- + Bixby + power for couple of seconds, can you access to download mode? If you can, I think you'll have to install the firmware all over again.
Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.
Did OP find a fix to this problem?
I am experiencing a similar issue. Picked my phone up to find had randomly gone into a boot loop. Tried soft reset, cache wipe, factory reset - all successful but the phone would still reboot and be stuck on device model screen. Next I decided to flash the device with stock firmware. The flash passed in Odin, the phone then rebooted, loaded to device model screen, then a screen appeared saying "installing updates" which would make it to 25% then crash. After this the phone keeps booting, shows a screen with a dead android icon and says "no command" or "error". I have tried to flash the device using Oreo and Nougat firmware but have failed every time (although the flash did pass in Odin)
Any help would be greatly appreciated as I would rather not buy a new phone due to a random hardware fault which is out of my control.
southsideswaggar said:
Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.
Click to expand...
Click to collapse
This is perfect if you have soft bricked your phone!
follow this video maybe it help you
https://forum.xda-developers.com/ga...g-aqg5-fix-t3636857/post73032395#post73032395
https://www.youtube.com/watch?v=VTi3uBkpJic&t=155s
Hey guys,
decided to flash the latest DBT Firmware via Odin to get back to stock completely. (G930FXXU3ESA3)
After flashing the firmware through Odin the phone reboots and then installs an update and erases data (blue background).
After a second reboot I end up with a blue screen and the simple error: "No command".
I can not get into recovery, as I end up with the same error message wether booting into recovery or the system.
I CAN however get into downloadmode and flash twrp, after that I can boot into system but I want to keep the whole system vanilla, without TWRP.
Installing TWRP keeps the device encrypted, no matter what. I can wipe, then install no-verity-encrypt and as soon as I reboot the device is encrypted again.
Ive tried: Different Firmware Version (December 2018), 3 different cables, different odin versions.
Edit: attached an Image of the message that Pops up after about 30sec on the no command screen.
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
FLASH No verity.zip
VIA TWRP
https://forum.xda-developers.com/attachment.php?attachmentid=4490455&d=1525176288
cooltt said:
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
Click to expand...
Click to collapse
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Scorpionea said:
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Click to expand...
Click to collapse
Did a efs backup through TWRP just in case, then flashed the latest DBT firmware with nand erase -> still the same problem.
I can only guess that this was caused by using a backup from another phone back when Oreo came out, this probably messed something up really badly. Very weird, im kinda lost.
Killuminati91 said:
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Click to expand...
Click to collapse
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
cooltt said:
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
Click to expand...
Click to collapse
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Killuminati91 said:
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Click to expand...
Click to collapse
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
cooltt said:
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
Click to expand...
Click to collapse
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Killuminati91 said:
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Click to expand...
Click to collapse
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
cooltt said:
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
Click to expand...
Click to collapse
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Killuminati91 said:
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Click to expand...
Click to collapse
Thats because he's a scammer. Never donate to get your phone fixed! Donate to Rom developers and things you like but never to get the phone fixed, they're usually lying.
The serial number should be the same ON the phone as displayed IN phone. Tell me the story about the phone, how did you get it? what region? where are you? what firmware was installed? Can you still flash a ROM with TWRP? Can you check OEM unlock?
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
nmnmnmnmnmnmnmnmnm
Pretty sure he was just trying to remote repair for a price, which is not allowed on XDA. Would obviously donated on my own if he actually fixed it.
Bought the phone unlocked directly from a provider (simply - germany - dbt - g930f) back in 2016. Tripped kn0x after a few months, installed a few custom roms until Oreo came out.
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Since then I had constant connection problems, weak internet connection, dropped calls and so on.
Broke my screen and then decided to repair it myself. Bought a new frame, screen, battery, usb-port, earpiece and vibrator - managed to assemble all of that.
I can install all latest official firmwares (bootloader 3) through Odin. If I leave it at that I have no recovery and end up with the initially shown screen and "No command".
If i install TWRP from there and simply root with magisk or apply dm-verity-fix I can boot into the stock firmware with everything working.
I can also install ROMs. Just going completely vanilla is not possible anymore. OEM Unlock is checked, USB debugging works.
Edit: What is also astounding: If I flash version DBT-G930FXXS3ERHD-20180918145033 (oldest possible Oreo Version) I can enter recovery and do a factory reset and wipe cache.
If I do that however I am stuck at the Galaxy S7 Logo, not even bootlooping.
Killuminati91 said:
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Click to expand...
Click to collapse
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
cooltt said:
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
Click to expand...
Click to collapse
Dang it. Thank you! Off to find someone who can do this via remote access or in Berlin.
Same situation right now with my S7. Damn.
Hi everyone. Did you guys find any way to resolve this issue? i have exactly the same issue here.. but in my case i cannot use twrp cuz i never installed it before... the issue happened right after i tried to enter the recovery mode by pressing the buttons...
my wife's galaxy s7 touch screen was acting weird and i tried to get into the recovey mode..which is pretty muh easy to do... but once i tried the no command msg came up and now i have exatly the same case as the guy that opened this thread....also done everything hes done....any clue about this anyone?
id appreciate some help..
thanks in advance
Diego Boffa
Anyone?
I have exactly the same error with "fail to open recovery_cause(No such file or directory)#
My Tablet is now stuck with a blue "android dead" screen saying "No command".
My history to disaster:
- i've recovered a "broken" Samsung Tablet (sm-T585) with corrupted file system via
* Download Mode works -> TWRP install -> Mount option -> use ADB to recreate EFS partition -> re-flash stock image (android 8) with odin
- device works fine
- then i've noticed it can only be used with a certain cell provider (o2)
- then i've tried to flash an older version of the stock rom (android 7) due some problems in Android 8 (often some slow downs while operating)
- this doesn't work, the flash don't start
- therefore nothing should be happend, or?
- then i've can't get anymore in the stock recovery to wipe all data
...therefore the mess began:
* i can't flash TWRP anymore
* i can't flash stock recovery anymore
* i only can get into download mode
* i can only flash a certain rom type successfully (green PASS within odin), but with the final stuck with boot loop, with the mentioned blue screen
* other rom version can't flashed
I hopefully ask you guys here, if anyone can help me?
Any help would be very appreciated ...
Been having problems a while now, they've been progressively getting worse. Seemed to happen after an update.
Basically the phone freezes and reboots. Can be anything, unlocking, playing games, opening internet browser, opening gmail. Just frustrating, the phone just freezes, then reboots and loads up. Progressively getting worse and just gets hotter and hotter which seems to throw it off more. With the exception of a Software problem from the update (Damaged O/S and/or Bootloader), I'm starting to think the phone may be damaged. I've dropped it a fair share of times, but it's in a case :cyclops: so shouldn't be too bad
What I've done so far
- Cleared cache via Recovery Mode, this temporarily fixes it, the phone boots up again normally, but randomly freezes and reboots again
- Booted phone in safe mode - same problems
- Factory Restore --> Phone restores, but even when installing the apps again in goes through 3/4 reboots
I've enabled Dev Options and USB Debugging (and also OEM Unlock). If I try flashing with ODIN I just get a SW Check Revision failed message.
When the phone gets stuck in it's boot, it just displays the initial "Samsung Galaxy S7 Android" screen and nothing else, the occasional Samsung loading screen, but that sometimes freezes too. The times when I can get into the recovery mode, I've looked at the last log files, and there's sometimes errors relating to /mnt and a couple of directories, but I don't know enough about the O/S to troubleshoot and sometimes it fails to get into Manual Mode, I'll see if I can get photos of the last log file. The reboot reason is UNKNOWN
I've installed ADB, when the phone is loaded up into Windows, and I use adb devices it shows up. When I go into download mode, it says "List of attached devices" and then shows nothing. So I'm assuming it's a different issue, otherwise it wouldn't work in windows either
Bit stumped now. The phone isn't rooted, I'm not bothered about losing data, since I backed it up the first time I factory restored, so there's nothing valuable on there. I'm just getting tired of factory restoring it, since I don't think that's the problem. I'm thinking either the Factory Restore image is damaged or the phone is.
Any suggestions would be appreciated.
Phone is UK Based on Giff Gaff network. These are the files I'm trying to use to flash it
The option isn't ticked in ODIN (3.14.4) to Wipe Partition either
AP_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship_meta.tar
BL_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship.tar
CP_G930FXXU4ESAE_CL987828_QB11799217_SIGNED.tar
HOME_CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
I read somewhere if I use this file it wipes the data. So haven't tried this
CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
GrabAndSmash said:
Been having problems a while now, they've been progressively getting worse. Seemed to happen after an update.
Basically the phone freezes and reboots. Can be anything, unlocking, playing games, opening internet browser, opening gmail. Just frustrating, the phone just freezes, then reboots and loads up. Progressively getting worse and just gets hotter and hotter which seems to throw it off more. With the exception of a Software problem from the update (Damaged O/S and/or Bootloader), I'm starting to think the phone may be damaged. I've dropped it a fair share of times, but it's in a case :cyclops: so shouldn't be too bad
What I've done so far
- Cleared cache via Recovery Mode, this temporarily fixes it, the phone boots up again normally, but randomly freezes and reboots again
- Booted phone in safe mode - same problems
- Factory Restore --> Phone restores, but even when installing the apps again in goes through 3/4 reboots
I've enabled Dev Options and USB Debugging (and also OEM Unlock). If I try flashing with ODIN I just get a SW Check Revision failed message.
When the phone gets stuck in it's boot, it just displays the initial "Samsung Galaxy S7 Android" screen and nothing else, the occasional Samsung loading screen, but that sometimes freezes too. The times when I can get into the recovery mode, I've looked at the last log files, and there's sometimes errors relating to /mnt and a couple of directories, but I don't know enough about the O/S to troubleshoot and sometimes it fails to get into Manual Mode, I'll see if I can get photos of the last log file. The reboot reason is UNKNOWN
I've installed ADB, when the phone is loaded up into Windows, and I use adb devices it shows up. When I go into download mode, it says "List of attached devices" and then shows nothing. So I'm assuming it's a different issue, otherwise it wouldn't work in windows either
Bit stumped now. The phone isn't rooted, I'm not bothered about losing data, since I backed it up the first time I factory restored, so there's nothing valuable on there. I'm just getting tired of factory restoring it, since I don't think that's the problem. I'm thinking either the Factory Restore image is damaged or the phone is.
Any suggestions would be appreciated.
Phone is UK Based on Giff Gaff network. These are the files I'm trying to use to flash it
The option isn't ticked in ODIN (3.14.4) to Wipe Partition either
AP_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship_meta.tar
BL_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship.tar
CP_G930FXXU4ESAE_CL987828_QB11799217_SIGNED.tar
HOME_CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
I read somewhere if I use this file it wipes the data. So haven't tried this
CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
Click to expand...
Click to collapse
Hello the SW Check error means the firmware your trying to flash is older than the firmware already on device. You can only flash the same or up, never down.
The firmware you've posted is quite old. The unbranded original for United Kingdom you need is BTU. I linked it off Sammobile but if you know how to use Sam Firm tool you can get it much faster direct from Samsung.
If problems persist after flashing this, then yes it's a hardware problem.
https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXS8ETC1/327922
cooltt said:
Hello the SW Check error means the firmware your trying to flash is older than the firmware already on device. You can only flash the same or up, never down.
The firmware you've posted is quite old. The unbranded original for United Kingdom you need is BTU. I linked it off Sammobile but if you know how to use Sam Firm tool you can get it much faster direct from Samsung.
If problems persist after flashing this, then yes it's a hardware problem.
https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXS8ETC1/327922
Click to expand...
Click to collapse
Thanks,
I've got the SamFirm download tool because I was irritated waiting for the download, I'll try downloading and flashing it.
Should I flash the lot, or just one specific thing?
Also, I used Sam Firm to download the firmware for the phone but using the Auto Method.
What is the "Version" I need to enter based on SamFirm, is it listed somewhere, or is it the phone itself? G930FXX8ETC1 ?
GrabAndSmash said:
Also, I used Sam Firm to download the firmware for the phone but using the Auto Method.
What is the "Version" I need to enter based on SamFirm, is it listed somewhere, or is it the phone itself? G930FXX8ETC1 ?
Click to expand...
Click to collapse
You don't need to specify a version just put in SM-G930F, then BTU in region. It will automatically find the correct firmware for download.
Download, let it do its checks. A zip file with 5 files inside, 2xCSC, only one goes in Odin. CSC_home will keep files and settings on device but can often cause problems. I alsway use just CSC for a clean install. Obviously put the other files where they need to go too.
Sorry yes, flash all files, you'll have a clean new phone.
First boot can take about 5-10 mins, and the updating, erasing screens are normal.
cooltt said:
You don't need to specify a version just put in SM-G930F, then BTU in region. It will automatically find the correct firmware for download.
Download, let it do its checks. A zip file with 5 files inside, 2xCSC, only one goes in Odin. CSC_home will keep files and settings on device but can often cause problems. I alsway use just CSC for a clean install. Obviously put the other files where they need to go too.
Click to expand...
Click to collapse
Thank you, I managed to figure it out, I'm sure it's what I did last time, not sure if it just picked up the wrong version somewhere. IT seems to match the info in your post anyway.
I don't give a toss about the data since I'm over writing it all anyway. Do I still ignore the option to wipe the partition in ODIN, or should that be included to?
GrabAndSmash said:
Thank you, I managed to figure it out, I'm sure it's what I did last time, not sure if it just picked up the wrong version somewhere. IT seems to match the info in your post anyway.
I don't give a toss about the data since I'm over writing it all anyway. Do I still ignore the option to wipe the partition in ODIN, or should that be included to?
Click to expand...
Click to collapse
Leave the default options already ticked in Odin. You don't need to change anything there.
cooltt said:
Leave the default options already ticked in Odin. You don't need to change anything there.
Click to expand...
Click to collapse
Thanks,
Just finished flashing the image now, so going about the restore process to see if it's fixed it or not.
(still think it's buggered though, my phone froze/rebooted even when doing android config)
If needed I'll just keep using it in a semi-working state until I buy a new one and put up with it
EDIT - Just froze / rebooted configuring the main O/S after connecting to google account. New phone time by looks of it
Only other possible thing I can think of is the battery. There were alarms in the log file and the phone does reboot more when it gets hot. Given the phone is 4 years old now, I wonder if the battery is damaged and the phone is having a hissy fit
GrabAndSmash said:
Thanks,
Just finished flashing the image now, so going about the restore process to see if it's fixed it or not.
(still think it's buggered though, my phone froze/rebooted even when doing android config)
If needed I'll just keep using it in a semi-working state until I buy a new one and put up with it
EDIT - Just froze / rebooted configuring the main O/S after connecting to google account. New phone time by looks of it
Click to expand...
Click to collapse
Yeah look like battery overheating making it reboot
cooltt said:
Yeah look like battery overheating making it reboot
Click to expand...
Click to collapse
I'll give it a try for now, I've got the correct files for flashing it at least this time thanks, I''ll try replacing the battery in the future, and if I find out it fixes the problems I'll update the post. Or if I figure out what's causing it
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