Related
Hi
I have run into a small problem with my SGS 9000. I wanted to flash Insanity ROM 8.5 and ran into some problems so I restored my phone using Odin. I then booted into recovery and flashed a new modem and Kanity kernel 2.0. I then accidentally hit reboot before flashing the new ROM and now the phone won't boot (halts at the first SGS logo).
I can access download mode but not recovery. When I connect the phone to USB, Windows gives me a message that USB unit not recognized. This means I can't restore it using Odin.
I've tried taking out the battery for 5 minutes and changing computer/cable. I also uninstalled/re-installed the Samsung drivers and re-booted the computer a couple of times. Could it have something to do with USB debugging mode?
mate, open odin and the insanity rom....
then go to download mode on ur sgs and plug in ur usb, if alls well? reflash the Insanity ROM 8.5 again
That would work if Odin could discover the phone. I can get into download mode but the computer does not recognize the phone and thus I can not flash anything through Odin.
Could it have something to do with USB debugging mode?
no...
ur in a stivky situation, have u sorted it yet? ask a custom rom dev about it
lilmo22 said:
Could it have something to do with USB debugging mode?
no...
ur in a stivky situation, have u sorted it yet? ask a custom rom dev about it
Click to expand...
Click to collapse
Thanks, I'll do that I haven't had any progress, just endless hours reading various forums without any luck.
Hi, I'm new and do not know if I put the post in the right place. Forgive. I have a I9100 with 4.1.2 official rom, no root and no usb debugging enabled. One day is automatically restarted and stayed in bootloop. I had no access to recovery, but yes in download mode. I tried multiple ways I found on Google, but without success. I can not retrieve it with kies. probe reinstall the recovery again and nothing, try adb and not worked. With odin can not flash with pit. When turned on I get the message that there has been a problem with the firmware and recover with kies, but can not. It is impossible to save him?
Sorry with my English.
Thank you.
k7neptune said:
Hi, I'm new and do not know if I put the post in the right place. Forgive. I have a I9100 with 4.1.2 official rom, no root and no usb debugging enabled. One day is automatically restarted and stayed in bootloop. I had no access to recovery, but yes in download mode. I tried multiple ways I found on Google, but without success. I can not retrieve it with kies. probe reinstall the recovery again and nothing, try adb and not worked. With odin can not flash with pit. When turned on I get the message that there has been a problem with the firmware and recover with kies, but can not. It is impossible to save him?
Sorry with my English.
Thank you.
Click to expand...
Click to collapse
You can flash custom recovery from bootloader mode
I do not have access to bootloader mode. Display show "Firmware Upgrade Encountered an issue ..." when I try to enter recovery mode / bootloader mode
k7neptune said:
I do not have access to bootloader mode. Display show "Firmware Upgrade Encountered an issue ..." when I try to enter recovery mode / bootloader mode
Click to expand...
Click to collapse
In this case, perhaps a JTAG service might be able to help you. Try if there is one in your region.
If that doesn't work you can sell it by pieces.
Thanks for your ideas. I'll see what I do ...
"Custom Binary blocked by FRP lock" & Odin/PC won't recognize the device
Okay so,
My phone has been rooted for a year, I disabled OEM Unlock by accident, my antivirus was always telling me its unsecure with this feature on and to 'click here' to disable it.. I forgot how important this was to have enabled while rooted and ended disabled it and that night rebooting my device.
I get this error when trying to boot my device:
"Custom Binary blocked by FRP lock"
I have the original stock firmware, and Odin and want to reset the phone but when I plug this device in ( while in download mode ) > the windows PC doesn't recognize it (no new device sound or any change in devicemanager) and therefore odin isn't recognizing anything either - - I can grab my other 2nd-device and boot it into download mode, plug it into the same setup and boom > recognized and 'Ready!' Status in odin almost immediately so I don't think it's my PC or the cables -- I don't think 1st-device has usb debugging enabled either and I'm not sure how to proceed ...
any help is much appreciated ...
Try to use Smart Switch (from Samsung website), which also has the latest drivers, to recover your phone. (Google "how to recover with smart switch")
Alright,
Forgot to mention I tried Samsung Kies but cannot find the serial number on the device, I'll give Smart Switch a try this evening on my other PC and report back... hopefully that PC recognizes it, my tablet connects to this laptop but not the phone.. could USB debugging being disable cause this?
How close to bricked is this?
I'm such a fool!
Thanks for the feedback so far..
Hi boot tar flash odin frp lock of after stock rom flash
I went through this a few weeks back. I found my serial number (was a sticker originally on back of phone) and used smart switch to recover firmware. Then enabled developer options, oem unlock, flash TWRP thru ODIN etc etc.
So if I find the serial number, I save it .. good to know, thanks!
Hi boot tar flash odin frp lock of after stock rom flash
Click to expand...
Click to collapse
Can you elaborate just a bit?
zerotrick said:
Okay so,
My phone has been rooted for a year, I disabled OEM Unlock by accident, my antivirus was always telling me its unsecure with this feature on and to 'click here' to disable it.. I forgot how important this was to have enabled while rooted and ended disabled it and that night rebooting my device.
I get this error when trying to boot my device:
"Custom Binary blocked by FRP lock"
I have the original stock firmware, and Odin and want to reset the phone but when I plug this device in ( while in download mode ) > the windows PC doesn't recognize it (no new device sound or any change in devicemanager) and therefore odin isn't recognizing anything either - - I can grab my other 2nd-device and boot it into download mode, plug it into the same setup and boom > recognized and 'Ready!' Status in odin almost immediately so I don't think it's my PC or the cables -- I don't think 1st-device has usb debugging enabled either and I'm not sure how to proceed ...
any help is much appreciated ...
Click to expand...
Click to collapse
Hey man, im having the exact same issue with my S7 edge.
So I got my IMEI number, and with my number I went to imei. info / and I got my serial number through a warranty check through the site, you have to register to do it.
I used Smart Switch and I get an error when trying to use the emergency recovery "Model number cannot be initialized"
I'm also getting the error on my PC when trying to connect my device to odin saying that "USB device cannot recognize" and with that I cannot flash the stock firmware on the device.
So if you have gotten any solution to the FRP lock please let me know.
Serial number is engraved on back cover next to the imei number -,- @samuraichick0n about "Model number cannot be initialized" try to write it in diffrent forms eg. G935f or SM-G935f uppercase or lowercase.
Domino5 said:
Serial number is engraved on back cover next to the imei number -,- @samuraichick0n about "Model number cannot be initialized" try to write it in diffrent forms eg. G935f or SM-G935f uppercase or lowercase.
Click to expand...
Click to collapse
Thank you for the response. I will give this a go when I get home later today.
samuraichick0n said:
Thank you for the response. I will give this a go when I get home later today.
Click to expand...
Click to collapse
If smartswitch doesn't work you can download latest firmware for you model number and flash using odin, should solve your issue very quick
dusterphil said:
If smartswitch doesn't work you can download latest firmware for you model number and flash using odin, should solve your issue very quick
Click to expand...
Click to collapse
PC doesnt want to recognize my device, so Odin doesn't pick it up.
Try it with other usb cable. What is given together with the charger is incongruent, it happened to me, the same problem. (galaxy s6, s7)
And you need the newest odin. Excuse me my crappy English.
feri1969 said:
Try it with other usb cable. What is given together with the charger is incongruent, it happened to me, the same problem. (galaxy s6, s7)
And you need the newest odin. Excuse me my crappy English.
Click to expand...
Click to collapse
I've tried everything, and I still cant get the PC to pickup the phone to flash with Odin.
samuraichick0n said:
I've tried everything, and I still cant get the PC to pickup the phone to flash with Odin.
Click to expand...
Click to collapse
Tried a different PC?
*Detection* said:
Tried a different PC?
Click to expand...
Click to collapse
Yes, I've tried a different PC - "USB Device Malfunctioned /Device cannot be recognized"
Also a PSA: Smart Switch removed the recovery option for phones, you are ONLY able to get a recovery with the code from a previous backup.
samuraichick0n said:
Yes, I've tried a different PC - "USB Device Malfunctioned /Device cannot be recognized"
Also a PSA: Smart Switch removed the recovery option for phones, you are ONLY able to get a recovery with the code from a previous backup.
Click to expand...
Click to collapse
Hardware fault with the phone then
Need same kind of help
samuraichick0n said:
Yes, I've tried a different PC - "USB Device Malfunctioned /Device cannot be recognized"
Also a PSA: Smart Switch removed the recovery option for phones, you are ONLY able to get a recovery with the code from a previous backup.
Click to expand...
Click to collapse
Hi just wanted to no did you get it fixed and if so how I can’t find help anywhere. Thanks
ladyhypa said:
Hi just wanted to no did you get it fixed and if so how I can’t find help anywhere. Thanks
Click to expand...
Click to collapse
Hello, after exhausting all options I had to take the device to Samsung themselves - eventually they had to replace the motherboard on the phone to fix it.
So check if your phone is under warranty and take it in.
I fixed this when I first rooted by flashing the stock bootloader, firmware etc everything through odin
Thanks
samuraichick0n said:
Hello, after exhausting all options I had to take the device to Samsung themselves - eventually they had to replace the motherboard on the phone to fix it.
So check if your phone is under warranty and take it in.
Click to expand...
Click to collapse
Ok seems like what most people are saying but unfortunately mine is not under warranty but thanks for your reply anyway.
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
M3DUS4 said:
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
Click to expand...
Click to collapse
this could be because the galaxy A51 wasnt built with fastboot, and the code to launch this option was just reused from a different device, or because something isnt connecting properly.
Hello, I have the same ... Android 11 (and currently 12) (from Frija). So it is not the fault of incorrect configuration or with connecting. Only something is wrong with this phone ...
I have this device and this solved it for me:
Enable OEM unlocking in developer settings
Shut down the phone
Hold volume up and volume down
Plug in a USB cable connected to a computer (the computer being turned on)
Keep holding
You're in download mode!
Side note: This might not work in USA or Canada, I am from europe and it works here. I have no idea if it works in another region. Also, you can't just flash a recovery.img on Samsung since there is no real "fastboot", you have to use download mode and Odin.
But I know how to enter download mode... Problem is Fastboot mode...
There is no fastboot mode on a modern Samsung device. If there is, it's fake and you cannot flash anything with it. As you can see even from Wikipedia, Odin is the Samsung replacement of fastboot.
So no fastboot, only download mode.
If a guide is saying to use fastboot, it is not compatible with Samsung.
If you would tell me why you specifically need fastboot, I'll be happy to tell you how you can do it with Odin, if possible.
Because I have Samsung Galaxy A51 5G (A516B) with new Android 12 and I can't do a root! Because I can't upload TWRP (custom recovery) because I haven't OEM unlock option in Deveoper Option. I tried trick with set back date by 7days but not succes. Everything I;ve metioned here - I did at my phone with Android 11.
And... I have read that I can turn this fu**ing OEM option by comend at ADB: fastboot oem unlock.
Phew ...
So this fastboot method is the last method to do a root with my phone.
Upload TWRP by Odin in download mode -ends red warning - of corse...
Have you any ideas?
I would be grateful for help...
I have read this fastboot method at:
How to Unlock Bootloader On Samsung Galaxy Phones [EASY GUIDE]
Are you looking for a Complete tutorial on How To Unlock Bootloader on Samsung Galaxy Phones? If yes, then you have come to the right place.
www.guidetoroot.com
Yeah, that guide is not relevant on any modern Samsung device. Besides, even if it was, which it isn't, you would first need to enable OEM unlocking from the Developer Settings.
But the fact that you don't have an option for OEM unlock is weird, since I have the exact same device model and it is there for me.
May I ask what is your region and is your phone locked to a telephone carrier?
My region is PLS - Poland. And not - phone is not locked. Have you the newest system Android 12?
Yes, I do. It's weird that there isn't even an option for you.
I'll try to come up with some new ideas if I have time...
I'll be glad for it...
Hej, do you have any idea?
stanwin said:
Hej, do you have any idea?
Click to expand...
Click to collapse
Have you tried everything listed here?
BloodyFruitDestroyer said:
Have you tried everything listed here?
Click to expand...
Click to collapse
Yes, I did. Evething exept the last one...
You could try it. It might be risky, but it's the only option I personally can come up with right now.
I've tried this option but Odin stuck on "files verification". Any help?
have any of you encountered this problem?
And how did you solve it?
You can also try searching for combination firmware for your device online
Problem solved. Trying different USB cable (2.0) worked.
-----
Hi, I was trying to downgrade from Android 12 to 11. Following guide step by step, including
USB Debugging, Turn on OEM Unlocking, then used adb to boot into bootloader. Device state was locked. Ran fastboot flashing unlock but then stuck at Waiting for Device. Phone didn't go into warning to unlock bootloader.
I noticed that Boot slot is b, not sure if that matters.
Also tried to follow Google's own flash too, got stuck at the same phone screen.
Any help is appreciated.
Kenneth
kenship said:
Problem solved. Trying different USB cable (2.0) worked.
-----
Hi, I was trying to downgrade from Android 12 to 11. Following guide step by step, including
USB Debugging, Turn on OEM Unlocking, then used adb to boot into bootloader. Device state was locked. Ran fastboot flashing unlock but then stuck at Waiting for Device. Phone didn't go into warning to unlock bootloader.
I noticed that Boot slot is b, not sure if that matters.
Also tried to follow Google's own flash too, got stuck at the same phone screen.
Any help is appreciated.
Kenneth
Click to expand...
Click to collapse
Sounds like a driver issue. It's either the Google USB driver: https://developer.android.com/studio/run/win-usb
or the ADB driver: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
Thks for the reply. Well I can't say for sure but switching USB ports and changing cable eventually solved my issue. I kept reinstalling Google USB driver as well so any one of them could be the problem. But I really don't worry now since I successfully flashed 11 back.