Related
is any workaround to modify oem.sin? i just want to add my operator VoLTE settings. Thanks
Did you ever figure this one out?
Its impossible to edit a .sin file and flash it using flashtool.
You have to do it via a custom ROM, hence a rooted device is needed
gregbradley said:
Its impossible to edit a .sin file and flash it using flashtool.
You have to do it via a custom ROM, hence a rooted device is needed
Click to expand...
Click to collapse
Is it possible though to take an OEM.sin from another firmware variant and flash that so I can get my VoLTE 'settings'
chris_j26 said:
Is it possible though to take an OEM.sin from another firmware variant and flash that so I can get my VoLTE 'settings'
Click to expand...
Click to collapse
hmm,, I do not know, you can try it. Just swap the necessary .sin files using flashtool and try to flash it. there are 3 outcomes.
1. it will work (Great)
2. It will not flash (No problem)
3. It soft brick s your phone, so just flash a .ftf to restore your phone.
It works to flash oem.sin from other regions firmware with no problems , my problem is that my operator just released VoLTE and VoWIFI and Sony didnt add the settings in their firmware and the only way to do it is if i root the phone or if i could edit OEM.SIN before flashing (but seems thats not possible). My operator doesnt sell any Sony phones so probably will take a long time till my operator will contact them to add the settings in the firmware or maybe not at all or maybe only for latest devices or for the future models (i cant know that). Sony does have the VoLTE settings in like all EU firmwares and VoLTE + VoWIFI in specific operator firmware but only for Orange in my country and im using some other operator.
Edit:// just get the firmware that has your operator settings then flash only the oem.sin from it with flashtool , i did that with mine and i had no problems.
chris_j26 said:
Is it possible though to take an OEM.sin from another firmware variant and flash that so I can get my VoLTE 'settings'
Click to expand...
Click to collapse
Or just do this of course...my bad.
izyer said:
Edit:// just get the firmware that has your operator settings then flash only the oem.sin from it with flashtool , i did that with mine and i had no problems.
Click to expand...
Click to collapse
izyer said:
Edit:// just get the firmware that has your operator settings then flash only the oem.sin from it with flashtool , i did that with mine and i had no problems.
Click to expand...
Click to collapse
I have a problem in that my phone was never released by my operator! Do you think it'd be possible to get an OEM.sin from another phone altogether? They have released both the XZ Premium and Z5 Premium (I have the X performance). Alternatively I think if I edit the modem.conf I might have a way to get VoLTE too
chris_j26 said:
Is it possible though to take an OEM.sin from another firmware variant and flash that so I can get my VoLTE 'settings'
Click to expand...
Click to collapse
this is experimental try replacing firmware folder with elabel-Gxxxx-india-row_xxxxxxxxx_41.3.A.2.XX_S1-ELABEL-LIVE-DE8D-PID1-0004-MMC.sin and also you need to manually extract update.xml from indian firmware.... if it is set to unpack automatically in xperia firm it will be replaced by update.xml from the big file that size 2.6GB , you need update.xml from the indian firmware placed inside 46MB file
FYI without unpacking there will be like 3 files
one size 2.6 , other two size 46mb and 1.2mb
we need update xml from 46mb file and sin from 1.2 mb also dont forget to remove elabel-Gxxxx-yourcountry-row_xxxxxxxxx_41.3.A.2.XX_S1-ELABEL-LIVE-DE8D-PID1-0004-MMC.sin
chris_j26 said:
I have a problem in that my phone was never released by my operator! Do you think it'd be possible to get an OEM.sin from another phone altogether? They have released both the XZ Premium and Z5 Premium (I have the X performance). Alternatively I think if I edit the modem.conf I might have a way to get VoLTE too
Click to expand...
Click to collapse
Unfortunately only phones on my provider which has VoLTE support for Xperia xz performance and I can't yet extract the sin from that firmware
I have edited the relevant files on my device. Is there any way to force the phone to pick up the new oem settings? Will it require a format (reset to get it to work)?
UPDATE : reflashed phone via Flashtool. Excluded oem partition from flash and now have working VoLTE
chris_j26 said:
I have edited the relevant files on my device. Is there any way to force the phone to pick up the new oem settings? Will it require a format (reset to get it to work)?
UPDATE : reflashed phone via Flashtool. Excluded oem partition from flash and now have working VoLTE
Click to expand...
Click to collapse
which files have you edited ?? can you explain step by step please?
Can you please explain how this was done in more detail?
Is it required to unlock bootloader or root the device? I want to keep all my DRM keys but just enable VoLTE (and VoWIFI if possible).
Guide is here. It should apply to any device that has an oem partition provided you have the relevant files. That being said I haven't tried it on any other devices https://forum.xda-developers.com/xp.../guide-enable-volte-operator-handset-t3816565
umm what does oem.sin do on a phone?
Bernard2243 said:
umm what does oem.sin do on a phone?
Click to expand...
Click to collapse
It contains the operator modifications plus specify what modem to use (so you can get operator functionality)
chris_j26 said:
It contains the operator modifications plus specify what modem to use (so you can get operator functionality)
Click to expand...
Click to collapse
If i flash SOV32 original oem.sin does it make my sim card locked to AU network?
Bernard2243 said:
If i flash SOV32 original oem.sin does it make my sim card locked to AU network?
Click to expand...
Click to collapse
I am not sure what the SOV32 is but usually network SIM unlocking is different.
chris_j26 said:
I am not sure what the SOV32 is but usually network SIM unlocking is different.
Click to expand...
Click to collapse
SOV32 is japanese version for z5 bundled with AU
So it's safe to flash original japanese z5 oem.sin
Oem.sin
Dear Friend,
How do we flash only oem.sin. I need volte on sony xperia x compact
Hello amazing XDA devs,
I need a bit of advise and help with flashing oreo firmware on my device. I have already done a lot of research already but have failed to find any satisfactory answer. So here is my story,
I purchased my galaxy s8+ from korea. Model number is G955N. I wasn't able to get volte signal on it hence, rooted it and changed the csc to India.
In the process I also had to update my BL to AQL3.
I am now trying to flash an indian firmware on my korean device. i.e. installing SM-G955FD firmware on SM-G955N device. I undestand hardware of both the devices (korean and indian) are same. So, there should not be any problem in this cross flashing of firmware. However, ODIN doesn't allow this.
Here are my few queries which I hope you can help me with
1) Would it allow me to flash *FD firmware on *N device if I use prince comsy odin or some other custom odin?
2) Do I need to flash *N oreo BL if I decide to flash any other custom oreo rom which supports F/FD/N variants?
3) Where can I find *N oreo BL and AP to flash if only option is to install custom oreo rom?
4) If I flash oreo firmware for *N variant, would I loose my csc changes and I will have to start all process again to get back volte signal?
I know this is a long list of question. But, I am sure a lot of people have these queries and it will help all of them in understanding the process and upgrade their devices if these questions can be answered.
Would appreciate your help on this matter.
Thanks,
I got it..just flashed the oreo rom from twrp and everything seems to be working fine.
hello. which custom did you flash ? also need it. thanks
I have my G955N made 2 sims aleady.
I observed that the developer did the following steps:
1. They made it support 2 sims: IMEI guru software
2. They flashed custom that supported G955X:Renovate ICE in xda
3. They changed 1 slot sim tray with 2 slot sim trays.
4. I observed that BL and CP are of G955N but AP and CSC are else from G955X.
Thanks?.
I have the SM-G955F.
I flashed TWRP using the instructions on here and everything worked perfectly fine. I even booted back into the stock OS - however, the Magisk app was not there.
I was going to boot back into TWRP when I got the message "Only official released binaries are allowed to be flashed" and went into a bootloop.
Then I followed the instructions to flash the stock firmware back on to my S8+, but it failed. Can someone point me in the right direction please?
I used Odin3_v3.13.1. I have attached 2 pictures to show the error.
negative_silent said:
I have the SM-G955F.
I flashed TWRP using the instructions on here and everything worked perfectly fine. I even booted back into the stock OS - however, the Magisk app was not there.
I was going to boot back into TWRP when I got the message "Only official released binaries are allowed to be flashed" and went into a bootloop.
Then I followed the instructions to flash the stock firmware back on to my S8+, but it failed. Can someone point me in the right direction please?
I used Odin3_v3.13.1. I have attached 2 pictures to show the error.
Click to expand...
Click to collapse
Sounds like you are trying flash older firmware than what is on your phone. Odin saying you are flashing firmware with bootloader ver 3. Download mode saying you have ver 4 bootloader. You will need latest version of firmware with ver 4 bootloader or higher and flash with Odin.
Bootloader version number is 5th number from right of firmware name.
spawnlives said:
Sounds like you are trying flash older firmware than what is on your phone. Odin saying you are flashing firmware with bootloader ver 3. Download mode saying you have ver 4 bootloader. You will need latest version of firmware with ver 4 bootloader or higher and flash with Odin.
Bootloader version number is 5th number from right of firmware name.
Click to expand...
Click to collapse
Thanks so much for responding. So from my reading and researching, I figured that was the case. However, I could only find the the official firmwares from here:
https://forum.xda-developers.com/galaxy-s8+/development/rom-galaxy-s8-t3749444
Which happens to be v3 bootloaders. Is there any specific v4 bootloader that I should be flashing? I am at my wits end here. I followed all the instructions perfectly...
I read that everything works fine until reboot then you get the "Only official released binaries are allowed to be flashed"
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009
Any help would be greatly appreciated.
negative_silent said:
Thanks so much for responding. So from my reading and researching, I figured that was the case. However, I could only find the the official firmwares from here:
https://forum.xda-developers.com/galaxy-s8+/development/rom-galaxy-s8-t3749444
Which happens to be v3 bootloaders. Is there any specific v4 bootloader that I should be flashing? I am at my wits end here. I followed all the instructions perfectly...
I read that everything works fine until reboot then you get the "Only official released binaries are allowed to be flashed"
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Firmware can be download from sammobil or updato and flashed with odin
https://www.sammobile.com/firmwares/
https://updato.com/firmware-archive-select-model
Select phone model then search for firmware for your region ( and carrier ).
Only official binary error is probably due to your rmm state being in prernormal state which means if you unlock your bootloader ( oem ) and reboot it will relock bootloader causing this message.
Reflash firmware to get phone running again.
Have a read through this guide for more info about rmm state
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
spawnlives said:
Firmware can be download from sammobil or updato and flashed with odin
https://www.sammobile.com/firmwares/
https://updato.com/firmware-archive-select-model
Select phone model then search for firmware for your region ( and carrier ).
Only official binary error is probably due to your rmm state being in prernormal state which means if you unlock your bootloader ( oem ) and reboot it will relock bootloader causing this message.
Reflash firmware to get phone running again.
Have a read through this guide for more info about rmm state
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
Thank you for the links. I can't tell you how much I appreciate you helping me out.
I bought the phone from eBay, it's a SM-G955F - as for the region and carrier, I live in United States using AT&T. My primary reason getting the international version is to install a custom ROM on it. Is there a specific firmware for my region (U.S.) and carrier (AT&T) that I should flash? I don't see it US listed.
Also, using the guide I mentioned above, I did flash the RMM bypass, however, it was not the version 2, found in the guide you posted. Is that where I messed up?
negative_silent said:
Thank you for the links. I can't tell you how much I appreciate you helping me out.
I bought the phone from eBay, it's a SM-G955F - as for the region and carrier, I live in United States using AT&T. My primary reason getting the international version is to install a custom ROM on it. Is there a specific firmware for my region (U.S.) and carrier (AT&T) that I should flash? I don't see it US listed.
Also, using the guide I mentioned above, I did flash the RMM bypass, however, it was not the version 2, found in the guide you posted. Is that where I messed up?
Click to expand...
Click to collapse
I don't live in the US but there should be filters on the websites to filter by region. I normally use updato and firmware for your region shows up under U.S.A it will show you all your carrier's like at&t, Sprint, t-mobile and non carrier firmware.
As for the rmm zip version 2 may have been better it is more up to date and is smaller in size. Both should do the same job though.
spawnlives said:
I don't live in the US but there should be filters on the websites to filter by region. I normally use updato and firmware for your region shows up under U.S.A it will show you all your carrier's like at&t, Sprint, t-mobile and non carrier firmware.
As for the rmm zip version 2 may have been better it is more up to date and is smaller in size. Both should do the same job though.
Click to expand...
Click to collapse
I looked on updato and sammobile, both do not have USA region. Can I flash firmware from another region and still get it to work on my carrier?
For example, can I flash U.K. (Vodafone) since its on ver 4 firmware and uses GSM - regardless of region and carrier?
negative_silent said:
I looked on updato and sammobile, both do not have USA region. Can I flash firmware from another region and still get it to work on my carrier?
For example, can I flash U.K. (Vodafone) since its on ver 4 firmware and uses GSM - regardless of region and carrier?
Click to expand...
Click to collapse
Just doubled checked saw you have the f series while updato has u1 version firmware that I can see.
You can flash firmware from the UK if you want but can't say for certain you will have full network capabilities due to the difference in region and carriers ( network capabilities ). I would try and find an unbranded version ( non carrier branded) firmware first if not then something like Vodafone .
There is a simple reason for this. If you came from TWRP as "reboot to download", this creates the problem. Turn off the phone. Go to download mode with Vol_Down+Bixby+Power and then press Vol_Up button. When I enter download mode like this, it flashes without any problems.
Hi , my XZP came with an unlocked bootloader, and the firmware is the one for my country, but is a lot bloated, and also I don't like the boot animation, and shut down one .
My question here is this , my firmware supports VoLTE , if I flash another firmware will i lose that option?? If yes, then what archive do I need to avoid in order to flash my device without losing the VoLTE option.
Thanks .
Anybody??
Also if I have my bootloader unlocked, how do i root the phone on Android pie ?? My firmware is
47.2.A.10.107
Well i flashed a german customized firmware,and excluded modem.sin from the flash, everything went smooth and i have the VoLTE settings.
I think that i need to call to my operator in order to have VoLTE calls because when i make one, it shows me HSDPA.
Also when i excluded the modem from the flashing, i was expecting yo have the same modem, but no, just look at the screenshots.
And finally can please anyone point me in the right direction in how to flash this device with this firmware : G8141_Customized DE_1308-5289_47.2.A.10.107_R6C
Thanks.
(WIP, files are currently processing and uploading)
For those who aren't already aware, F711U is the model number of all of the US carrier versions of the Z Flip3. The F711U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I have access to an internal Samsung firmware download tool that usually gets new versions before they hit the public firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=327752
U1 firmware: https://www.androidfilehost.com/?w=files&flid=327753
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single flagship model, so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit the firmware download tools.
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
nwb_sam said:
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
Click to expand...
Click to collapse
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
iBowToAndroid said:
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
Click to expand...
Click to collapse
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
nwb_sam said:
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
Click to expand...
Click to collapse
Which F711U1 version did you flash?
iBowToAndroid said:
Which F711U1 version did you flash?
Click to expand...
Click to collapse
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
nwb_sam said:
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
Click to expand...
Click to collapse
Well UG7 is the latest that's available. So yes, I would expect you to get an error.
Once an update is available, if the phone is still giving the same error, then you can worry about it
Hello, well from my understanding Xfinity is bootloader unlockable after 60days and fully played for. I am wondering if anyone is planning on making a thread for Xfinity specifically. Or want too work with me on One. Sorry too spam or thread. But if u are familiar with how rom building, and flashing was with any other recent samsung model/Xfinity/bootloader unlock. It would be highly appreciated too know your experience.
jokono421 said:
Hello, well from my understanding Xfinity is bootloader unlockable
Click to expand...
Click to collapse
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
iBowToAndroid said:
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
Click to expand...
Click to collapse
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
twistedumbrella said:
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
Click to expand...
Click to collapse
Probably so
Can someone locate the thom browne fimware please?
blkghost22 said:
Can someone locate the thom browne fimware please?
Click to expand...
Click to collapse
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
iBowToAndroid said:
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
Click to expand...
Click to collapse
Thank you and always the best.
blkghost22 said:
Thank you and always the best.
Click to expand...
Click to collapse
Added, UGC build
iBowToAndroid said:
Added, UGC build
Click to expand...
Click to collapse
Guess its taking time to upload? Dont see the files just yet..
Edit:
Nvm i see the files now... again thank you so much
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
blkghost22 said:
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
Click to expand...
Click to collapse
1. Thom Browne *is* U1 firmware
2. USERDATA belongs to U firmware, not U1. So I have absolutely no idea. You'll have to try it and see what happens
Have successfully flashed F711U1 to F711W. Everything working fine. Used Odin 3.14, CSC_OMC_OYV, and working on Telus with all available features working.
Please note that AFTER the flash, you will be prompted to reset the device to stock. Reason being is that it needs to install the appropriate CSC linked to the inserted SIM card.
Can anyone confirm if cross flashing different build firmwares that it will unlock the unlock bootloader option?
Currently on carrier firmware for TMobile and I'm wondering if this is possible or if the u1 firmware has the unlock bootloader option available