yashsingh1/xdaforums huggingface dataset:
[XPERIA X1 ROM Development] gtrab:
Use the file I edited and uploaded to the LIBRARY (sticky thread)

I didn't hex-edit "hex-value 60" (left the original x301 code)

to let be compatible with the CID lock and I even flashed it on a CID-locked xperia to test, and it worked

Give my file a try

I prepared it for you

Download it and report
[XPERIA X1 ROM Development] Sully99:
Hello

I have tried some Radios from the LIBRARY

- FUZE Radio 1.02.25.27

- DIAMOND Radio 1.09.25.23

- BLACKSTONE Radio 1.08.25.23

- BLACKSTONE Radio 1.10.25.25

- RAPHAEL Radio 1.02.25.28

and I get on all Versions the Red failture looks like this:

00018003

KOVSIMG.nbh - Fail

Radio - RSH Fail

Update - Terminate

Update - Fail

Then I hex-edit on - RAPHAEL Radio 1.02.25.28 the "hex-value 60" to 1 and it works without a Fail.

What does this hex-value 60?

Bye
[XPERIA X1 ROM Development] gtrab:
It's sort of a security lock
[XPERIA X1 ROM Development] moisesz:
to all this. Is there any security unlocker available so far?. :confused:

thanks
[XPERIA X1 ROM Development] elee888:
Hi everyone,

I just got an X1a and I'm using it on AT&T Wireless in the San Francisco area. I live in a fringe reception area for 3G and I was wondering if anyone knows which radio they flashed to to get better reception. Also, does my phone have this security lock issue? It's not branded with carrier.

Thanks!
[XPERIA X1 ROM Development] moisesz:
i' trying to flash one of the blackstone radios but my xperia is security locked. does anyone knows how to unlock it or a workaround to sucessfully flash that blackstone radio?.

thanks
[XPERIA X1 ROM Development] gtrab:
There's a turotial for Hex editing the radio

then you can flash it into your Xperia

You will have to do the inverse process (00 -> 01) and updated radio version will not display but the radio will be flashed
[XPERIA X1 ROM Development] chalid:
Thanks for the tutorial. However, step 3 causes the flash failure on security locked devices. But I can say with 99% certainty that flashing a radio without the change will work on a security locked phone too - the change just doesn't show in the device info.

I was using both official Xperia radios for quite some time now and had bad reception at home. I flashed diamond 1.09.15.23 radio and have significant improvements in finding a network (takes less than 1 second - before ~ 5 seconds) and of course the network isn't lost as fast as with the other radio roms.
[XPERIA X1 ROM Development] gtrab:
yes, that's right

step 3 shows the radio version, but prevents flashing to a security locked device
[XPERIA X1 ROM Development] E90 Commie:
I´ve just tried the Diamond 1.09.15.23 radio and got the dreaded RSA Fail message. Yesterday I flashed the latest Raphael radio without any problems.

It would be nice with a solution for the Diamond radio. I tried to check it with the hex editior but couldn´t found anyting abnormal.

AFAIK is my device not CID locked. But I´m not really sure. It was buyed from a swedish "3" store but I haven´t seen any branding in it and before I switched to Hard-SPL it could be updated with the SE-US without any problems.

The Diamond radio flashed OK until about 99,5% - then it said "flash failed".
[XPERIA X1 ROM Development] AxE-mAn:
I am a noob when it comes to Radio's, I would just like to know if the Radio's are like location dependant? Why would I want to flash another radio? Im in South Africa, I have a SE Xperia X1i.

Will any radio work on my phone? which would be the best, and if it depends om my opinion, what is the difference between each of the radio's?

Please help me out on this.

Thanx in advance
[XPERIA X1 ROM Development] whitemdx03:
I've only experimented with the 3 official xperia radios. My X1i came with the beta radio. Voice quality/signal was bad compared to my N95. Flashed to 1.06 and the voice quality/signal improved, but I had problems with the GPS signal. Flashed to 1.10 and the GPS signal improved dramatically without loosing voice quality/signal, so that's what I am using.

I tried flashing the RAPHAEL Radio 1.11.25.01, read really good things about it, but so far been unsuccessful.
[XPERIA X1 ROM Development] tjex:
I've got a X1 that says it's "Security Unlocked" does this mean I can flash without worrying about messing around with changing settings?

Currently my Radio is 1.01.25.06, no complaints, works well but I hear the latest version is better for the battery. My main goal is to see if the GPS can get a faster lock.

Any ideas?
[XPERIA X1 ROM Development] Sover3igN:
Using same Radio (1.10.25.18).

