Related
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, as only a few versions of unbrick tool are available here and that they allow to rollback to specific versions of Oxygen OS I decided to search for more and succeeded in that.
As the instructions and Qualcomm drivers are already available here, I don't feel a need to rewrite them.
You can ask questions here on how to use and issues, however I might not be able to answer immediately.
Here are the files uploaded on AndroidFileHost ordered by Android version:
ANDROID 9:
OOS 9.0.6
OOS 9.0.5
OOS 9.0.4
ANDROID 8:
OOS 5.0.8
OOS 5.0.6
OOS 5.0.5
OOS 5.0.4
OOS 5.0.3
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
Happy unbricking
Credits:
@Titokhan for giving advice on how to present thread
@headsh0t95 for suggesting me to request an access to upload files on AndroidFileHost
@AndroidFileHost for the hosting
OnePlus for the device and OS
Reserved -v1
hey man, could you add OOS 9.0.2 unbrick tool now that the Android 9 update has been released for 3T.
em4viki said:
hey man, could you add OOS 9.0.2 unbrick tool now that the Android 9 update has been released for 3T.
Click to expand...
Click to collapse
Hi, I would like to but as of now, it looks like there is no EDL image available based on Pie
Added first Pie unbrick tool based on OOS 9.0.4
em4viki said:
hey man, could you add OOS 9.0.2 unbrick tool now that the Android 9 update has been released for 3T.
Click to expand...
Click to collapse
Hey, look at above
what is password for 3.5.4?
andivivaldi said:
what is password for 3.5.4?
Click to expand...
Click to collapse
Hi, as I said in original post I don't have it but share it in the hope that someone will be able to bruteforce it and share it decrypted
Hi
Will this be helpful if I want to rollback the official 9.0.4 update to 5.0.8?
bldysabba said:
Hi
Will this be helpful if I want to rollback the official 9.0.4 update to 5.0.8?
Click to expand...
Click to collapse
Hi, yes you can rollback to 5.0.8 using 5.0.8 MSM tool
@Some_Random_Username how much time does it take to flash 9.0.4?
Mine is taking more than 10 min - its stuck at param preprocessing.
Edit- got it working.
step 1. download and install driver - https://androidfilehost.com/?fid=11410963190603879743
step 2. reboot pc.
step 3. connect oneplus device in edl mode.
step 4. pc installs driver again.
step 5. run msm tool for 9.0.4 and install.
Added OOS 9.0.5 unbrick tool
Hi. Thanks for sharing all the links. I"m trying to download DECRYPTED OOS 5.0.3 and it's really slow (like 40KBPS). Is it possible to upload these files to a different host? Thanks!
mugenishere said:
Hi. Thanks for sharing all the links. I"m trying to download DECRYPTED OOS 5.0.3 and it's really slow (like 40KBPS). Is it possible to upload these files to a different host? Thanks!
Click to expand...
Click to collapse
Unfortunately no as I do not know any other provider hosting for free such an amount of files (I have same thread for OP3/5/5T/6/6T/7/7 Pro).
You could however select the mirror the more near to your location when downloading via AFH to get a faster download speed.
Some_Random_Username said:
Unfortunately no as I do not know any other provider hosting for free such an amount of files (I have same thread for OP3/5/5T/6/6T/7/7 Pro).
You could however select the mirror the more near to your location when downloading via AFH to get a faster download speed.
Click to expand...
Click to collapse
I tried it again from another server and this time it downloaded at 9MBPS! I got the file!
Thanks a load for sharing all these files! The normal "unbrick your phone" by flashing Android 6 wasn't working for me. From your link I was able to download the file for Android 8 (Oxygen 5.0.3). And it worked! My phone got unbricked finally!
A note to everyone: For whomever the earlier unbrick step doesn't work, you need to try downloading some other Oxygen OS (different Android version than the one you tried earlier).
I'm going to make a post in the main "unbrick" thread and let other people know about this. Once again, thanks a lot for posting these files and saving my phone!
Some_Random_Username said:
Hi, yes you can rollback to 5.0.8 using 5.0.8 MSM tool
Click to expand...
Click to collapse
@Some_Random_Username ... i am guessing the procedure to unbrick is the same as in this thread ... right ?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
aiamuzz said:
@Some_Random_Username ... i am guessing the procedure to unbrick is the same as in this thread ... right ?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
Except that normally you shouldn't need to turn off driver signature enforcement and that drivers should automatically be downloaded and installed if you're on Windows 10 that's it yeah.
Some_Random_Username said:
Except that normally you shouldn't need to turn off driver signature enforcement and that drivers should automatically be downloaded and installed if you're on Windows 10 that's it yeah.
Click to expand...
Click to collapse
thanks @Some_Random_Username ... it was a breeze ... my windows 100 let me flash it effortlessly without having to turn off driver signature enforcement feature ... can't thank you enough for this thread which collates the various versions that are directly flashable ... its a delight to get back directly to the latest official ROM and the MSM software is smooth no issues there ... i believe this is MSM software is akin the the RSD light Motorola devices have !!!
Hope you are able to update this thread with all future official upgrade versions !!!
Did you repack this tool kit for Android Pie yourself ?
aiamuzz said:
thanks @Some_Random_Username ... it was a breeze ... my windows 100 let me flash it effortlessly without having to turn off driver signature enforcement feature ... can't thank you enough for this thread which collates the various versions that are directly flashable ... its a delight to get back directly to the latest official ROM and the MSM software is smooth no issues there ... i believe this is MSM software is akin the the RSD light Motorola devices have !!!
Hope you are able to update this thread with all future official upgrade versions !!!
Did you repack this tool kit for Android Pie yourself ?
Click to expand...
Click to collapse
Well, not to be pessimistic but firstly OnePlus would need to deliver one last update for this device as November is when they should drop support as per their software maintenance schedule thread https://forums.oneplus.com/threads/oneplus-software-maintenance-schedule.862347/ .
No, I didn't repack it for Pie by myself, I just managed to get it from OnePlus.
Some_Random_Username said:
Well, not to be pessimistic but firstly OnePlus would need to deliver one last update for this device as November is when they should drop support as per their software maintenance schedule thread https://forums.oneplus.com/threads/oneplus-software-maintenance-schedule.862347/ .
No, I didn't repack it for Pie by myself, I just managed to get it from OnePlus.
Click to expand...
Click to collapse
thanks for sharing the latest updates for OP3T (9.0.6) ... you are pretty prompt at it ... good work !!!
will look forward to the MSM unbrick tool for this latest version ... hopefully you'll be able to get your hands on it soon !!!
Code:
/*
* I am not responsible for bricked devices, dead SD cards or
* anything related with the following files. Please do some
* research if you don't know what you're doing!
*/
Hayo!
Here I bring you the stock recovery and boot images for the realme X2 Pro with Global/European ROM.
I'll try to keep this up to date, I swear .
Also, thnx to @Jerry08 for helping out to bring you this
Download:
https://sourceforge.net/projects/rmx1931ex-stock-files/files/RMX1931EX_11_A06_GLOBAL.zip/download
good job man
kindly provide stock recovery of chinese rom
can someone confirm this?
is this legit? can someone confirm this by testing CN rom to EU/GLOBAL? anyone? i really need the global. please!
realmayar said:
is this legit? can someone confirm this by testing CN rom to EU/GLOBAL? anyone? i really need the global. please!
Click to expand...
Click to collapse
It's only boot and recovery, not system. You can't change CN to Global with this.
sorry, my bad. i hope global rom will be out soon.
InsaneDarkness said:
Code:
/*
* I am not responsible for bricked devices, dead SD cards or
* anything related with the following files. Please do some
* research if you don't know what you're doing!
*/
Hayo!
Here I bring you the stock recovery and boot images for the realme X2 Pro with Global/European ROM.
I'll try to keep this up to date, I swear .
Also, thnx to @Jerry08 for helping out to bring you this
Download:
https://sourceforge.net/projects/rmx1931ex-stock-files/files/RMX1931EX_11_A06_GLOBAL.zip/download
Click to expand...
Click to collapse
Seriously, why don't you backup partitions in Twrp except your EFS and upload somewhere ? If you really make yourself useful of course.
os_man said:
Seriously, why don't you backup partitions in Twrp except your EFS and upload somewhere ? If you really make yourself useful of course.
Click to expand...
Click to collapse
We're trying to fix another thing first, so just wait first everything comes when it has to
InsaneDarkness said:
We're trying to fix another thing first, so just wait first everything comes when it has to
Click to expand...
Click to collapse
Tell me your problem and I'll fix it for you.
Unlock problems
InsaneDarkness said:
Code:
/*
* I am not responsible for bricked devices, dead SD cards or
* anything related with the following files. Please do some
* research if you don't know what you're doing!
*/
Hayo!
Here I bring you the stock recovery and boot images for the realme X2 Pro with Global/European ROM.
I'll try to keep this up to date, I swear .
Also, thnx to @Jerry08 for helping out to bring you this
Download:
https://sourceforge.net/projects/rmx1931ex-stock-files/files/RMX1931EX_11_A06_GLOBAL.zip/download
Click to expand...
Click to collapse
Hi, could you pls give us a link to the full rom ? I unlocked my phone after i updated it to this version and since then there are some probs, fp not working and so on.....thx. I googled that about 1 h but i found only the previous version and the phone doesn't install this previous cause the current OS is newer...
Zooytron said:
Hi, could you pls give us a link to the full rom ? I unlocked my phone after i updated it to this version and since then there are some probs, fp not working and so on.....thx. I googled that about 1 h but i found only the previous version and the phone doesn't install this previous cause the current OS is newer...
Click to expand...
Click to collapse
i think there is Global Rom in their website (EU) but for some reason i cant make it to work i got CN version of the phone.
realmayar said:
i think there is Global Rom in their website (EU) but for some reason i cant make it to work i got CN version of the phone.
Click to expand...
Click to collapse
yeah same here can't install it in my CN rom version would love it though!! Any insight?
lutherkingmartin said:
It's only boot and recovery, not system. You can't change CN to Global with this.
Click to expand...
Click to collapse
After doing this can I install global rom in Realme x2 pro??
Does it mean, we can't not convert a Chinese version to a global for the moment? Just got the Cinese version, it was supposed to be a global/EU
Yup, the wait is going to be long, not even the realme x can be flashed to global from cn, so the phone is kinda limited now
Surprisingly, my device got bricked with theese.
It's a Realme X2 Pro Global.
I was planning to go back to all stock + locked after being tired of root hiding stopping working from time to time. So I full flashed stock and the flashing worked but strangely TWRP was surviving the flash - flashing stock should also overwrite the recovery - also there were issues with enabling wifi. Then I tried flashing this boot and recovery in order to force all factory software to run, and now the device is hardbricked on QUSB_BULK mode.
I suppose there is no solution now since I see the only procedure to unbrick from QUSB_BULK involves SD card and this device doesn't have one.
Just sharing, not blaming those binaries, what happened seems very strange for me.
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
So, I managed to install IN2025 C.11 ROM on my IN2023 (downloaded wrong ROM via Oxygen Updater), now was trying to flash latest C.15 2023 update but it just fails.
Is there an easy way to flash back the IN2023 ROM?
Pretty sure it was working on Android 11.
Thanks!!!
There are rollback packages around but they will wipe your data.
So i would advice using MSM Tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
OOS12 is not good imo.
Please watch out what you do on A12.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
xtcislove said:
There are rollback packages around but they will wipe your data.
So i would advice using MSM Tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
OOS12 is not good imo.
Please watch out what you do on A12.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Click to expand...
Click to collapse
Thaks a million for the info! I'll give the MSM a go!
###########################################################################################Use this to spread awareness to the dead OnePlus phones, cause of death: flashing official firmware file from official OnePlus
###########################################################################################
wont ever buy a oneplus phone after 7, using my old but gold oneplus 3 now
lighting up candles for them 🕯🕯🕯
[One Plus 8, One Plus 8 Pro, One Plus 8T]
1. As i see, most of cases were caused by flashing (in fact official) files through fastboot mode.
2. Probably, but i can be wrong, it's flashing through some... tools like all-in-one tool OR without awareness that there are xbl files for DDR4 and DDR5. On this forum there's topic where one smart guy wrote all things which users should know before flashing. YES, i know that putting in one package two versions of xbl file is stupid move...
3. I unpacked OOS13 Beta and i saw, that there's no more two versions of xbl files, so from OOS13 this problem shouldn't exist (atleast i hope).
true.. but i was using a simple fastboot flash from a tutorial from xda which i thought to be way safer than flashing hard-style with MSM tool
i even rant out and offended anyone replying to me, im so fckd up like that.. sorry "Nimueh" if you reading this, my appologies, its just that i paid much money on this phone, am experienced with flashing and never would have guessed an issue like that
Like i said before. This is known. Which will not help dead devices i know.
Its a shame that this can happen. Anyway lets keep the forums clean and push deadicated threads with all the infomation instread of opening new ones.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
xtcislove said:
Like i said before. This is known. Which will not help dead devices i know.
Its a shame that this can happen. Anyway lets keep the forums clean and push deadicated threads with all the infomation instread of opening new ones.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Click to expand...
Click to collapse
but what if we can find a solution to total dead phones ? like this mofo below here:
| https://multi-com.eu/,details,id_pr,22443,key,service-edlmaster-ct-280-cable.html |
it seems that this could work, ill order one and will let you know, if not, ive already bought a motherboard for < 20.-€ from ebay
u can see this thread as a try-hard thread for death bricked OP8 phones, not settling yet with this issue
ikram.senguen said:
but what if we can find a solution to total dead phones ? like this mofo below here:
| https://multi-com.eu/,details,id_pr,22443,key,service-edlmaster-ct-280-cable.html |
it seems that this could work, ill order one and will let you know, if not, ive already bought a motherboard for < 20.-€ from ebay
u can see this thread as a try-hard thread for death bricked OP8 phones, not settling yet with this issue
Click to expand...
Click to collapse
We had other threads here talking about this issue a lot. I would be very happy if you could solve this issue. But the problem is not the we cant enter EDL Mode, the problem is that your RAM is dead. You wont fix a piston seizure with jump start spray.
xtcislove said:
We had other threads here talking about this issue a lot. I would be very happy if you could solve this issue. But the problem is not the we cant enter EDL Mode, the problem is that your RAM is dead. You wont fix a piston seizure with jump start spray.
Click to expand...
Click to collapse
As wrote on another thread, there is no proof that ram is dead, my guess is that flashing wrong xbl, ram can't be intialized and the phone won't start. On telegram i read that someone with 8t could enter edl mode by shorting test pins on Mobo and recovered his 8t. Some Chinese guy used engeering cable to enter edl.
ppajdek said:
As wrote on another thread, there is no proof that ram is dead, my guess is that flashing wrong xbl, ram can't be intialized and the phone won't start. On telegram i read that someone with 8t could enter edl mode by shorting test pins on Mobo and recovered his 8t. Some Chinese guy used engeering cable to enter edl.
Click to expand...
Click to collapse
and thats why this thread stays for further clarification, no matter how hard one wants to have it closed
+ the thread that lead to this issue, yes i mean the one where it is explained how to flash stock rom through adb and fastboot, is closed for commenting guess because many people encontered this isse
than again, why is it closed so nobody can see that this method can lead to death, thus resulting in countless dead phones where one cant even complain at the thread that lead his phone to death
ppajdek said:
As wrote on another thread, there is no proof that ram is dead, my guess is that flashing wrong xbl, ram can't be intialized and the phone won't start. On telegram i read that someone with 8t could enter edl mode by shorting test pins on Mobo and recovered his 8t. Some Chinese guy used engeering cable to enter edl.
Click to expand...
Click to collapse
I read a lot about potential methods to unbrick but for 6 months we dont have anything that works and nobody proofed that he unbricked his device. The only reasons i am against another and another thread is that we loose calrity and that you give people false hope.
ikram.senguen said:
and thats why this thread stays for further clarification, no matter how hard one wants to have it closed
+ the thread that lead to this issue, yes i mean the one where it is explained how to flash stock rom through adb and fastboot, is closed for commenting guess because many people encontered this isse
than again, why is it closed so nobody can see that this method can lead to death, thus resulting in countless dead phones where one cant even complain at the thread that lead his phone to death
Click to expand...
Click to collapse
I dont "want" you thread to be closed i state my opinion, we need to have clarity on this topic and not a lot of useless information aside from "dont brick you device by flashing the wrong image". At least as long we dont have anything that helps.
The main thread that i post everytime i give flashing advice is still alive:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
It should be the first sticky in every forum for each device that is affected.
Threads without the advice should be closed or the first post should be the advice on "how to not kill your device".
As i said, dont give people false hope. Like the chinese dude etc.
This problem is known for nearly 7 months and we would already know if there is something to do about it.