Hi everyone, sorry if I am doing this wrong, this is my first post, just thought someone might want to know how I fixed this problem. For some context I am an absolute noob when it comes to all this, and decided I should try flash a custom rom (probably not my brightest thought). When trying to install TWRP, somehow ended up stuck in ODIN MODE, all the ways I found online to exit weren't working (holding down combinations of power buttons, volume buttons and home buttons).
I don't have photos unfortunately but the screen looked like this at the top,
COULD NOT DO NORMAL BOOT
ODIN MODE (HIGH SPEED)
The way I fixed it was by using the legend @Chainfire SM-N910F root method on the phone, as it is already in download mode (Odin mode). Here is the link to the thread for rooting
https://forum.xda-developers.com/note-4/help/sm-n910-cf-auto-root-t2897428
I am no expert but I think the rooting method installs stock recovery as part of its process, therefore solving my problem.
One thing I will mention however, as part of the process of rooting, "USB debugging" is enabled in developer settings. It just happened that I already had it enabled when my phone got stuck in ODIN MODE, but if your phone did not already have "USB debugging" enabled then I am not sure what will happen. Maybe look into that before you do anything.
After I had done all of this, phone started up fine, functions perfectly, and I am still using it to this day. Please note that this method will root your phone if that is a problem for you.
I hope this helps someone out there, thank you once again @Chainfire
Related
I have just received a s4 with a really confusing problem . When you power the phone on normally it displays a weird semi solid green screen but when you boot into download mode everything displays perfectly. Also while phone is off if you connect charger it displays the battery icon perfectly. Phone is 100% stock dont know what rom/baseband version was installed. Green screen also in recovery mode. Phone does not have usb debugging enabled nor is it rooted. Can anyone help?
Download Mode says
ODIN MODE
PRODUCT NAME SCH-I545
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION Enable
eMMC BURST MODE enabled
If you're able to get into download mode, download the latest stock firmware and install it to see if that corrects the problem. There should be a link for the stock firmware in the Verizon Galaxy S4 forums, along with other aids that may be of use to you. Installing the firmware is a must, because it will either correct the problem you're having, or it will reveal the problem to be deeper, and likely hardware related.
In the unlikely event that the stock firmware is not available on the forums, you can get a copy from either sammobile.com or samsung-updates.com.
I dont know what version was previously installed I tried flashing twrp via odin it comes back as failed because of a auth error. I think the bootloader may be locked if it isnt I dont want to upgrade only to learn bootloader was previously unlocked and I just locked it up by updating. It seems to me if this is a hardware related problem I would think the phone would be green screen in download mode and while charger plugged in? Any suggestions on which android version to try first?
You clearly didn't read my previous post. That pisses me off, because now I'm having to repeat myself when I should NEVER have to.
If you want to brick the S4, then continue doing what you were doing. Otherwise, pay attention, because at no point did I ever mention downloading and installing TWRP. I did however mention downloading and installing the STOCK Verizon S4 ROM from the Verizon S4 forums. You will use Odin to install the ROM. If the Verizon S4 forums do not have a link to the stock Verizon S4 ROM, you are to download the latest copy of the ROM from either sammobile.com or samsung-updates.com. It doesn't matter one whit what was on there before, because by installing the stock ROM you were supposed to have downloaded, you will have the S4 at a known starting point so you can truly diagnose the problems it may have.
AT&T and Verizon bootloaders are locked, thus you cannot just install a recovery and expect it to work. Installing a stock ROM however will work since all the components are verified by Verizon. In installing the stock Verizon S4 ROM through Odin, you will make sure you are using a proper cable, do not have the S4 connected through a hub, will make sure the Samsung USB drivers are installed (available at Samsung's website), and either do not have Kies installed, or have Kies disabled.
Sorry I have flashed the latest official verizon firmware and odin said pass, everything went perfect. Phone restarted and again hazy green screen returned. Still cannot veiw anything in recovery or normal mode, safe mode does not help either. Download mode and battery charging still show up perfectly fine. Any help would be greatly appriciated.
It's hard to think of this as a hardware issue, but I believe you have one. As strange as it may seem, the issue is not with the screen itself, but the GPU.
Using Windows equivalents, Download Mode is "Safe Mode with Command Prompt" while Safe Mode is just like Windows' "Safe Mode". "Safe Mode with Command Prompt" dumps you to the command line, i.e. DOS. It doesn't need a GUI so it doesn't have drivers loaded to support it. "Safe Mode" has a GUI so it has to load drivers to support that.
On the S4 the concept is similar, only the drivers are called "libraries". Download mode doesn't use a GUI as it's part of the bootloader, so it doesn't need the GPU, thus it doesn't need the GPU library. This is why download mode functions. The other modes all have a GUI, which requires the GPU and a library for the GPU loaded. Since the GPU has failed you get the green screen instead of what you should see. The library itself isn't the culprit because if it were, loading a new ROM as you had would have fixed the problem. The screen isn't the culprit because the screen works correctly in download mode. If it were the screen, the green would appear in Download Mode as well as the other modes. Therefore the GPU is most likely the problem.
Unfortunately, that means a new motherboard, on top of trying to remove the glass for replacement.
PROBLEM ALMOST FIXED!!.. Well kind of, i seperated the broken glass from the screen and placed the phone in the freezer. An hour or so later i pulled the phone back out of the freezer and switched it on everything worked perfect i switched on usb debugging and rooted the phone using towelroot and safestrapped it. when i updated supersu i had to reboot the phone and then again green screen i also noticed the phone had gotten really hot. I tried the freezer trick again and the phone turned on like normal no green screen. Does anyone know what maybe causing this issue???
Thank you very much for all the help and info you have given me i really do appriciate it
Bad GPU, as previously stated, though there are two other possibilities I can think of. The first is that GPU has a bad connection to the motherboard that manifests when heated. Or else the motherboard has a stress fracture that manifests when heated. The latter has happened with other devices but is not common. A solder reflow of the GPU could cure the former problem.
Before I give the reflow a shot I wanted to mention another piece to this puzzle. When the phone is working fine as long as the screens backlight is on the phone will display everything correctly as soon as it turns off and you turn it back on green screen. It doesn't matter if you wait two minutes or 20 minutes. Dont know if thathelps narrow down culprit
It doesn't narrow things down any.
the solution
you need to change your battery than you install the firmware using odin than you download antivirus. :good:
I rooted my galaxy s7 edge (snapdragon) and everything was fine and working except I couldn't get SuperSU to install properly. I would get the app screen, but nothing else. A couple of apps would show up (Root Checker, Flashfire) after I had run them but I didn't get the typical SU screen with settings. I'm not including the softwares used (I did have debugging enabled in Develper options on the phone, secure boot unchecked, and the correct Samsung USB drivers installed) because I don't think it's relevant to my question - if not so, let me know and i'll be glad to provide the info - I'm a newbie at this so please bear with me). I read about the warning to not update the 2.74 version of SuperSU but then I saw the update beta for 2.77 so I tried that. It appeared to run ok; I could see all the commands being executed and then ending and then the phone rebooted, as it's suppose to do. This is when the problem emerged; a screen came up saying "start up failed" and at the top left of the screen it said 'Custom binary blocked by secure boot (boot.img). I rebooted to TWRP recovery mode and tried rebooting which again resulted in the start up failure screen. I then tried the wipe data\factory reset setting and the same thing happened. I then booted to maintenance mode and got the warning screen about a custom OS installation can cause problems but if you want to proceed press volume up key which I did and got the usual Downloading page. At the top of the Downloading page I noted it said, among other identifying info: Odin mode (high speed), FRP lock: off, QUALCOMM Secure Boot: enable, and Secure Download: enable.
But, when connecting the usb cable to the phone and pc, my computer (Win 10) doesn't even see it. Not sees and doesn't recognize, but doesn't even see it. I tried a second USB cable and different ports but got the same results. I tried a second computer and got the same thing.
I am guessing that if I could still access the phone to run rooting apps I could get past the lock. If not now, maybe later on when someone figures our a way to do so. But without a working connection to the phone I am helpless. I am wondering if Verizon disables USB intentionally, so that the phone essentially becomes useless. Or, is it a coincidence and perhaps there is something wrong with the usb hardware.
Is there a way out of this other than having to pay for it to be fixed (which Samsung won't do - I called - and maybe Verizon not either).
Thanks in advance -
j-brah
Hi all,
First message in this wonderful community.
Anywas, having owned a Galaxy Note 3 for a few years now I thought I'd give it a shot at installing a new ROM to get it in better shape and try to stay with it a bit longer. Nothing really wrong with the phone other than getting a bit sloooow, specially the camera.
Anyways, not being a very geeky person, I soon realized the learning curve is steep.
This is what I've done so far:
1) Identified the model (SM-N9005)
2) Downloaded and unzip the SDK platform tools
3) Downloaded the TWRP custom recovery
4) Unlocked developer tools, allow unknown source (not sure if that is needed) and allowed USB debugging. In this phone I think there is no option for OEM unlocking.
5) Installed latest Samsung USB driver
5) Tried to proceed with unlocking the bootloader. This is where I ran into issues:
- I installed ADB Installer saying YES to everything
- Connected phone to pc with a usb cable
- From the command prompt (in my user) I executed adb reboot bootloader. I initially got an error (something about daemon and a port?....) but was able to move ahead
- The green android logo appeared along with this message "Downloading ...Do not turn off target!!"
At this point, pressing the volume down, power and select at the same time I tried to get out but kept on coming back to the same android menu stuck in "Downloading ...Do not turn off target!!". After the third try, a new warning message came up asking me if I want to proceed or reboot phone (pressing volume down) and I rebooted the phone to "escape" this predicament. I thought I was going to brick the thing!
Anyways, any recommendations on how to proceed? Is there an easier method to root the phone? Or to circumvent the issue I encountered?
As you might have guessed by my message, I can (sometimes) follow instructions but the underlying knowledge of what I am doing is .... well ...missing? :silly:
Hope you guys can help me. Thank you all in advance for your assistance.
PierreBCN said:
Hi all,
First message in this wonderful community.
Anywas, having owned a Galaxy Note 3 for a few years now I thought I'd give it a shot at installing a new ROM to get it in better shape and try to stay with it a bit longer. Nothing really wrong with the phone other than getting a bit sloooow, specially the camera.
Anyways, not being a very geeky person, I soon realized the learning curve is steep.
This is what I've done so far:
1) Identified the model (SM-N9005)
2) Downloaded and unzip the SDK platform tools
3) Downloaded the TWRP custom recovery
4) Unlocked developer tools, allow unknown source (not sure if that is needed) and allowed USB debugging. In this phone I think there is no option for OEM unlocking.
5) Installed latest Samsung USB driver
5) Tried to proceed with unlocking the bootloader. This is where I ran into issues:
- I installed ADB Installer saying YES to everything
- Connected phone to pc with a usb cable
- From the command prompt (in my user) I executed adb reboot bootloader. I initially got an error (something about daemon and a port?....) but was able to move ahead
- The green android logo appeared along with this message "Downloading ...Do not turn off target!!"
At this point, pressing the volume down, power and select at the same time I tried to get out but kept on coming back to the same android menu stuck in "Downloading ...Do not turn off target!!". After the third try, a new warning message came up asking me if I want to proceed or reboot phone (pressing volume down) and I rebooted the phone to "escape" this predicament. I thought I was going to brick the thing!
Anyways, any recommendations on how to proceed? Is there an easier method to root the phone? Or to circumvent the issue I encountered?
As you might have guessed by my message, I can (sometimes) follow instructions but the underlying knowledge of what I am doing is .... well ...missing? :silly:
Hope you guys can help me. Thank you all in advance for your assistance.
Click to expand...
Click to collapse
flash custom recovery.download supersuzip latest version is 2.82.push it to your phone.reboot to recovery mode.flash supershu zip.reboot to system.your phone is rooted.that's it.
Sent from my SM-N930F using Tapatalk
Normal method .
Flash TWRP via Odin.Put custom rom on SD card .
Boot to TWRP recovery and flash .
N9005 does not have a locked bootloader .
Hi Guys,
Today I think I bricked my phone and I would appreciate any help.
I will describe the whole situation.
So around 2019 May, I rooted my device and decided to flash a stock based,debloated custom rom. Everything work just fined including downloading mode and recovery menu. Today, I decided to try out [S7/S7 Edge][OneUI Pie][JetBlackUI] LightROM, however strangely I was not able to boot either to TWRP neither to downloading mode via key combination.
However I had install TWRP app and from there i was able to boot to recovery mode,install the new rom and try it out.
For some reason root was not enabled in the new rom, so i figured I will try to do it via TWRP however I was unable to boot, since root access is needed to boot from TWRP app + key combo still did not work.
After searching on google, I found a poprgram which can do the trick. (Recovey-Download (CMD)
With this I was able to boot to recovery mode. Now I thought, since all this mess up was started with the new roms, I decided to restore my original stock rom, which I had a back up of. It booted up first and seemed okay, but I was curious if this solved the issues with the key comb, so I tried it going downloading mode, but it only worked with the program ((Recovey-Download (CMD)), and I saw that it is probably not gonna be good, since it only had the blue screen, but no data in the upper left corner.
Then I restarted the device and now it say " Custom binary blocked by FRP lock". and turns off itself.
I saw that FRP lock could be solved easly with Odin fresh install, problem is I have no idea how to go downloading mode. ( Assuming at this point I still can).
Sorry for the long essay but i think the more detail the easier to diagnose. Also, thank you for reading.
I would greatly appreciate any help.
BR
Csaba
Managed to solve it with USB JIG.
Is your phone an Exynos/Snapdragon variant?
csesztes said:
Managed to solve it with USB JIG.
Click to expand...
Click to collapse
Hey, how did you manage to get your phone into dl mode with an USB jig? I want to try this out, but you're the only one here who's confirmed that you were able to do this on an S7 Edge.
Hello all,
I have been a long-time peruser of this site, but this is the first time I couldn't find a good answer to my issue.
My phone (SM-G950F) ran out of power, I didn't notice till after it died completely. When I tried to turn it on while charging it displays the message "Custom binary blocked by FRP lock" on the logo screen, then turns off. If plugged in to a charger, it'll just keep booting like that in a loop. I'm not even able to access recovery, only the download mode. I'm not against factory resetting my phone, however I have important data that in the phone storage I need to keep. I have searched online and youtube with no success.
Any ideas or suggestions will be much appreciated.
NOTE: Before the phone battery died, i wasn't tinkering with any setting that may lead to this; just regular use
flash it with odin
Flash official firmware..but make sure to use HOME_CSC not CSC...to keep your data...then boot direct to download mode after flashing ia done and flash twrp recovery
I have same issue bot Windows dosn't see my phone (drivers installed) so I'm unable to flash it. I can see only unrecognizable device in windows device manager. Is there any hope to fix it. Please help
mic225 said:
Flash official firmware..but make sure to use HOME_CSC not CSC...to keep your data...then boot direct to download mode after flashing ia done and flash twrp recovery
Click to expand...
Click to collapse
How to rid rmm and kg without 7 days?