Only flashed my radio in the beginning once (when I signed up for XDA) and used this one ever since.

Only in my home reception isn't all that good, but more mobile phones have them issue in me crib.

GPS and 3G reception actually pretty okies. Battery life seems to be decent as well. HEX crap iunno what all that means, I just want me phone to work. :D

Hope my input helps...?
[XPERIA X1 ROM Development] fards:
The 1.10.25.18 x1 radio is imho much better and should flash whether your device is CID locked or not.

the R2a roms actually include it, and I think the rilphone.dll included in Itjes latest rom is from the R2a10 rom (but may be wrong, I haven't decompiled it to find out) which seems to work even better (it's certainly different to the R2a8 version)..

mm i wonder if the people who are complaining about 3g with this 4.0RC1 are using this radio combo or not?

How fast is your current gps lock? as long as quickgps is upto date, I get 6-7 birds after about 8 seconds outside and 3 birds inside (nearish a window) in about 20 seconds
[XPERIA X1 ROM Development] gtrab:
Not sure if R2A with new radio and RIL is really improving GPS performance because I got better figures since version R1A (great SAT-lock time)

I don't have any complaints, what's more, I find the X1's GPS faster that that of the Diamond or TyTn (comparing side by side)
[XPERIA X1 ROM Development] AxE-mAn:
Please can anyone recommend any radio versions on for the Xperia?? Will it be wise to flash a Blackstone or Rapheal to my Xperia??
[XPERIA X1 ROM Development] tjex:
20 seconds by the window? WOW!

It takes me over 6 minutes for it to lock (blue bars in TomTom), I'm going to flash the new radio and will let you guys know if things improve. This could very well be the problem some are having with the GPS.

Update: Flashed your recommended Radio and wow, HUGE difference. The GPS locks in really fast now. And that's with aGPS turned off, makes me wonder if aGPS is even needed.
[XPERIA X1 ROM Development] fards:
no it's not, it's a pile of smelly dirty pants that you should pretend isn't really there.
[XPERIA X1 ROM Development] eboy44:
so im new to this xperia stuff i just got my xperia yesterday i tried to registry edit the latest touch pro radio that just came out last week and when i flashed it it went to 100% but then gave me a flash write error 226.

am i missing a step or is that what is supposed to happen with a radio from another device?

and here is my .nbh file if you guys can take a look at it and see if i did something wrong?

http://sharebee.com/5b46eef2
[XPERIA X1 ROM Development] adolfotregosa:
guys, the new 1.04.xxx rom comes with radio 1.11.25.71

I've flashed the rom to see if it had a new radio and it has.

I don't know how to extract it. I'm sure that someone that knows will extract it and share.

Just to let you know
[XPERIA X1 ROM Development] eboy44:
where can i find that rom with that radio so i can try and extract it?
[XPERIA X1 ROM Development] fards:
missed that!

mmm r2B strange.. and korean I wonder what the differences are.

I'll get the radio..
[XPERIA X1 ROM Development] eboy44:
thanks fards! also would you be able to check out the radio i tried to convert to the x1 i posted it like 2 comments back but it doesnt seem to flash to my x1 can you see what i did wrong?
[XPERIA X1 ROM Development] fards:
I've not had any real success with other devices radios.

I'd stick with the one I posted (unless this new one is much better), the 1.10 is a better radio than the default one.

ps I think you mean hex edit, not registry edit :P

had a look at the radio you posted and can't see anything wrong.

maybe it's one for Gtrab to try, or someone who's device is security unlocked.
[XPERIA X1 ROM Development] fards:
What's the build version btw and what's the language of the rom?

am downloading but @22kb from RS it's going to take a long time.
[XPERIA X1 ROM Development] fards:
okay heres the radio off the korean rom, I've called it 1.11.25.71 radio as that's what adolfotregosa says it reported on his flashed device. (i've not flashed the full rom it's from)

can't see any difference yet, I think GPs might be a bit slower than the 1.10

[edit] I have got a gps fix, 7 birds, Hdop 1.3m (which sounds very good) about 5ft inside the house.

included the custom RUU for radio flashing that doesn't hard reset the x1.

This is x300 so flashes on security LOCKED devices..

http://www.megaupload.com/?d=JGVLRBV0

seems to hold GSM signal okay
[XPERIA X1 ROM Development] eboy44:
yea haha i meant hex edit my bad, this radio was the most stable for service and battery life and gps fix when i had my touch pro so i believe if we can get it working with our x1 it will be a really good radio

