Database Users

Flashing custom ROM on my S5 Neo G903W

I feel like I am doing something wrong here and can't figure out
I have a Samsung Galaxy S5 Neo (Virgin Mobile, Canada) G903W
I have been looking at this thread to flash LineAge OS
I can't post link but its title is
Lineage OS 14.1 for Galaxy S5 Neo (G903F, s5neoltexx) Nougat ROM
on cyanogenmod website
First off is unlocking bootloader and install TWRP, which looks simple but it isn't
Pre note: OEM unlock is enabled, rooted with chainfire/odin, USB debugging is on
I have installed ADB Fastboot on my Windows 10 PC
Got the correct TWRP image (twrp-3.1.1-2-s5neolte.img)
Then I used the instruction to download TWRP with adb
typing adb reboot bootloader just reboots the phone normally. I can still get to download mode by using combination of home+power+volume down
fastboot oem unlock just sits at <waiting for device>
same thing with fastboot flash recovery twrp-3.1.1-2-s5neolte.img
I seem to be able to flash it with Odin by pressing AP and choose the tar file but upon rebooting to download mode it just shows normal download mode screen, not TWRP.
This is my first post here, if I made any mistake or needed any more information please let me know.

deXterlab97 said:
I feel like I am doing something wrong here and can't figure out
I have a Samsung Galaxy S5 Neo (Virgin Mobile, Canada) G903W
I have been looking at this thread to flash LineAge OS
I can't post link but its title is
Lineage OS 14.1 for Galaxy S5 Neo (G903F, s5neoltexx) Nougat ROM
on cyanogenmod website
First off is unlocking bootloader and install TWRP, which looks simple but it isn't
Pre note: OEM unlock is enabled, rooted with chainfire/odin, USB debugging is on
I have installed ADB Fastboot on my Windows 10 PC
Got the correct TWRP image (twrp-3.1.1-2-s5neolte.img)
Then I used the instruction to download TWRP with adb
typing adb reboot bootloader just reboots the phone normally. I can still get to download mode by using combination of home+power+volume down
fastboot oem unlock just sits at <waiting for device>
same thing with fastboot flash recovery twrp-3.1.1-2-s5neolte.img
I seem to be able to flash it with Odin by pressing AP and choose the tar file but upon rebooting to download mode it just shows normal download mode screen, not TWRP.
This is my first post here, if I made any mistake or needed any more information please let me know.
Click to expand...
Click to collapse
just dl twrp for ur device as .tar file and flash with odin, same procedure with CF-root
here's the link https://dl.twrp.me/s5neolte/

By default Odin will reset after flashing, you need to disable this and try again. Go to the options tab and disable "Auto-Reboot".
You must boot directly to recovery mode on the first boot, otherwise it will automatically override everything and go back to the stock bootloader. TWRP warns you about this in the instructions.

Fastboot is not an option for the s5 neo. Because theree doesnt seem to be a bootloader option. Odin. Adb only will work with adbd insecure app. Or modding sbin file
---------- Post added at 05:53 AM ---------- Previous post was at 05:46 AM ----------
Make sure you have developer mode open on your phone. Select allow oem. Or set to unlock. Make sure usb debugging is enabled.
Turn the phone off.
Volume down+home button+power to open the download mode on your phone.
Open odin on your PC. Select AP
Make sure your phone is detected. You make need usb drivers..
When you see you phone on odin and the file you selected is checked by odin.
Click start. Done. Of course you must know this if youre rooted. Oops. Otherwise do that first. Same process but with the autoroot file

I'm pretty sure the problem is flashing a ROM for G903(F) on a G903(W) device

JeffG79 said:
I'm pretty sure the problem is flashing a ROM for G903(F) on a G903(W) device
Click to expand...
Click to collapse
thats not a problem at all
the differences between all s5 neo models (G903F, G903M and G903W) are so minimal that you can ignore them safely
the main differences are that they are made for different countries to meat their mobile standards (eq. support the lte bands that are used in that country)
i havent found a single critical difference between these devices based on their specs

