Related
The title says it all, I'm very hesitant to flash anything to my Xperia M2, even FTFs! I'm scared to death one day my sim card functionalities will cease to work (cannot call, no data, only emergency calls, etc). I am aware that the only way that can happen from an ftf is if I flash the simlock.ta by accident, but my question is this: Is there any way to lose sim-card functions, by flashing too many ROMs or FTFs (upgrading, downgrading)?
Naa man, feel safe to flash. I've flashed my M2 like around 20 times with out any issues. But, i screwed my sim functionality because when flashing a lollipop ftf i didn't excluded simlock.ta. Other than that, everything is perfect. So when ever flashing a rom, just see if it has a simlock.ta, and make sure you exclude it. In my case, i have ftf for JB, KK and L, and only the one for L has a simlock. So just make sure you don't flash the simlock.
Sidow said:
Naa man, feel safe to flash. I've flashed my M2 like around 20 times with out any issues. But, i screwed my sim functionality because when flashing a lollipop ftf i didn't excluded simlock.ta. Other than that, everything is perfect. So when ever flashing a rom, just see if it has a simlock.ta, and make sure you exclude it. In my case, i have ftf for JB, KK and L, and only the one for L has a simlock. So just make sure you don't flash the simlock.
Click to expand...
Click to collapse
Huh, I'll always check for a simlock.ta! Thanks for the clarification!
Sidow said:
Naa man, feel safe to flash. I've flashed my M2 like around 20 times with out any issues. But, i screwed my sim functionality because when flashing a lollipop ftf i didn't excluded simlock.ta. Other than that, everything is perfect. So when ever flashing a rom, just see if it has a simlock.ta, and make sure you exclude it. In my case, i have ftf for JB, KK and L, and only the one for L has a simlock. So just make sure you don't flash the simlock.
Click to expand...
Click to collapse
I don't have simlock on my Xperia M2 but I will ask anyway, is there any way you can back-up that simlock.ta file ?
It's only included on carrier ftf's I think as my m2 is a sim free network unlocked device and I've never removed it from customised ftf's
D2303 5.1lollipop customised NCB LB rooted Nuts t2u dual recovery bravia engine 2+x-reality debloated viper audio
G3RV0 said:
I don't have simlock on my Xperia M2 but I will ask anyway, is there any way you can back-up that simlock.ta file ?
Click to expand...
Click to collapse
Ima be honest, i don't know much about "ta", i don't know if simlock.ta is on the TA partition (it might sound dumb but i don't know). I read a post about a guy explaining Sony's recurity system, that as of today no one can hack it. Simlock.ta is part of that security system(which means that there is no way to backup, as far as i know). So in my case i locked my device, and since there is no way to hack the sec system, i'm screwed (according to what that guy said). But one thing i'm sure about, just whenever flashing an ftf, if it has simlock.ta, exclude it. And even more because your phone doesn't have a simlock.
For example, i had an Xperia S, and whenever flashing ftf including simlock, it would just skip it because it was locked to an specific network. My M2 wasn't, so when trying to flash simlock, and succeded and i locked my phone. So as long as you exclude simlock.ta, you'll be safe.
About what i said about TA partition, and Sony's security system, that's what i've read. I might not be completly right.
Sidow said:
Ima be honest, i don't know much about "ta", i don't know if simlock.ta is on the TA partition (it might sound dumb but i don't know). I read a post about a guy explaining Sony's recurity system, that as of today no one can hack it. Simlock.ta is part of that security system(which means that there is no way to backup, as far as i know). So in my case i locked my device, and since there is no way to hack the sec system, i'm screwed (according to what that guy said). But one thing i'm sure about, just whenever flashing an ftf, if it has simlock.ta, exclude it. And even more because your phone doesn't have a simlock.
For example, i had an Xperia S, and whenever flashing ftf including simlock, it would just skip it because it was locked to an specific network. My M2 wasn't, so when trying to flash simlock, and succeded and i locked my phone. So as long as you exclude simlock.ta, you'll be safe.
About what i said about TA partition, and Sony's security system, that's what i've read. I might not be completly right.
Click to expand...
Click to collapse
I see, so this simlock file is somehow encrypted or lock I guess if it cannot be accessed by people like us. Anyway what would happen if I won't exclude it from a flashing ? My smartphone doesn't have any simlock since I bought it brand new in a shop.
I have a huge favour to ask if you don't mind me asking, I want to unlock my bootloader in Xperia M2 and flash it to a custom rom, I have posted it around two days ago and it has 61 views but no one posted anything. I will appreciate your help if you do. Link to my thread.
Thanks
Ta (Trim Area) can be backup and restored if you have root, but can't be modified. There's a thread in sony Cross device that explains a lot of it.
Sent from my D2303 using Tapatalk
G3RV0 said:
I see, so this simlock file is somehow encrypted or lock I guess if it cannot be accessed by people like us. Anyway what would happen if I won't exclude it from a flashing ? My smartphone doesn't have any simlock since I bought it brand new in a shop.
I have a huge favour to ask if you don't mind me asking, I want to unlock my bootloader in Xperia M2 and flash it to a custom rom, I have posted it around two days ago and it has 61 views but no one posted anything. I will appreciate your help if you do. Link to my thread.
Thanks
Click to expand...
Click to collapse
Your phone does not have a simlock, which means, that if you flash a simlock.ta, it's going to lock it. Just like it happen to me, with no way to fix it. And sure, i'll try to answer on your post.
Sidow said:
Your phone does not have a simlock, which means, that if you flash a simlock.ta, it's going to lock it. Just like it happen to me, with no way to fix it. And sure, i'll try to answer on your post.
Click to expand...
Click to collapse
lol, so it locks and you can never use your Xperia M2 ? Pretty lethal if you ask me until you have backup of the original file. Tho I have flashed few times back to KitKat and I don't think so KitKat TFT file has that file. Ok , I really appreciate it ! :good:
G3RV0 said:
lol, so it locks and you can never use your Xperia M2 ? Pretty lethal if you ask me until you have backup of the original file. Tho I have flashed few times back to KitKat and I don't think so KitKat TFT file has that file. Ok , I really appreciate it ! :good:
Click to expand...
Click to collapse
You're wlecome, but you can't backup the simlock file. Watch:
1-If you phone is already locked to a network, you can't remove it, not replace it. (You can unlock the phone with a code but that's another story). So if you try to flash an ftf with simlock, nothing will happen.
2-If your device is not locked to an specific network (doesn't have a simlock) and you flash an ftf with simlock, there's when you have screwed your phone.
I have not received the 32.2.A.0.305 update for my Z5 yet, so I went to XperiFirm to check which region my device's firmware is from. It turns out the firmware is CDA 1298-2996 (South Africa).
I live in Australia and wish to flash the Customized AU firmware with CDA 1298-7277. I want to do this so that my device will be updated and will be using the Australian firmware.
My bootloader is locked; is flashing possible without unlocking the bootloader?
Will flashing a different firmware potentially cause damage (my device is not network locked, and single sim E6653).
Will this affect my warranty / DRM keys?
Thank you in advance, I appreciate any help :angel:
You are safe to flash almost any E6653 Firmware onto your E6653
Obviously dont flash test firmwares or ones that May lock your sim
Sent from my E6653 using XDA-Developers mobile app
Envious_Data said:
You are safe to flash almost any E6653 Firmware onto your E6653
Obviously dont flash test firmwares or ones that May lock your sim
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you And the DRM keys should not be affected? I have read that unlocking the bootloader only affects the keys.
csfrank271 said:
Thank you And the DRM keys should not be affected? I have read that unlocking the bootloader only affects the keys.
Click to expand...
Click to collapse
Flashing a FTF shouldent touch DRM At all.
Envious_Data said:
Flashing a FTF shouldent touch DRM At all.
Click to expand...
Click to collapse
Thanks again, I appreciate the knowledge!
csfrank271 said:
I have not received the 32.2.A.0.305 update for my Z5 yet, so I went to XperiFirm to check which region my device's firmware is from. It turns out the firmware is CDA 1298-2996 (South Africa).
I live in Australia and wish to flash the Customized AU firmware with CDA 1298-7277. I want to do this so that my device will be updated and will be using the Australian firmware.
My bootloader is locked; is flashing possible without unlocking the bootloader?
Will flashing a different firmware potentially cause damage (my device is not network locked, and single sim E6653).
Will this affect my warranty / DRM keys?
Thank you in advance, I appreciate any help :angel:
Click to expand...
Click to collapse
you can flash and what ever with your device, DRM keys are safe!
when u ulock bootloader, the device WIPE user Data and sony partitions (TA (trimArea) partitions) and DRM keys and FIDO keys will be lost!
this $h!t is with sony only!!
i rooted my fone and having modified kernel having DRM stimulation installed. its working fine now.
- at any given day, to a thirsty user who wants to CONTROL his Xperia to the most. i would say, ignore drm keys and make a deal with devil to have root access
- however since Xperia Z5 (unlike latest xperia Xseries) came out on LP kernel. so u can FLASH LP kernel and root it with app like kingroot and extract your DRM keys to windows pc and back it up. now u can flash the LASTED Android back on you Xperiaz5 and unlock your boot loader to have root access.
check this
http://forum.xda-developers.com/z5-...ting-xperia-z5-z5p-variants-drm-keys-t3437902
YasuHamed said:
you can flash and what ever with your device, DRM keys are safe!
when u ulock bootloader, the device WIPE user Data and sony partitions (TA (trimArea) partitions) and DRM keys and FIDO keys will be lost!
this $h!t is with sony only!!
i rooted my fone and having modified kernel having DRM stimulation installed. its working fine now.
- at any given day, to a thirsty user who wants to CONTROL his Xperia to the most. i would say, ignore drm keys and make a deal with devil to have root access
- however since Xperia Z5 (unlike latest xperia Xseries) came out on LP kernel. so u can FLASH LP kernel and root it with app like kingroot and extract your DRM keys to windows pc and back it up. now u can flash the LASTED Android back on you Xperiaz5 and unlock your boot loader to have root access.
check this
http://forum.xda-developers.com/z5-...ting-xperia-z5-z5p-variants-drm-keys-t3437902
Click to expand...
Click to collapse
Thanks for the advice, I will look into it in the future when CyanogenMod improves and I need to unlock the bootloader to install it. My main incentive for this would be to greatly improve the camera, which we all know takes very washed-out photos.
I have just gone through the firmware flashing process. Thankfully there are many guides available and it all worked just fine, so I am using the current, correct firmware now
The worst part was just the waiting and suspense (feels like a lot could go wrong).
Thanks again Envious_Data and YasuHamed!
csfrank271 said:
Thanks for the advice, I will look into it in the future when CyanogenMod improves and I need to unlock the bootloader to install it. My main incentive for this would be to greatly improve the camera, which we all know takes very washed-out photos.
I have just gone through the firmware flashing process. Thankfully there are many guides available and it all worked just fine, so I am using the current, correct firmware now
The worst part was just the waiting and suspense (feels like a lot could go wrong).
Thanks again Envious_Data and YasuHamed!
Click to expand...
Click to collapse
i had flashed Cm13 on XperiaZ and inbuilt camera app of CM13 was worse than xperia! and if you think you z5 camera isn't working properly then God Help you when you won't have DRM keys in place! because the DRM keys actually enables feature of camera which wont be activated if DRM keys are lost
nothing will go wrong! be confident! sony devices are Hardcore stallions! once you nail them! they will be your pet!
Hi. Hope some Sony Xperia guru can help me with this.
I recently went on vacation and left my Xperia XA F3111 at home. Some a***hole had access to it for over 2 weeks and installed some malware on it. When I found out I factory reset the phone, but I really want to restore the stock ROM too in case he has flashed the phone with a malware-infested ROM which will survive a reset.
My problem is, the phone settings say "Bootloader unlock allowed = No". The guide here on XDA Developers say that this setting means he could not root the phone. My first question is, would this setting have also prevented him from installing a custom ROM?
If that would not have stopped him, are there any step-by-step instructions as to how I can reinstall a clean stock Sony ROM with that bootloader config setting in place?
Thx. D.
Hi, factory reset of the phone was the best choice. You don't need to worry about the integrity of the system as long as your bootloader stay locked so you don't need to flash it again.
For the malwares it's probably coming from crappy apps, for sample: https://www.google.com/amp/s/bgr.com/2018/11/25/google-play-store-apps-removed-malware-found/amp/
@rrvuhpg
Many thanks for your answer. The phone says the bootloader cannot be unlocked, but does this mean he could not have unlocked it, flashed a virus infected ROM and then re-locked it?
I mean, does that config setting mean that nobody can ever unlock the bootloader and change the ROM?
dmeddings said:
@rrvuhpg
Many thanks for your answer. The phone says the bootloader cannot be unlocked, but does this mean he could not have unlocked it, flashed a virus infected ROM and then re-locked it?
I mean, does that config setting mean that nobody can ever unlock the bootloader and change the ROM?
Click to expand...
Click to collapse
Yes exactly, almost nobody can corrupt the system (for now). If one day you see a TA dumper for locked bootloader on Nougat or a root exploit it will mean that your phone can be corrupted.
So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.
Update> Currently I recommend this method only for unbrick, if you are going to change regions or install stock use this new method: Here
>> Need bootloader unlocked <<
If you want to unbrick or flash stock, you must download the package corresponding to your device and RUI version
1. Download the .zip package and extract the .ofp file
Packages:IndiaRUI 2.0 Android 11 A.07: DownloadRUI 3.0 Android 12 C.03: Download---------------EuropeRUI 2.0 Android 11 A.06: DownloadRUI 3.0 Android 12 C.02: Download---------------ChinaRUI 2.0 Android 11 A.06: Download---------------Russia, Middle East, Africa, Latin America, and other regionsRUI 2.0 Android 11 A.02: DownloadRUI 3.0 Android 12 C.02: Download---------------
2. Download and Install OppoRealme-OFP-Flash Tool: Here
3. Place the extracted .ofp file in the same folder as the program.
4. Run OppoRealme-OFP-Flash
5. When running if you have placed only one .ofp file in the folder it will automatically select it.
6. Choose the region you want to install, if you don't know you can search on google country code, or go in automatic mode by adb (if your cell phone isn't bricked).
7. Then it will ask if you want to keep some partitions (if you're doing it for bootloader lock you can't keep any).
8. Accept the terms and then plug the device into fastboot mode.
9. Done!
Note: after this process if you want to lock the bootloader, restart again in fastboot mode and type the command "fastboot flashing lock"
At last! Thank you! Will try it as soon as I have some free time to do it!
One quick question please. So let's say I want to go from Europe to India rom. I need to unlock bootloader and start the process you described. Do I need to take backup any partition in order not to lose IMEI or something? And after flashing to relock bootloader only type "fastbook flashing lock"? Some people were saying there is no official method to relock the bootloader again that's why I'm asking.
Malediktion said:
One quick question please. So let's say I want to go from Europe to India rom. I need to unlock bootloader and start the process you described. Do I need to take backup any partition in order not to lose IMEI or something? And after flashing to relock bootloader only type "fastbook flashing lock"? Some people were saying there is no official method to relock the bootloader again that's why I'm asking.
Click to expand...
Click to collapse
almost that, you don't lose the imei, you lock the bootloader I've already tested and proven it, but I don't recommend doing it without the rom that comes on your device.if you want to test, but it can happen hardbrick.
SrCDA said:
almost that, you don't lose the imei, you lock the bootloader I've already tested and proven it, but I don't recommend doing it without the rom that comes on your device.if you want to test, but it can happen hardbrick.
Click to expand...
Click to collapse
You mean lock the bootloader with the rom that my device has already? So if it's europe it has to stay europe and do the lock if I understand correctly.
Malediktion said:
You mean lock the bootloader with the rom that my device has already? So if it's europe it has to stay europe and do the lock if I understand correctly.
Click to expand...
Click to collapse
That's right, I don't know if blocking with a system from another region would work, it could even work, but it's risky to test, only if you have 10usd to pay for the hard unbrick.
SrCDA said:
That's right, I don't know if blocking with a system from another region would work, it could even work, but it's risky to test, only if you have 10usd to pay for the hard unbrick.
Click to expand...
Click to collapse
Listen, the thing is that I wouldn't even bother to test another rom. I already have made a thread here asking for some help because I have problem with incoming caller ID on 4G/5G with VoLTE enabled. Since no solution has been found, even after contacting Realme, the next thing to try was another (stock always) rom to see if it would work. If I would try to change rom I have to be VERY careful because there are absolutely NO service centers of Realme in my country. That's why I'm asking these questions. I want to know how safe is to "transfer" from another rom and if it is posible to return to my stock rom again with locked bootloader.
Malediktion said:
Listen, the thing is that I wouldn't even bother to test another rom. I already have made a thread here asking for some help because I have problem with incoming caller ID on 4G/5G with VoLTE enabled. Since no solution has been found, even after contacting Realme, the next thing to try was another (stock always) rom to see if it would work. If I would try to change rom I have to be VERY careful because there are absolutely NO service centers of Realme in my country. That's why I'm asking these questions. I want to know how safe is to "transfer" from another rom and if it is posible to return to my stock rom again with locked bootloader.
Click to expand...
Click to collapse
It's with my tool, it's totally safe, and it's easy to return to your region of origin, she has some protection so that nothing serious happened.
SrCDA said:
It's with my tool, it's totally safe, and it's easy to return to your region of origin, she has some protection so that nothing serious happened.
Click to expand...
Click to collapse
Thank you man. Totally appreciate your effort. Just to be clear one last time. You can do w/e test you want by changing roms/regions with unlocked BL and then after if you want to return your phone to what it was from factory you flash again your initial rom and lock BL.
Malediktion said:
Thank you man. Totally appreciate your effort. Just to be clear one last time. You can do w/e test you want by changing roms/regions with unlocked BL and then after if you want to return your phone to what it was from factory you flash again your initial rom and lock BL.
Click to expand...
Click to collapse
correct
great work thank you
Sorry if I may ask for clearer steps. The steps is kinda vague like you did not mention anything that need to be prepared from the device. And, if we change to another region rom, do we get future OTA official update form realme? Thank you in advance.
Alifirdaus said:
Sorry if I may ask for clearer steps. The steps is kinda vague like you did not mention anything that need to be prepared from the device. And, if we change to another region rom, do we get future OTA official update form realme? Thank you in advance.
Click to expand...
Click to collapse
I tested it yesterday, with a person, she downloaded, changed the region installing an older version, and managed to update by ota.
SrCDA said:
I tested it yesterday, with a person, she downloaded, changed the region installing an older version, and managed to update by ota.
Click to expand...
Click to collapse
Thanks for your reply. One more thing, for other region, does it come with Google? Mine was chinese rom and want to see if changing region will get Google service preinstalled. And, can you help me to check the Widevine level as well. Hope I'm not bothering you
Alifirdaus said:
Thanks for your reply. One more thing, for other region, does it come with Google? Mine was chinese rom and want to see if changing region will get Google service preinstalled. And, can you help me to check the Widevine level as well. Hope I'm not bothering you
Click to expand...
Click to collapse
yes, you can change to europe, russia, india, it comes with google, widevine depends, there are people who keep it on L1 and others move to L3, I don't know why.
I got an error when extracting the zip file. its been a 5th tried now. I downloaded the other region one.
Alifirdaus said:
I got an error when extracting the zip file. its been a 5th tried now. I downloaded the other region one.
Click to expand...
Click to collapse
I just successfully change my chinese rom to indian rom and thank god all google services are working fine. I will test everything first and will update here again. Thank you so much for coming with this!
Hi, im from europe and i have realme gt neo 2 europe variant. Just for information:
i unlocked bootloader, flashed chinese rom and locked bootloader again and everything worked like a charm.
No hardbrick.
PS. i relock bootloader because my bank accounts didnt worked with unlocked bootloader.
PSS. OTA updates works like a charm too on chinese rom.
joksax said:
Hi, im from europe and i have realme gt neo 2 europe variant. Just for information:
i unlocked bootloader, flashed chinese rom and locked bootloader again and everything worked like a charm.
No hardbrick.
PS. i relock bootloader because my bank accounts didnt worked with unlocked bootloader.
Click to expand...
Click to collapse
You just flashed every partition and everything worked ok after locking it? That's very nice to hear.