and about the new 1.11.25.71 radio...it has the WEAKEST signal out of all the radios ive tried on both my xperia and my touch pro
[XPERIA X1 ROM Development] gtrab:
Curously enough, I always get FULL signal and great HSDPA speeds whatever radio I test... I am no good comparison point since my operator has a very strong signal here

As I've stated before, I am still using the stock radio and I have no complaints
[XPERIA X1 ROM Development] eboy44:
gtrab can you see if the radio i converted over to the xperia works on your phone since its security unlocked? i hex edited and everything it just doesnt allow me to flash i just get a flash 226 error and i have to reflash a radio. do you know what i did wrong? its the 1.12.25.19 radio a couple posts back (one of the posts on bottom of page 16)
[XPERIA X1 ROM Development] fards:
having done some testing this mornng i prefer the new 1.11 to the 1.10

my son was up at 4am so took him out for a walk, it picks up signal much faster, it still lost it at one point, and seems a bit more stable, in fact im using now over gprs. not much chance to test 3g today..
[XPERIA X1 ROM Development] ianl8888:
I've flashed it OK, instead of 1.10.

At first blush, not really any different - GPS, wifi, BT, GSM, GPRS, 3G seem much the same - all good.

This really needs a week or two under varying atmospheric and geographic conditions, so I'll post it again then.

Later edit: I haven't seen any increase in GSM/GPRS/3G sensitivity, but the GPS has shown 10 sats and an HDOP of 0.9m from the same location (my open front verandah) as previously showed 7-8 sats and 1.0m - seems to be an increase in GPS sensitivity in this radio.
[XPERIA X1 ROM Development] Tekguru:
Is the new 1.04 ROM officially available, if so where from?
[XPERIA X1 ROM Development] fards:
the korean (SKT) 1.04 is in the thread at the top of the section.

No other languages yet.

I've had a look and there's some new stuff in there, most of it relates to SKTelecoms..
[XPERIA X1 ROM Development] neock:
downloaded Blackstone_Radio_1.12.25.161 yesterday and hex edited its BLAC***** to KOVS*****, then change hex address 60's value from 01 to 00.

