G960U TMB US "Custom Binary" - Samsung Galaxy S9 Guides, News, & Discussion

Hi all i posted about the OEM toggle previously stating that's its on factory binary. Well to my surprise also i was able to finish a custom binary on my G960u tmb phone. Here is a picture it wouldn't let me boot properly because i continue to receive this security message but i remember seeing this on my g950f when its rooted but oem toggle not on. Hope this helpsi believe unlock bl is possible and will continue to try. Stuff since my phone is in warranty.
Additional info. When i first got the g960u its originally tmb on sw rev1. I stupidly accidentally flashed rev 2 on it becausei was jumping from 2 phones.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://imgur.com/gallery/RYsrkAZ

I did the OEM Unlock toggle while on factory binary. It rebooted and wiped phone. How can I tell if OEM Unlock stayed on while on this normal ROM.

Hi unless it says custom binary in odin and boots up its been removed when you wiped it

Can you post the binary file?

guys the u version US is a signed bootloader just because the oem toggle is in binary system it isnt in any other this isnt unlocking the bootloader it dont even persist over reboots or dont on s8
The only way your gonna unlock this bootloader is the key samsung signed it with

I'm going to look more into it

TheMadScientist said:
guys the u version US is a signed bootloader just because the oem toggle is in binary system it isnt in any other this isnt unlocking the bootloader it dont even persist over reboots or dont on s8
The only way your gonna unlock this bootloader is the key samsung signed it with
Click to expand...
Click to collapse
the oem toggledoes what its intended to do and does persist a reboot.. you can check when back on stock, the prop value in getprop will read sys.oem_unlock_allowed=1 (normally if u never toggled the switch will say 0)
but you are mostly correct lol.. the toggle is on but on our devices itdoesnt allow flashing custom firmware.. wehave no way to run fastboot flashing unlock commands due to no fastboot.. basically all the switch really does is disable frp from what i can tell..
also, your device says custom binary because you are mostly rev2 but one of the binary checked files you flashed is rev1 which u can see in ur screenshot while in dl mode... i imagine u were only flashing stock/combo signed firmware in odin.. if u can successfully flash an actual custom img then let usknow lol

elliwigy said:
the oem toggledoes what its intended to do and does persist a reboot.. you can check when back on stock, the prop value in getprop will read sys.oem_unlock_allowed=1 (normally if u never toggled the switch will say 0)
but you are mostly correct lol.. the toggle is on but on our devices itdoesnt allow flashing custom firmware.. wehave no way to run fastboot flashing unlock commands due to no fastboot.. basically all the switch really does is disable frp from what i can tell..
also, your device says custom binary because you are mostly rev2 but one of the binary checked files you flashed is rev1 which u can see in ur screenshot while in dl mode... i imagine u were only flashing stock/combo signed firmware in odin.. if u can successfully flash an actual custom img then let usknow lol
Click to expand...
Click to collapse
Don't they flash Twrp through a custom version of Odin on the China and Hong Kong Snapdragon S9s? If so then this should all work together to get root correct?
---------- Post added at 12:33 PM ---------- Previous post was at 12:25 PM ----------
Vell123 said:
Hi all i posted about the OEM toggle previously stating that's its on factory binary. Well to my surprise also i was able to finish a custom binary on my G960u tmb phone. Here is a picture it wouldn't let me boot properly because i continue to receive this security message but i remember seeing this on my g950f when its rooted but oem toggle not on. Hope this helpsi believe unlock bl is possible and will continue to try. Stuff since my phone is in warranty.
Additional info. When i first got the g960u its originally tmb on sw rev1. I stupidly accidentally flashed rev 2 on it becausei was jumping from 2 phones.
https://imgur.com/gallery/RYsrkAZ
Click to expand...
Click to collapse
Which firmware did you flash exactly? I am going to try some things on my s9 to see if I can get TWRP to flash through the custom Odin software. They already have twrp made for the China and Hong Kong snapdragon s9. If we get twrp flashed then we can do it all. There is also a file to flash to make oem toggle persist. Which firmware did you flash and which thread was it on? Do I have to flash the custom binary to get oem toggle? Thanks! I hope we get this figured out

jflow36 said:
Don't they flash Twrp through a custom version of Odin on the China and Hong Kong Snapdragon S9s? If so then this should all work together to get root correct?
---------- Post added at 12:33 PM ---------- Previous post was at 12:25 PM ----------
Which firmware did you flash exactly? I am going to try some things on my s9 to see if I can get TWRP to flash through the custom Odin software. They already have twrp made for the China and Hong Kong snapdragon s9. If we get twrp flashed then we can do it all. There is also a file to flash to make oem toggle persist. Which firmware did you flash and which thread was it on? Do I have to flash the custom binary to get oem toggle? Thanks! I hope we get this figured out
Click to expand...
Click to collapse
no it shouldnt and it hasnt been for years now.. the firmware is different mainly the bootloader which theirshas a "crom" lock on it which they use crom apk to unlock it whereas our devices have no such crom lock or apk to unlock the bl.. and no, crom.apk will not work for us as our bl is different and ours doesnt have the same locking mechanisms as well as we cant even install it without root

