Related
Hello,
I've bricked my Note 10.1 after updating to the official Kitkat (N8010XXUDNE4_N8010OXXDNF1_HOME.tar.md5). I did a wipe data and cache and all seemed to be working fine for 2 days... but the tablet got stuck on a game and after a force close has been stuck in a bootloop with no access to recovery mode. I do manage to get into download mode and have tried to flash a number of times with different roms (going back seems to be impossible with KitKat) but to no avail as I keep getting an issue about 'no PIT partition'. I took it to a shop (as my warranty ran out a month ago - lucky me!) and they were also unable to flash the tablet so the issue does not seem to be the cable or the drivers (as Odin recognizes the tablet). I tried flashing with a PIT file (ticking re-partition with and without the kitkat rom) that I got on some website but I'm not certain it is the right one for my GT-N8010 and it also fails. Before I try a Nand erase I want to make sure that I have the right PIT file. Does anybody please have a secure PIT file for the GT-N8010 16GB bought in France? By the way does the PIT file you have work with KitKat as the one I found seems to be for an outdated version of Android and as Kitkat doesn't enable one to go back to an older version of Android I'm in a catch 22 with only the Nand erase option left?
FYI, I tried flashing a recovery like TWP to try flashing custom roms but it also doesn't work.
Any other ideas? Should I tick Nand Erase and Phone EFS Clear. As the issue seems to be the kitkat bootloader is it possible to flash a bootloader? Can't find any trace of anything other than the tar files for GT-N8010 in Jelly Bean or KitKat. Anybody have a bootloader, PDA, CSC and Phone file for the GT-N8010? Can one attempt the following on a GT-N8010: http://forum.xda-developers.com/show...2610757&page=2 ?
Thanks for any help as I've been without my tablet for weeks now!!:crying:
Same issue with my N8013. When I try to just flash a new recovery or a stock rom(that took me forever to find because neither of the 2 recommended sites had them) I get a PIT error. I managed to find a PIT file on here, but when I try to flash that I get a error message. I can past my ODIN log if needed, but I'm curious as what I should do as I don't want to NAND ERASE quite yet. I was just watching a youtube video and the tablet froze, waited like 30mins and it finally rebooted, and then gave me bootloop, then just went to a white screen all togeher after I let the battery die out. I can get ODIN mode and that's it. Tried multiple versions of ODIN to no avail. Multiple usb ports and pcs also.
onlysafonne said:
Same issue with my N8013. When I try to just flash a new recovery or a stock rom(that took me forever to find because neither of the 2 recommended sites had them) I get a PIT error. I managed to find a PIT file on here, but when I try to flash that I get a error message. I can past my ODIN log if needed, but I'm curious as what I should do as I don't want to NAND ERASE quite yet. I was just watching a youtube video and the tablet froze, waited like 30mins and it finally rebooted, and then gave me bootloop, then just went to a white screen all togeher after I let the battery die out. I can get ODIN mode and that's it. Tried multiple versions of ODIN to no avail. Multiple usb ports and pcs also.
Click to expand...
Click to collapse
I believe our problem is all related to this bloody blocked Kitkat bootloader. If Samsung go down the Apple path by blocking its system then they can say goodbye to many of their customers!
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).
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 ...
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
philipp-h said:
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
Click to expand...
Click to collapse
Philip, it helps if you let us know what country your in.
Anyway the solution to your problem is pretty straight forward, you just need to flash the latest firmware for your region with Odin. No need to mess about with TWRP at this point.
Official firmware will contain a copy of the stock kernal which will also be installed when you flash with Odin 99% of the time. If for some reason the kernal is not flashed (it happens) and you continue to get the reboot issue then you will need to flash the kernal seperately first with Odin then the firmware afterwards.
The issue with the FRP lock will remain after this but should allow you to unlock with google email and password.
So we're talking, downlaod mode, flash official fimrware and go from there.
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
philipp-h said:
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
Click to expand...
Click to collapse
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
cooltt said:
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
Click to expand...
Click to collapse
Hi cooltt and thanks for your help!
Unfortunately the BTU-ROM did not solve the freeze-reboot-problem but led to another: After flashing the phone gets stuck with a blue screen "Erasing". After several hours I force rebooted and now it is showing a similar screen with "Error!" and a percentage which is increasing to a random number from 0% to 12% on each boot. On first boot it shows the boot screen ("Galaxy S7"), then "Installing system update" shortly and then "Erasing". After force-reboot it shows boot screen, "Erasing" then "Installing system update", both for a very short time (sometimes misses "Installing...")
As suggested I used SamFirm to download the newest BTU-ROM (SM-G930F_1_20191218140415_dgobhw6g3v_fac; G930FXXS7ESL5/G930FOXA7ESL5/G930FXXS7ESL5/G930FXXS7ESL5). I just ticked F. Reset Time and Reboot. Re-Partitioning did not change anything. Using Odin v3.13.1 does not make a difference. The other ROMs, like SM-G930F_1_20191226131628_8ds2p6kf0v (G930FXXS7ESL9/G930FDBT7ESL9/G930FXXS7ESLA/G930FXXS7ESL9) which I downloaded with Frija (should do the same: download enc4-files from Samsung and decrypt) make the phone going to the initial setup fine, but with the reboot-problem. Tried also with Odin 3B patched.
At this point I was going to write, that I could not access the recovery mode with the BTU-ROM but just now I started it unintentionally when looking for the sequence of screens showed on boot. So I used my chance, made a full wipe and screenshot. After this the phone booted until the glowing "Samsung"-logo appeared. Then rebooted and went to initial setup (after "Androi"Installing applications") in German. The freeze-reboot-issue appears as with all the other ROMs.
The phone is certainly an original SM-930F as it was bought directly from a big, trustworthy dealer and then just used by my aunt. The only one touching it when problems appeared was me. There is SM-G930F printed on the backside and showed in download mode.
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
philipp-h said:
Hi cooltt and thanks for your help!
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
Click to expand...
Click to collapse
Hi Phill
The only options checked in Odin should be F-Reset and Auto reboot. Don't check any others.
The blue screen erasing and updating is normal after a flash with Odin, the phone will restart a couple of times, just leave it do it's thing for a bout 10 minutes or so. If it's any longer than that as you have mentioned then it's stuck as you've said.
So we're going to start from the begining again but do something slightly different.
1. Place the phone into download mode
2. Run Odin but uncheck "Auto Reboot" so the only option checked is F-Reset Time.
3. Use whatever firmware you want, BTU or DBT the latest version. Make sure files are in the correct boxes.
4. Connect phone and flash with Odin, wait until Odin says "succeed 1" and "dissconnected" . It may even say "pass" in green, not important but "succeed 1" is important.
5. Your phone will show the bar and do not disconnect. So....disconnect from laptop / PC. The screen should remain "do not disconnect".
6. Hold volume down+home+power (in that sequence).
7. As soon as the screen goes black move your finger to volume up, while still holding down home + power. You are trying to get the phone into Recovery mode as you said earlier.
8. The option to choose in the recovery menu is "wipe cache partition" NOT "wipe/factory reset". I can see from your pictures that this option has failed because the FRP lock is still on!!
9. When you've chosen "wipe cache partition" then choose "reboot system now"
The phone should go through it's normal set up routine, erasing, update, installing apps etc, just leave it do this and hopefully the phone will boot then ask for the Google email and password which was used on the phone.
There are very few reasons for the phone to get stuck on boot....
1. Incorrect firmware,
2. Water damage
3. The phone has been Rooted with FRP lock on. It is very rare to be a hardware issue.
You should always turn FRP lock off and enable OEM unlock in settings before flashing to a phone. I know it's a little late for that but something to remember.
To check for water damage.
1. Remove SIM card and holder
2. Shine a light in the hole, you will see a WHITE sticker which turns PINK if water has ever got inside the phone.
Thanks a lot again for your great efforts!
I tried as you wrote but did not manage to start recovery immediately after flashing (tried >10 times). But after some while the BTU-ROM started and now keeps doing so even after new flash without wiping cache afterwards. Wiping data worked for me in past when I sometimes had enough time to enter Wi-Fi-password. It was saved even after reboot and away when I did data wipe in recovery. With the newest ROMs I never got beyond typing Wi-Fi credentials.
I cannot see a water damage. A root was never tried before (and OEM-lock and FRP were always on because stock, which is very bad now ). Would be absolutely no problem if this !#@*#% stock ROMs would work... TWRP installation was directly blocked when I tried my luck as last resort. I did not try other images.
Thanks nevertheless for your time and patience!
Hi. I'm looking for some help after exhausting every suggestion I can find on the web.
Background to the problem (this goes back to last September so my recollections might be a bit vague):
1. My SM-G930F (with custom ROM) started overheating.
2. I took it to my local Samsung store (first mistake) who ran diagnostics and said the battery need to be replaced.
3. I paid to have the battery replaced and collected the handset from the store where everything appeared to be working.
4. 100 yards from the store, the handset rebooted. This continued every few minutes.
5. Returned to the store who said "Nothing to do with us mate, it was working when you left".
6. After many escalated communications with Samsung support, they collected the handset, ran some other diagnostics, and returned the handset stating that the main board had failed and would cost hundreds of pounds to replace.
7. I decided to spend my money on a heat gun and a second hand main board (from a well known auction site). Replacement went well and everything was working fine. It was a UK Stock ROM, but I can't remember which.
8. I then made my second mistake, I installed TWRP and performed a full restore (including the EFS partition) from the backup I'd taken of the previous main board. The handset booted into my custom ROM OK but the IMEI was blank and the SIM no longer worked.
9. I then made my third mistake, I used ODIN to install the latest stock ROM at the time (PDA G930FXXS6ESGD / CSC G930FXEU6ESGD from sammobile.com) which updated the bootloader. The installation completed successfully but somehow triggered the FRP lock and boot loops.
Current status:
1. Stock ROM boot loops. I just get the yellow triangle containing an exclamation mark and the message "Error!" (I don't get the "No Command" message).
2. I can't install any custom recovery / ROMs / etc. due to FRP.
3. All I can really do is boot the handset into "Download Mode". Can't get into "Recovery Mode". Smart Switch reports "Unrecognized device".
I believe my only option is a U6 combination ROM to clear the FRP and repair the IMEI, but it looks like this has yet to be released.
Questions:
1. I'm not sure what "Error!" means. I can't find anyone else reporting it. Does anyone know?
2. As it's been a year since the U6 bootloader was released, is a U6 combination ROM likely to ever be released?
3. Is anyone aware of any free options to resolve my problem without a combination ROM?
4. I've spent hours and hours trying different tools / methods to fix the handset, all to no avail. Do I just bite the bullet and buy another main board?
Many thanks in advance for any advice. Much appreciated.
tibbsbrookside said:
Hi. I'm looking for some help after exhausting every suggestion I can find on the web.
Current status:
1. Stock ROM boot loops. I just get the yellow triangle containing an exclamation mark and the message "Error!" (I don't get the "No Command" message).
2. I can't install any custom recovery / ROMs / etc. due to FRP.
3. All I can really do is boot the handset into "Download Mode". Can't get into "Recovery Mode". Smart Switch reports "Unrecognized device".
I believe my only option is a U6 combination ROM to clear the FRP and repair the IMEI, but it looks like this has yet to be released.
Questions:
1. I'm not sure what "Error!" means. I can't find anyone else reporting it. Does anyone know?
2. As it's been a year since the U6 bootloader was released, is a U6 combination ROM likely to ever be released?
3. Is anyone aware of any free options to resolve my problem without a combination ROM?
4. I've spent hours and hours trying different tools / methods to fix the handset, all to no avail. Do I just bite the bullet and buy another main board?
Many thanks in advance for any advice. Much appreciated.
Click to expand...
Click to collapse
The original problem was the battery which is common now as they don't last forever. The solution is to change the battery as you did but the main board was already damaged at that point. Repair versus cost in this case is too high hence them telling you to go away and buy a new phone.
Buying a new board is great but you have to ensure the connected Google account has been signed out of for that device.
You tried to overwight the EFS with your data, that's when it got into a real mess as the FRP lock prevents this.
Which brings me to the yellow exclamation mark, it means the bootloader file is missing or corrupt and thus the firmware cannot start. This would make sense because now the EFS partition is also corrupt from earlier.
There isn't going to be a new release of the combination ROM as the S7 is an old device and the devs have moved on from it.
Solution (but no gurantees)
Nand erase whole device, all partitions including EFS.
Flash stock fimrware, if phone boots the IMEI will be blank
Flash TWRP
With TWRP flash your EFS back up from original mainboard which was damaged
Pray that it works, if not then i'm sorry but the phone is now with the angels.
Thanks for the response.
You are referring to the "Nand Erase" option in Odin, yeah?
Will flashing the stock firmware re-create the partitions, or would I have to re-create them first using a PIT file?
tibbsbrookside said:
Thanks for the response.
You are referring to the "Nand Erase" option in Odin, yeah?
Will flashing the stock firmware re-create the partitions, or would I have to re-create them first using a PIT file?
Click to expand...
Click to collapse
Hello, yes nand erase in Odin.
PIT file is included in the firmware no need to extract and falsh seperately
Tried flashing various stock ROMs with the "Nand Erase" option checked.
Although the phone spends a long time "erasing" after the flash completes successfully, it still eventually just boot loops with the same "Error!" message.
Thanks for the advice anyway.
I will be performing the last rights on the handset later