flash it, then error showed up, said "error in code" (or something, quite don't remember).

then i try to find out other radio roms such as Blackstone_Radio_1.10.25.25_for_X1, RAPHAEL_Radio_1.11.25.01_for_XperiaX1, found out that in this two roms, hex address 60's value is actually 01 not 00.

so i modified Blackstone_Radio_1.12.25.161 to 01 then flash. then flashing is ok but in device information it shows the original one's version but 1.12.25.161, same as protocol version.

that means successful or not? i've hard-spl my device already....
[XPERIA X1 ROM Development] cursor:
just upgraded to 1.11, no problems so far :P
[XPERIA X1 ROM Development] Tekguru:
Keep us posted!
[XPERIA X1 ROM Development] tjex:
Any luck out there with the new HD_Radio_1.12.25.16?

Still running 1.10, thinking of skipping 1.11 to 1.12 if it's feasible.
[XPERIA X1 ROM Development] eboy44:
well i tried to update to the new-er TouchPro radio 1.12.25.19 but i had no luck, i keep getting a flash 226 error and i get stuck on the bootloader screen until i flash another xperia radio.

hopefully we can find a fix because id LOVE to use these new radios on my xperia!
[XPERIA X1 ROM Development] fards:
Find someone who can come up with a security unlock for the x1!

Just noticed that cmonex has an X1 listed now in her sig as a main device.

Maybe she can enlighten us all, (I've asked) as she's a damn site clever than most of us put together!
[XPERIA X1 ROM Development] ninja.rogue:
@ fards

I have an Italian R2A08 Rom, the latest available. Can I simply copy rilphone.dll from R2A10 Rom to mine or shall I do something more complex? In case, what should I do to have it working on my R2A08 Rom?

Thank you

Paolo
[XPERIA X1 ROM Development] :
Fards you gonna give the new blackstone a try@editing for X1?

WC
[Xiaomi Mi 11] iBURGER:
Hello

I have Xiaomi mi 11 global version with a 1 year warranty from the seller but I've read that the mi 11 series got an extra one year of warranty (2 in total) due to widespread board/wifi problems

So anyone can confirm this?
[OnePlus Nord N200 5G] Gateway05184:
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
[OnePlus Nord N200 5G] Sprunglicious:
Under no circumstance should you relock the bootloader. The only OS that I know of that currently lets you do that on any device is Graphene OS on pixel devices. And that is written by extremely gifted developers. So... no... not now or anytime soon. Sorry!
[OnePlus Nord N200 5G] lzgmc:
Nope. While you could relock your bootloader now, you'd get an error message the next time you turned on your phone and it would refuse to boot. (And there's no guarantee that you could recover it, though usually the MSM tool works.) In most cases, you should never relock the bootloader unless you're on stock, unmodified firmware. In some cases, it is possible if the custom ROM you're using instructs you to relock your bootloader and provides their own keys for you to flash or if you build and sign your own ROMs yourself, but otherwise, it's just not worth it.

You should read this reddit post for more details as to why you shouldn't relock your bootloader.
[OnePlus Nord N200 5G] Gateway05184:
Yeah, I kind of figured. I tried locking the bootloader out of curiosity (obviously, you shouldn't do this.) which caused it to brick. I unbricked it using the MSM tools for the specific model. I also tried flashing the public key but it only allows recovery to boot and boot loops if you just leave it sit. lol
[OnePlus Nord N200 5G] pvsgh:
Don't' try this ever, you will most probably soft brick the device without being able to recover it.

You can only safely relock the bootloader on stock OS without the risk of bricking the device.
[OnePlus Nord N200 5G] optimumpro:
Not entirely true. CalyxOS allows relocking bootloader on Pixels. My own development for Oneplus 6/6T/8/8T/8Pro/9 and 9Pro allows relocking bootloader.
[OnePlus Nord N200 5G] Gateway05184:
I managed to find a way to relock the bootloader with LineageOS installed by compiling it from source and patching a few files. Then I flashed the avb_custom_key partition via fastboot with the key I used to sign the image I've compiled. This resulted in me getting the yellow error screen (Your device has loaded a different OS.) rather than the usual orange screen you get with the bootloader unlocked. I even used a tool called "avbroot" to patch the image for magisk support.
[OnePlus Nord N200 5G] AiM2LeaRn:
just use the MSMDownload tool for the firmware you want, it will set it back to factory defaults and factory OS including re-locking the bootloader

NOTE: if you ever want to unlock it again just use the token file/bin file that oneplus sent you originally to unlock. no need to re-apply or ask oneplus again for new token, can just use the original one they sent you.
[OnePlus Nord N200 5G] KeysStickler:
I don't like seeing my Nord n200 boot to the unlocked bootloader screen, and found a way to prevent that.

I found the method on the Reddit forum for LineageOS.

From CevicheMixto:

I was able to complete the upgrade (dirty flash from the latest LineageOS 19.1). Here's what I had to do.

First, I upgraded the device firmware, following this guide. Note that the oneplus.com page that is linked from that guide does not appear to actually provide firmware for the Nord N200. The Oxygen Updater app does allow you to download the firmware, once the app's settings have been changed to enable "Advanced mode." It will save the firmware file in the /sdcard directory, and adb can be used to transfer it to your PC. (Alternatively, the firmware can be directly downloaded from https://android.googleapis.com/packages/ota-api/package/6be3f133f8fb9bbcc30d787679bd7b5da5e30995.zip.)

At this point, my phone would not boot into the LineageOS recovery (19.1 or 20); it kept returning to bootloader mode. I fixed this by flashing the LineageOS 20 boot, dtbo, and vendor_boot images onto the device. These images can be extracted from the LineageOS 20 ZIP file with payload-dumper-go, or they can be downloaded from the dre builds page.

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash vendor_boot vendor_boot.img

(Unlike fastbootd, the bootloader does not appear to support the --slot=all option, but I only needed to flash these for the active slot.)

I was now able to boot into the (installed) LineageOS 20 recovery, choose "Apply update" and "Apply from ADB" to put the device into sideload mode. I then followed the upgrade instructions to flash the LineageOS 20 ZIP file, reboot back to recovery, and flash the MindTheGapps ZIP file.

Do yourself a favor and just load Oxygen Updater onto another Android phone and download the files. It will pop up a notice that the phone isn't the correct one, but just click advanced and download the file, then continue on.

My Nord n200 now boots with the OnePlus logo then directly to LineageOS with Android 13 :)
[OnePlus Nord N200 5G] Gateway05184:
That doesn't solve what I was originally attempting to do but I appreciate the suggestion nonetheless. However, the DE2117 OTA update is not meant for the carrier exclusive models (i.e. DE2118 aka the MetroPCs T-Mobile model.) I've already attempted this on my own DE2118 and it resulted in a boot loop. This problem doesn't exist in Lineage 19.1.
[OnePlus Nord N200 5G] KeysStickler:
I used this to update to LineageOS 20
[OnePlus Nord N200 5G] AiM2LeaRn:
there is no known way to relock the boot-loader on a custom rom on the nord n200 . However you can re-lock in on the official firmware. You can always go back to the official firmware with the locked bootloader by flashing the official firmware via MSM Download tool
[OnePlus Nord N200 5G] Banane123:
I bricked my S8 on android 8 with frp lock and locked Bootloader on a custom ROM I managed too fix it because I flashed remove frp binary 2 with samfw which shows the blue error screen updated failed recover with smart switch so I reflashed stock without a problem
[OnePlus Nord N200 5G] izo18jr:
Hello everyone how are you guys all doing

Hello guys how are you all doing?? So I installed the stock ROM in my Att Samsung s23 Ultra, the bootloader is not unlocked but the "OEM unlock" option does not appear, also I am not getting the option to relock the bootloader, can anyone help me with that???
[OnePlus Nord N200 5G] HarmitR:
can you share the process in more detail
[OnePlus Nord N200 5G] Gateway05184:
This no longer works if you are using the OxygenOS 12 firmware or later (Android 12) since they made changes to the bootloader that prevents loading a custom key for AVB. If you do attempt to do this on that firmware or later, it will end up bricked. Do let me know though if you still want me to explain the process.
[OnePlus Nord N200 5G] Gateway05184:
Sorry, but you are posting this in the wrong device forum. To answer your question anyway, most, if not all Samsung devices in the US don't allow bootloader unlocking. This is common with other brands as well if they were bought from a carrier, even if the phone was paid in full or carrier unlocked. Your best bet would be to get a phone that is well known to allow bootloader unlocking (OnePlus and Google Pixel to name a few).
[OnePlus Nord N200 5G] HarmitR:
I am testing with an old oneplus 6 (just for learning purposes) so i don't care about android version. oneplus 6 has android 8.1 to 11 support so i think i can try with older versions. I just want to run a custom rom with a locked bootloader (for testing if i can pass play integrity with that configuration)

So please, go ahead, share the process.
[OnePlus Nord N200 5G] izo18jr:
The thing is I had to use a patched Odin to by pass the "OEM Unlock toggle" because Att phones don't let you unlock the bootloader. When I turned on my phone a padlock on the top left of my phone after I installed the fresh copy of stock One Ui. I put my phone in down load mode to see if the option to lock the bootloader again would appear, but nothing. I tried switching the sim to a different carrier and nothing. I only won't to lock the bootloader because I lost some functionality of the phone and I want to just it regularly again.

a

ppeared on my
[OnePlus Nord N200 5G] Gateway05184:
I basically followed this guide while making some changes to compile for the OnePlus N200 5G. This should allow you to lock the bootloader for LineageOS and still boot since stock LineageOS boot loops when the bootloader is locked, even when flashing the proper files. This will not allow you to pass SafetyNet. How I got SafetyNet to pass was by including Magisk in the compiling process which allows the phone to boot with a valid signature and still maintain root access as well as magisk modules.

Re-locking the bootloader on the Google Pixel 8 Pro with a self-signed build of LineageOS 21.0

What is this tutorial? This tutorial will: Creating an unofficial build of LineageOS 21.0 suitable for using to re-lock the bootloader on a Google Pixel 8 Pro Take you through the process of re-locking your bootloader after installing the...

xdaforums.com
[OnePlus Nord N200 5G] izo18jr:
What is the right forum to post this on?
[Redmi Note 12 5G / Xiaomi Poco X5] shag001:
I have a new Redmi Note 12Pro+ which has the Chinese MIUI ROM (14.0.3) installed. Is it possible to replace this ROM with the international version? If the answer is yes is an instruction post available?

Also for those who might know is this the correct ROM as refers only to Redmi Note 12?
[Redmi Note 12 5G / Xiaomi Poco X5] emadhamid:
To switch from Chinese rom to global one you have to unlock the bootloader first , the wait time for unlocking bootloader should be 7-14 days .

Also your phone is note 12 pro + and the note 12 is definitely different both hardware and software wise 🙂

Hope it helps.
[Redmi Note 12 5G / Xiaomi Poco X5] shag001:
Thanks for your reply. Just to better my understanding, unlocking the bootloader is the same as what used be called rooting the phone? Why 7-14 days?

Updated my search and I think this is the right one.
[Redmi Note 12 5G / Xiaomi Poco X5] sunny_moonasd:
unlocking the bootloader need a tool called MITOOL,this tool do not work util the phone login a account and keep 7-14 days.

it is a rule set by the XiaoMi LTD