Hello! I've recently got my hands on a brand new Nubia Alpha. This device is based on Snapdragon 2100 and uses modified Android Wear (based on Android 7.1). But global version is a crap - it does not have ability to install apps. That ability is just locked away. That's ridiculous!
So I want to unlock my device to make it fully functional. I've tried:
Installing apps via adb install. It says:
Code:
>>adb install WearforInstagram.apk
$ adb: failed to install WearforInstagram.apk:
Exception occurred while dumping:
java.lang.IllegalArgumentException: forbiden install apk.
at com.android.server.pm.PackageInstallerService.createSessionInternal(PackageInstallerService.java:581)
Yep, with misspelled "forbiden". Some proprietary locking mechanism, I guess.
Invoking package.installer via ADB. It does not work as installer, which is pretty common for Wear devices. I managed to call uninstallation screen that finishes successfully, but it has no effect on any app.
Calling system and factory apps using ADB. Looks like no special engineering menu is present here.
Using ADB --disable command to stop some system processes and see native interface. Yep, that works, and I even managed to disable a launcher. But then Alpha displays just "Loading Android" screen with running circle. No crashes to some fallback GUI, sadly.
Bootloader unlock from Fastboot. Does not works, displaying a standard message about oem lock.
DirtyCow exploit to get root. That could work... but ah, ADB shell seems pretty limited - I can't use chmod there, so I can't run anything executable from PC. I had an sh, but Shellshock vulnerability seems fixed here.
Temporary TWRP loading from Fastboot. Nope, it is locked too.
So, I've started to run out of ideas.
What should I try next to free my device from that nasty lock?
Thanks!
I bought a nubia alpha, is there anything new?
Navy Lik said:
Hello! I've recently got my hands on a brand new Nubia Alpha. This device is based on Snapdragon 2100 and uses modified Android Wear (based on Android 7.1). But global version is a crap - it does not have ability to install apps. That ability is just locked away. That's ridiculous!
So I want to unlock my device to make it fully functional. I've tried:
Installing apps via adb install. It says:
Code:
>>adb install WearforInstagram.apk
$ adb: failed to install WearforInstagram.apk:
Exception occurred while dumping:
java.lang.IllegalArgumentException: forbiden install apk.
at com.android.server.pm.PackageInstallerService.createSessionInternal(PackageInstallerService.java:581)
Yep, with misspelled "forbiden". Some proprietary locking mechanism, I guess.
Invoking package.installer via ADB. It does not work as installer, which is pretty common for Wear devices. I managed to call uninstallation screen that finishes successfully, but it has no effect on any app.
Calling system and factory apps using ADB. Looks like no special engineering menu is present here.
Using ADB --disable command to stop some system processes and see native interface. Yep, that works, and I even managed to disable a launcher. But then Alpha displays just "Loading Android" screen with running circle. No crashes to some fallback GUI, sadly.
Bootloader unlock from Fastboot. Does not works, displaying a standard message about oem lock.
DirtyCow exploit to get root. That could work... but ah, ADB shell seems pretty limited - I can't use chmod there, so I can't run anything executable from PC. I had an sh, but Shellshock vulnerability seems fixed here.
Temporary TWRP loading from Fastboot. Nope, it is locked too.
So, I've started to run out of ideas.
What should I try next to free my device from that nasty lock?
Thanks!
Click to expand...
Click to collapse
Any news on this?
Im completely in love with the design of the watch but i really need to get it working with apps. Ive been thinking if flashing a proper android os would work?
Navy Lik said:
Hello! I've recently got my hands on a brand new Nubia Alpha. This device is based on Snapdragon 2100 and uses modified Android Wear (based on Android 7.1). But global version is a crap - it does not have ability to install apps. That ability is just locked away. That's ridiculous!
So I want to unlock my device to make it fully functional. I've tried:
Installing apps via adb install. It says:
Code:
>>adb install WearforInstagram.apk
$ adb: failed to install WearforInstagram.apk:
Exception occurred while dumping:
java.lang.IllegalArgumentException: forbiden install apk.
at com.android.server.pm.PackageInstallerService.createSessionInternal(PackageInstallerService.java:581)
Yep, with misspelled "forbiden". Some proprietary locking mechanism, I guess.
Invoking package.installer via ADB. It does not work as installer, which is pretty common for Wear devices. I managed to call uninstallation screen that finishes successfully, but it has no effect on any app.
Calling system and factory apps using ADB. Looks like no special engineering menu is present here.
Using ADB --disable command to stop some system processes and see native interface. Yep, that works, and I even managed to disable a launcher. But then Alpha displays just "Loading Android" screen with running circle. No crashes to some fallback GUI, sadly.
Bootloader unlock from Fastboot. Does not works, displaying a standard message about oem lock.
DirtyCow exploit to get root. That could work... but ah, ADB shell seems pretty limited - I can't use chmod there, so I can't run anything executable from PC. I had an sh, but Shellshock vulnerability seems fixed here.
Temporary TWRP loading from Fastboot. Nope, it is locked too.
So, I've started to run out of ideas.
What should I try next to free my device from that nasty lock?
Thanks!
Click to expand...
Click to collapse
Couple of month ago I also tried things on my own but I lost hope. For the unlock part did you try this command ?
Code:
fastboot oem nubia_unlock NUBIA_SW1002
RomeusPrime said:
Couple of month ago I also tried things on my own but I lost hope. For the unlock part did you try this command ?
Code:
fastboot oem nubia_unlock NUBIA_SW1002
Click to expand...
Click to collapse
THERE ARE SOME VIDEO ON YOUTUBE THAT SOME PEOPLE WILL BE ABLE TO INSTALL APPLICATIONS BUT I DON'T KNOW HOW
RomeusPrime said:
Couple of month ago I also tried things on my own but I lost hope. For the unlock part did you try this command ?
Code:
fastboot oem nubia_unlock NUBIA_SW1002
Click to expand...
Click to collapse
rafrgt said:
Click to expand...
Click to collapse
There are actually 2 versions : the eSim Version and the bluetooth ( or global ) version. I think the eSim version is only available in China and it is the unlocked version where you can easily install app. For the Bluetooth version (ours) it looks like there is a lot of restriction. But Definitely we could have a great toy in our hands if it was unlocked....
I don't know if anyone speak Chinese but there is a lot of Chinese forum, maybe they also have hack but I could find anything good as I am using google translate. I remember finding a small exe file to push apk to the watch but couldn't make it work.
Here is a link
Link: https://pan.baidu.com/s/1CfuRFKSagi2NQjzZqIW8Lw
Extraction code: 6wy5
I don't know if anyone could make it work on bluetooth version
RomeusPrime said:
Na verdade, existem 2 versões: a versão eSim e a versão bluetooth (ou global). Acho que a versão eSim está disponível apenas na China e é a versão desbloqueada, onde você pode instalar o aplicativo facilmente. Para a versão Bluetooth (nossa) parece que há muitas restrições. Mas, definitivamente, poderíamos ter um grande brinquedo em nossas mãos se ele fosse desbloqueado ....
Eu não sei se alguém fala chinês, mas há muitos fóruns chineses, talvez eles também tenham hack, mas eu poderia encontrar qualquer coisa boa porque estou usando o google tradutor. Lembro-me de encontrar um pequeno arquivo exe para enviar o apk para o relógio, mas não consegui fazer funcionar.
Aqui está um link
Link: https://pan.baidu.com/s/1CfuRFKSagi2NQjzZqIW8Lw
Código de extração: 6wy5
Não sei se alguém conseguiria fazer funcionar na versão bluetooth
Click to expand...
Click to collapse
a minha é a versão esim china, como instalar o app? este link não funciona com o nome do aplicativo
SO in theory you guys are saying, that the Chinese eSim version would work if properly set up?
Any chance we could modify the ROM on the International Version (or even chinese). My main concern with the china version is the lack of bluetooth tbh - as without an esim it'd be impossible to connect to a phone. While Local providers here do allow the configuration of an eSim, im concerned it wont work - let alone the fact that we do not know whether the China version allows for app installs.
So in essence we're here, someone correct me if im wrong:
1. Chinese version of the watch MAY allow installing apps.
2. International version of the watch MAY allow for the Chinese ROM to be installed .
Any ideas if the above would work?
Any ideas on modding the International ROM?
Additionally I made a reddit thread on it, that's going nowhere aswell.
https://www.reddit.com/r/androidroot/comments/myfvce
Neuralnox said:
SO in theory you guys are saying, that the Chinese eSim version would work if properly set up?
Any chance we could modify the ROM on the International Version (or even chinese). My main concern with the china version is the lack of bluetooth tbh - as without an esim it'd be impossible to connect to a phone. While Local providers here do allow the configuration of an eSim, im concerned it wont work - let alone the fact that we do not know whether the China version allows for app installs.
So in essence we're here, someone correct me if im wrong:
1. Chinese version of the watch MAY allow installing apps.
2. International version of the watch MAY allow for the Chinese ROM to be installed .
Any ideas if the above would work?
Any ideas on modding the International ROM?
Additionally I made a reddit thread on it, that's going nowhere aswell.
https://www.reddit.com/r/androidroot/comments/myfvce
Click to expand...
Click to collapse
Hi everyone,
My message is just to support you in what you are trying to achieve. The OS I confirm is horrible, and the worst part is that its biggest strength (its huge display) it is nowhere used to its full extent, starting from the watchfaces.
It is such a pity that such a marvel in terms of HW is ruined by such a poor SW.
I personally got the Nubia Watch and I was wondering in terms of OS/ROM how different it really is from the Nubia Alpha ?
I do only have limited skills in rooting devices, but I am willing to perform tests on my watch/es if it can help.
Let's push this!
#FreeNubiaAlphaOS
Thanks,
dgnoise75 said:
Hi everyone,
My message is just to support you in what you are trying to achieve. The OS I confirm is horrible, and the worst part is that its biggest strength (its huge display) it is nowhere used to its full extent, starting from the watchfaces.
It is such a pity that such a marvel in terms of HW is ruined by such a poor SW.
I personally got the Nubia Watch and I was wondering in terms of OS/ROM how different it really is from the Nubia Alpha ?
Let's push this!
#FreeNubiaAlphaOS
Thanks,
Click to expand...
Click to collapse
Completely Agree. The software is so horrible, ive even thought of ways to make it work with some RaspberryPi or any device that provides better support - even though realistically it seems unlikely that it'd be possible knowing the way manufacturers design screen cables .
Im realistically open to anything to make it function properly and provide us with a window of opportunity to leverage the capacities of the device.
#FreeNubiaAlphaOS
Neuralnox said:
Completely Agree. The software is so horrible, ive even thought of ways to make it work with some RaspberryPi or any device that provides better support - even though realistically it seems unlikely that it'd be possible knowing the way manufacturers design screen cables .
Im realistically open to anything to make it function properly and provide us with a window of opportunity to leverage the capacities of the device.
#FreeNubiaAlphaOS
Click to expand...
Click to collapse
Well, that is the part I have already been through. I know the details of the display HW and it uses a MIPI interface that could be theoretically interfaced to a Raspberry. However, the connector (which includes both signals for display and touch, see attached photo) requires an adapter (contacts are super tiny). That would need to be built on a custom PCB, requiring fairly high electronics skills. On top of that since the resolution (960x192) is not standard I'm sure several custom parameters would need to be set. Last but not least a driver would need to be found/written in order to be able to talk to the display controller (RM69330).
As an alternative, an evaluation board like the one from ST could be used, but the same issues would apply.
32F469IDISCOVERY - STMicroelectronics
32F469IDISCOVERY - Discovery kit with STM32F469NI MCU, STM32F469I-DISCO, STMicroelectronics
www.st.com
That's why the easiest option is still to use the Nubia HW...
#FreeNubiaAlphaOS
dgnoise75 said:
Well, that is the part I have already been through. I know the details of the display HW and it uses a MIPI interface that could be theoretically interfaced to a Raspberry. However, the connector (which includes both signals for display and touch, see attached photo) requires an adapter (contacts are super tiny). That would need to be built on a custom PCB, requiring fairly high electronics skills. On top of that since the resolution (960x192) is not standard I'm sure several custom parameters would need to be set. Last but not least a driver would need to be found/written in order to be able to talk to the display controller (RM69330).
As an alternative, an evaluation board like the one from ST could be used, but the same issues would apply.
32F469IDISCOVERY - STMicroelectronics
32F469IDISCOVERY - Discovery kit with STM32F469NI MCU, STM32F469I-DISCO, STMicroelectronics
www.st.com
That's why the easiest option is still to use the Nubia HW...
#FreeNubiaAlphaOS
Click to expand...
Click to collapse
Great post.
Ill still investigate how can this be expedited as a process - while of course I focus on a way to leverage the current handset.
Even if we can interface it with a RaspberryPI, most raspberries tend to be pretty large for the power they provide - so I'm not to keen on doing that tbh.
#FreeNubiaAlphaOS
Neuralnox said:
SO in theory you guys are saying, that the Chinese eSim version would work if properly set up?
Any chance we could modify the ROM on the International Version (or even chinese). My main concern with the china version is the lack of bluetooth tbh - as without an esim it'd be impossible to connect to a phone. While Local providers here do allow the configuration of an eSim, im concerned it wont work - let alone the fact that we do not know whether the China version allows for app installs.
So in essence we're here, someone correct me if im wrong:
1. Chinese version of the watch MAY allow installing apps.
2. International version of the watch MAY allow for the Chinese ROM to be installed .
Any ideas if the above would work?
Any ideas on modding the International ROM?
Additionally I made a reddit thread on it, that's going nowhere aswell.
https://www.reddit.com/r/androidroot/comments/myfvce
Click to expand...
Click to collapse
Hi,
Thank you for the post.
My understand is that the Chinese Esim version does have the Bluetooth/Wifi. The Esim is just an additionnal feature. You can read the description of Esim here : https://www.fonearena.com/blog/276408/nubia-alpha-price-specifications.html
So to me your are right on both point,
1- The Chinese version allow installing apk. In a previous a post a link to a tool I found on a Chinese website.
2- International version of the watch MAY allow for the Chinese ROM to be installed. To me the difference between the Chinese and Bluetooth are only on a software level. The HW should be the same. ( this is only my thought)
I tried hard to find the original Esim Rom but wasn't able to find it.... But knowing that I'm not the only one working on it bring my hopes back
#FreeNubiaAlphaOS
RomeusPrime said:
Hi,
Thank you for the post.
My understand is that the Chinese Esim version does have the Bluetooth/Wifi. The Esim is just an additionnal feature. You can read the description of Esim here : https://www.fonearena.com/blog/276408/nubia-alpha-price-specifications.html
So to me your are right on both point,
1- The Chinese version allow installing apk. In a previous a post a link to a tool I found on a Chinese website.
2- International version of the watch MAY allow for the Chinese ROM to be installed. To me the difference between the Chinese and Bluetooth are only on a software level. The HW should be the same. ( this is only my thought)
I tried hard to find the original Esim Rom but wasn't able to find it.... But knowing that I'm not the only one working on it bring my hopes back
#FreeNubiaAlphaOS
Click to expand...
Click to collapse
@RomeusPrime
I did see your post about the tool on the Chinese website. I was able to see the file list but I wasn't able to download them since apparently, it requires to have an account that can be created only with a Chinese phone number. Am I missing something?
Definitely bring your hopes (and contributions) back ;-)
Thanks!
#FreeNubiaAlphaOS
RomeusPrime said:
Hi,
Thank you for the post.
My understand is that the Chinese Esim version does have the Bluetooth/Wifi. The Esim is just an additionnal feature. You can read the description of Esim here : https://www.fonearena.com/blog/276408/nubia-alpha-price-specifications.html
So to me your are right on both point,
1- The Chinese version allow installing apk. In a previous a post a link to a tool I found on a Chinese website.
2- International version of the watch MAY allow for the Chinese ROM to be installed. To me the difference between the Chinese and Bluetooth are only on a software level. The HW should be the same. ( this is only my thought)
I tried hard to find the original Esim Rom but wasn't able to find it.... But knowing that I'm not the only one working on it bring my hopes back
#FreeNubiaAlphaOS
Click to expand...
Click to collapse
Hey thanks for the heads up!
That's a big step in the right direction. It seems that Aliexpress. Has the chinese version available. Maybe it's worth a try to get it.
Would i be able to unlock the eSim?
Does it have english?
And if i do get it would I be able to pull an image of the ROM for you guys?
Is it the same thing with the Nubia watch (that one seems a bit prettier)?
I think we should keep this thread alive and slowly work on this until we have a solution.
#FreeNubiaAlphaOS
Neuralnox said:
Hey thanks for the heads up!
That's a big step in the right direction. It seems that Aliexpress. Has the chinese version available. Maybe it's worth a try to get it.
Would i be able to unlock the eSim?
Does it have english?
And if i do get it would I be able to pull an image of the ROM for you guys?
Is it the same thing with the Nubia watch (that one seems a bit prettier)?
I think we should keep this thread alive and slowly work on this until we have a solution.
#FreeNubiaAlphaOS
Click to expand...
Click to collapse
From the information I have I can tell the following:
1) The Chinese version you are pointing out supports both Chinese and English languages.
2) The e-Sim it is stated works only in China. Not sure whether this is a software lock or else.
The supported frequencies are as follows:
2G: GSM:1800
3G: WCDMA:2100; CDMA:BC0
4G: LTE FDD:B1/B3; TDD-LTE:B38/B39/B40/B41
Ultimately however the goal is to unlock the OS, so even if eventually the e-SIM does not work it will be just like the global version, which I understand is the one we all currently have.
Nubia alpha vs Nubia Watch: they of course definitely share a lot of features, see the attached comparison.
The main difference being the camera on the Alpha. The internal PCB I would assume it is different since on the Watch it has been reduced greatly in size.
The major difference I see however is in the ROM/software. Just by comparing the available pre-installed apps and settings the 2 watches are quite different.
I currently own a Nubia Watch Global, but I would pull the trigger on the Alpha Chinese if that can help.
I would personally suggest creating a new thread in which we start collecting all useful information and keep updating the initial sticky post? This could attract more interest and stimulate people to contribute. Or we could ask the moderators to create the Nubia Alpha/Watch dedicated section. Agree?
Let's continue!
#FreeNubiaAlphaOS
dgnoise75 said:
From the information I have I can tell the following:
1) The Chinese version you are pointing out supports both Chinese and English languages.
2) The e-Sim it is stated works only in China. Not sure whether this is a software lock or else.
The supported frequencies are as follows:
2G: GSM:1800
3G: WCDMA:2100; CDMA:BC0
4G: LTE FDD:B1/B3; TDD-LTE:B38/B39/B40/B41
Ultimately however the goal is to unlock the OS, so even if eventually the e-SIM does not work it will be just like the global version, which I understand is the one we all currently have.
Nubia alpha vs Nubia Watch: they of course definitely share a lot of features, see the attached comparison.
The main difference being the camera on the Alpha. The internal PCB I would assume it is different since on the Watch it has been reduced greatly in size.
The major difference I see however is in the ROM/software. Just by comparing the available pre-installed apps and settings the 2 watches are quite different.
I currently own a Nubia Watch Global, but I would pull the trigger on the Alpha Chinese if that can help.
I would personally suggest creating a new thread in which we start collecting all useful information and keep updating the initial sticky post? This could attract more interest and stimulate people to contribute. Or we could ask the moderators to create the Nubia Alpha/Watch dedicated section. Agree?
Let's continue!
#FreeNubiaAlphaOS
Click to expand...
Click to collapse
Completely agree.
Also sounds (id rather not experiment) like ill pull the trigger to the Nubia Alpha Chinese Version these days aswell so that we can work on something concrete. I dont care about the esim so im not really worried about that.
Also if mods could create a section for us to talk and share it'd increase the exposure we get and hopefully pull more people in - as well as itd make it much easier to followup on this task.
#FreeNubiaAlphaOS
RomeusPrime said:
There are actually 2 versions : the eSim Version and the bluetooth ( or global ) version. I think the eSim version is only available in China and it is the unlocked version where you can easily install app. For the Bluetooth version (ours) it looks like there is a lot of restriction. But Definitely we could have a great toy in our hands if it was unlocked....
I don't know if anyone speak Chinese but there is a lot of Chinese forum, maybe they also have hack but I could find anything good as I am using google translate. I remember finding a small exe file to push apk to the watch but couldn't make it work.
Here is a link
Link: https://pan.baidu.com/s/1CfuRFKSagi2NQjzZqIW8Lw
Extraction code: 6wy5
I don't know if anyone could make it work on bluetooth version
Click to expand...
Click to collapse
I can not download has as upa for me?
I will make a video tutorial on my channel if any developer wants to make apk for nubia in his resolution to test the following channel https://youtube.com/channel/UClO2rkU5tqgHNgUhRshgFfA
Related
Hi,
It will probably take some time until I'll get my phone, but I am trying to understand how to start.
I am OK with having only English on my phone, but I would prefer to have a clean and bloat free rom that has the GAPPS and that can get OTA updates.
I want to do the minimum needed to get this, I really don't want to change roms every other week.
How should I start? I am a bit lost.
Is the Chinese rom that bad?
Should I change the rom and root it?
Thanks in advance,
Asaf
I think this should be in the Q&A forum
It sounds like you want a stable ROM with Gapps. Xiaomi offer several ROM types. If you want Gapps included from the start, you want their stable international ROM. The trouble is that at the moment they don't do one for the XRN2 yet. Head over to en.miui.com, pick a phone that has been around for longer and in the download section for that device you will see the different ROM types (there are tabs at the top of each phone section). There are also a couple of great explanatory pages in their forum that guide you through the different ROM types.
Use the xiaomi.eu ROM. Multilanguage, clean and with Gapps. OTA also included
Sent from my Redmi Note 2 using Tapatalk
First, get TWRP installed in your phone.
Then flash a stable rom
At the end, install proper gapp using TWRP.
Thanks.
So
1. Install TWRP, will this link should be enough to install it? http://en.miui.com/thread-156838-1-1.html
2. Go to http://xiaomi.eu --> ROMs DOWNLOAD and take the DOWNLOAD WEEKLY rom (http://miuif.celogeek.com/5.9.10/xiaomi.eu_multi_hermes_5.9.11_v7-5.0.zip)?
shemsha said:
Thanks.
So
1. Install TWRP, will this link should be enough to install it? http://en.miui.com/thread-156838-1-1.html
2. Go to http://xiaomi.eu --> ROMs DOWNLOAD and take the DOWNLOAD WEEKLY rom (http://miuif.celogeek.com/5.9.10/xiaomi.eu_multi_hermes_5.9.11_v7-5.0.zip)?
Click to expand...
Click to collapse
BUT, you said you don't want to have to flash a new ROM every week. The xiaomi.EU weekly ROMs are a beta ROM, they are not the same as the 'stable' ROM. I'm using the weekly version just fine, but there are a few bugs. This ROM may or may not suit your needs. Please be aware of that As soon as Xiaomi release the official stable International ROM with Gapps, that's the one you want (based on your stated requirements).
Thanks
So perhaps I'll wait, hopefully it will come up soon enough.
Hope the Chinese rom isn't too bad...
shemsha said:
Thanks
So perhaps I'll wait, hopefully it will come up soon enough.
Hope the Chinese rom isn't too bad...
Click to expand...
Click to collapse
The first ROM I flashed was the stable ROM from MIUI.com. At the moment this is available as Chinese only (with only Chinese and English languages on board). It is also MIUI version 6 not 7. You do not need TWRP installed to flash this. You can just download it straight to internal storage, then use the Xiaomi updater app (which is already on the phone) to manually flash it. This ROM is not rooted.
Next I tried the weekly ROM from MIUI.com. At that point I incorrectly thought that it would be multi language, but it wasn't. It did at least have MIUI 7 on board though. TWRP is also not needed to flash this. This ROM is rooted. Root settings can be accessed via the Security app. You can also install SuperSU, grant it root access, then use it to control the root access of other apps if you wish. There are no Google apps on board. I was on n holiday at the time so I manually placed all the relevant files, set permissions and so on using ES File explorer that I side loaded and granted root privileges to. Yes, my girlfriend thought it was very romantic of me to spend a whole evening split between doing this and hunting some particularly aggressive mosquitoes trapped in our room. Only the best for my love.
Finally I downloaded the latest weekly (not stable) ROM from from Xiaomi.EU. As well as being a beta, it is not an official Xiaomi ROM. They do also have a stable ROM in offer, but it is not rooted. Basic Google apps are installed. TWRP is not needed here either. However, I installed it briefly to make a full backup of my phone, and a separate backup of the NVRAM portion of the device where the IMEI resides. Experience tells me this is important on an MTK phone in case the area becomes corrupt during an incorrect flash. You can also use SPFlash Tools to do this from a computer. Google the process, it's well worth being prepared. Damian Parsons over on GizBeat and China Phone Arena has done some useful tutorials with videos. Make sure you have the right version of SPFlash tools (which is not the same as MTKdroidtools -or something like that). I have only used a couple of times with my first two MTK phones so I don't know what version you need to use with this chipset.
For my purposes NONE of these ROMs actually fit the bill. Why? Because none of them so far allow me to select UK English as the default language or select the UK as the region I'm in. It's a small thing, but the last three Chinese phones I've had all suffered from the same problem. I end up rooting and using More Locales app to create a new default language code over and above selecting UK English in Google keyboard.
Once Xiaomi release an official global ROM the download page for the Note 2 will look like in the attached screenshot which shows the Mi4 page. Note the two tabs at the top, global and Chinese, in addition to the 'stable' and 'developer' sections down the left hand side.
Please somebody correct me if I'm wrong because I'm new to Xiaomi devices
Thanks for the detailed response.
Sounds like that for my purposes, and until an official rom is out, the easiest option is either the latest weekly or stable from xiaomi.eu.
I understand they can be installed using xiaomi updater as well?
Yes, you can install them the same way as official ROMs.
shemsha said:
Thanks for the detailed response.
Sounds like that for my purposes, and until an official rom is out, the easiest option is either the latest weekly or stable from xiaomi.eu.
I understand they can be installed using xiaomi updater as well?
Click to expand...
Click to collapse
Also, when I received my phone there was a lot of non-MIUI related bloatware and possibly malware on board. It was multi language (with UK English as a built in option) but it all felt wrong, slow and dodgy. Reading elsewhere it was recommended the best thing to do was flash a ROM from a PC using the fastboot method to erase everything, then start from there. There are fastboot ROMs with instructions on the en.miui.com site. If you think you need to, you could flash via fastboot, then download your subsequent choice of ROM from xiaomi.EU and flash that however you please. As I was away (and impatient) I didn't do the first flash via fastboot. I just did a full wipe from the stock recovery, then put a ROM into internal memory, then flashed it from the stock recovery, then factory reset again. No idea if that was sufficient, but there's no sign of the extra apps any more.
You don't need TWRP
Sent from my Redmi Note 2 using Tapatalk
Ouzo said:
I installed it briefly to make a full backup of my phone, and a separate backup of the NVRAM portion of the device where the IMEI resides. Experience tells me this is important on an MTK phone in case the area becomes corrupt during an incorrect flash. You can also use SPFlash Tools to do this from a computer. Google the process, it's well worth being prepared. Damian Parsons over on GizBeat and China Phone Arena has done some useful tutorials with videos. Make sure you have the right version of SPFlash tools (which is not the same as MTKdroidtools -or something like that). I have only used a couple of times with my first two MTK phones so I don't know what version you need to use with this chipset.
For my purposes NONE of these ROMs actually fit the bill. Why? Because none of them so far allow me to select UK English as the default language or select the UK as the region I'm in. It's a small thing, but the last three Chinese phones I've had all suffered from the same problem. I end up rooting and using More Locales app to create a new default language code over and above selecting UK English in Google keyboard.
Click to expand...
Click to collapse
Thanks for the info, this is great for me. I will follow what you said regarding backing up this NVRAM you speak of, as I just read that the source code for the Helios X10 has been released, so we can expect more people including members of the HTC M9+ forum playing around with code.
It would be nice to have an option for UK English (or Australian English for me, to be precise) however I haven't noticed much of a difference, maybe because I have Swiftkey installed and that already has the correct language setting.
zan5hin said:
Thanks for the info, this is great for me. I will follow what you said regarding backing up this NVRAM you speak of, as I just read that the source code for the Helios X10 has been released, so we can expect more people including members of the HTC M9+ forum playing around with code.
It would be nice to have an option for UK English (or Australian English for me, to be precise) however I haven't noticed much of a difference, maybe because I have Swiftkey installed and that already has the correct language setting.
Click to expand...
Click to collapse
Changing the language to UK English is only part of the problem for me. Basically the phone thinks I'm in the U.S, or rather, that I have a U.S phone in the UK. This can cause problems within apps that want tailor content to my region code (or even deny me content). I've tried editing the build.prop a little, but it doesn't seem to help.
Mobile Uncle tools (free in Play Store) used to be able to back up one's IMEI number, but it didn't work on this phone. Dunno if that's because it runs lollipop. Anyway, that's why TWRP was handy and I will try using SPFlashTools again at some point.
This is my first ROM for a MTK device, so you will need to have some patience.
No files by now, because it's a pre-alpha. Once the rom is somewhat useable I will upload the needed files.
By now you can see:
http://imgur.com/tzUFoD0
Please, don't ask me for files. I will work on this image only in my sparse time, so the development could be slow.
WORKING:
Wifi
Bluetooth
Lights (screen brightness)
NOT WORKING:
Audio
Default android launcher (no watchface)
Sensors
No Gapps
NOT TESTED:
Modem
For my use
And this too
Cojo sitio!
Enviado desde mi MX4 mediante Tapatalk
Very nice
Amazing!
Nice! I think with us devs playing to our strengths we should be able to put some polish on the W812a. A working 5.1 base also opens up a few doors app wise.
corvus said:
This is my first ROM for a MTK device, so you will need to have some patience...... .....
Click to expand...
Click to collapse
Excellent idea, and thank you for this work. It is a pleasure to see these active community for this device.
Sorry for my translation by goolge
Very pleased to see this @corvus
Great effort mate - thanks very much !
This will open be a big step forward in the way of development.
Let us know if there's anything we can do.
I have a K8 Mini, a D5 and a K8 regular round - so does @Lokifish Marz and @cyrux75.
Cheers
There are some big problems with this rom. I try to port the launcher of the K8 mini but like Lokifish said in another thread there is not a unique apk and some resources are spread in several apks in the stock image. Audio is not working, and I do everything that I can to get it working, but by now no luck, and the bigger problem is sensors, they have some kernel modules (not a problem, because we use the same kernel) that are loaded with a bunch of binary files, and those binary files only run in KitKat, and don't work in Lollipop (and they will never work without recompile them to work in L), so no sensors in this image and seems that we will never get them until some chinese manufacturer release a L image in a device with this sensors.
I try to port the Omate Truesmart+ image that it's Lollipop and same mtk chipset, but without luck (and seems that they have another sensors, so I don't spend so much time on this).
So, if some one with more experience that me in mtk devices wants to take a look or ask something, I'm open to share my work with anyone.
What about a simple ROM with Nova Launcher and GAPPS?
Without audio or sensors? and with a draining battery... I'm not sure that this will be useful for anyone. I could share the zip, but I don't want users without the needed knowledge using it, breaking their devices and coming back to ask me why it's not working.
Anyway I continue searching for another rom from where make a porting with the same sensors.
-----
Vamos, que la rom es bastante inutil por ahora y no quiero romper nada a nadie. Pero sigo investigando...
corvus said:
Without audio or sensors? and with a draining battery... I'm not sure that this will be useful for anyone. I could share the zip, but I don't want users without the needed knowledge using it, breaking their devices and coming back to ask me why it's not working.
Anyway I continue searching for another rom from where make a porting with the same sensors.
-----
Vamos, que la rom es bastante inutil por ahora y no quiero romper nada a nadie. Pero sigo investigando...
Click to expand...
Click to collapse
what about using the android 5.0 that is on W3 smartwatch , i know that it is a BT watch but before the new update it had android 4.3 that means it is'nt Wear but lollipop, no?
check with
https://www.youtube.com/watch?v=k-O80LWcILQ
soniasophie9697 said:
what about using the android 5.0 that is on W3 smartwatch , i know that it is a BT watch but before the new update it had android 4.3 that means it is'nt Wear but lollipop, no?
check with
https://www.youtube.com/watch?v=k-O80LWcILQ
Click to expand...
Click to collapse
The W3 is completely different architecture. It uses an Ingenic M200 MIPS.
I stumbled across this one:
http://www.mtkroms.com/2016/02/bugless-resurrection-remix-for-mt6572.html
I'm actually not a developer, but maybe it is of some use for your work. At least it is our chipset and kernel.
Yes, one of this roms is what I use as base, but sensors are hardware dependant and watch has not the same hardware than a phone
Hello to all, was abandoned this project? We are not talking any more.
bettuccio said:
Hello to all, was abandoned this project? We are not talking any more.
Click to expand...
Click to collapse
Nothing to talk about. No drivers = no rom.
pablo11 said:
Nothing to talk about. No drivers = no rom.
Click to expand...
Click to collapse
I am sorry for this. Thanks for the reply Pablo.
Hi, today install the last lineage os version for my Moto G4 Plus xt1644:
lineage-14.1-20180613-nightly-athene-signed.zip
next I install the root file:
addonsu-15.1-arm-signed.zip
I go to developer menu and activate app and ADB root but this no take effect, the device is not rooted.
Can anyone help me?
Look closely, please ...
You seem to be trying to apply a LOS 15 root add-on to a LOS 14 base OS.
What part of "square peg in a round hole" is not clear ?
The way this is SUPPOSED to work is that you flash the CORRECT root add-on at the same time as the OS.
Thank you. Yesterday I repair the problem.
I downloaded the previos versión of super su from lieage page and this run ok.
I don't understand why the developers make the last version of su incompatible witht the last version of lineage...
For lack of a better explanation
Eduadc.celu said:
Thank you. Yesterday I repair the problem.
I downloaded the previos versión of super su from lieage page and this run ok.
I don't understand why the developers make the last version of su incompatible witht the last version of lineage...
Click to expand...
Click to collapse
First, you're welcome. Glad you solved the problem which is, after all, why we are all here :laugh:
To put this as non-technically but still as usefully as I can, each version of Android has different and unique sets of "switches" which must be flipped on or off to enable root access. The switches for LOS 14 (Nougat-derived) and LOS 15 (Oreo-derived) are different. The devs did not choose to make the su versions incompatible across the two version of LOS. They had no choice. Android implementations are still extremely hardware dependent, which reflects their ancestry in single core CPU devices with limited RAM. One of these years, it will hopefully grow out of it, since an octa-core CPU running at 2 GHz with at least 32GB RAM really doesn't need that level of hardware dependent optimization anymore to perform adequately (gamers - spare me, please - I know you want it and why !!!) but for now, the universe is what it is.
As I said, glad your problem is solved.
Hello everyone, forgive my English, I am Spanish. I have a PSMART 2021 and I want to know if there is any ROM compatible with this Mobile.
Do you know if the Lineageos is compatible?
Thank you.
No, and probably won't be until people find a way to unlock the bootloader of newer huaweis
Nothing yet for this device I guess not even mod ports...
Hopefully someone finds a way to TWRP, ROOT & Custom Rom the device....
What a pity that this Huawei P Smart 2021 does not have any ROM or modification ... Ayyyy
Qué lástima que este Huawei P Smart 2021 no tenga ningúna ROM o modificación... Ayyyy
Any update on this ? The hardware is pretty good but it is a PITA to have to keep my old phone about to use Google Maps or indeed the NHS COVID apps
John The Hat said:
Any update on this ? The hardware is pretty good but it is a PITA to have to keep my old phone about to use Google Maps or indeed the NHS COVID apps
Click to expand...
Click to collapse
No, Huawei shut down their service for unlocking the bootloader (which is required to do any modding really) a long time ago. Since these new phones could never be unlocked at all, their bootloader can't be extracted and modded to use with PotatoNV is my guess, pretty new to this topic though.
Busquet40 said:
Hello everyone, forgive my English, I am Spanish. I have a PSMART 2021 and I want to know if there is any ROM compatible with this Mobile.
Do you know if the Lineageos is compatible?
Thank you.
Click to expand...
Click to collapse
LeaOS Android 13 version erofs is compatible
LeaOS-A13-20230105-iceows-pot.xz
EDIT1: Thanks to Telegram users @Andrea900 and @valentinosantos I was able to fix a few incorrect indications I gave. If anyone has suggestions please don't hesitate to comment or message me.
POCO F2 Pro and Redmi K30 Pro have a lot in common - so much, that they are exactly the same phone. The K30 Pro, however, was launched together with a Zoom edition, with improved camera hardware. Now: is it possible to get that hardware on the POCO F2 Pro, and make a homemade "zoom edition" out of it?
The question is fascinating, and the answer is: yes! With few exceptions, it is possible, and the result is great!
I'm about to guide you through the process, but first let me say a word about myself.
I'm very new to XDA, and I essentially subscribed to participate in a thread that was discussing just the topic of this guide. The information was confused, and since I'm inexperienced I felt very lost. But I was determined, and worked my way into this hardware and software stuff that I never handled before. Now, I'm ready to try and tell others what I did, and how you can do it yourself.
Here's all you need to know in order to change POCO F2 Pro's cameras to Redmi K30 Pro Zoom's. Please bear in mind that almost nothing is originally mine: I'm just collecting info and commenting it with my personal notes. I'll give all the credit to who owns it every time is possible.
PREMISE
First and foremost, you must check the lot your product comes from. I haven't tested it and I haven't many sources on this, but chances are that if it's too recent it might not have some of the parts needed on the motherboard to implement OIS. If so, you'll need to solder those components, which is something I will not go through in this guide. Keep in mind that the production was ended in Sept 2020, so if your phone has been produced in August or Seprember you may have this problem. You can verify the batch through your IMEI - google is your best friend here.
Once you're sure your phone will be compatible with the mod, you need to have the cameras. You may find some on eBay or on AliExpress: I bought them from an eBay reseller. Once you get them, in order to verify that they are indeed those of the K30 pro zoom, you can very easily check for OIS on the main and on the 3x lenses.
Now, before putting the new hardware on the phone, you need to go through a bunch of software passages. The reason is very simple: when you mount the K30 Pro Zoom's cameras on the POCO F2 Pro, it will recognise itself as the former. This implies some limits:
unlocking the bootloader won't be possible anymore (unless you get back to F2 pro's cameras)
EDIT: I've been told that some were able to do it, but info is not super clear on this;
SafetyNet won't pass and you won't be able to use any banking app, Google Pay included.
EDITED: It has been confirmed by many that the reception of 4G/5G bands does not change with the swap, whichI initially believed it did. No worries there then!
For some banking apps, passing SafetyNet does not suffice however: you need to have phone recognised as European. I have no clue why, but my bank is one of them. For this reason, I'll also guide you through the process of changing the fingerprint of your phone back to that of POCO F2 Pro, which is only possible if you have done all the rooting and modding stuff before changing the hardware. Keep in mind that you might not need it!
In the following you may find a complete guide: keep in mind that if you're experienced you may find many things redundant. I'm inexperienced, so I noted them down anyway.
THE SOFTWARE PART
This part guides you if you, like me at the time, are starting from original MIUI Global (or any MIUI that is not China). If you are already mounting MIUI China, you can skip step 4, but the process is still the same.
However, if you have already an unlocked bootloader and you are mounting a custom rom (such as Xiaomi.eu o MIUImix et cetera) you can skip to step 7. But if that's the case, this guide isn't really for you mate: you are good to go! Make the hardware swap without worries
Backup through Google One and by copying pics and videos on the PC. Barbaric, but efficient. Just copy it back to the phone later. Remember Whatsapp's backup if you use it. Also, use Xiaomi Cloud if you intend to stay on a MIUI based ROM (as this guide will invite you to do).
Begin Unlocking Bootloader process. It takes 7 days so do it as soon as possible, don't wait to have the cameras with you. The process is very easy and you may find many guides, but I've followed this:
The tutorial omits one last passage: once you've unlocked your bootloader with the tool, you'll have to restart your phone and do a set up, in order to unlock (again) the developer options and the USB debugging. The first time you start up your unlocked device, you'll be asked to log in to your Mi Account as the very first thing, so keep in mind its password and email.
Install ADB and Fastboot tools on your computer. It's basic but you need them. I've used this guide:
Flash the China ROM through fastboot. [EDIT: I've been reported that this might not be needed. It was for me: flashing xiaomi.eu from Global sent my phone in bootloop. Refer to your custom ROM of choice for official info on this - and xioami.eu does say that flashing from China ROM is preferable] I suggest you follow this guide as it's explained well enough. I DO NOT recommend going through TWRP as it bricked my phone, and TWRP in general gave me lots of issues. Guide:
Flash Xiaomi.eu through the process they suggest. Remember: use the one they give you, do not go through recovery, as again recovery bricked my phone and many others as far as I know. If you want to go through recovery, use LineageOS recovery (see point 6). Guide:
[GUIDE] How to install Xiaomi.eu ROM for Redmi K30 / K30 5G
How to install Xiaomi.eu ROM for Redmi K30 / 5G This guide is only for ROM released before 10th February as before this date, was TWRP not available! Xiaomi.eu ROMs are now installed via TWRP as usually.. Due to TWRP issues for native Android 10 devices we have developed installation of our...
xiaomi.eu
Install a custom recovery. This is not something you need now, but rather something that may help with keeping Xiaomi.eu up to date (as it's easier to flash updates through recovery). I suggest you use LineageOS Recovery. You can find the recovery itself and a guide to install it here:
Redirecting…
--> Step 7 and 8 will guide you through the process of passing SaetyNet. This might not be necessary, because xiaomi.eu theorically should grant you pass it automatically: I personally needed to do what follows. Even if you pass SafetyNet, sometimes banking apps still won't work. If so, go ahead with these steps.
The first thing to do will be to install Magisk and use it to root your phone. I suggest you DO NOT FLASH IT as a .zip, but rather use the process that the developer suggests. To me, the only version of Magisk that worked was Canary, but others have had success with the regular release. The different releases are the same thing, just in different stages of development: canary is the "alpha", more or less. You can find very thorough instructions here:
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
The installation instructions are found by scrolling down; the latest releases are on the right.
Once Magisk is successfully installed, you can use it to fix your SafetyNet stuff. In order to do so, you'll need to do 3 (or 4!) things.
go to settings and hide the app
go to settings and activate zygisk, then activate "enforce denylist", and in the denylist add:
Google Play Services (you'll have to make them appear by clickinG on the three dots on the top right and selecting "show system") --> snet --> check the mark
Banking apps (if you have any) --> check the mark
download the Magisk Module "Universal SafetyNet Fix" and simply install it. Follow the link here to get the file and more info:
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
ONLY IF YOUR BANKING APPS STILL DON'T WORK
download the Magisk Module "MagiskHide Props Config" and use it to change the fingerprint and the BASIC Key attestation of the phone to POCO F2 Pro Global (A11). You can get the Module from here:
GitHub - Magisk-Modules-Repo/MagiskHidePropsConf: This tool is now dead...
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
And you can follow either the instructions given by this post:
[GUIDE][POCO F2 Pro] How to pass SafetyNet on Android 11 and Magisk on Xiaomi.eu ROM
1. Install the latest weekly or global firmware in twrp. (without magisk) 2. reboot. 3. complete the first setup. 4. reboot to recovery. 5. install latest magisk canary (now the latest stable version is v20.4, but need higher) 6. reboot. 7...
forum.xda-developers.com
or you can follow this guide, which contains one difference (it's explained as to change the fingerprint to Pixel 3a) and which also includes the next passage (the 8.4 in this guide I'm writing):
How to Pass Magisk SafetyNet on Rooted Android 11
In this tutorial, we will show you how to pass the Magisk SafetyNet test on your rooted Android 11 device with Hardware attestation type.
www.droidwin.com
If you were able to install a regular Magisk version, enter the app and verify SafetyNet; if you've installed Magisk Canary, simply go to Play Store and install a Safetynet Checker: you should pass the test, and your banking apps should work regularly.
THE HARDWARE PART
Do the hardware swap! I've used this teardown video to help me go through it:
Beware of two things that frightened me:
Both the motherboard cover and the motherboard should come out very easily. If you have to force it the slightest, check for screws you've missed! One is under an orange "mi" sticker, for example, one one is a weird "screw in the screw" of silver-ish colour
You must have both the motherboard and the motherboard cover screwed in in order for the phone to turn on. You can't just plug in the connectors and make a rapid check: you must screw everything together
EDIT: some have asked if the plastic caps have to be left on the module, and my take is they don't. They do offer protection but it's mostly for transport: once inside the phone, the lens are pretty much protected by the back glass. Plus my plastic caps came in scratched so leaving them on would have been stupid. They are quite well glued tho! So don't worry if you have to apply force to remove them.
EPILOGUE
I hope you've found this useful. Please let me know if any passage might benefit of further clarification. I know this is somewhat "rough" (there are plenty better guides on XDA) but I think I didn't miss any fundamental passage.
what happens if i dont install china rom before flashing eu rom?
Thanks in advance
luis181193 said:
what happens if i dont install china rom before flashing eu rom?
Thanks in advance
Click to expand...
Click to collapse
Hi! I bricked my phone and it went into bootloop. Plus xiaomi.eu explicitly states on their website that the ROM is made to be installed from China so it's really best to just follow the instructions of the developer
My modding
{
"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"
}
Thanks so much bro, worked well
I don't think you really need to flash xiaomi.eu. Any rom that supports lmipro should suffice. I will try LineageOS when I received my hardware.
heinhuiz said:
I don't think you really need to flash xiaomi.eu. Any rom that supports lmipro should suffice. I will try LineageOS when I received my hardware.
Click to expand...
Click to collapse
Xiaomi.eu is the one I suggest but yeah different roms have been tried out and work just fine
Just a quick PSA >>>
I was one of those 'early adopters' of the cam module switch, purely relying on comments in russian in Aliexpress. As such, I switched the module before unlocking the bootloader, resulting in mismatched specs, causing the dreaded 'Coudn't add. Device basic data verification failed' when trying to add the device to my account. A few weeks ago while waiting for the MIUI 13 update (& on the latest Poco F2 Pro 12.5 stock EU Rom), I installed the MIUI Downloader & downloaded the following ROM for K30 Pro / Zoom devices.
I installed the rom using the following steps
Transfer the download .zip file to your phone, and ensure you place the file in the “downloaded_rom” folder in the internal storage of your device. If no such folder exists, create one in your internal storage base directory.
On your phone, navigate to Settings > About Phone > System Update, and then press the three-dot icon in the top-right corner, and select “Choose Update Package”. If the “Choose Update Package” is not visible, you need to tap on the MIUI version logo 7-10 times.
If the “Choose Update Package” option is missing, tap on the MIUI logo 10 times to activate the option.
Choose the downloaded .zip file.
Wait for the update to install.
The phone booted normally on MIUI 13 & just for the sake of it I added my MIUI account & attempted to add the device to my account. Miraculously it worked! By following the steps mentioned in the OP (big thanks @CMCarlo ) I just made my first payment w/ Google Pay since about this time last year. Hope it helps
Peace
With MIUI by xiaomi.eu 13.0.2 it's work well.
Poco f2 pro change to k30 pro zoom edition After change hardware cam.
Thanks you
heinhuiz said:
I don't think you really need to flash xiaomi.eu. Any rom that supports lmipro should suffice.
Click to expand...
Click to collapse
Is it possible to keep stock miui after this camera upgrade?
brent0r said:
Is it possible to keep stock miui after this camera upI'm on global
Click to expand...
Click to collapse
I'm on Global ROM an tried several others without any issue, so I think you can stay on stock ROM
CMCarlo said:
Keep in mind that the production was ended in Sept 2020, so if your phone has been produced in August or Seprember you may have this problem. You can verify the batch through your IMEI - google is your best friend here.
Click to expand...
Click to collapse
I missed this information prior to purchasing the K30 pro zoom module, which I now have. I've also waited the 7 days to be allowed to unlock the bootloader. My question is, how does one determine their batch number or production date from an IMEI number? I've googled but haven't had any luck figuring this out.
Ximo F. Verde said:
Miraculously it worked! By following the steps mentioned in the OP (big thanks @CMCarlo ) I just made my first payment w/ Google Pay since about this time last year. Hope it helps
Peace
Click to expand...
Click to collapse
Is your bootloader locked for gpay to work? Did you need to root and apply the various fixes mentioned in the OP?
brent0r said:
Is your bootloader locked for gpay to work? Did you need to root and apply the various fixes mentioned in the OP?
Click to expand...
Click to collapse
The bootloader has to be unlocked to flash the rom. Xiaomi.eu passes safety net & the device appears to be certified in Play even without rooting the device. Having said that, I did proceed with rooting the device because there were a couple of apps the required it, but I can't say that Wallet was one of them. Theoretically, if the device is certified in Google Play, you shouldn't need root for that.
Ximo F. Verde said:
The bootloader has to be unlocked to flash the rom. Xiaomi.eu passes safety net & the device appears to be certified in Play even without rooting the device. Having said that, I did proceed with rooting the device because there were a couple of apps the required it, but I can't say that Wallet was one of them. Theoretically, if the device is certified in Google Play, you shouldn't need root for that.
Click to expand...
Click to collapse
Thanks for that. I have no interest in the xiaomi.eu rom and want to stay with official ROMs (eg K30 Pro Zoom - Global Stable ROM). Do you know if this would actually be possible though? I asked earlier and heard it is, but not sure on the path to get there from the latest Poco F2 Pro Global Stable ROM. I'm yet to swap my camera and have noticed since unlocking the bootloader, my gpay via NFC no longer works. If I manage to flash the global stable K30 pro zoom ROM, would locking the bootloader perhaps allow the device to pass whatever checks necessary for gpay, or would doing so cause bootloops?
brent0r said:
Thanks for that. I have no interest in the xiaomi.eu rom and want to stay with official ROMs (eg K30 Pro Zoom - Global Stable ROM). Do you know if this would actually be possible though? I asked earlier and heard it is, but not sure on the path to get there from the latest Poco F2 Pro Global Stable ROM. I'm yet to swap my camera and have noticed since unlocking the bootloader, my gpay via NFC no longer works.
Click to expand...
Click to collapse
I'm not really sure, but I guess you could stick to the first steps of the OP tutorial. That is, unlock bootloader & then flash the latest chinese ROM for the K30PZ. You might or might not need rooting for GPay to work, depending on whether your device appears to be certified in GPlay. Keep in mind that you might also run into issues with DRM in specific apps, like Netflix (L1 winevine) or problems with banking apps. Generally speaking, the most troublesome part of switching cam modules is being able to unlock the bootloader. Once that's done, there are many options to choose from, although I'm not sure what's the best approach if you wanna stick to stock ROMs. Btw, xiaomi.eu is basically a stock ROM, simply optimized & overall better performing. As always, proceed with caution & please don't blame me if you brick your device..
Ximo F. Verde said:
As always, proceed with caution & please don't blame me if you brick your device..
Click to expand...
Click to collapse
Thanks. Hopefully bricking isn't an option for me. My biggest worry about the hardware procedure is breaking a motherboard ribbon or stuffing up the glueing when sealing the case closed. I'm actually quite worried about it. How difficult did you find it?
brent0r said:
Thanks. Hopefully bricking isn't an option for me. My biggest worry about the hardware procedure is breaking a motherboard ribbon or stuffing up the glueing when sealing the case closed. I'm actually quite worried about it. How difficult did you find it?
Click to expand...
Click to collapse
It's definitely not for the faint hearted, but it's not very difficult either. You need the right tools though, gun heater, tweezers etc. I admit that I did it with a friend's help, but it can be done alone too, just be careful and don't force anything. The brackets holding the module are tricky, keep that in mind. If you haven't changed thar hw yet, I would definitely suggest unlocking the bootloader first.
If anybody thinking about changing the cameras, here's a link. Arrived yesterday, already changed. The phone specs says my f2 pro is now a k30 pro zoom edition, macro option gone as i expected.
https://a.aliexpress.com/_mPYwYS2
Homeye said:
If anybody thinking about changing the cameras, here's a link. Arrived yesterday, already changed. The phone specs says my f2 pro is now a k30 pro zoom edition, macro option gone as i expected.
https://a.aliexpress.com/_mPYwYS2
Click to expand...
Click to collapse
Thanks ! I ordered one for myself, let's see when it arrives.
Planning to replace battery at the same time and make my backcover transparent.
Also not sure about which ROM to use, currently on global MIUI with locked bootloader, don't feel like using xiaomi.eu since the security patch is outdated ( global just got an update )
Probably I will have to use a non MIUI rom since Xiaomi is abandoning this phone but I need a super stable and reliable one