I have been given an S7 SM-930FD [Dual Sim] that was supposed to be bricked. It wouldn't boot into anything but I have successfully got it into download mode and been able to successfully flash a stock ROM downloaded from Sammobile [several times] with no errors. Each time I have used the full set of AP,CP,CSC files and the previous owner is not sure what ROM it was on or what he tried to install. I have tried different versions of the firmware for this model for various android versions and regions simply to try and get it to boot, but without success. I have tried HOME CSC and CSC files too.
But each time it starts to install the update / reboot it hangs. Either when it installing the update on the blue screen with the robot and its "erasing" - small rotating symbol just stops and nothing happens OR it loads to the GALAXY S7 normal boot screen then hangs.
When it hangs it will only respond to one key combination Power + Vol Down. It then "switched off" and will not reboot in any mode. When I say "switched off" I mean the screen goes black. However if I then connect the charger, it won't show the charging symbol UNLESS I leave it for a few hours and the battery goes flat. It will then charge and I can boot into download / recovery mode but normal boot starts installing the update and it will hang all over again. On one occasion it hung with and black screen and blue flashing light but again no key combinations worked and I had to wait for the battery to drain.
Also tried Smart Switch Emergency Recovery. Even with the drivers freshly installed it does not recognise the phone, it does accept the model number during initialisation, but once the S/N is entered it comes back and says it can't find the model, S/N or IMEI in the database!
I have researched the web for hours and watched every relevant youtube video and tried their suggested key combinations etc and they just don't work.
So I'm hoping someone can help me resolve this frustrating situation, not least because of the delays between attempts!
Presumably as I can consistently get it into download mode there is a solution out there somewhere???????
What am I doing wrong? Should I be looking at a custom ROM or trying something else?
All help appreciated.
Related
Hi,
I have a Galaxy S (I900) which I attempted to root yesterday. Stupidly, I used the wrong root kit and when I rebooted I was left hanging on the startup screen with the network logo (orange) flashing.
My boot menu was disabled for some reason but I could however access download mode - which I did. Whilst trying to rectify this I downloaded a couple of kernels that were recommended to fix the problem but to no avail.
Finally, running out of options I downloaded Odin3Execution v1.00 One-Click downloader, connected the phone and clicked start (which was also recommended to me). This completed successfully but when the phone tried to re-boot I was left with a flashing AT&T logo (which is not my carrier) and download mode no longer executes when pressing the buttons. Also, when I plug the charger in the screen just goes black.
I realise that this is my own stupid fault but i'd really appreciate some help on the matter.
(would a USB jig get me back into download mode?)
The unit has been used for about 2 months and remains quite new. It was quite stable before. Yesterday night, about half an hour after plugged in for charging and with WiFi Hotspot turned on for sharing 3G data to another netbook, the unit suddenly rebooted itself. It then stopped at the start-up screen and remained there for several minutes. I kept holding the power button for a few seconds to turn it off but it then automatically reboot itself afterwards, and stopped at the start-up screen again. It means that even complete turning off is not possible.
Trying to enter into recovery mode showed the following few lines:
# MANUAL MODE #
-- Updating application...
Copying Common Apks.
Click to expand...
Click to collapse
and then it automatically rebooted again. It means that it can't enter into recovery mode normally.
It was possible to enter into download mode. And it was the first time this machine went into download mode. I run Odin Downloader and flashed the official stock ROM. After showing "Pass", the device rebooted itself. Unfortunately, it still stopped at the start-up screen, just showing "Samsung Galaxy Tab 7.0 plus". It is really troubesome. I have experience playing several Android devices before and it is the first time I face such troublesome problem.
The device is an official product. The biggest problem is that the original purchase invoice was lost and most likely that I couldn't get official support, repair service or replacement.
May I ask if anyone would kindly provide me some help or advice. Thanks!
Instead of going into download mode go into recovery mode and see if there are any errors. Your scenario is sounding very similar to the one I had in the past.
I just ran into a nasty snag at boot logo as well. nandroid, stock kernel and factory reset were no help. Try Odin back to Stock, it still may not get past boot logo, hold vol up and power to get into recovery and factory reset. Hope it works for you.
Unfortunately I was unable to get into recovery mode even after odin flashing stock ROM.
It rebooted itself a few seconds after displaying some lines of text. I can't see the normal recovery menu.
Hey, I bought a galaxy note 4 which as the seller said "doesnt turn on anymore or gets stuck on boot logo".
I can confirm this issue. first time it booted up and said something with "reactivation lock" I couldn't read all cz it just rebooted and is now either stuck on boot logo or shows "recovery booting" in a blue font in the upper left corner but nothing happens. Also I can not boot into recovery mode. The hardware buttons are ok as I can click volume up during booting into download mode. I searched the whole internet and found this unbrick thread: https://pastebin.com/7KQxRRNF which I followed exactly. not the first time I'm fixing such issues but this time I'm out of knowledge. this thread didn't work it ended up in boot loop. I used the correct firmware I guess?..
there are plenty of firmwares. my model: N910F (vodafone branded I think cz it was showing a vodafone screen before it got this issue).
I tried using Samsung Kies but it says my model is not supported. same in SmartSwitch (not supported model). then I downloaded an older version of Kies 2.7 and it says connecting but even after 20 minutes or so nothing happens. I reinstalled the drivers several times, I'm using the OG Cable plugged into the motherboard directly. no hubs or frontpanel things (laptop). the only thing I can do with this phone is go into download mode. I don't know if this has something to do with this stupid reactivation lock in Download Mode it says "on". but I find only tutorials how to bypass this when you can boot the phone "aka samsung account trick". so useless for me.
Can I flash stock firmware with reactivation lock=on at all? or is that impossible? If so how can I disable this stupid lock? I never had a phone which broke my mind as hard as the note 4.. and I had many phones from many different brands and actually thought china phones like xiaomi are hard to crack or set back to stock n stuff..
Please help. I can not power it on nothing happens. battery removed for 5 minutes while holding the power key. nothing. only download mode is possible. and only if it's plugged into my pc. what the heck is wrong with this phone? sending it to support center is no option.
Had it for 3 years now, it first looped in October 2017, broke all the sensors but has otherwise been working fine since. I also rooted it about 7 months ago in case that makes any difference with recovery. During both of these loops I have been unable to reliably get into recovery/download mode. I left it alone for an hour earlier today and came back to find that it was somehow in Odin/download mode with the text in the top left but still on the boot screen. So I plugged it into my computer, it was detected and then I flashed it with the correct G930T firmware and home csc. Got the success message in Odin and it seemed to be working but it was just stuck on the boot screen now. So now I've just been trying to flash it again with the other csc but it has been failing for a lot of different reasons and I don't know what any of them mean. I did manage to get it to power on a lot more reliably and into download mode, but still having problems. The biggest problem is when I get to either the download screen or warning screen, the screen suddenly gets all glitchy and I can't do anything. Whenever that happens it also shuts off after 10 seconds. This also happened on the Smart Switch emergency recovery screen when I cancelled a stalled flash and then tried to flash it again from that screen. I've also gotten errors when trying to flash from the download/boot screen. The ones I can remember are "unsupport dev_type", "secure check fail : tz eMMC write fail : tz" and "secure check fail : hyp eMMC write fail : hyp". I can't even find anything else on these errors and have no idea what they mean. I also have no idea how it is getting into Odin mode on the boot screen but so far that is the only way I have been able to do anything since I can't get into download mode the proper way. Lastly I tried to check in Smart Switch to recover it but it says the device is unsupported and there is nothing in emergency recovery.
Operation Ivy said:
Had it for 3 years now, it first looped in October 2017, broke all the sensors but has otherwise been working fine since. I also rooted it about 7 months ago in case that makes any difference with recovery. During both of these loops I have been unable to reliably get into recovery/download mode. I left it alone for an hour earlier today and came back to find that it was somehow in Odin/download mode with the text in the top left but still on the boot screen. So I plugged it into my computer, it was detected and then I flashed it with the correct G930T firmware and home csc. Got the success message in Odin and it seemed to be working but it was just stuck on the boot screen now. So now I've just been trying to flash it again with the other csc but it has been failing for a lot of different reasons and I don't know what any of them mean. I did manage to get it to power on a lot more reliably and into download mode, but still having problems. The biggest problem is when I get to either the download screen or warning screen, the screen suddenly gets all glitchy and I can't do anything. Whenever that happens it also shuts off after 10 seconds. This also happened on the Smart Switch emergency recovery screen when I cancelled a stalled flash and then tried to flash it again from that screen. I've also gotten errors when trying to flash from the download/boot screen. The ones I can remember are "unsupport dev_type", "secure check fail : tz eMMC write fail : tz" and "secure check fail : hyp eMMC write fail : hyp". I can't even find anything else on these errors and have no idea what they mean. I also have no idea how it is getting into Odin mode on the boot screen but so far that is the only way I have been able to do anything since I can't get into download mode the proper way. Lastly I tried to check in Smart Switch to recover it but it says the device is unsupported and there is nothing in emergency recovery.
Click to expand...
Click to collapse
When you flash with Odin tick "'re partition" in Odin options.
When "pass" appears disconnect phone from pc. Force reboot by holding home+volume down+power.
As soon as screen goes black press volume up while keeping home and power pressed. When recovery menu appears choose wipe / factory reset. Then reboot.
What is obviously very important is you are flashing the correct firmware for the device in the first place.
Greetings everyone,
I decided to post my problem with my phone after searching the entire internet for similar problem but with no luck. Anyway I used to play around with my Samsung j7 pro for 2 years, I managed to flash twrp and thus many other custom roms, until last week when I recklessly flashed a sboot.img.tar file through Odin in order to fix cellular network in a rom I flashed earlier, this alone bricked my phone refusing to get past the Samsung logo, so like I do always, I tried to restore my phone by flashing the stock firmware (9.0) which I always keep on my PC, but surprise, the phone refuses to go through the process and gives me this error:
sw rev check fail bootloader device -1 binary 6
(same with 8.0 and 7.0 firmware)
I searched the internet for same error but with no luck, because I understand it's a mismatch between device bootloader current version and the firmware bootloader's, that they should be the same or higher, meaning you can't downgrade, I get that! but I never seen device with negative figure (-1) what that's supposed to mean? my device bootloader used to be on 6, how did it managed to jump to minus one ?
then I tried to flash TWRP to see if I could flash a rom and get around it, so I did, but when booting into recovery the screen goes black, I thought first the phone turned off, but not really, because TWRP seems to work with screen completely black, I knew that because I accidentally touch the screen and I sense vibration, I managed to reboot the phone via twrp just by guessing the buttons location (screen always black) in order to prove that TWRP is working with screen off. I tried to flash multiple TWRP versions but the same problem, no screen just touch, by the way there is nothing wrong with display hardware because it shows Samsung logo at start and also can boot into download mode just fine.
I hope someone could help me overcome this big of an issue, because I tried everything.