jflow36 said:
Don't they flash Twrp through a custom version of Odin on the China and Hong Kong Snapdragon S9s? If so then this should all work together to get root correct?
---------- Post added at 12:33 PM ---------- Previous post was at 12:25 PM ----------
Which firmware did you flash exactly? I am going to try some things on my s9 to see if I can get TWRP to flash through the custom Odin software. They already have twrp made for the China and Hong Kong snapdragon s9. If we get twrp flashed then we can do it all. There is also a file to flash to make oem toggle persist. Which firmware did you flash and which thread was it on? Do I have to flash the custom binary to get oem toggle? Thanks! I hope we get this figured out
Click to expand...
Click to collapse
he never flashed s custom binary lol.. just bcuz it says that in odin doesnt mean its custom.. more like he mixed up his rev versions..
the "custom" odin u speak of has nothin really to do with it.. it only disableshash checks, flash will still fail if bl is locked which it will remain so until theres some new exploits found
all the recent methods were patched with the s8/s8+ with regards to odin.. but good luck lol maybe ull have a freakish luck and find something

jflow36 said:
Don't they flash Twrp through a custom version of Odin on the China and Hong Kong Snapdragon S9s? If so then this should all work together to get root correct?
---------- Post added at 12:33 PM ---------- Previous post was at 12:25 PM ----------
Which firmware did you flash exactly? I am going to try some things on my s9 to see if I can get TWRP to flash through the custom Odin software. They already have twrp made for the China and Hong Kong snapdragon s9. If we get twrp flashed then we can do it all. There is also a file to flash to make oem toggle persist. Which firmware did you flash and which thread was it on? Do I have to flash the custom binary to get oem toggle? Thanks! I hope we get this figured out
Click to expand...
Click to collapse
he never flashed s custom binary lol.. just bcuz it says that in odin doesnt mean its custom.. more like he mixed up his rev versions..
the "custom" odin u speak of has nothin really to do with it.. it only disableshash checks, flash will still fail if bl is locked which it will remain so until theres some new exploits found
all the recent methods were patched with the s8/s8+ with regards to odin.. but good luck lol maybe ull have a freakish luck and find something
also to add, twrp would need to be built most likely for our specific variant.. you might think theyre the same but theyre not.. else youd see all them flashing u and u1 firmware to their unlocked devices

elliwigy said:
he never flashed s custom binary lol.. just bcuz it says that in odin doesnt mean its custom.. more like he mixed up his rev versions..
the "custom" odin u speak of has nothin really to do with it.. it only disableshash checks, flash will still fail if bl is locked which it will remain so until theres some new exploits found
all the recent methods were patched with the s8/s8+ with regards to odin.. but good luck lol maybe ull have a freakish luck and find something
Click to expand...
Click to collapse
I dunno... I'm kinda nervous to attempt... I'm almost ready to give up and sell my s9.

Related

[Q] Return to stock

