Hopefully I posted to the correct section. After flashing, the device always shutdown midway through boot even when the battery is full, so I have no way to get the device to the modem mode now.
History:
Update: found the phone.bin file I need a WM6.1 radio ROM for Samsung Blackjack II, searched Google/Bing but find none.
When running the official WM6.1 update to flash my Samsung SGH-i617 or flashing the radio rom, the screen is always stuck at the radio rom flashing. The phone displays 3 Phone [START] [GOOD] - DPRAM = 0x454D444E. Time: xxx, where the time xxx keeps changing. The upgrade program on the computer displays "waiting for a next image". the first time I flashed I decide that the upgrade malfunctioned and pulled the battery off after an hour.
Now I have a phone that does not boot successfully, even after a factory reset. No matter what cooked/official rom I throw at it, it always shut down midway through the booting process. The furthest I can get is having it to display "SIM not found" or the unlock device screen for a second or two, before it shuts down.
There is a thread somewhere else says modem mode needs to be enabled, and I do see COM5 in a screen shot, so I assume modem mode is required to flash radio rom, but I have no way to get to the settings now due to boot failure. Since modem mode is a software setting, is there a ROM that has this setting on by default?
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?)
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.
I bricked/bootlooped my phone.
I've been using Superman ROM v2.4.1 for a while, but recently my Snapchat stopped working and I couldn't pass the SafetyNet, so I tried to fix it.
I turned off my developer options, and downloaded this App: https://forum.xda-developers.com/sho....php?t=2524485
My phone warned me this App might be harmful but I ignored it, and then changed the setting to permissive and then enfordcing a couple times. Then I rebooted my device, now it is stuck in a loop. It doesnt go beyond the 'Samsung Galaxy S7" logo and just turns off after that.
I cannot boot into recovery either, only download mode.
When i try to boot up or into recovery, it says on the top of the screen in red text "Custom Binary blocked by FRP Lock".
Can anyone help me? I have a flight in the morning so I really need this fixed. Is this caused by the App I used to change the SELinux Mode? Or is it because Developer options and hence OEM Unlocking is turned off in the settings?
What can I do to fix this?
Cheers
Dear Sir just Flash with stock firmware be sure u are using latest one to revive phone back to life.
thanks
FRP locked and cannot load stock FW
I'm having the same issue as theDroidfanatic, but i cannot flash the stock FW.
I have a Samsung S7 edge, running Superman, i believe marshmallow (i don't recall the exact version).
I accidentally enabled the OEM lock in the phones settings.
On trying to boot normally, I see the superman startup screen, and the FRP message across the top of the screen in red. "Custom Binary blocked by FRP Lock"
I can only boot into download mode.
Odin (3.12.7 and 3.12.3) can detect the phone being plugged in (so i think this system has the correct drivers, and my cables/ports are good).
I downloaded the latest FW from sammobile.com for the MTA region (its a Canadian MTS phone).
I load all of the files into Oden and everything appears fine. When i try to start the transfer it hangs at SetupConnection. Ah hour later, its still hanging there.
I've tried 2 PCs, and about a dozen USB cables; same result every time.
Its been a while since i played with rom stuff, am i missing something somewhere?
## EDIT
## Above represents 8+ hours of frustration;
## below, 20 minutes on a hunch and some dumb luck;
## proving that sometimes it is better to be lucky than good.
For anyone else having similar issues:
After installing Kies (on Windows 10; which required a Microsoft Virtual C++ pack for Kies to install), Kies installed a different USB driver.
Odin did not show any difference regarding seeing the phone. After the new driver was installed, Odin is now able to flash stock FW.
Did you manage to repair your phone. My note 9 don’t show up on my laptop usb not recognised
I had similar issue when i was trying to install firmware while developer mod was was disabled (in my Note 5). FRP lock was ON, then it got bricked. I gave my phone to a local phone repair shop, they have some technology to bypass FRP lock by using FRP bypass box.
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.