Database Info

[Q] Unable to factory reset

Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section

Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).

I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.

Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App

Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?

I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.

I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back

Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.

rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything

DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty

I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric

Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App

rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.

Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.

[Q] Did I buy a bricked Nexus S

I bought a Nexus S from craigslist last night and it was out of juice. The seller was like oh bring it back if it doesnt work and I fell for it! I have the box/manuals/charger and everything so the phone was not stolen. When I put it on charge and turned it on this morning all that comes on the screen is google and a unlocked padlock on it. I thought that I can restore it. Went to the recovery mode by pressing volume up an power switch and tried reboot/recover and power off and they all lead to the same screen. volume down and power leads to nothing. So I called the seller and his phone keeps saying its disconnected. I realize I should have been more careful.
Now I am wondering if there is a way to restore the phone as I think that the seller messed up trying to mod the phone and there is no OS on the phone. Does anyone know how to fix this problem? I tried installing various recoveries and nothing seems to work since I cannot get super user to load nor can I boot up the phone to the OS. Please help a noob!

What is that "same screen" you are talking about? If it's the Droid with a "!" then you have to press vol up + power again to activate stock recovery.
Since you can access fastboot you should be able to flash a new recovery with adb.
Download the cwm recovery image, put it in /tools folder, run adb in cmd prompt, command is "fastboot flash recovery <recoveryimagename>.img", after that you can mount the internal storage via cwm recovery, copy any rom you like onto it, then "install from zip". I'd also format all parts of the phone once (mount and storage) and wipe dalvik cache (wipe) before you flash the new rom.
If it all doesn't help put the phone into download mode (vol up + vol down and then plug in usb cable while holding those two buttons), samfirmware.com has files (Odin) for the i9020 and i9023 (not NS4G yet).
In case your pc/laptop misses USB drivers you can find a guide on how to install adb and the drivers on unlockr.com.

even easier then that, just download the one click root (the gsm version for gsm or the ns4g one for cdma). turn the phone off then boot it back up by holding volume up and power. this will get you into fastboot, from there run the one clicks until it starts to do stuff to your phone, you may need to boot into fastboot mode again at some point. but it will get you a custom recovery loaded up from there you can download a custom rom and flash it in recovery and have a fully working phone
sounds liek the guy tried to root it and messed up something so he sold it privatly seeing as he couldnt figure it out. his loss is now your gain
the phone as you describe it is fully recoverable (dont use odin as its rather risky if you dont know what to do with it, not when you have things like fastboot or recovery mode)

mitrals said:
So I called the seller and his phone keeps saying its disconnected. I realize I should have been more careful.
Click to expand...
Click to collapse
If you were interested in getting in touch with the seller, try calling that number from another phone. You have been Google Voice blocked.
However, your issue is easily fixed I think and this shouldn't be needed.

rentaric: It keeps going back to the screen that says Google and has a unlocked padlock at the bottom center. I tried doing the recovery by the following link: http://forum.xda-developers.com/showthread.php?t=1007782 (The phone is unlocked as it states in Lock State-Unlocked). I was able to finish part 3 as well. In part 4 I get stuck at step #8, where pressing recovery gets me back to Google and unlocked padlock screen. I repeated the procedure multiple times and always get stuck at part 4 step 8. I am trying to get samfirmware going after I try one click root. Will post results.
shabbypenguin: I will download one click root and see where that takes me. I also think there might be some water damage to the phone as the strip on the phone is red and at times buttons dont work.
t1n0m3n: I called the seller from 5 different numbers (US and Canada numbers) and it says the line is disconnected for all numbers. I think he disconnected his phone.
Other notes: Phone looks in great condition so if I can get it running it would be awesome. I paid $250 for it thinking its a great price if the phone worked. Attached is the picture of what the phone does on start up.

are you sure you were able to flash the recovery correctly? does the md5 match? maybe try re-downloading the file?
fastboot flash recovery recovery.img
make sure you are using the recovery specific to your device (NS, NS4G)

Where do I find the MD5?
Here is what the phone says on the bootloader mode:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 16
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020UCKD1
CARRIER INFO - ATT
SERIAL NUMBER - 31310A98550B00EC
LOCK STATE - UNLOCKED
And the rest..
Please let me know if anyone can help! Thank you

Are you rebooting the phone after installing the custom recovery (part 3, step 5)?
If yes, skip the rebooting part and go directly into recovery from bootloader screen. In case it works you can continue to mount the usb storage, copy a ROM on your sdcard, unmount, then go back to "Install from zip" after doing all 3 wipes available in "wipe" menu.
If no, then I have no further ideas then using Odin.

Same issue for me, maybe this phone got the NAND Flash problem. Warm it up then try to turn on your Nexus, it worked for me but I sent my Nexus last week to Samsung for repair.
There is a thread in Google Mobile Help Forum (google.com) in Help forum > Google Mobile > Android Devices > Android Applications (not listed above)
Sorry but i can't post the link.
Regards.

I am having the same exact problem with my phone. The only difference is that my Nexus is a sprint phone. Were you able to get your phone working and how did you do it?
---------- Post added at 05:27 PM ---------- Previous post was at 05:15 PM ----------
Im having the same problem with my phone. I have a nexus s and I think I need to flash [RECOVERY] clockwork because it says "fastboot mode - No boot or recovery img." Im using a mac but I cant seem to get it working. Can someone help me. I cant seem to figure out what to do and where to start.