Hi,
I have a Moto X xt1058, with 4.2.2 post camera update, locked bootloader but rooted. I've been postponing the OTA to 4.4 for a while now. I now i can't just install it, because of the modifications i've been doing while rooted, and i'm pretty sure i can't restore everything i've done.
It seems that is pretty easy to brick this phone while changing versions. I would like to return it to stock, so that i can accept all OTAs. I don't care losing any data or root permissions. I've found this method to return to stock here in XDA:
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
(cant post urls)
Android SDK
(cant post urls)
MFastboot(Used for manually downgrading to 4.2.2)
(cant post urls)
For firmware Download pick what firmware you want from the link below
(cant post urls)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
I would like to know if there's any risk in doing this, or which would be the better way to get to android 4.4.
Thanks!
You can flash the same or higher versions . It's downgrading that bricks. On 4.4.2 and higher. ?
KJ said:
You can flash the same or higher versions . It's downgrading that bricks. On 4.4.2 and higher. ?
Click to expand...
Click to collapse
So does that mean if my carrier give me an update from 4.4.2 to 4.4.4 i can take it and not worry. Also, with an unlocked boot loader will it re lock it?
Thanks
vagh_nagas said:
So does that mean if my carrier give me an update from 4.4.2 to 4.4.4 i can take it and not worry. Also, with an unlocked boot loader will it re lock it?
Thanks
Click to expand...
Click to collapse
No, it won't relock it. But, you can't take an ota if you have a custom recovery or have made many system changes....like Xposed. It needs to be uninstalled, properly.
KJ said:
No, it won't relock it. But, you can't take an ota if you have a custom recovery or have made many system changes....like Xposed. It needs to be uninstalled, properly.
Click to expand...
Click to collapse
Okay, so that means that as long as I leave the recovery alone, and uninstall xposed before i take the update I can keep the boot loader. that is good. but does that mean that I can easily re root it? also thanks for the help, I have never rooted a phone that still gets updates and that is activated.
vagh_nagas said:
Okay, so that means that as long as I leave the recovery alone, and uninstall xposed before i take the update I can keep the boot loader. that is good. but does that mean that I can easily re root it? also thanks for the help, I have never rooted a phone that still gets updates and that is activated.
Click to expand...
Click to collapse
If you have the stock recovery, yes....that's good. As long as Xposed is the only system changes you've done....You should be good.
Root is the same as any version with an unlocked bootloader.
But how did you root without a custom recovery?
OP, you can just use RSDlite to update directly to 4.4.4. Just download RSDlite, as well as the 4.4.4 firmware for your phone. Boot to fastboot while keeping your phone plugged in to your PC with USB debugging on, and RSDlite will detect your phone on fastboot mode. Select the firmware zip and flash it.
KJ said:
If you have the stock recovery, yes....that's good. As long as Xposed is the only system changes you've done....You should be good.
Root is the same as any version with an unlocked bootloader.
But how did you root without a custom recovery?
Click to expand...
Click to collapse
When I first tried to use xposed, I Soft bricked my phone. That was just using towel pie's method of root. So I decided that it was not a good idea to do any modifications to my phone that I did not feel I had much control over. That is why I used the 4.4.2 boot loader unlocker (I forgot who made it already, sorry) . After that I re-installed a newer version of towel pie, and super SU (I have better luck keeping root with this app), and towel pie asked if I was going to install xposed and i said yes. then I attempted the xposed and reboot. at first it had said that it did not install correctly. then after the third time of me attempting it it and after soft rebooting the phone after using towel pie's software it let me keep xposed. I believe it was the soft restart that did it but I am not quite sure.
I have pics if you want to see my recovery.
Just to let people know i am using a Republic Wireless Moto X, That is why I must leave the recovery alone. Yes all features still work as if I had done nothing to it, Just in case some people were wondering that have this service.
---------- Post added at 11:49 PM ---------- Previous post was at 11:10 PM ----------
Another question I have for somebody that has republic wireless. if I unlocked my boot loader can I go back to jelly bean or is that just an impossibility?
mauri6870 said:
OP, you can just use RSDlite to update directly to 4.4.4. Just download RSDlite, as well as the 4.4.4 firmware for your phone. Boot to fastboot while keeping your phone plugged in to your PC with USB debugging on, and RSDlite will detect your phone on fastboot mode. Select the firmware zip and flash it.
Click to expand...
Click to collapse
so in my case i can flash my careers firmware (4.4.4) while on 4.2.2? there's no risk bricking it that way? or if i get the same firmware (4.2.2 post cam) right?
jisola said:
so in my case i can flash my careers firmware (4.4.4) while on 4.2.2? there's no risk bricking it that way? or if i get the same firmware (4.2.2 post cam) right?
Click to expand...
Click to collapse
Right.
Tho, let it be said....everything we do on XDA, everything , comes with risk.
Anything can go wrong, anytime.
Just wanted to remind of that. No one will, or at least should, guarentee anything on XDA. We all take the responsibility ourselves if something goes very wrong.
?
So in theory , yes, you should be absolutely fine. But again....stuff happens. Proceed at your own risk.
jisola said:
Hi,
I have a Moto X xt1058, with 4.2.2 post camera update, locked bootloader but rooted. I've been postponing the OTA to 4.4 for a while now. I now i can't just install it, because of the modifications i've been doing while rooted, and i'm pretty sure i can't restore everything i've done.
Click to expand...
Click to collapse
Before you upgrade, do you want to root after you've upgraded?
If so, you need to be aware of what can/can't be done BEFORE you update.
well, like things usually happen, if there's risk it will go wrong.
i flashed my careers 4.4.2 and kind of brick it. when it powers up the motorola logo shows up and instantly enters ap fastboot mode with the security downgrade failure.
i'll try flashing a 4.2.2 firmware (same career) to see if that fixes it, if not, i dont know what else could i try.
thanks everyone for your comments!
jisola said:
well, like things usually happen, if there's risk it will go wrong.
i flashed my careers 4.4.2 and kind of brick it. when it powers up the motorola logo shows up and instantly enters ap fastboot mode with the security downgrade failure.
i'll try flashing a 4.2.2 firmware (same career) to see if that fixes it, if not, i dont know what else could i try.
thanks everyone for your comments!
Click to expand...
Click to collapse
If your bootloader is unlocked and you can get to a functioning bootloader mode you are not bricked.
Wansanta said:
If your bootloader is unlocked and you can get to a functioning bootloader mode you are not bricked.
Click to expand...
Click to collapse
i have a locked bootloader...
i've tried flashing 4.2.2 and there were a lot of errors during installation that werent there when i tried to go to 4.4, after flashing was complete i got the same boot error, is there anything else to try?
jisola said:
great to hear that, i have a locked bootloader
Click to expand...
Click to collapse
Locked is above my paygrade.
But by functioning bootloader I mean you can use fastboot commands to flash.
lanemst curr
Wansanta said:
Locked or unlocked?
Click to expand...
Click to collapse
i edited... i misread when u said unlocked...
jisola said:
i edited... i misread when u said unlocked...
Click to expand...
Click to collapse
Have you tried sunshine to see if you can unlock? I don't know if it would work in the state your phone is in but it is worth the $25 if it would work.
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Also, this site has resources on it for the XT1058 but make sure you read them thoroughly and understand what you are doing b/f you proceed with any of these methods.
http://www.theandroidsoul.com/?s=xt1058
Of the utmost importance is that you know what version of the bootloader your device is on. You MUST know this b/f you do anything. What version is it?
Wansanta said:
Have you tried sunshine to see if you can unlock? I don't know if it would work in the state your phone is in but it is worth the $25 if it would work.
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Also, this site has resources on it for the XT1058 but make sure you read them thoroughly and understand what you are doing b/f you proceed with any of these methods.
http://www.theandroidsoul.com/?s=xt1058
Of the utmost importance is that you know what version of the bootloader your device is on. You MUST know this b/f you do anything. What version is it?
Click to expand...
Click to collapse
thanks for all this help.
never heard of sunshine before, i assume is way to unlock your bootloader right?
im kind of new with bootloaders phones, how could i check my bootloader version, doesn't seem to appear in the fastboot menu
jisola said:
how could i check my bootloader version, doesn't seem to appear in the fastboot menu
Click to expand...
Click to collapse
It is the second line. Mine is 30:B7 b/c I am on 4.4.4.
Wansanta said:
It is the second line. Mine is 30:B7 b/c I am on 4.4.4.
Click to expand...
Click to collapse
thanks again
mine is: 30.B4

