Hello,
I'll try to be as specific as I can with my steps, so sorry If you don't like the format (or if its not even allowed), it's the best way I can explain step by step everything I did.
so... what do I want to do? Simply install some custom ROM to my SM-G570M so I can get rid of all the bloatware.
What's stopping me from doing it like I did it before? well...
>I flashed last version of TWRP via Odin
>Download mode (V- + Power + Home), Odin, the flash itself, everything went well, at least it appeared so
>When trying to load into it (V+ + Power + Home), I get a blue screen with android's logo and the words "Instaling system update"
>Immediately after I get another screen, this time android's logo is laying down, with a yellow ! above and the words "No command"
>Waiting a few seconds will get me to Android Recovery (the clasic move with Volume select with Power menu) with this in it:
>I factory reset my phone (I don't really know why)
this is when things get interesting (that is, frustrating af)
>Phone boots fine, but OEM Unlock is not available. Not even greyed out, not even locked. It's not there at all
>I Google about it and try about... 50 different "solutions"
>Change system date to 7+ days to the past and trigger a false Update lookout, restart... nothing
>Triggered Update lookouts twice to make the sure the phone "knows" I searched for it 10 days ago and today... nothing
>I Literally write the steps down and start superpermutating that **** for around two hours... nothing
>Some other random non-Samsung, non-my-phone-specific "solutions"... nothing
>I come across adb (never used it before, never had to)
>It claimed I could do the OEM Unlock from Windows cmd
>I download adb 15 seconds installer, adb and fastboot drivers (both), I already had Samsung specific USB drivers, everything I need
>open CMD and do adb devices
>see my device there, nice
>adb reboot bootloader
>it boots there, n i c e
>fastboot devices
>... nothing
>fastboot device, maybe it was without the s
>stuck in waiting for device
>close everything, start again
>this time I do directly fastboot OEM unlock
>waiting for device
here I'll explain what I saw in Device Manager in all my adb odyssey:
Drivers are recognized in its normal state (that is, phone connected, no dev ****, just using it) with its full name (Samsung J5 Prime bla bla bla). Besides that I have some Samsung USB Drivers showing as modems? idk why. Once I change my phone state (let's say, I do adb reboot bootloader) drivers completely dissapear. Not even showing as *Unrecognized !*, no "Android Device 1.0". It's not there at all. Only thing I see is is the usb modems? drivers.
And yes, I used every USB Port I have, the only thing it changes is a #n besides the modem drivers.
I did read you have to install drivers twice? Once in each state? I did so and nothing.
I did "Added Legacy Hardware", where I saw different ones: ADB Interface, Samsung ADB Interface, Bootloader Interface, etc. Added every single one of them, updated them (I even got the Google USB thing, it did nothing) Sometimes it would bring some error (Can't do that right now or something like that), sometimes "It's already the best we have", but still not regognizing it in cmd fastboot devices.
I also superpermutated every step I could, even doing things completely illogical. I didn't care, I stayed awake until 9AM doing it... and nothing
I did noticed, at around 5am, half asleep, that my "bootloader" window (in my phone) was... not... really... a bootloader? whenever I would adb reboot bootloader it would get me to the same Download Mode I would get by pressing V- + Power + Home. I dismissed it, not only it was really late, It could have just been a normal misunderstanding... you know, language barriers and such (I'm not english native, so I'm constantly reading things in practically two languages, maybe *Bootloader* and the *DW Mode* where actually the same and people are arbitrarily obtuse, I thought) but it still bothers me nonetheless.
I also tried, since, you know, all I want is a custom ROM, to play with Recovery Mode adb sideload? But I would always get some error 21 and other I didn't really catch.
That's my problem(s). I don't really know what to do, and I don't want to wait seven days (or more, because I read some people waiting for weeks) to have the actual OEM Unlock option in my Dev Options.
Can I get a hand with this? Is my bootloader even active? Can I even do OEM unlock in my current state? did I miss a driver, among the 100+ I downloaded even from dubious webs? Never worked with phones before so I'm practically new on this, last time I touched android I did perfectly flash TWRP through Odin and did everything from there.
please
pretty please
I'll try to be as specific as I can with my steps, so sorry If you don't like the format (or if its not even allowed), it's the best way I can explain step by step everything I did.
so... what do I want to do? Simply install some custom ROM to my SM-G570M so I can get rid of all the bloatware.
What's stopping me from doing it like I did it before? well...
>I flashed last version of TWRP via Odin
>Download mode (V- + Power + Home), Odin, the flash itself, everything went well, at least it appeared so
>When trying to load into it (V+ + Power + Home), I get a blue screen with android's logo and the words "Instaling system update"
>Immediately after I get another screen, this time android's logo is laying down, with a yellow ! above and the words "No command"
>Waiting a few seconds will get me to Android Recovery (the clasic move with Volume select with Power menu) with this in it:
>I don't really know what to do, TWRP is nowhere to be seen
>I factory reset my phone (I don't really know why)
this is when things get interesting (that is, frustrating af)
>Phone boots fine, but OEM Unlock is not available. Not even greyed out, not even locked. It's not there at all
>I Google about it and try about... 50 different "solutions"
>Change system date to 7+ days to the past and trigger a false Update lookout, restart... nothing
>Triggered Update lookouts twice to make the sure the phone "knows" I searched for it 10 days ago and today... nothing
>I Literally write the steps down and start superpermutating that **** for around two hours... nothing
>Some other random non-Samsung, non-my-phone-specific "solutions"... nothing
>I come across adb (never used it before, never had to)
>It claimed I could do the OEM Unlock from Windows cmd
>I download adb 15 seconds installer, adb and fastboot drivers (both), I already had Samsung specific USB drivers, everything I need
>open CMD and do adb devices
>see my device there, nice
>adb reboot bootloader
>it boots there, n i c e
>fastboot devices
>... nothing
>fastboot device, maybe it was without the s
>stuck in waiting for device
>close everything, start again
>this time I do directly fastboot OEM unlock
>waiting for device
here I'll explain what I saw in Device Manager in all my adb odyssey:
Drivers are recognized in its normal state (that is, phone connected, no dev ****, just using it) with its full name (Samsung J5 Prime bla bla bla). Besides that I have some Samsung USB Drivers showing as modems? idk why. Once I change my phone state (let's say, I do adb reboot bootloader) drivers completely dissapear. Not even showing as *Unrecognized !*, no "Android Device 1.0". It's not there at all. Only thing I see is is the usb modems? drivers.
And yes, I used every USB Port I have, the only thing it changes is a #n besides the modem drivers.
I did read you have to install drivers twice? Once in each state? I did so and nothing.
I did "Added Legacy Hardware", where I saw different ones: ADB Interface, Samsung ADB Interface, Bootloader Interface, etc. Added every single one of them, updated them (I even got the Google USB thing, it did nothing) Sometimes it would bring some error (Can't do that right now or something like that), sometimes "It's already the best we have", but still not regognizing it in cmd fastboot devices.
I also superpermutated every step I could, even doing things completely illogical. I didn't care, I stayed awake until 9AM doing it... and nothing
I did noticed, at around 5am, half asleep, that my "bootloader" window (in my phone) was... not... really... a bootloader? whenever I would adb reboot bootloader it would get me to the same Download Mode I would get by pressing V- + Power + Home. I dismissed it, not only it was really late, It could have just been a normal misunderstanding... you know, language barriers and such (I'm not english native, so I'm constantly reading things in practically two languages, maybe *Bootloader* and the *DW Mode* where actually the same and people are arbitrarily obtuse, I thought) but it still bothers me nonetheless.
I also tried, since, you know, all I want is a custom ROM, to play with Recovery Mode adb sideload? But I would always get some error 21 and other I didn't really catch.
That's my problem(s). I don't really know what to do, and I don't want to wait seven days (or more, because I read some people waiting for weeks) to have the actual OEM Unlock option in my Dev Options.
Can I get a hand with this? Is my bootloader even active? Can I even do OEM unlock in my current state? did I miss a driver, among the 100+ I downloaded even from dubious webs? Never worked with phones before so I'm practically new on this, last time I touched android I did perfectly flash TWRP through Odin and did everything from there.
please
pretty please
