How I bricked (and unbricked) my tablet SM-T820 due to OEM Unlock setting and battery drain - I hope this is useful for someone making the same mistake! I successfully rooted my Tablet S3 T820 with TWRP 3.2.1-1 and Magisk and installed SM-T820 Tweaked without any problem the moment I received it - it's a great daily driver!
While fiddling to fix an app crashing due to safetynet issues, I unchecked OEM-Unlock and forgot about it. The tablet ran out of power and upon reboot gave an FRP boot error "Security Error: This device has been flashed with unauthorized software & is locked. Call your mobile operator for additional support...". Any attempt at booting into TWRP was FRP blocked I guess because of the locked Bootloader. I immediately tried doing a stock firmware restore etc. via ODIN which failed at about 65%, probably due to a low battery (which I didn't know as there was no way of seeing the battery status). Upon reboot I had a screen saying "use the emergency recovery function in the smart switch PC software". When I tried reflashing stock firmware through Odin again, the tablet connection kept disconnecting/dropping out every 10 seconds or so and restarting always going back to the same “use smart switch” error message. The same happened in Download mode. I now know this was due to a drained battery. I couldn't power off the Tablet in order for it to charge as it always switched on as soon as power was connected.
The fix: I noticed when in the error boot screen "use smart switch to recover" it didn’t charge at all (I had it plugged in for 8 hours) and always cut out and rebooted to error msg. every 10 seconds. The first time I managed to stop it cutting out was by booting into Stock Recovery Mode with "Home & Vol+ & Power" buttons while plugged into the wall socket (stock recovery must have installed just before Odin failed the first time I tried to unbrick). I had it plugged into the wall socket in Recovery Mode for about 2 hours where it very slowly charged a tiny bit. In stock recovery I booted into "Reboot Bootloader" where it went directly to Odin Mode saying “Downloading... Do not turn off target”. I then reflashed my firmware without any errors. After first boot the battery was still only on 1%! I again have a brand new, functional Tablet! Now back to Rooting . . . and never touching oem-unlock again!
Hello i hope you can help me, same mistake but i cant find the correct firmware. originaly it has the android 7.0 ara2, but later i flash the SM-T820 TWEAKED Based on latest stock BRJ1 firmware, and have to flash the oreo bootloader. i tried a uk BRJ1, ARA2 and others from mexico where i buy the tablet but it fails. i dont want to waste more battery so any suggestions are welcomed
Masterchivo said:
Hello i hope you can help me, same mistake but i cant find the correct firmware. originaly it has the android 7.0 ara2, but later i flash the SM-T820 TWEAKED Based on latest stock BRJ1 firmware, and have to flash the oreo bootloader. i tried a uk BRJ1, ARA2 and others from mexico where i buy the tablet but it fails. i dont want to waste more battery so any suggestions are welcomed
Click to expand...
Click to collapse
Are you using the latest Odin? 3.13.1 I think.
Sent from my [device_name] using XDA-Developers Legacy app
recovery is twrp, I can't boot to recovery and charge
Related
OK I screwed up. I would appreciate any help here. Rogers S6 Edge, G925W8. It was stock 5.0.2.
Wanted to try a ROM so flashed TWRP, then flashed Kingfisher ROM v1.1 (it seemed the safest / W8-friendly). ROM was fantastic (much better battery), but GPS would never lock.
Tried to start over by flashing stock Rogers 5.0.2 via Odin but it wouldn't flash. I read (a little too late) that downgrading isn't something Samsung enjoys. Argh!
Then out of desperation, I flashed the BL (BL_G925W8VLU2BOH8_5.1.1.tar) from http://forum.xda-developers.com/galaxy-s6-edge/general/canadian-odin-5-1-1-bootloader-twrp-t3196595 , which was a very bad move, I assume because I wasn't on 5.1.1 to begin with. Crap!!
So now the phone gets to the Galaxy S6 edge splash screen, with "KERNEL IS NOT SEANDROID ENFORCING", and it stays there. The phone also gets very warm, and I can't shut it off. Using VolDown+Power+Home reboots it (showing the same message) but doesn't shut it off. Using VolUp+Power+Home reboots it but only says the same thing about Recovery.
Please tell me that I didn't just brick this phone!!
UPDATE:
Am able to get the phone into Download/Odin mode by holding the 3 buttons (voldown+power+home) while plugging the phone into USB. The stock Rogers image refuses to flash (Odin says fail immediately), but I am a step closer thanks to @brar.arsh's thread ( http://forum.xda-developers.com/galaxy-s6-edge/general/canada-galaxy-s6-edge-canadian-users-t3069314 )
From there I grabbed the "S6 Edge Stock Firmware OG2" which comes in 4 parts (BL, AP, CP, and CSC). I added all 4 pieces to Odin and started flash. Boot.img and recovery flashed, but then during the system.img flash, it failed about half-way through. Right after that failure, something changed because the device now became "Unknown Device" to windows, and it complained that "a USB device has malfunctioned, and Windows no longer recognizes it".
This gave me hope that I could get into Recovery (since that flash was successful), but the phone likes to boot directly to the "The update failed so please launch Smart Switch" message - regardless of starting with VOLUP+PWR+HOME button combination. So no recovery access... but making progress.
I belive I initiated a flash that contained JUST the BL, CP, and CSC portions, and it passed quickly. This, of course, isn't enough to get the system going. I just wanted to see if it would fail in other areas.
Trying the emergency flash via Smart Switch: Smart Switch said it required the phone to be in Recovery mode, but it still attempted the fix even though I was in Odin/Download mode. Good news, but unfortunately it gave the same result - a failure at around 50% of the entire flash operation.
I have tried re-flashing the AP portion several times and it fails at different progressions (50%, 75%, 90%)... so close.
I was thinking that it was maybe a power issue (since the battery was completely dead during the "kernel is not seandroid enforcing" period, with no way to turn the phone off or pull battery), I wondered if the battery just needed a little juice before starting the operation. I let it stay plugged in for a few minutes after one of the many failed flash attempts (screen was illuminated with the progress bar frozen at the point of failure). I noticed that when I unplugged it, it didn't die immediately, so I plugged it back in (getting the "USB device has malfunctioned" message again), and forced it to restart by holding the VOLDOWN+PWR+HOME buttons). It got back into Odin mode and the PC recognized it again. Loaded up just the AP portion in Odin, hit Start, left the room, and when I came back it said PASS! I cannot prove that it had any battery power from this method... or if it even helped. This could have just been a fluke.
The phone automatically rebooted into Recovery mode (which scared me) so I hit Power Down.
Rebooted the phone - I hear the lame Samsung startup song, and it is booting. Hallelujah.
So I recently got a Nexus 9. I think it was affected by the battery issues with android nougat. I rooted and used greenify and got much better battery life but decided I wanted to unroot and see if over a couple days the battery life would have gotten better. So I connected to my computer and stupidly sent the "fastboot flashing lock" command and now my Nexus is stuck in a boot loop because of TWRP. I knew that locking the bootloader would initiate a factory reset but didn't take into account that TWRP may affect that so now I can not use my Nexus. The device says it is a developer edition and not intended for personal use and I don't I know what to try. Just letting everyone know I only tried to sideloading and flash. I appreciate everyone who takes the time to read this and try to help.
Have you tried following instructions from google to flash a factory image ?
https://developers.google.com/android/images
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
AUSTIZ1997 said:
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
Click to expand...
Click to collapse
Did you try booting your nexus to fast boot and execute fastboot oem unlock?
I have, it just send me an error message
Update, I was able to finally get into the custom recovery and tried to flash the stock recovery and now it just boots into fastboot mode but I got rid of the custom recovery (as far as I know) and the boot screen that said the tablet was a developer device
Same problem here in May 2017, the OTA update prompted by Google sent the device into a bootloop. As the Bootloader was locked and there was no way to change to USB debugging mode it wasn't possible to use Recovery mode or to flash an OTA. Wiped data cache, tried all options in HBoot menu, tried flashing OTAs and full block OTA didn't work either. Just stuck in bootloop.
Repair shop encountered same problems so they then suspected the logic board. They heated it up to reflow the solder and success! Logic board may fail again through dry joint but I believe this risk can't be avoided by switching manufacturer as they all use the same component-to-board soldering practice.
R3 Pro (3GB/32GB, 2015817 version) came with some chinese/sellers custom ROM (and locked bootloader). It was heavy and bloated, so I decided to update it. Tried latest global stable (fastboot) ROM via miflash, flash was successful but that's was a lie - it stuck on mi logo...
Then I tried various other ROMs, global and developers, latest and older, some xiaomi.eu, manhit, etc. (for locked bootloader) and all I've got was either just a mi logo or mi logo with "powered by android" animation beneth. I left it for hours after flash and still nothing.
Then I found some ways to flash twrp, did that successfully, booted into it, wonder around in terminal and file manager, tried some recovery ROMs - but the result is the same - just logo or logo + animation.
I can get into fastboot (but it doesn't realy matters since bootloader is locked), download (EDL) mode, that Xiaomi menu (with Power and Vol+, with "shortcuts" to all the modes, hardware tests - btw. everything works there, etc.), twrp, charge battery (with some ROMs phone just gets warm and I know it's charging, there are no LED and/or animation, but in some everything works just like it should), but just can't boot into OS.
And I'm going nuts!
Here are some logs from the last ROM (i don't even know anymore which one is it) - pastebin.com/qaKVzxue and pastebin.com/dM3nEVj0
I'm not so experienced in looking at that but seems like every other thing in there, like cpu, i2c (touch/sensor), sound, battery, etc. is broken/faulty which is not true - everything was fine before update, and everything IS still fine according to inbuilt (xiaomi) hardware tests.
So somehow it seems that all the ido ROMs I tried are wrong for this device? Or am I missing something (quite possibly, I'm tired and pissed off)
Last night I did a backup of efs/nvram and then wiped internal memory/partitions, flashed latest global ROM, restored efs/nvram - phone stuck, but this time not on MI logo but freakin' penguin logo (like here en.miui.com/thread-377870-1-1.html). Same logo is for fastboot mode, no more bunny. Then flashed twrp and phone now shows mi logo with "powered by android" animation beneath, like before...
I don't know how this works with Xiaomi phones, but looks like it worked with some factory/seller special combination of ROM and bootloader. Then I did update and something stuck, maybe differences between ROM and bootloader, or some inside/hidden security mechanism that stops boot process? And because I can't find original firmware and/or bootloader is locked (maybe even updated?) it's now stuck...
Either that or some HW fault, but it would be insane that official ROM update with official tools and in factory download mode with full battery can cause such problem!
Can you go to twrp recovery?
Yes, like I said in the first post. I can do anything but boot android/MIUI. It's either because of locked bootloader or somehow official ROM installed officialy (via MiFlash in EDL mode) bricked phone, which is catastrophic bug i.e. epic design/implementation fail by Xiaomi.
Try this
https://forum.xda-developers.com/redmi-3/help/bootloop-bootloader-locked-options-t3331139
Sorry to intrude, I have pretty much the same problem.
Phone is stuck in bootloop and I can only access fastboot mode and EDL mode (but in EDL the phone does not connect to pc) and when I try to flash a stock ROM (since I know it is a software issue due to an unfortunate update) it says "locked device". So I tried to unlock it via MiUnlock... but phone cannot be verified 'cause "account not bound to this device" and obviously I cannot change any options since I cannot use my phone.
Please, help
it was happened to me about 3 days ago when i play around with the twrp & rooting thingy... tried everything from youtube to various forum solutions... just one link really works when you only have fastboot options and your phone bootloader is still unlocked. just follow the steps in the OP... key things here is downloading the tool to read your phone as mentioned in the OP i.e [TOOL]Minimal ADB and Fastboot [1-6-17]
1) Download Tool -> https://forum.xda-developers.com/showthread.php?t=2317790
2) Follow all the steps in the OP -> http://en.miui.com/thread-277276-1-1.html
3) Enjoy your phone from back from the dead.. LOL!
4) Remember here, the key is NEVER GIVE UP and PATIENT!
NOTE : The Device will start, wait till completion , it can take up to 10 Minutes. -> for me around 15-20 minutes for I have flashed the current beta rom of MIUI8 7.6.8
cheers, guys!
blx-
I had a similar situation.
Officially unlocked boot loader. Flashed TWRP using fastboot. Only got the mi logo and a boot loop on start up.
Could not turn on. Could not boot into TWRP.
When the phone was boot looping I could still get into fastboot mode by holding power+volume down.
I booted from fastboot mode into TWRP by opening the command prompts and using
"fastboot boot twrp2.img"
That got the phone available from windows explorer. I was able to move a new ROM image to the SD card and install from TWRP.
Currently running lineage 14.1 -20190112.
I lost a bunch of **** but my phone seems to turn on for the moment.
Note, I still cannot boot into TWRP using the phone only. I can only boot in from fast boot as above.
Hello,
I have a Samsung Galaxy SM-J320M with Android 5.1.1 which I have successfully rooted (installing SuperSU via TWRP).
Everything works OK except when the phone runs out off battery and switches off: when I plug the charger and try to turn it on, I get "Custom binary blocked by FRP lock" message.
This doesn't happen if I turn off the phone normally or long pressing power button or pulling the battery out, only when it self turns off because of battery low state.
I have always been able to recover the phone by reflashing stock firmware (via ODIN), and then rooting it again (always same procedure: enable OEM unlock, flash TWRP, flash SuperSU).
I would like to ask if anybody knows a way to prevent this from happening again. As a workaround, I try to have the phone charged before the battery dies, but sometimes it is not possible. I'm worried of this happening on a trip out of home with no access to a computer for reflashing.
Thanks.
Hello dear users of xda.
I have read alot of threads on several forums to find a fix for my broken phone, since I am hoping that the problem is caused by the software, rather than the hardware.
Sadly I was not able to find the fix yet and therefor you guys are my last shot at this issue. This account is also freshly registered, so I will not be able to post any links or images to help you guys out understanding what happened ... so please just bear with me here
Since I am from Germany I hope you can also excuse small mistakes regarding my writing in this thread. Thank you in advance
Lets dive right into this with a few details:
Samsung Galaxy S6 Edge (SM-G925F)
Never rooted, flashed -> always official updates
Android 7 was up to date
Phone has no branding or any kind of simlock
What happened:
My phone was turned off a few days ago when I woke up. Since I always charge it over night it couldnt be out of power and that confused me.
I then pressed the On/Off-Button to start it and the phone booted up.
But the boot did get stuck on the Samung logo-animation. I mean the animation which is usually displayed after the big "Samsung Galaxy S6 Edge powered by Android".
I waited a minute or something and nothing happened, it seemed like the boot froze up and I turned it off.
When I booted it up again the samsung animation would not even finish and then freeze up. The animation is displaying the letters from left to right and it froze this time displaying only "Samsu".
After that I plugged the phone back into the wall to charge and went to the PC to google this issue. The phone displayed around 25% battery when I plugged it in.
So apparently it was not charging this night?
Anyways ... after googling and not finding any similiar problems I tryed to boot with Safe Mode ( holding Volume Down + On/Off Button .... no success) and then downloaded Samsung Switch and all drivers needed to get a device connected to the PC.
I connected the phone to the PC with an original Samsung cable and Samsung Switch was not showing anything until I entered the Download Mode on my phone by pressing Volume Down + Home + On/Off.
Then Samsung Switch displayed that the connected device was not compatible (even though it meets all requirements).
I went to the device manager to make sure that the drivers are working and the phone indeed was showing up in the list. It also disappeared properly when I unplugged it from the PC.
After that I again tryed out to boot the phone several times. It would always freeze up anywhere within that Samsung animation.
Not knowing what to do I thought an factory reset might help out and I pressed Volume Up + Home + On/Off for several seconds when the phone was turned off.
Nothing happened. I could only boot up the phone by pressing the On/Off button alone and by doing that it always froze up. Just the Download-Mode was accessable (Volume Down + Home + On/Off).
Since I had no way to recover or reset anything by using Samsung Switch or the Recovery Mode I decided to flash an official Samsung rom on the device using ODIN.
I downloaded the following:
Odin ( v3.12.3 )
Firmware ( G925FXXU5EQK8_G925FDBT5EQK1_G925FXXU5EQKF_HOME.tar.md5 // from a german android forum, information below )
FIRMWARE INFORMATION
Model: SM-G925F
Model name: Galaxy S6 edge
Country: Germany (DBT)
Version: Android 7.0
Changelist: 10958180
Build date: Thu, 09 Nov 2017 10:08:50
Android security patch level: 2017-11-01
Product code: DBT
PDA: G925FXXU5EQK8
CSC: G925FDBT5EQK1
When I connected the phone Odin was recognizing the device and I was able to flash the firmware successfully. Odin did not display any kind of errors.
After the flash the phone was still connected to the PC since I feared it would run out of power. I know that the first boot after a flash can take a while. Since the LED was flashing while the big "Samsung Galaxy S6 Edge" logo was displayed I thought it was doing something in the background. I kept it like this (big logo, LED flashing, plugged into the PC) for over an hour and nothing did change. The device was warm but I doubted that it's doing anything since one hour for a boot, even after flashing, is way too long.
After that hour I turned it off and it instantly started to boot up again, but this time and all the other times after that it kept getting stuck at the big logo. It did not proceed into the animation like before.
I tested if I could enter the Recovery Mode at this point but it still was only able to get into the Download Mode.
The only way to stop it from trying to boot now was to get into that Download Mode, else it would just keep looping around, but not turn off by its own.
Every now and then, instead of displaying the big logo, it showed a blue screen with a yellow warning sign and the android mascot laying on the ground with "No command" beneath it. If you want to see how it looks you can google images "android 7.0 no command" and look for the full blue screen pictures.
Googling this blue screen with no command said that it can be easily fixed by wiping the data/cache from your device. But as I said the recovery mode was not showing up when I pressed the buttons for it. So a friend of mine suggested using ADB or fastboot to wipe the cache / dalvik cache.
Using both (ADB + fastboot) the device was not detected. We made sure that the drivers were installed properly. There was and there still is no way to connect to the phone with these both tools. Sadly.
After the first try of using ADB/fastboot we decided that the issue might have been the firmware I downloaded in the beginning and we used SamFirm (v0.3.6) to download the newest firmware for my SM-G925F ( G925FXXU5EQK8_G925FDBT5EQK1_G925FXXU5EQKF_HOME.tar.md5 )
This firmware appears to be the same as the one I downloaded before, but this one was slightly bigger.
This is a paste of the SamFirm window:
Checking firmware for SM-G925F/DBT/G925FXXU5EQK8/G925FDBT5EQK1/G925FXXU5EQKF/G925FXXU5EQK8
Model: SM-G925F
Version: G925FXXU5EQK8/G925FDBT5EQK1/G925FXXU5EQKF/G925FXXU5EQK8
OS: Nougat(Android 7.0)
Filename: SM-G925F_1_20171129140113_g7auy18e0c.zip.enc4
Size: 1950442496 bytes
LogicValue: 8ikzg48ul7hryauq
The flash was again successfull and still the same problem remained: no full boot.... sometimes a blue no command mascot.
After that we flashed again but with another PIT file attached. At first we got an error after the hidden.img but after changing the PIT file to this one ( ZEROLTE_EUR_OPEN_HIDDEN300M ) it worked again without any errors displayed by Odin. Apparently the PIT file we used at first did not have enough space for our hidden.img ...
We flashed that firmware several times and sometimes after the flash there would be a blue screen with an android mascot saying it is erasing, but the animation of that mascot freezes also after 10 to 20 seconds. I've kept the phone in this blue screen for several hours (up to 5h I think) since a few forum threads said that it sometimes takes very long to work and the LED was actually flashing all the time, but nothing changed.
We did not try to flash anything else because the Reactivation Lock is enabled and I have no idea how to turn this thing off w/o booting the device.
I would not mind flashing a custom firmware on the device as long as it just works again. So if this is somehow possible and might be a solution I am up for it.
What currenctly is going on with the phone:
· It only turns completly off when the power runs out.
· No button combination is working to turn it off.
· I can enter Download Mode easily but I can not enter the Factory Reset Mode.
Within the Download Mode it says:
ODIN MODE
Product Name: SM-G925F
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: On
Secure Download: Enabled
KNOX Warranty Void: 0 (0x0000)
RP SWREV: B:5 K:2 S:2
· The boot ends either up with showing an "Samsung Galaxy S6 Edge powered by Android" logo for the whole time (kept it like that for several hours, no boot)
· or with a blue screen (yellow warning sign, android mascot laying on the ground and a "no command" beneath it).
· Odin is recognizing it as a device.
· The device manager is recognizing the device.
· Samsung Switch is saying the device is not compatible.
· ADB/fastboot can not detect the device.
So ... is it possible to get this damn thing to work again or is it gone for good?
If you still got any questions regarding the current state of the phone please ask. I will try to reply ASAP.
Thank you very much for any reply you guys might throw at me.
It sounds like a hardware fault and your phone is kaput.
Interesting.I would love to open the phone to inspect it
FaKeT said:
Hello dear users of xda.
I have read alot of threads on several forums to find a fix for my broken phone, since I am hoping that the problem is caused by the software, rather than the hardware.
Sadly I was not able to find the fix yet and therefor you guys are my last shot at this issue. This account is also freshly registered, so I will not be able to post any links or images to help you guys out understanding what happened ... so please just bear with me here
Since I am from Germany I hope you can also excuse small mistakes regarding my writing in this thread. Thank you in advance
Lets dive right into this with a few details:
Samsung Galaxy S6 Edge (SM-G925F)
Never rooted, flashed -> always official updates
Android 7 was up to date
Phone has no branding or any kind of simlock
What happened:
My phone was turned off a few days ago when I woke up. Since I always charge it over night it couldnt be out of power and that confused me.
I then pressed the On/Off-Button to start it and the phone booted up.
But the boot did get stuck on the Samung logo-animation. I mean the animation which is usually displayed after the big "Samsung Galaxy S6 Edge powered by Android".
I waited a minute or something and nothing happened, it seemed like the boot froze up and I turned it off.
When I booted it up again the samsung animation would not even finish and then freeze up. The animation is displaying the letters from left to right and it froze this time displaying only "Samsu".
After that I plugged the phone back into the wall to charge and went to the PC to google this issue. The phone displayed around 25% battery when I plugged it in.
So apparently it was not charging this night?
Anyways ... after googling and not finding any similiar problems I tryed to boot with Safe Mode ( holding Volume Down + On/Off Button .... no success) and then downloaded Samsung Switch and all drivers needed to get a device connected to the PC.
I connected the phone to the PC with an original Samsung cable and Samsung Switch was not showing anything until I entered the Download Mode on my phone by pressing Volume Down + Home + On/Off.
Then Samsung Switch displayed that the connected device was not compatible (even though it meets all requirements).
I went to the device manager to make sure that the drivers are working and the phone indeed was showing up in the list. It also disappeared properly when I unplugged it from the PC.
After that I again tryed out to boot the phone several times. It would always freeze up anywhere within that Samsung animation.
Not knowing what to do I thought an factory reset might help out and I pressed Volume Up + Home + On/Off for several seconds when the phone was turned off.
Nothing happened. I could only boot up the phone by pressing the On/Off button alone and by doing that it always froze up. Just the Download-Mode was accessable (Volume Down + Home + On/Off).
Since I had no way to recover or reset anything by using Samsung Switch or the Recovery Mode I decided to flash an official Samsung rom on the device using ODIN.
I downloaded the following:
Odin ( v3.12.3 )
Firmware ( G925FXXU5EQK8_G925FDBT5EQK1_G925FXXU5EQKF_HOME.tar.md5 // from a german android forum, information below )
FIRMWARE INFORMATION
Model: SM-G925F
Model name: Galaxy S6 edge
Country: Germany (DBT)
Version: Android 7.0
Changelist: 10958180
Build date: Thu, 09 Nov 2017 10:08:50
Android security patch level: 2017-11-01
Product code: DBT
PDA: G925FXXU5EQK8
CSC: G925FDBT5EQK1
When I connected the phone Odin was recognizing the device and I was able to flash the firmware successfully. Odin did not display any kind of errors.
After the flash the phone was still connected to the PC since I feared it would run out of power. I know that the first boot after a flash can take a while. Since the LED was flashing while the big "Samsung Galaxy S6 Edge" logo was displayed I thought it was doing something in the background. I kept it like this (big logo, LED flashing, plugged into the PC) for over an hour and nothing did change. The device was warm but I doubted that it's doing anything since one hour for a boot, even after flashing, is way too long.
After that hour I turned it off and it instantly started to boot up again, but this time and all the other times after that it kept getting stuck at the big logo. It did not proceed into the animation like before.
I tested if I could enter the Recovery Mode at this point but it still was only able to get into the Download Mode.
The only way to stop it from trying to boot now was to get into that Download Mode, else it would just keep looping around, but not turn off by its own.
Every now and then, instead of displaying the big logo, it showed a blue screen with a yellow warning sign and the android mascot laying on the ground with "No command" beneath it. If you want to see how it looks you can google images "android 7.0 no command" and look for the full blue screen pictures.
Googling this blue screen with no command said that it can be easily fixed by wiping the data/cache from your device. But as I said the recovery mode was not showing up when I pressed the buttons for it. So a friend of mine suggested using ADB or fastboot to wipe the cache / dalvik cache.
Using both (ADB + fastboot) the device was not detected. We made sure that the drivers were installed properly. There was and there still is no way to connect to the phone with these both tools. Sadly.
After the first try of using ADB/fastboot we decided that the issue might have been the firmware I downloaded in the beginning and we used SamFirm (v0.3.6) to download the newest firmware for my SM-G925F ( G925FXXU5EQK8_G925FDBT5EQK1_G925FXXU5EQKF_HOME.tar.md5 )
This firmware appears to be the same as the one I downloaded before, but this one was slightly bigger.
This is a paste of the SamFirm window:
Checking firmware for SM-G925F/DBT/G925FXXU5EQK8/G925FDBT5EQK1/G925FXXU5EQKF/G925FXXU5EQK8
Model: SM-G925F
Version: G925FXXU5EQK8/G925FDBT5EQK1/G925FXXU5EQKF/G925FXXU5EQK8
OS: Nougat(Android 7.0)
Filename: SM-G925F_1_20171129140113_g7auy18e0c.zip.enc4
Size: 1950442496 bytes
LogicValue: 8ikzg48ul7hryauq
The flash was again successfull and still the same problem remained: no full boot.... sometimes a blue no command mascot.
After that we flashed again but with another PIT file attached. At first we got an error after the hidden.img but after changing the PIT file to this one ( ZEROLTE_EUR_OPEN_HIDDEN300M ) it worked again without any errors displayed by Odin. Apparently the PIT file we used at first did not have enough space for our hidden.img ...
We flashed that firmware several times and sometimes after the flash there would be a blue screen with an android mascot saying it is erasing, but the animation of that mascot freezes also after 10 to 20 seconds. I've kept the phone in this blue screen for several hours (up to 5h I think) since a few forum threads said that it sometimes takes very long to work and the LED was actually flashing all the time, but nothing changed.
We did not try to flash anything else because the Reactivation Lock is enabled and I have no idea how to turn this thing off w/o booting the device.
I would not mind flashing a custom firmware on the device as long as it just works again. So if this is somehow possible and might be a solution I am up for it.
What currenctly is going on with the phone:
· It only turns completly off when the power runs out.
· No button combination is working to turn it off.
· I can enter Download Mode easily but I can not enter the Factory Reset Mode.
Within the Download Mode it says:
ODIN MODE
Product Name: SM-G925F
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: On
Secure Download: Enabled
KNOX Warranty Void: 0 (0x0000)
RP SWREV: B:5 K:2 S:2
· The boot ends either up with showing an "Samsung Galaxy S6 Edge powered by Android" logo for the whole time (kept it like that for several hours, no boot)
· or with a blue screen (yellow warning sign, android mascot laying on the ground and a "no command" beneath it).
· Odin is recognizing it as a device.
· The device manager is recognizing the device.
· Samsung Switch is saying the device is not compatible.
· ADB/fastboot can not detect the device.
So ... is it possible to get this damn thing to work again or is it gone for good?
If you still got any questions regarding the current state of the phone please ask. I will try to reply ASAP.
Thank you very much for any reply you guys might throw at me.
Click to expand...
Click to collapse
If your not bothered about tripping knox (0x1) and voiding your warranty you can flash twrp recovery. Then wipe from there or flash a custom ROM. This way we can know for sure if it's software or hardware issue.
callumbr1 said:
If your not bothered about tripping knox (0x1) and voiding your warranty you can flash twrp recovery. Then wipe from there or flash a custom ROM. This way we can know for sure if it's software or hardware issue.
Click to expand...
Click to collapse
Thanks for that reply.
Sadly I can not flash twrp recovery because of that Reactivation Lock ... and I do not know how to deactivate it at the current state of the phone
Is there a way to workaround that lock?
same here lol. but even twrp recovery cannot run LOl, sammy charged me as U$$ 700 to repair,
of course i did not let them repair, and now i have a dead phone, that only goes to download mode, and the bootlogo with glitches
What if you get a stock ROM and flash it via Odin, if your phone goes to Download Mode...? I didnt totally understand your situation but that came to my mind, flashing stock firmware via Odin.
EDIT: Just went through your SITUATION a bit, you should get it inspected by someone and then decide, otherwise you might lose your phone permanently.
Same here
Same here.... But with s6....
Only download mode. Not even a bootlogo. No recovery... Tried flashing literally everything. is it possible to flash a custom Rom with Odin? Convert a rom.zip t a tar file? I tried flashing cf-root but I don't know if it's rooted...