Remove this thread please.

Removed because SM-G935U is bootloader locked. Please close this thread.
travis82 said:
This is for the U.S. Unlocked variant. SM-G935U
Flash twrp via odin: https://www.androidfilehost.com/?fid=385035244224389793
Rom (bloated) + Kernel: re-doing rom
no-verity-opt-encrypt-2.1.zip: https://www.androidfilehost.com/?fid=385035244224381666
Flash twrp via odin, Boot up in to twrp, format data partition, flash the rom that you copied to your phones sd or microsd card, than flash no-verity because I forgot to fix it in your kernels ramdisk.
This is a test our devies are exactly the same minus the dual sim card part. Please post back and let me know O the rom is pre rooted and the kernel is permissive too.
Click to expand...
Click to collapse
Crossing my fingers that something good will come of this though I am a bit skeptical.
Hi there. I TEST it on my G935T but not with out some issue. Flashing the rom TRIPS QUALCOMM SECURITY BOOT, the BINARY GOES CUSTOM. To BOOT the phone, you'll have to FLASH THE US SM-G935 Samsung_G935x_QC_Rooted_BOOT Tar file for the phone to BOOT. That FILE changes the BINARY from CUSTOM to OFFICIAL and BOOT up. Next issue, the PHONE randomly REBOOT WHILE THE WI-FI ON. Turn off the WIFI and skip through everything, and you'll be ok after that. The PHONE I used to FLASH THE ROM HAVE NO SIM CARD IN IT, So I don't know if you'll get RANDOM REBOOTS AS IT CONNETED TO LTE. As for the ROM, it LOOKS FAIRLY AS STOCK G935U FIRMWARE. I compared it with my G935T RUNNING STOCK OFFICIAL G935U FIRMWARE, it LOOKS THE SAME EXCEPT FOR THE VOICEMAIL APP and the phone SAY CUSTOM. IT WOULD OF WORK, it just have to prepared different to FLASH USING FLASHFIRE app. Just a little bit more TWEAKS AND IT WILL RUN ON ALL US SNAPDRAGON SM-G935 MODELS.
Okay so what's all been debloated? Also had issues with twrp recently when I downloaded it through the play store. Next question is SU removed when doing a hard reset? Otherwise than those of definitely want to run it. Let me set up an account here, I have some questions like removing knock and stuff like that but if you could answer what I asked it'd be great.
\_○RD_b€rU$ said:
Okay so what's all been debloated? Also had issues with twrp recently when I downloaded it through the play store. Next question is SU removed when doing a hard reset? Otherwise than those of definitely want to run it. Let me set up an account here, I have some questions like removing knock and stuff like that but if you could answer what I asked it'd be great.
Click to expand...
Click to collapse
It says this is a bloated ROM, and download directly from the links provided for the best chance of it working. There is a reason they provide the downloads sometimes.
Ok so let me get this strait. That bootimage sets the status to official? is that because its a stock kernel? The wifi can be fixed with a default.prop edit so can secure storage. Give me more info on that boot tar you guys have to use. Maybe I can modify it with my kernel blob so it boots through still.
G935U Int unlocked users, did you use crom.apk to unlock your bootloaders? If so I can compile a kernel for YOU when I get the time. But if you used crom.apk than unlocked your bootloaders, than in dev options have oem unlock checked still, that top rom and kernel should boot up. The wifi issues, you can fix by editing default.prop, secure storage also.
So I really need you G935U users to speak up like I had to tell the dual sim guys. Does this work on SM-G935U? :
Download and install S6-Crom.apk, it will allow the bootloader to be unlocked for the S7 Edge SM-G9350:
http://forum.xda-developers.com/attachment.php?attachmentid=3270074&d=1429412423
NOTE: You must Enable Developer Options in Settings and turn on OEM Unlock!!!
travis82 said:
This is for the U.S. Unlocked variant. SM-G935U
Flash twrp via odin: https://www.androidfilehost.com/?fid=385035244224389793
Rom (bloated): https://www.androidfilehost.com/?fid=457095661767106988
Kernel permissive: https://www.androidfilehost.com/?fid=457095661767106995
no-verity-opt-encrypt-2.1.zip: https://www.androidfilehost.com/?fid=385035244224381666
Flash twrp via odin, Boot up in to twrp, format data partition, flash the rom that you copied to your phones sd or microsd card, than flash no-verity because I forgot to fix it in your kernels ramdisk.
This is a test your devies are exactly the same minus the dual sim card part. Please post back and let me know O the rom is pre rooted and the kernel is permissive too.
Click to expand...
Click to collapse
Can Twrp be flashed on a Tmobile s7Edge flashed with the U firmware?????
travis82 said:
G935U Int unlocked users, did you use crom.apk to unlock your bootloaders? If so I can compile a kernel for YOU when I get the time. But if you used crom.apk than unlocked your bootloaders, than in dev options have oem unlock checked still, that top rom and kernel should boot up. The wifi issues, you can fix by editing default.prop, secure storage also.
So I really need you G935U users to speak up like I had to tell the dual sim guys. Does this work on SM-G935U? :
Download and install S6-Crom.apk, it will allow the bootloader to be unlocked for the S7 Edge SM-G9350:
http://forum.xda-developers.com/attachment.php?attachmentid=3270074&d=1429412423
NOTE: You must Enable Developer Options in Settings and turn on OEM Unlock!!!
Click to expand...
Click to collapse
Well, I can't speak for the genuine 935U, but I tried it on my SM-G935R4 (US Cellular) and it force-closes upon opening. If it helps at all, I'm not running the stock USCC ROM, but rather the Verizon-based Stang5.0litre custom ROM that can be found over in the Verizon S7E forum. I've successfully used the 935U firmware on this phone also. Kinda makes me think it's not gonna work on a real 935U either, but I dunno.
(Oh and yeah, I've been wondering about TWRP too - Can we really flash it through Odin despite the bootloader lock?)
The G935U bootloader cannot be unlock nor can any USA S7 models that I know of. I tried to flash the twrp after installing the s6-crom.apk , but twrp won't flash and the s6-crom.apk keeps FC.
Sent from my SM-G935U using Tapatalk
Than what model is the unlocked single sim s7 edge snapdragon?
It's the SM-G935U it has sim unlocked but has a locked bootloader.
Sent from my SM-G935U using Tapatalk
travis82 said:
Than what model is the unlocked single sim s7 edge snapdragon?
Click to expand...
Click to collapse
I believe there's a Chinese version with snapdragon that's G9300 not G930U
Kernel no funciona el enlace
---------- Post added at 05:32 AM ---------- Previous post was at 05:26 AM ----------
Does not work the link to the amigo kernel, you can pass it to me please? Best regards!
travis82 said:
G935U Int unlocked users, did you use crom.apk to unlock your bootloaders? If so I can compile a kernel for YOU when I get the time. But if you used crom.apk than unlocked your bootloaders, than in dev options have oem unlock checked still, that top rom and kernel should boot up. The wifi issues, you can fix by editing default.prop, secure storage also.
So I really need you G935U users to speak up like I had to tell the dual sim guys. Does this work on SM-G935U? :
Download and install S6-Crom.apk, it will allow the bootloader to be unlocked for the S7 Edge SM-G9350:
http://forum.xda-developers.com/attachment.php?attachmentid=3270074&d=1429412423
NOTE: You must Enable Developer Options in Settings and turn on OEM Unlock!!!
Click to expand...
Click to collapse
We don't have unlocked bootloaders crom apk force closes on opening it
Has anyone tried this on the G935U with success or can this device be rooted?
This doesn't work for the SM-G935U the crom.apk force closes without it we cannot unlock bootloader
Sent from my SM-G935U using Tapatalk
Twrp doesn't flash thru Odin. I have eng bootloader installed but Odin freezes at start. How long should it take to start to flash?
Any update on this
I've tried loading twrp through odin but keep getting a fail. I'm rooted and was wondering if it's easier to just add it through adb? Or would it be possible to flash it through the terminal emulator? I'd really like to get exposed on my phone lol I'm Currently on a 935A with the 935U firmware Rooted

Galaxy S9 SM-G960U (Snapdragon) Engineering ROM

Hi, I just wanted to share what I just came across. I'm sure this will help getting root. I found a hybrid stock/samsung testing rom. Check it out, I'm sure it'll help us get root. https://drive.google.com/uc?id=1xQbXIDex1aDaAHoBmoecXPZkjtuQFAyC&export=download
UPDATE: There is an option to OEM UNLOCK. It seems to have full adb control.
MetalPhoenix45 said:
Hi, I just wanted to share what I just came across. I'm sure this will help getting root. I found a hybrid stock/samsung testing rom. Check it out, I'm sure it'll help us get root. https://drive.google.com/uc?id=1xQbXIDex1aDaAHoBmoecXPZkjtuQFAyC&export=download
Click to expand...
Click to collapse
I'll take a look at it.. question is, where'd you get it and do they have a g965u version?
To add, looks like a regular combo firm, they have OEM unlock option in settings and adb debuggable and permissive
Im not sure if they have a 965u version. I found it while trying to find an engineer kernel.
Any idea what the security patch is? I'm on May with the version 2 bootloader so I dunno if I can flash this but if it's the newer bootloader I could do some tests.
So I reset my s9 and I get this when trying to flash the combination ROM.
Any suggestions or is this due to the bootloader being V2
Forgot to attach the image.
ChongoDroid said:
Forgot to attach the image.
Click to expand...
Click to collapse
I didn't get that error but I was on the April patch. That particular ROM was in the January patch I believe. I did use the modified ODIN by Raymonf.
My bad I meant the February patch (T-Mobile isn't sending any updates)
From initial look at it, it appears to be a standard combination firmware
Yeah I'm on the may update so I don't think I can flash it. Best of luck hopefully someone can find something useful with it. Anybody get it to respond to fastboot commands?
What does this mean? Can I potentially flash this, unlock my bootloader, flash TWRP?
Malvarose said:
What does this mean? Can I potentially flash this, unlock my bootloader, flash TWRP?
Click to expand...
Click to collapse
no
Well there isn't a twrp for the snapdragon variant. However, to be fair we don't actually know what we can do with this.
ChongoDroid said:
Well there isn't a twrp for the snapdragon variant. However, to be fair we don't actually know what we can do with this.
Click to expand...
Click to collapse
There is an unofficial twrp for Chinese snapdragon models. But I did try flashing it and with no success.
MetalPhoenix45 said:
There is an unofficial twrp for Chinese snapdragon models. But I did try flashing it and with no success.
Click to expand...
Click to collapse
Did you unlock your bootloader? What did it spit out after issuing fastboot commands
---------- Post added at 05:19 PM ---------- Previous post was at 05:15 PM ----------
Try
fastboot flashing unlock
or
fastboot flashing unlock_critical
lemme know what it says.
I'm pretty sure fastboot commands don't work on Samsung phones. I tried fastboot devices and nothing showed up
Ah gotcha. Yeah I'm not too experienced with Samsung but from what I've read cf autoroot is the way to go or unlock with heimdall.
I guess ive got some reading up to do.
There's a guy trying to root but he needs the ENG ROM, so I sent him the link, hope he can do something
There's a link for all combination ROM either for s9 as well as s9+
https://www.t-flash.net/samsung-combination-firmware/
Is possible to flash the ZTO G9600 (brazilian rom) to the 960u device I've bought in USA?
Thank you.

OTA 9.0 Update RET EU

Did someone in the RETEU Channel allready have this ?
I dont see it on lolinet.
Also. Is it possible that i flash a RETUS or DTEU image towards my phone ? Do i still get the RET EU updates or does it not matter?
Kind regards and thanks !
You won't be able to flash the boot.img from RETUS or the international version and you won't get OTA updates if you have an unlocked bootloader.
If it's not in the firmware list yet, the update likely isn't out yet. I'm using a German Moto G6 with the ALI_RETAIL_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC firmware and it works really well.
@HeavyHDx Idid the same, but my device got the reteu PIE upgrade today.
mcc2005 said:
@HeavyHDx Idid the same, but my device got the reteu PIE upgrade today.
Click to expand...
Click to collapse
I updated with the from stated before. But then when i tried to call i could not hear anyone nor they could hear me... Searched the internet. Tried all solutions... nothing helped...
Rerolled to 8.0 If you got it yesterday i hope i get it soon then.
H377Y said:
I updated with the from stated before. But then when i tried to call i could not hear anyone nor they could hear me... Searched the internet. Tried all solutions... nothing helped...
Rerolled to 8.0 If you got it yesterday i hope i get it soon then.
Click to expand...
Click to collapse
Did you end up getting the update? Sadly the firmware isn't on lolinet yet (the hell kind of name is that anyway?)
https://mirrors.lolinet.com/firmware/moto/ali/official/RETEU/
Downgrading to 8.0 and locking the bootloader won't work since even an unlocked bootloader won't allow you to install older versions. I'm not sure if you can actually get OTA updates with an unlocked bootloader.
Does anyone have the OTA package? It's still nowhere to be found and Motorola support can't provide me with the firmware file unfortunately.
They finally added it:
https://mirrors.lolinet.com/firmware/moto/ali/official/RETEU/
---------- Post added at 01:26 PM ---------- Previous post was at 12:49 PM ----------
Ok so this is disappointing, I'm still getting "(bootloader) Image signed with key bad key" on boot.img even though this is definitely the right version for my phone (XT1925-5 RETEU). Any ideas? I've tried literally every boot.img that's available from that site and none worked. I want to relock my bootloader to give the phone to someone else who needs updates to work.
HeavyHDx said:
They finally added it:
https://mirrors.lolinet.com/firmware/moto/ali/official/RETEU/
---------- Post added at 01:26 PM ---------- Previous post was at 12:49 PM ----------
Ok so this is disappointing, I'm still getting "(bootloader) Image signed with key bad key" on boot.img even though this is definitely the right version for my phone (XT1925-5 RETEU). Any ideas? I've tried literally every boot.img that's available from that site and none worked. I want to relock my bootloader to give the phone to someone else who needs updates to work.
Click to expand...
Click to collapse
You can relock it; it's a little complicated though.
Care to elaborate?
HeavyHDx said:
They finally added it:
https://mirrors.lolinet.com/firmware/moto/ali/official/RETEU/
---------- Post added at 01:26 PM ---------- Previous post was at 12:49 PM ----------
Ok so this is disappointing, I'm still getting "(bootloader) Image signed with key bad key" on boot.img even though this is definitely the right version for my phone (XT1925-5 RETEU). Any ideas? I've tried literally every boot.img that's available from that site and none worked. I want to relock my bootloader to give the phone to someone else who needs updates to work.
Click to expand...
Click to collapse
Bad key is normal. It doesn't mean anything is wrong, it just means your bootloader is unlocked. You can also take OTAs with an unlocked bootloader. The bootloader and gpt.bin refusing to flash is also normal. Bootloader's don't allow downgrades, so it keeps the most recent one. You can skip it if that happens. Just flash everything else in order. You can also downgrade. However, if you flash a firmware that's too old, sometimes the radio or touchscreen won't work. If that happens, just flash a more recent firmware. (Ex. Instead of using the first Oreo firmware, use the latest Oreo release.)
And is relocking the bootloader possible at all?
HeavyHDx said:
And is relocking the bootloader possible at all?
Click to expand...
Click to collapse
It's possible, but I wouldn't recommend doing it. If one thing about the system is off, it'll lock you into read only mode, which will brick the phone. Not even stock firmware can flash in read only. I'm also uncertain of the exact commands to do it. I'd tell you how if I knew. Motorola has their own set of commands they like to use for it.

Oneplus nord N100 Root-10.5.4

The boot.img posted below is from firmware
Oxygen OS 10.5.4 BE81AA
If your looking to root download magisk canary from this link
(I have posted stock boot.img and a patched boot.img for the original boot.img this is just a quick post for those looking to root there oneplus Nord n100 I have provided everything you will need if you need a tut on how the root process goes refer to google or youtube On how to flash the boot.img to get magisk to work
BUT BEFORE YOU DO ANYTHING YOU WILL HAVE TO UNLOCK THE BOOTLOADER THE FASTBOOT COMMAND TO DO SO IS
fastboot oem unlock
Use volume key to highlight unlock the bootloader
Use the power key to select unlock the bootloader
***If you don't no how to get to the bootloader refer to youtube***
Oneplus Nord n100 stock boot.img
You can download the file here:
boot.img
Yandex
Finds everything
yadi.sk
EDIT: I went ahead and patched the boot.img so all you will have to do is download magisk apk and flash the boot.img via fastboot
You can download the file here:
magisk_patched_suVe7.img
Yandex
Finds everything
yadi.sk
Magisk apk
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Safetynet will not pass within magisk here is a magisk flashable zip to fix safetynet
After flash and reboot of phone check within magisk to see if it has worked
You can download the file here:
safetynet-fix-v1.1.0.zip
Yandex
Finds everything
yadi.sk
Is there a way to roll back from the latest update? The oem unlocking switch is greyed out and doesn't work now. I'll post the new build number with this post.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DenverMO said:
Is there a way to roll back from the latest update? The oem unlocking switch is greyed out and doesn't work now. I'll post the new build number with this post.
View attachment 5225783
Click to expand...
Click to collapse
You can still root on the latest version:
Download the stock firmware of your version from OnePlus' website
Extract the boot.img with payload dumper
Unlock the bootloader
Download Magisk Manager
Use it to patch the boot.img from earlier
flash the patched boot.img with fastboot
EDIT: I didn't read the post correctly. The reason your OEM unlocking is greyed out is likely because your carrier disabled it. There's a high chance you can't fix that, but you can still try manually updating to the latest version using the link from step 1 by choosing to manually update from zip file (when it's done updating remove your SIM card to get rid of any chance of carrier tampering).
DenverMO said:
Is there a way to roll back from the latest update? The oem unlocking switch is greyed out and doesn't work now. I'll post the new build number with this post.
View attachment 5225783
Click to expand...
Click to collapse
Connect to your carrier with a SIM, and then it should be un-greyed out.
If not, reset the N100, and then setup from the beginning with a SIM.
Is there TWRP or other recovery for N100?
I'm also having issues with unlocking the bootloader in the dev settings. it's greyed out. I called Metropcs and they told me it takes 180 days before you can unlock the phone. There is a little "Unlock" application on the phone but I guess it won't actually work until after 6 months.
I'm here wondering if there is any way around this? or if there is a way we can obtain root and/or install a custom recovery somehow. or perhaps even unlock the bootloader before 180 days?
I'm on version 10.5.9.BE82CF but when I go to the official OnePlus website it's showing me version 10.5.5.BE81AA which seems to be an older version. And there isn't any options on the site to view any other versions.
would it be possible to somehow downgrade to 10.5.4 and use the pattched boot image provided here then acquire root?
Edit: ok I did a little more digging and found this quote from another user on this forum:
Units with model numbers BE2012 (T-Mobile) and BE2015 (Metro by T-Mobile) are running a special version of the OS which lacks local update and therefore cannot install updates manually. Sideloading the system update APK and trying anyway would not work as the device name for these units is different.
Click to expand...
Click to collapse
so basically the nord from Metropcs runs a sliightly diff of than the others.
10.5.7.BE81AA magisk patched boot_*.img
BenTheTechGuy said:
You can still root on the latest version:
Download the stock firmware of your version from OnePlus' website
Extract the boot.img with payload dumper
Unlock the bootloader
Download Magisk Manager
Use it to patch the boot.img from earlier
flash the patched boot.img with fastboot
EDIT: I didn't read the post correctly. The reason your OEM unlocking is greyed out is likely because your carrier disabled it. There's a high chance you can't fix that, but you can still try manually updating to the latest version using the link from step 1 by choosing to manually update from zip file (when it's done updating remove your SIM card to get rid of any chance of carrier tampering).
Click to expand...
Click to collapse
hi
to patch the boot.img with Magisk Manager?
I'm on build 10.5.11 model BE2015, and OEM is grey-out. I do have carrier service and I recently got this phone . So I want to OEM toggle option for unlocking bootloader
Smil3yWulf said:
I'm on build 10.5.11 model BE2015, and OEM is grey-out. I do have carrier service and I recently got this phone . So I want to OEM toggle option for unlocking bootloader
Click to expand...
Click to collapse
I think you have to wait 6 months to 1 year depending on your service provider. I have this phone on MetroPcs by Tmobile and I have to wait 6 months before I can unlock it
My phone forced the update to Android 11. I even downgraded to 10.5.8 again, had root working, and without any prompts at all it restarted on it's own and updated. I don't see the version 11 image on the OnePlus website yet. Any ideas?
If only someone would post the OTA zip file! Please! My n100 (BE81AA) updated overnight without warning and I lost root. I'd really like to get a hold of it so I could patch boot.img and get root back.
Does anyone know how to get the OTA zip file after the update has run? Any other ways to re-obtain root without flashing back to android 10? Any advice would be greatly appreciated!
mozingodavid8 said:
The boot.img posted below is from firmware
Oxygen OS 10.5.4 BE81AA
If your looking to root download magisk canary from this link
(I have posted stock boot.img and a patched boot.img for the original boot.img this is just a quick post for those looking to root there oneplus Nord n100 I have provided everything you will need if you need a tut on how the root process goes refer to google or youtube On how to flash the boot.img to get magisk to work
BUT BEFORE YOU DO ANYTHING YOU WILL HAVE TO UNLOCK THE BOOTLOADER THE FASTBOOT COMMAND TO DO SO IS
fastboot oem unlock
Use volume key to highlight unlock the bootloader
Use the power key to select unlock the bootloader
***If you don't no how to get to the bootloader refer to youtube***
Oneplus Nord n100 stock boot.img
You can download the file here:
boot.img
Yandex
Finds everything
yadi.sk
EDIT: I went ahead and patched the boot.img so all you will have to do is download magisk apk and flash the boot.img via fastboot
You can download the file here:
magisk_patched_suVe7.img
Yandex
Finds everything
yadi.sk
Magisk apk
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Safetynet will not pass within magisk here is a magisk flashable zip to fix safetynet
After flash and reboot of phone check within magisk to see if it has worked
You can download the file here:
safetynet-fix-v1.1.0.zip
Yandex
Finds everything
yadi.sk
Click to expand...
Click to collapse
Can the patched image work with Oxygen OS 10.5.BE83BA
are you able to change the phone date to a year ahead and see if the unlock option becomes available then?
Also, are you able to disable automatic updates in developed options? to stop the android 11 updates?
ways2 said:
I think you have to wait 6 months to 1 year depending on your service provider. I have this phone on MetroPcs by Tmobile and I have to wait 6 months before I can unlock it
Click to expand...
Click to collapse
Shoot you don't even have to wait a week.. you just have to be willing to put in a little bit of work on it.. I'll tell you I was MetroPCS and I found Qualcomm firmware and a decryptor for the Qualcomm firmware and I decrypted the global firmware and I also decrypted a MetroPCS version of the firmware I went into the settings file and I changed only the third line I switched them out in the settings file I re-encrypted and packed in the file and then I used a debloating script which disabled the block on the bootloader option and voila I had OEM unlock and I am rooted also and I didn't have to get metropcs's bootloader code which they will not give out
rogjr1986 said:
Shoot you don't even have to wait a week.. you just have to be willing to put in a little bit of work on it.. I'll tell you I was MetroPCS and I found Qualcomm firmware and a decryptor for the Qualcomm firmware and I decrypted the global firmware and I also decrypted a MetroPCS version of the firmware I went into the settings file and I changed only the third line I switched them out in the settings file I re-encrypted and packed in the file and then I used a debloating script which disabled the block on the bootloader option and voila I had OEM unlock and I am rooted also and I didn't have to get metropcs's bootloader code which they will not give out
Click to expand...
Click to collapse
So you managed to flash the global rom to the metropcs N100 using modified msm tool's firmware?
If so, can you share the modified global msm .ops firmware for metropcs n100 be2015?
I assume you followed the instructions from the nord n10 thread: https://forum.xda-developers.com/t/...to-tmobile-metro-w-locked-bootloader.4297501/

Categories

Resources