Stuck at Boot Logo and no Recovery Mode

Hi all,
So I got soft bricked Samsung Galaxy S6.
Here are the issues:
- The person got it when he tried to root it
- Stuck in boot logo (Samsung S6, Powered by Android) and does not go further
- I can flash original firmware (Vodafone, Australia) through ODIN successfully, but the problem remains
- Cannot access recovery mode, tried to flash both stock recovery and custom (TWRP, all versions available at twrp.me)
- Have tried both Kies3 and SmartSwitch, emergency recovery went smooth, flashed successfully, but the problem remains
- After each successful flashing, I try to boot into recovery mode in order to clear cache, but it does not boot into recovery at all
- Tried all versions of ODIN and used all cables at home
- Another strange behavior, it can power on only when it is connected to cable. So it either stuck or can boot into Download mode when I press combination. But if I disconnect, after some time it switches off and cannot power on unless you connect it to the cable. Does it mean that the person ticked NAND erase as it is also related to energy dependency of the memory? I don't believe it to be battery issues as I saw this issue on another phone too (Samsung A9)
It is weird. I just want to understand, why I am not able to boot into recovery mode even after successful flashing stock ROM?
Any help is appreciated

Hi, I too have similar issue. Would like to know how you got it resolved.

tanzeeb210 said:
Hi, I too have similar issue. Would like to know how you got it resolved.
Click to expand...
Click to collapse
I could not solve it. Sold the phone for spare parts
Seems like motherboard issue

oscar_ferreiro said:
I could not solve it. Sold the phone for spare parts
Seems like motherboard issue
Click to expand...
Click to collapse
its seems like battery issue more for me than the board!
you should replace or disconect her first before selling the device... could worth the try...

oscar_ferreiro said:
Hi all,
So I got soft bricked Samsung Galaxy S6.
Here are the issues:
- The person got it when he tried to root it
- Stuck in boot logo (Samsung S6, Powered by Android) and does not go further
- I can flash original firmware (Vodafone, Australia) through ODIN successfully, but the problem remains
- Cannot access recovery mode, tried to flash both stock recovery and custom (TWRP, all versions available at twrp.me)
- Have tried both Kies3 and SmartSwitch, emergency recovery went smooth, flashed successfully, but the problem remains
- After each successful flashing, I try to boot into recovery mode in order to clear cache, but it does not boot into recovery at all
- Tried all versions of ODIN and used all cables at home
- Another strange behavior, it can power on only when it is connected to cable. So it either stuck or can boot into Download mode when I press combination. But if I disconnect, after some time it switches off and cannot power on unless you connect it to the cable. Does it mean that the person ticked NAND erase as it is also related to energy dependency of the memory? I don't believe it to be battery issues as I saw this issue on another phone too (Samsung A9)
It is weird. I just want to understand, why I am not able to boot into recovery mode even after successful flashing stock ROM?
Any help is appreciated
Click to expand...
Click to collapse
Same issue here, any idea to solve that? (I'm Brazilian, sorry for some typing wrong)
I don't opened the device (yet), but if is a battery issue, someone tried to fix?
My device is SM-G920I, i tried to flash this FW: G920IDVU3FQD1_G920IXSA3FQC3_XSA without sucess, i will try with a "pit" file that i've found here on XDA and update here, but until the moment, the problem remains
Update: The PIT file does not solved the problem, after this I decided to open the device and swap the battery, but the problem remained, i'm buying a new board today, i think this board can't be saved

I've had similar problem with my Note4. It would sucessfuly apply firmware via Odin but refuse to boot. (tried multiple times)
I then did a flash via SmartSwitch (takes forever) but the phone worked again.

any update for this ? i have the same issue

Hi, I've had a rooted android for a couple of years now. Today I wanted to run the new Magisk root so that I could use apps that prevent rooted phones from using them. Following the instructions here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I went to SuperSU and clicked 'Wipe Root' which then sent my device into constant bootlooping.
I can only get the blue screen saying 'Odin Mode' and a big down arrow saying 'Downloading... Do not turn off target' or a constant bootlooping.
I followed the instructions here though when I have put the four BL, AP, CP and CSC files and click Start, all that happens is in the log on the left it says: <OSM> All threads completed . (succeed 0/ failed 0). From what I can make out, the Odin software on the laptop is not communicating at all with the Samsung S6 in Download mode.
Could someone please help!

bestfootie said:
Hi, I've had a rooted android for a couple of years now. Today I wanted to run the new Magisk root so that I could use apps that prevent rooted phones from using them. Following the instructions here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I went to SuperSU and clicked 'Wipe Root' which then sent my device into constant bootlooping.
I can only get the blue screen saying 'Odin Mode' and a big down arrow saying 'Downloading... Do not turn off target' or a constant bootlooping.
I followed the instructions here though when I have put the four BL, AP, CP and CSC files and click Start, all that happens is in the log on the left it says: <OSM> All threads completed . (succeed 0/ failed 0). From what I can make out, the Odin software on the laptop is not communicating at all with the Samsung S6 in Download mode.
Click to expand...
Click to collapse
Had to come back and add on to my previous post - I sorted it. It was simply a driver issue... Make sure you download all the correct Samsung USB Drivers people if you're having similar issues...
I finally restored my Android to Stock Android (albeit the latest Android system 7.1).

G955FD Softbricked. OEM Unlock is Disabled.

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

Stock-S7 freezes on startup after Oreo-update (full wipe, different stock ROMs)

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!