Have s8+ on HK firmware. Cant flash anything custom due to blocked binary by frp. No oem in dev options, removed google account and samsung account, unlocked BL via CROM. Please help how to fix it. Thanks
It's a Snapdragon 835 device, which means the bootloader cannot be unlocked, just like the US carrier variant bootloaders. If your bootloader really was unlocked, FRP wouldn't be blocking custom firmware. Exynos bootloaders can be unlocked from dev settings, but not Snapdragon bootloaders.
soulless_div said:
Have s8+ on HK firmware. Cant flash anything custom due to blocked binary by frp. No oem in dev options, removed google account and samsung account, unlocked BL via CROM. Please help how to fix it. Thanks
Click to expand...
Click to collapse
Hi,
Have you followed this guide first?
https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/recovery-twrp-galaxy-s8-s8-snapdragon-t3636718
galaxyYtester said:
It's a Snapdragon 835 device, which means the bootloader cannot be unlocked, just like the US carrier variant bootloaders. If your bootloader really was unlocked, FRP wouldn't be blocking custom firmware. Exynos bootloaders can be unlocked from dev settings, but not Snapdragon bootloaders.
Click to expand...
Click to collapse
as far as i know china and HK variants may be unlocked and thats the only s8's on snap where is possible to unlock and flash custom recovery or boot.
rasseru16 said:
Hi,
Have you followed this guide first?
https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/recovery-twrp-galaxy-s8-s8-snapdragon-t3636718
Click to expand...
Click to collapse
if you mean disable R/L and unlock bootloader - yes. That is what i did. But still getting error with blocked by frp in odin
soulless_div said:
as far as i know china and HK variants may be unlocked and thats the only s8's on snap where is possible to unlock and flash custom recovery or boot.
Click to expand...
Click to collapse
You're saying that you unlocked the BL via CROM, but it's not unlocked if you can't flash custom firmware in download mode. Having a locked bootloader means that flashing custom firwmare is blocked, exactly what's happening here. If the BL can be unlocked, just unlock it, I don't get what the problem is?
galaxyYtester said:
You're saying that you unlocked the BL via CROM, but it's not unlocked if you can't flash custom firmware in download mode. Having a locked bootloader means that flashing custom firwmare is blocked, exactly what's happening here. If the BL can be unlocked, just unlock it, I don't get what the problem is?
Click to expand...
Click to collapse
explaining again.. CROM told that bootloader is unlocked( i dont know any other tools or ways to unlock bootloader on that device), but i still getting message, that it is blocked by frp, which means that something is not setted up like it should be. THat is why Im asking here fo any way to fix that issue on current device.
I'm also having this problem. Upon trying to either install TWRP 3.2.1 or chainfire's root file via ODIN, I get the error "Custom Binary (recovery) Blocked by C-ROM". I have tried to run the CROM service apk, versions 1.0.4, 1.0.6 and 1.0.7; however, upon opening, they all freeze and close, which seems to mean they didn't do anything. When going into download mode after running the CROM Service app, CROM Service is on and, when trying to install via ODIN, I get my errors.
I have the Samsung Galaxy 8+, G9550, 128gb and 6gb rom, Snapdragon Variant. I have found articles saying that the 9550 variant can be rooted since it's the HK version, although some say that it needs HK firmware. I'm on the AQF7 build.
Any help is greatly appreciated!
Related
Alright, so as the title says, I'm not asking if the bootloader is unlocked. I know it's not and its quite depressing. Anywho, I was curious what the process of unlocking is. If someone could explain in detail, that'd be awesome. I read somewhere there's something about brute forcing a SHA-256 key or RSA-1024.
If you could explain, I'd love to know!
Thanks!
Don't know about unlock process, but I found some interesting video. Some guy changes imei on g935v. After the process there is unlocked padlock at Samsung boot logo. Does it means that bootloader unlocked?
https://youtu.be/0OWO6fqG3x4
Or look here some guy claims that he flashed g930v to g930f with UAE version . And again unlocked padlock.
https://youtu.be/sIJv2gMygbI
spiderkr said:
Don't know about unlock process, but I found some interesting video. Some guy changes imei on g935v. After the process there is unlocked padlock at Samsung boot logo. Does it means that bootloader unlocked?
Or look here some guy claims that he flashed g930v to g930f with UAE version . And again unlocked padlock.
Click to expand...
Click to collapse
When the guy changed the imei did he have to root?
If so that's where the custom padlock came from most likely.
The padlock often means custom binary, which means root/non stock ROM. To see if the bootloader is unlocked you must boot to loader (vol down + power + home? Maybe vol up). There it will tell you if you are unlocked. Cool videos and thanks for sharing!
spiderkr said:
Don't know about unlock process, but I found some interesting video. Some guy changes imei on g935v. After the process there is unlocked padlock at Samsung boot logo. Does it means that bootloader unlocked?
https://youtu.be/0OWO6fqG3x4
Or look here some guy claims that he flashed g930v to g930f with UAE version . And again unlocked padlock.
https://youtu.be/sIJv2gMygbI
Click to expand...
Click to collapse
Guys this g930v to g930f is a really big deal, right? Doesn't having g930f signify the fact we can unlock the bootloader? Or does it have to be the exynos proc?
CyanideHD said:
Guys this g930v to g930f is a really big deal, right? Doesn't having g930f signify the fact we can unlock the bootloader? Or does it have to be the exynos proc?
Click to expand...
Click to collapse
Flashing the F firmware is basically like flashing the U firmware. The F's stock phone is Exynos though meaning it's bootloader unlockable. The F firmware itself won't unlock the bootloader unfortunately. I see what you are getting at though. Thanks for taking a look!
CyanideHD said:
Guys this g930v to g930f is a really big deal, right? Doesn't having g930f signify the fact we can unlock the bootloader? Or does it have to be the exynos proc?
Click to expand...
Click to collapse
Maltego said:
Flashing the F firmware is basically like flashing the U firmware. The F's stock phone is Exynos though meaning it's bootloader unlockable. The F firmware itself won't unlock the bootloader unfortunately. I see what you are getting at though. Thanks for taking a look!
Click to expand...
Click to collapse
Yes, but the F isn't just a different firmware. It's a different phone. Nothing you ever do will change our phone into the F. And you can never flash the F firmware on our phone (or vice versa).
FoxyDrew said:
Yes, but the F isn't just a different firmware. It's a different phone. Nothing you ever do will change our phone into the F. And you can never flash the F firmware on our phone (or vice versa).
Click to expand...
Click to collapse
Makes sense, thanks haha!
Is it possible to flash dev-edition firmware on our s5's to get the bootloader unlocked? No matter the cid/emmc of the device?
AWESOME1092387456 said:
Is it possible to flash dev-edition firmware on our s5's to get the bootloader unlocked? No matter the cid/emmc of the device?
Click to expand...
Click to collapse
if its locked bootloader cid then no the bootloader will prevent any unsinged firmwares to be loaded.
it would probly hard brick your device trying.
I may be wrong but this is how its been for most of time
AWESOME1092387456 said:
Is it possible to flash dev-edition firmware on our s5's to get the bootloader unlocked? No matter the cid/emmc of the device?
Click to expand...
Click to collapse
I am sure, people did that the day the Dev S5's firmware was made available. The reverse however is most definitely true, several people ended up locking their Dev S5's bootloader by flashing regular S5 firmware. They weren't able to get them unlocked until when the exploit for CID 15s was discovered and released.
I just bought Xperia X Compact in Japan, phone's carrier is NTT Docomo. (model SO-02J)
I tried *#*#7378423 , but it shows "bootloader unlock allow : NO"
then I tried ADB , but I cannot use commands like "su" , "root" . It shows : /system/bin/sh: su: not found :crying:
What can I do now to root this phone?
Or maybe I should buy a new phone that is global-version,simfree ?
I need help !
I think you cannot root without unlocking bootloader...
Maybe Kingroot...but I'm not sure...
Rikanotank1 said:
I just bought Xperia X Compact in Japan, phone's carrier is NTT Docomo. (model SO-02J)
I tried *#*#7378423 , but it shows "bootloader unlock allow : NO"
then I tried ADB , but I cannot use commands like "su" , "root" . It shows : /system/bin/sh: su: not found :crying:
What can I do now to root this phone?
Or maybe I should buy a new phone that is global-version,simfree ?
I need help !
Click to expand...
Click to collapse
You can not do anything if the bootloader is not allowed to unlock.
No bootloader unlock, no root, custom recovery (twrp), roms, etc.
What does the OEM Unlock switch in developer options say? if there is one? greyd out maybe with some explanation below?
A possible solution is to look for the F5321 model of this phone (sim free international) as I can see in xperifirm that only 1 provider (NTT DoCoMo) is tied to the SO-02J and they are also well behind with updates.
Theoretically you can use exploits in the system to gain root, but for this you need a vulnerable stock firmware. You can flash an older firmware even with locked bootloader, as long as it is stock. But I would strongly advise against permanently downgrading to a vulnerable firmware, you might not be the only one to exploit it . On that firmware, you could install root software that does not touch the kernel, but the use is limited for customizations and also realize that the whole community here revolves around unlocked phones, so all guides etc. expect that.
Hope you still enjoy your phone or find somebody else who does Not everybody cares about root and custom ROMs, I suggest you resell. If you get another model, as suggested, buy a F5321. Even branded ones, bootloader is unlockable and you remove the branding with flashing another (stock or custom) ROM.
ypnos42 said:
Theoretically you can use exploits in the system to gain root, but for this you need a vulnerable stock firmware. You can flash an older firmware even with locked bootloader, as long as it is stock. But I would strongly advise against permanently downgrading to a vulnerable firmware, you might not be the only one to exploit it . On that firmware, you could install root software that does not touch the kernel, but the use is limited for customizations and also realize that the whole community here revolves around unlocked phones, so all guides etc. expect that.
Hope you still enjoy your phone or find somebody else who does Not everybody cares about root and custom ROMs, I suggest you resell. If you get another model, as suggested, buy a F5321. Even branded ones, bootloader is unlockable and you remove the branding with flashing another (stock or custom) ROM.
Click to expand...
Click to collapse
Thanks very much !
Rikanotank1 said:
Thanks very much !
Click to expand...
Click to collapse
did you succeed?
I was looking into buying a J727V, it looks like the bootloader may be locked, obviously this stops me from putting in my own custom rom, can anyone confirm?
Last time I bought a (I think) Note 4 I had to get a developer version so that the boot loader was not locked in order to put on a custom rom.
If it is bootloader locked is there a different version of the J7 that I can get that I can use on Verizon?
MAsterOSkillio said:
I was looking into buying a J727V, it looks like the bootloader may be locked, obviously this stops me from putting in my own custom rom, can anyone confirm?
Last time I bought a (I think) Note 4 I had to get a developer version so that the boot loader was not locked in order to put on a custom rom.
If it is bootloader locked is there a different version of the J7 that I can get that I can use on Verizon?
Click to expand...
Click to collapse
yes all carrier bootloader is locked you need to buy unlocked phone or i think there are some unique processes are available also on xda to unlock boot loader but i am not confirm.
Hello, I am trying to root my Samsung s8 G950w. It is the Canadian model and was locked to Virgin Mobile.
Since the oreo 8.0 upgrade, I no longer have the unlock OEM option.
Baseband and build info is as follows
dreamqltevl/dreamqltecan/R16NW G950WVLU4BRF/
Ive tried samPWND and PartyCyborg tutorials and neither of them worked either.
Please help i have tried flashing twrp with Odin but it fails everytime. I have frp bypassed, unlocked and rooted many phones but this one is killing me
illkonikon said:
Hello, I am trying to root my Samsung s8 G950w. It is the Canadian model and was locked to Virgin Mobile.
Since the oreo 8.0 upgrade, I no longer have the unlock OEM option.
Baseband and build info is as follows
dreamqltevl/dreamqltecan/R16NW G950WVLU4BRF/
Ive tried samPWND and PartyCyborg tutorials and neither of them worked either.
Please help i have tried flashing twrp with Odin but it fails everytime. I have frp bypassed, unlocked and rooted many phones but this one is killing me
Click to expand...
Click to collapse
You cannot root or flash twrp You have upgraded your device to far and cannot downgrade to root either
SOL get a older firmwared S8 or new device
illkonikon said:
Hello, I am trying to root my Samsung s8 G950w. It is the Canadian model and was locked to Virgin Mobile.
Since the oreo 8.0 upgrade, I no longer have the unlock OEM option.
Baseband and build info is as follows
dreamqltevl/dreamqltecan/R16NW G950WVLU4BRF/
Ive tried samPWND and PartyCyborg tutorials and neither of them worked either.
Please help i have tried flashing twrp with Odin but it fails everytime. I have frp bypassed, unlocked and rooted many phones but this one is killing me
Click to expand...
Click to collapse
You have a snapdragon version that has a locked bootloader, there is no current standalone root method, if you have the latest bootloader installed then the mentioned methods you've used won't work as they haven't patched it yet. Blame the network providers for all this.
same issue
hey i got the same problem im trying to root my canadian varient s8 and im having no luck
this is my baseband information:
samsung/dreamqltevl/dreamqltecan:8.0.0/R16NW/G950WVLS5BSA1:user/release-keys
is it even possible to root this version of s8 if so how cuz everything i tried is not working
Xshady420 said:
hey i got the same problem im trying to root my canadian varient s8 and im having no luck
this is my baseband information:
samsung/dreamqltevl/dreamqltecan:8.0.0/R16NW/G950WVLS5BSA1:user/release-keys
is it even possible to root this version of s8 if so how cuz everything i tried is not working
Click to expand...
Click to collapse
5th digit back from end is bootloader revision there is now a method of rooting nougat only. No oreo or pie. Fortuanatly the method installs safestrap where you can flash a nougat system img. Su and busybox. On top of a revision 5 combination nougat bootloader. Look up s8 safestrap edl
As a side note more than likely you will convert your model to a U model instead of a w