neokronic said:
Fastboot is not an option for the s5 neo. Because theree doesnt seem to be a bootloader option. Odin. Adb only will work with adbd insecure app. Or modding sbin file
Click to expand...
Click to collapse
Is this true? I'm actually facing the same situation as the OP with a SM-G903F here. Just asking out of curiousity, not actually trying to flash the device.

Samsung J5 SM-J530f: do I need to unlock OEM bootloader to boot into TWRP?

TL;DR: Do I need to unlock OEM bootloader to boot into TWRP on the SM-J530f?
A friend of mine own a Samsung J5 (J530F), and she broke her screen (of course, USB debugging is not enabled), and she really would like to recover some files & contacts. I tried to blindly unlock the screen with an OTG keyboard, but for now, I'm not very successful (it's even harder when you never used a phone to blindly unlock it ), so I also tried to flash this TWRP recovery. (my hope is to get access to ADB shell after booting TWRP) Using heimdall, I didn't see error that looks fatal, just a minor (?) error during the session ending:
HTML:
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
However, after rebooting with Power+Volume up+Home, nothing special happens (at least given that I can't see the broken screen). And "adb shell" can't find the device.
So do you think I just did something wrong, or do I really need to unlock the bootloader to boot TWRP on the SM-J530f? If I do need to unlock the OEM, is there some signed image that could let me boot something with ADB access? If not, any other idea?
Thanks!

Odin
Hey !
I don't really understand but I could advise you to use Odin for Samsung instead ADB shell (if you use it, think to uncheck auto reboot). If you don't use it maybe try to install samsung usb drivers.
For the OEM unlock, It depend of your android version. I am not sure but you can unlock it in the dev options in the settings in Android Oreo or Nougat but not in Pie or Ten.
In theory, you can access to the device storage in recovery mode by using a computer.
I think it is all,
Cheers.

Thanks for your answer, but unfortunately I can't access the dev settings because the screen is broken. If I could go in dev settings, I'd just enable usb debugging directly.

Phone doesn't get recognised in Download mode (bootloader)

Hi Guys
So my current goal is to root my galaxy S10+ (SM-G975F) running exynos with android 11. I've seen many methods that are supposed to work for android 11, some more complicated than the others.
The method I chose to stick with, is to enter bootloader through adb using cmd on my computer and to flash twrp that way. (Bootloader is unlocked already)
After that I should be able to install magisk via twrp to complete the root access.
My inital thought was to flash twrp via odin, because odin did recognize my phone after entering bootloader. The problem was that after flashing twrp with odin and performing vol down + power then bixby + vol up + power which normally makes you enter twrp, I got stuck in a bootloop. After that I had to flash the stock ROM via Odin to "repair" my phone.
From what I've read this is due to the vbmeta protection mechanism, that you need to deactivate to avoid bootlooping.
So I heard that you can extract the boot.img file from the official firmware and edit the file with HxD Binary editor to replace a bitcode's value with a series of 0's. Unfortunately I couldn't find that specific code in boot.img.
So the remaining option was to manually flash vbmeta.img and to disable verity verification via cmd.
This is where the big problem lies, my PC does not recognize the device as soon as I enter Download mode. I tried every possible fix I could find online, they all revolve around installing certain drivers and applying them to the device in the device manager. Apparently the device needs to appear in the device manager under "other devices" with a yellow triangle then you can manually select a driver to install. Unfortunately as soon as I enter Download mode (Via cmd command or manually) my device totally disappears from the pc. Only Odin still recognises it somehow.
I installed official android device drivers, specific drivers for bootloader etc.
Every online guide about solving this problem needs you to locate the device and to apply certain drivers to it, but nothing appears for me.
I hope somebody can help me

Format data?

What your twrp version ? your twrp version must be version support 11.

You cant flash Magisk via TWRP. It doesn't work, Install the magisk App

Wrong place to ask this stuff

SM-G903F won't reboot into bootloader

Hi,
I'm on a Galaxy S5 neo (SM-G903F) running stock ROM 6.0.1. I'm using Windows 10 and both ADB and Google drivers are properly installed (the device is recognised both by adb devices and by ODIN when in download mode). OEM unlock is activated in the developer options.
I can adb reboot recovery flawlessly, but when selecting reboot to bootloader from the stock recovery, the phone just reboots to Android. Same applies when trying to abd reboot bootloader or adb reboot fastboot.
Am I missing something? Is there no bootloader unlock needed for flashing custom recoveries or ROMs for this device?

blablubb1234 said:
Hi,
I'm on a Galaxy S5 neo (SM-G903F) running stock ROM 6.0.1. I'm using Windows 10 and both ADB and Google drivers are properly installed (the device is recognised both by adb devices and by ODIN when in download mode). OEM unlock is activated in the developer options.
I can adb reboot recovery flawlessly, but when selecting reboot to bootloader from the stock recovery, the phone just reboots to Android. Same applies when trying to abd reboot bootloader or adb reboot fastboot.
Am I missing something? Is there no bootloader unlock needed for flashing custom recoveries or ROMs for this device?
Click to expand...
Click to collapse
I've working hard this week to completely reflash and root my S5 Neo on Android 7.1. If you want a clean reinstallation use this way.. or if you are already on 7.1 use only the CF_Auto_Root method.
this method work if your OEM is locked or not.
You need to download lastest firmware for your model (if found it on galaxyfirmware.com)
and For Odin, search the web for the modified version "Odin PrinceComsy"
You need the .PIT file for your phone model (ex: mine is S5NEOLTE_CAN_OPEN.pit for Canadian).
Extract firmware (AP_ BL_ CP_ CSC_files)
Launch Odin PrinceCmsy.exe (with phone disconected)
load each file BL to BL AP to AP etc...
Tick Repartition and Nand Erase under Options.
Load .PIT File (and return to the Log page)
Put your phone in download mode (vol down, home + power) click vol up to continue
Connect phone USB to Windows PC (wait loaded..)
Click START
optional, after first boot, close phone and do exactly the same thing but use the odin version coming with the CF-Auto-Root-s5neolte-s5neoltexx-smg903f. load the CF-Auto-Root-s5neolte-s5neoltexx-smg903f.tar.md5 in the AP section and click start (use default settings. no need to touch options and Pit page)
And if you want My package with all my files are using for my Canadian Galaxy S5 Neo

How to make sure to Unlock Bootloader : Samsung Galaxy A 3 : SM-A300H ; Android 5.0.2 ( Lolipop ) ?

Hi,
1. My plans are Magisk Root ( version 25.2 ) & then TWRP through TWRP Official App. I want to unlock the bootloader & make sure there are no related issues.
2. I see there is no option available for Unlocking OEM Bootloader in developer options on the model. Also tried the 7 days date fooling method but still no such options appear.
3. Fastboot commands are not recognized by the model.
4. And the bootloader screen tells : Qualcomm Secure Boot : Enable ( CSB ) & Secure Download : Enable
Please help!

LittlePro said:
Hi,
1. My plans are Magisk Root ( version 25.2 ) & then TWRP through TWRP Official App. I want to unlock the bootloader & make sure there are no related issues.
2. I see there is no option available for Unlocking OEM Bootloader in developer options on the model. Also tried the 7 days date fooling method but still no such options appear.
3. Fastboot commands are not recognized by the model.
4. And the bootloader screen tells : Qualcomm Secure Boot : Enable ( CSB ) & Secure Download : Enable
Please help!
Click to expand...
Click to collapse
Hi, Samsung doesn't have fastboot mode, it only has odin. I'm not sure, but I feel that there is no need to have an unlocked bootloader on a phone this old. I know it may sound ridiculous, but I also had a Samsung with android 5 and in the settings I enabled OEM unlocking and installed TWRP without problems using odin. Try it too

Jan Skokan said:
in the settings I enabled OEM unlocking
Click to expand...
Click to collapse
that setting is not available for this device. Probably, ''Qualcomm Secure Boot'' is it's place holder & the thing to disable.
One or two posts on this forum mentions Qualcomm Secure Boot ( CSB ). Even one thread briefs about unresolved booting / loading problems due to that.
I have another Samsung phone which has Oem Unlocking setting. When enabled, it says OEM Lock : OFF & FRP Lock : OFF & everything else quite clear / as desired.
Anyway, Thanks for the response!