Hi guys, I've read almost all a of the post avalaible about converting the Chinese NE2210 to NE2215 or NE2213, but I've seen a lot of bricked devices around there.
So I want to ask to all the people that make successful the conversion, if there so risky at it appears, it worth the price?
I'm very pleased with Color OS, but the WhatsApp notification problem it's driving me crazy, something it works sometimes not.
Thanks in advance for your response guys.
dannytgt said:
Hi guys, I've read almost all a of the post avalaible about converting the Chinese NE2210 to NE2215 or NE2213, but I've seen a lot of bricked devices around there.
So I want to ask to all the people that make successful the conversion, if there so risky at it appears, it worth the price?
I'm very pleased with Color OS, but the WhatsApp notification problem it's driving me crazy, something it works sometimes not.
Thanks in advance for your response guys.
Click to expand...
Click to collapse
So I converted from NE2215 to NE2213, easy enough I'll tell you exactly how I did it. First and foremost you want to factory reset your device and if you where rooted make sure you're not anymore. Then you'll want to get one of the Rollback ZIPs from here:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
You'll want to follow the instructions on how to flash the rollback with your desired rom.
That's it, your phone will boot up on A.12 of whichever version you rollback too and you can update OTA normally from there. If you need anymore help just ask!
unsafe8989 said:
So I converted from NE2215 to NE2213, easy enough I'll tell you exactly how I did it. First and foremost you want to factory reset your device and if you where rooted make sure you're not anymore. Then you'll want to get one of the Rollback ZIPs from here:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
You'll want to follow the instructions on how to flash the rollback with your desired rom.
That's it, your phone will boot up on A.12 of whichever version you rollback too and you can update OTA normally from there. If you need anymore help just ask!
Click to expand...
Click to collapse
Thanks for your answer, but i'm ny case it will be from NE2210 to NE2213 or any similar oxygen os model, coming from the chinese Color OS, i don't know if that's posible, i've tried with the enhanced fast boot tool múltiple times but was unsuccessful.
dannytgt said:
Thanks for your answer, but i'm ny case it will be from NE2210 to NE2213 or any similar oxygen os model, coming from the chinese Color OS, i don't know if that's posible, i've tried with the enhanced fast boot tool múltiple times but was unsuccessful.
Click to expand...
Click to collapse
I have a NE2210 which the seller converted to NE2215 using the same method. I then converted it from NE2215 to NE2213 using this method as well.
abdulhamid1978 said:
I have a NE2210 which the seller converted to NE2215 using the same method. I then converted it from NE2215 to NE2213 using this method as well.
Click to expand...
Click to collapse
I've tried this method right now; but definitely doesn't worked, i guess it will work when you roll back from any Oxygen model version; but not from Color OS.
dannytgt said:
I've tried this method right now; but definitely doesn't worked, i guess it will work when you roll back from any Oxygen model version; but not from Color OS.
Click to expand...
Click to collapse
Did you use this method? If so, what exactly happened? There are 2 methods below. Also which version of Color Os are you on?
OBT to MP rollback guide - via Local OTA update (NA ONLY)
Note: This downgrade method only works for NA version, IN and EU users please refer to the rollback guide above.
Note: This rollback method will erase all the contents of the phone, please be sure to backup first. Some applications may be lost after upgrading, you can restore the lost applications by installing the packages below.
Download the latest ROM rollback zip package from the specified server.
Copy the Rollback package to the phone storage.
Install this apk . You'll need it to rollback. Then, open the app -> tap the top right gear icon -> find the downgrade package and tap it -> wait to finish the installation -> tap reboot
After the rollback is complete, click Restart.
Rollback successful.
Please note that if you are not able to click "Local install", you can try the following step to fix it:
Disconnect all Wi-Fi and Mobile data
Go to Settings -> Apps -> App management -> Click the top right button -> Show system -> search "Software update" in the search bar and tap "Software update" -> Storage usage -> Clear data
Keep all networks disconnected and repeat the upgrade or rollback guide
Want to go back to OxygenOS 12? Download the Rollback package from the links below:
OnePlus 10 Pro NA Version
OnePlus 10 Pro IN Version
OnePlus 10 Pro EU Version
Or did you use this metod:
OBT to MP rollback guide - via Local OTA update (IN&EU ONLY)
Note: This downgrade method only works for the IN&EU version, NA users please refer to the rollback guide below.
Note: This rollback method will erase all the contents of the phone, please be sure to backup first. Some applications may be lost after upgrading, you can restore the lost applications by updating to the latest MP version via Local OTA update.
Download the latest ROM rollback zip package from the specified server.
Copy the ROM rollback package to the phone storage.
Go to Settings -> About device -> Version -> Click Build number 7 times and enter the password, now you are in the developer mode.
Go back to Settings -> About device -> Up to date -> Click the top right button -> Local install -> Click on the corresponding rollback package -> Extract -> Upgrade -> System upgrade completed to 100%.
After the rollback is complete, click Restart.
Rollback successful.
Want to go back to OxygenOS 12? Download the Rollback package from the links below:
OnePlus 10 Pro NA Version
OnePlus 10 Pro IN Version
OnePlus 10 Pro EU Version
Thanks for yoour interest and help, I've tried the second method you quoted trought the system updater, but i try on "local install" I get a "Verification failed" message.
After your answer I've tried the listed apk method , but doesn't happen, i've got : "move installation package into roor directory", tried your recommendations, but doesn't work either.
I'm actually on Color OS 13.0.0 NE2210_11_C.18, i dont know if that has some influence.
dannytgt said:
Thanks for yoour interest and help, I've tried the second method you quoted trought the system updater, but i try on "local install" I get a "Verification failed" message.
After your answer I've tried the listed apk method , but doesn't happen, i've got : "move installation package into roor directory", tried your recommendations, but doesn't work either.
I'm actually on Color OS 13.0.0 NE2210_11_C.18, i dont know if that has some influence.
Click to expand...
Click to collapse
See if there is a rollback package to go from Color OS 13 to 12, and then try again. I have no idea if neither method worked.
After your answer I've tried the listed apk method , but doesn't happen, i've got : "move installation package into roor directory", tried your recommendations, but doesn't work either.
Did you save the rollback package on the root of the internal storage?
That's exactly what i´m doing right now, i can´t find a rollback package but i guess and old Color 12.1 version will work as well.
Yes, i've moved the file into the root folder and delete the .jar extension on the name.
This was the rollback package file I downloaded:
OnePlus 10 Pro EU Version
2354_sign_NE2213_11_A_OTA_0120_all_9f570f_01000100.zip
I did not have to rename it at all, just saved the above file in the root. Mine did not have a .jar extension.
Used this apk to install from root
I then installed this the same way:
Here are the latest packages of OxygenOS 12 to help you restore the lost applications after rollback to Android 12:
OnePlus 10 Pro EU Version (A.15)
NE2213_11_A_OTA_0150_all_90846a_01000100.zip
Hope you find a solution
I've tried with the Color OS 12.1 package, al least get recognized by the "local upgrade app" but it gives me this error:
"The version of your selected package is lower than that of the current systema. To avoid booting failure, downgrading is not allowed".
So Im stuck at Color OS 13 i guess, i dont know if there is an especific Color Os 13 rollback package, i've search it , but cand find anyone, onle the same you quoted me.
I would asume the only avalible method is to flash trought enhanced fastboot, however since I've tried multiple times and can't delete de .cow files at partition, better to get familar with Color OS.
abdulhamid1978 said:
I have a NE2210 which the seller converted to NE2215 using the same method. I then converted it from NE2215 to NE2213 using this method as well.
Click to expand...
Click to collapse
just discovered i have the same phone.. 2210 12gb256 converted to 2215 out of the box (bootloader was locked)..
may i ask what are the advantages, if any, of shifting to 2213 over the 2215?
i just found that rooting a 2210 converted to 2215 causes the ram extension feature to break. (phone is on android 13 c26 jan update)
is yous rooted on 2213? does anything break or are there any major bugs? does the ram extension work (does it show 12gb+xgb in about device)?
I have not rooted the phone. One benefit for 2213 is OTA updates are received faster.
Related
hello friends today i will share a method that i found on youtube how to switch from chinese to global firmware on Meizu Pro 7
all the credits are for Uncle MokuS
i just wanted to help people that is searching for it like me
so just follow the totorial - https://www.youtube.com/watch?v=aDp...5wdjofattwgksn3zi1jpw03c010c.1508299039136556
the totorial is in russian so if you have any doubt just read the coments in video discription
that method is different that the one that i use in my old mx5 by terminal emulator... i really would prefer the terminal emulator method because just change the phone and you can install any G firmware by flyme recovery and keep with ota updates and without the phone rooted (i dont want root because i use some apps that doesnt allow me use if i have root) but i didnt find a diferent mode yet i hope some one could show a diferent method like i did to mx5
everything works because its original firmware the only thing is that to next updates you´ll have to do by flashfire
anyway i hope you all enjoy G firmware
Hi, thanks for the good news.
Does anyone know whether this method also works with the Meizu Pro 7 PLUS?
The people in comments say that its not working
You can find an english Guide for the installation of the Global ROM on the chinese Meizu Pro 7 here:
https://www.china-phone.net/meizu-pro-7-global-rom-guide.html
Lost imei
I have lost my imei numbers and they become null.
Also i have lost root access after intalling the update.zip from flymeos.com. Because i cant login into meizu account after installing the update.zip,
it says ''invalid parameter ''.
Phone has locked bootlader. Cant flash anything..
Any suggestions ?
Dennis1311 said:
Hi, thanks for the good news.
Does anyone know whether this method also works with the Meizu Pro 7 PLUS?
Click to expand...
Click to collapse
I've got this one working for Pro 7 Plus, model M793Q:
1. Download Flyme 6.7.10.31 beta rom from official chinese Flyme site and put it to your phone's main folder
2. Enter Recovery mode (Volume Up + Power), select "Update firmware" and "Wipe data", then wait until the update is done
3. Download Flyme 6.1.2.0G rom from official site and also put it to your phone just like the chinese rom
4. Enter Recovery mode again and do the same things - select "Update firmware" and "Wipe data", then wait until the update is done
Thanks for your Method..It is working great on Meizu Pro 7 PLUS Model: M793H to :good:
T3Rm0 said:
I've got this one working for Pro 7 Plus, model M793Q:
1. Download Flyme 6.7.10.31 beta rom from official chinese Flyme site and put it to your phone's main folder
2. Enter Recovery mode (Volume Up + Power), select "Update firmware" and "Wipe data", then wait until the update is done
3. Download Flyme 6.1.2.0G rom from official site and also put it to your phone just like the chinese rom
4. Enter Recovery mode again and do the same things - select "Update firmware" and "Wipe data", then wait until the update is done
Click to expand...
Click to collapse
Just one thing you still have ota updates right?
im trying in my pro 7 (standard) and when i try to install the G firmware in recovery i got the message firmware corrupt do the people with pro 7 plus is lucky
its not working in the standard version i give up xD
1. I have still my ota updates on Meizu pro 7 plus with the global version that i recently update from A chinese firmware to beta chinese then to Global version.
2. You need to have the Chinese Beta version first on your phone to update to Global version.
3. You can download the chinese flyme firmware beta version from Meizufans. Search Meizufans on the Google.
4. Allways backup your Imei number so you can restore it. That is only if the Imei NR gets NULL.Best place to have your backup is PC.
5. Download the global version from the flymeos.com
6. It should work on the standard version because it has the beta version too.
Good Luck :good:
DiogoSepultura said:
Just one thing you still have ota updates right?
im trying in my pro 7 (standard) and when i try to install the G firmware in recovery i got the message firmware corrupt do the people with pro 7 plus is lucky
its not working in the standard version i give up xD
Click to expand...
Click to collapse
TedGok said:
1. I have still my ota updates on Meizu pro 7 plus with the global version that i recently update from A chinese firmware to beta chinese then to Global version.
2. You need to have the Chinese Beta version first on your phone to update to Global version.
3. You can download the chinese flyme firmware beta version from Meizufans. Search Meizufans on the Google.
4. Allways backup your Imei number so you can restore it. That is only if the Imei NR gets NULL.Best place to have your backup is PC.
5. Download the global version from the flymeos.com
6. It should work on the standard version because it has the beta version too.
Good Luck :good:
Click to expand...
Click to collapse
lets see...
so i download the firmwares from flyme websites (they are the same that we have in meizu fans) so i installed flyme 6.7.10.31 beta
after that i went to recovery and put the G firmware inside the phone main folder, the only G firmware version that pro7 standard has is 6.1.3.0
and in recovery i try to update and always say that the firmware is corrupt
DiogoSepultura said:
lets see...
so i download the firmwares from flyme websites (they are the same that we have in meizu fans) so i installed flyme 6.7.10.31 beta
after that i went to recovery and put the G firmware inside the phone main folder, the only G firmware version that pro7 standard has is 6.1.3.0
and in recovery i try to update and always say that the firmware is corrupt
Click to expand...
Click to collapse
Try to do this:
1. Get Root permissions in settings and download Root Explorer
2. Put Global rom into your main folder
3. Start Root Explorer, grant root permissions to him and go to /dev/block/platform/bootdevice/by-name
4. Open devinfo as text file and change it from 0x79101001 to 0x79151001, then save it
5. Open the standard Flyme explorer, click on your global rom and agree with wipe
I can't guarantee that it will work but if it won't nothing bad will happen - the phone will just reboot
T3Rm0 said:
Try to do this:
1. Get Root permissions in settings and download Root Explorer
2. Put Global rom into your main folder
3. Start Root Explorer, grant root permissions to him and go to /dev/block/platform/bootdevice/by-name
4. Open devinfo as text file and change it from 0x79101001 to 0x79151001, then save it
5. Open the standard Flyme explorer, click on your global rom and agree with wipe
I can't guarantee that it will work but if it won't nothing bad will happen - the phone will just reboot
Click to expand...
Click to collapse
Hello! But i have there not 0x79101001 in "devinfo" i have 0x79201001
How can i change?
best regards
peter
pmartin said:
Hello! But i have there not 0x79101001 in "devinfo" i have 0x79201001
How can i change?
best regards
peter
Click to expand...
Click to collapse
In that case change it to 0x79251001, "5" means european device
Do you have Pro 7 HE or something? I thought there are only 2 IDs:
PRO 7 Plus 0x79351001
PRO 7 0x79151001
T3Rm0 said:
In that case change it to 0x79251001, "5" means european device
Do you have Pro 7 HE or something? I thought there are only 2 IDs:
PRO 7 Plus 0x79351001
PRO 7 0x79151001
Click to expand...
Click to collapse
pmartin did you tried this already? let us know what happend
DiogoSepultura said:
pmartin did you tried this already? let us know what happend
Click to expand...
Click to collapse
I've already tried it on my Plus device and nothing happened
The problem is that the developer has made a protection against changing ID - there are several scripts named loop, so if you change ID in devinfo and reboot they will roll back the changes.
Also I've searched for previous scripts that were working on old meizu devices, there are several ways of doing that:
1. Rewrite devinfo by using unix commands - as I understood the program finds a sector where the ID is based and replaces it. The problem is that you need to know an exact binary address for the ID but I don't know how to disassemble .img files :<
2. Get devinfo straight from the same EU device and replace it - it's easier but I don't have an EU file (If someone has it please contact me)
3. Use flash tool to write the ID directly in chipset - the most dangerous way but I can't find binary files for Helio X30, and also you need to know an adress of ID
So the easiest and the most safe way is method 2, because even if something will go wrong you can just reinstall rom from recovery mode, but if someone here knows unix\assembler he can try to locate the ID, I have extracted devinfo file (it's still has chinese ID but I believe we can find a way out)
Hello!
At first i had to install the "beta"-Rom. Because i had installed the SuperSu and i am at the "bootloop".
I am back, i try the version.
regards
peter
T3Rm0 said:
In that case change it to 0x79251001, "5" means european device
Do you have Pro 7 HE or something? I thought there are only 2 IDs:
PRO 7 Plus 0x79351001
PRO 7 0x79151001
Click to expand...
Click to collapse
pmartin said:
Hello!
At first i had to install the "beta"-Rom. Because i had installed the SuperSu and i am at the "bootloop".
I am back, i try the version.
regards
peter
Click to expand...
Click to collapse
it work´d for you?
Hi
I just tried the devinfo method with no success, as stated before, it rolls back to it original stage, I even change the permissions of devinfo file with read and exwcute only, but the permissions Also rolls back
I purchased a meizu pro 7, spanish model(global model) And I will probably Return it since I purchased Also one meizu pro 7 plus, but if you want, I can accept it a few days in order to get the files needed from the European model.
Thanks!
kralde said:
Hi
I just tried the devinfo method with no success, as stated before, it rolls back to it original stage, I even change the permissions of devinfo file with read and exwcute only, but the permissions Also rolls back
I purchased a meizu pro 7, spanish model(global model) And I will probably Return it since I purchased Also one meizu pro 7 plus, but if you want, I can accept it a few days in order to get the files needed from the European model.
Thanks!
Click to expand...
Click to collapse
if you can just share the information mate, i praying for someone who understant about this crack this thing so we can all use global firmware in our phones
T3Rm0 said:
Try to do this:
1. Get Root permissions in settings and download Root Explorer
2. Put Global rom into your main folder
3. Start Root Explorer, grant root permissions to him and go to /dev/block/platform/bootdevice/by-name
4. Open devinfo as text file and change it from 0x79101001 to 0x79151001, then save it
5. Open the standard Flyme explorer, click on your global rom and agree with wipe
I can't guarantee that it will work but if it won't nothing bad will happen - the phone will just reboot
Click to expand...
Click to collapse
DiogoSepultura said:
it work´d for you?
Click to expand...
Click to collapse
Hey guys! Now i have the beta-version from "a" but no "g" version!
I have change the devinfo but nothing happend.
Has anyone an idea how i can install the "g" version?
Best regards.
peter
I ran the Firmware Finder tool today and was surprised to find there was an update for the P9. Apparently it has some security patches. The firmware finder tool has instructions how to upgrade, but they're somewhat involved.
I'm currently on EVA-L09C432B504, and I've checked but there's no OTA update available. Is there a way to do this update manually? I've read on this thread these instructions - is this likely to work for this update?
Download the two files, update.zip and update_data_full_hw_meafnaf.zip, do not unzip, put into DLOAD folder on your SD card.
Phone better to be charged, switch off, disconnect USB, press and keep pressing both Vol+ and Vol-, then boot - it should start DLOAD
commandonz said:
I ran the Firmware Finder tool today and was surprised to find there was an update for the P9. Apparently it has some security patches. The firmware finder tool has instructions how to upgrade, but they're somewhat involved.
I'm currently on EVA-L09C432B504, and I've checked but there's no OTA update available. Is there a way to do this update manually? I've read on this thread these instructions - is this likely to work for this update?
Download the two files, update.zip and update_data_full_hw_meafnaf.zip, do not unzip, put into DLOAD folder on your SD card.
Phone better to be charged, switch off, disconnect USB, press and keep pressing both Vol+ and Vol-, then boot - it should start DLOAD
Click to expand...
Click to collapse
Pure DLOAD applies only to FullOTA-MF-PV, b506 is without PV
Check Firmware Access Availability in FF, if it shows Approved for your SIM, you could try if HiSuite or eRecovery give you a chance to upgrade (I don't believe it will work yet)
Otherwise, with unlocked Bootloader and methods like HWOTA/no-check-recovery, you should be able to force DLOAD to b506
Thanks @zgfg. In Firmware Finder it says "firmware approved for installation for 506".
I ran eRecovery yesterday but it started to download the 504 version. Would it look on the SD card somewhere for an updated version? If not, can you give / link me to a bit more information on how I would use HiSuite to do the update?
I see in another thread that Android 8 is available if you jump through many, many hoops. Given the age of the phone I don't think it's worth the bother.
commandonz said:
Thanks @zgfg. In Firmware Finder it says "firmware approved for installation for 506".
I ran eRecovery yesterday but it started to download the 504 version. Would it look on the SD card somewhere for an updated version? If not, can you give / link me to a bit more information on how I would use HiSuite to do the update?
I see in another thread that Android 8 is available if you jump through many, many hoops. Given the age of the phone I don't think it's worth the bother.
Click to expand...
Click to collapse
If using newer versions of HiSuite, somewhere at the bottom (HiSuite window on PC) you have an option to install different firmwhere, and there an option to upgrade (and sometimes to downgrade).
But if eRecovery does not offer you b506, Im pretty sure HiSiute would not either
Unfortunately HiSuite doesn't offer an upgrade. The "System Update" is the only control I can find, and it says 504 is the latest official firmware. Seems odd that I have the latest firmware but can't install it.
Any ideas @zgfg , or anyone else?
commandonz said:
Unfortunately HiSuite doesn't offer an upgrade. The "System Update" is the only control I can find, and it says 504 is the latest official firmware. Seems odd that I have the latest firmware but can't install it.
Any ideas @zgfg , or anyone else?
Click to expand...
Click to collapse
Read my previous answer, with unlock bootloader, HWOTA method
But why bothering only because security patch
True, I might not bother. Appreciate your pointers, I'd have to go work out what the acronyms stand for and how to do it - all this kind of thing isn't very well documented, as the people who understand it describe it in a way that they understand, rather than for beginners. Better than nothing though
commandonz said:
True, I might not bother. Appreciate your pointers, I'd have to go work out what the acronyms stand for and how to do it - all this kind of thing isn't very well documented, as the people who understand it describe it in a way that they understand, rather than for beginners. Better than nothing though
Click to expand...
Click to collapse
HWOTA full decription with resources for download:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Use TWRP for P9 Nougat from the same thread, OP post #1 (not some others like from the official site, etc)
If you need more (unlocking Bootloader, flashing TWRP, please search on XDA)
Edit: Btw, you have also Xiaomi Mi 9T?
https://forum.xda-developers.com/showpost.php?p=81817031&postcount=41
zgfg said:
HWOTA full decription with resources for download:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Use TWRP for P9 Nougat from the same thread, OP post #1 (not some others like from the official site, etc)
If you need more (unlocking Bootloader, flashing TWRP, please search on XDA)
Edit: Btw, you have also Xiaomi Mi 9T?
https://forum.xda-developers.com/showpost.php?p=81817031&postcount=41
Click to expand...
Click to collapse
Thanks @zgfg, I appreciate the link and information.
I had a 9T. The fingerprint reader is so awful I sold the phone at loss and moved back to the P9.
commandonz said:
Thanks @zgfg, I appreciate the link and information.
I had a 9T. The fingerprint reader is so awful I sold the phone at loss and moved back to the P9.
Click to expand...
Click to collapse
Yes, unfortunately fingerprint reader on Xiaomi Mi 9T is TOTALLY USELESS. First and last Xiaomi phone ever for me
Please read all indications before proceeding.
Proceed always at your own risk!!!
I did the test to perform the transition from OpenBeta firmware to stable release, using the keep_data file without deleting data, and keeping the root already present on the phone.
The steps are simple, first of all you need to:
Download the complete firmware file
Download the keep_data apk file
save them in the phone's memory, after which you proceed with the local update (ignore the data deletion warning) and once the installation is completed you DO NOT NEED TO RESTART THE PHONE (if you restart now all data will be erased).
Now we install the keep_data.apk and run it, confirming that we do not want to delete the data, even now we DO NOT RESTART but we open magisk, select the "install" button next to the magisk version already present and select "install in the inactive slot (after OTA)", proceed with the installation and when completed, we can finally reboot.
We will have our Oneplus with OxygenOS 11 Stable firmware, root and magisk installed and all our data present.
I tested everything on Oneplus 7 going from OpenBeta4 to OxygenOS 11.0.1.1, I still recommend making a backup of all your data before proceeding, safety first of all.
TESTED ONLY WITH OXYGENOS 11 FIRMWARE.
The keep_data application, has been released for use with OxygenOS 11, I have no way of knowing if it is also possible to use it with OxygenOS 10.
I was a tester and everything went smoothly, no problems or abnormal behavior but
it is important to remember that proceed always at your own risk!!!
full wipe is always recommended in the transition from beta to stable and vice versa.
Good luck!
Original reference source for the keep_data.apk file, present on the oneplus forum here.
UPDATE: the guide is valid and working even using the rollback package firmware necessary to switch from OpenBeta 5 to OxygenOS 11.0.1.1
Proceed always at your own risk!!!
If I wanna try this, it means that I have to install the rollback build from here and then install the keep_data.apk, right?
kamalikhwan3 said:
If I wanna try this, it means that I have to install the rollback build from here and then install the keep_data.apk, right?
Click to expand...
Click to collapse
I didn't use the rollback package, I used the standard 11.0.1.1 firmware.
I believe that, with rollback package, wipe is done before firmware installation so keep_data apk would be useless.
However, using the standard firmware file I have not encountered any problems.
UPDATE: keep_data apk work also with rollback package firmware.
dianoandr said:
I didn't use the rollback package, I used the standard 11.0.1.1 firmware.
I believe that, with rollback package, wipe is done before firmware installation so keep_data apk would be useless.
However, using the standard firmware file I have not encountered any problems.
Click to expand...
Click to collapse
Alright. I already downloaded the full 11.0.1.1 firmware but now a new problem arise in which it doesn't allow me to downgrade as per the attached image. My device is OnePlus 7 Pro and currently on Open Beta 5. Is there any workaround for this?
kamalikhwan3 said:
Alright. I already downloaded the full 11.0.1.1 firmware but now a new problem arise in which it doesn't allow me to downgrade as per the attached image. My device is OnePlus 7 Pro and currently on Open Beta 5. Is there any workaround for this?
Click to expand...
Click to collapse
Unfortunately this is normal, OpenBeta 5 is newer than stable 11.0.1.1.
In this situation, the options are full wipe with the rollback firmware package, another option is to wait for a new stable firmware release, that will be newer than openbeta 5, another option is to check if the procedure I wrote also works with the firmware rollback but I have no information about it.
kamalikhwan3 said:
Alright. I already downloaded the full 11.0.1.1 firmware but now a new problem arise in which it doesn't allow me to downgrade as per the attached image. My device is OnePlus 7 Pro and currently on Open Beta 5. Is there any workaround for this?
Click to expand...
Click to collapse
Update from the Oneplus forum:
the guide is valid and working even using the rollback firmware necessary to switch from OpenBeta 5 to OxygenOS 11.0.1.1
Tried this just now and it works flawlessly! Thanks bud!!!! Now to wait until the pixel 6 comes out and switch to that
FYI for those who want, the new stable update V11.0.2.1 can be updated over Beta 5 without having to use the rollback update and using the keep_data apk works to avoid wiping data when flashing.
Hello is that working for Update from 11.0.0.2 to 11.0.2.1 without losing root ?
prad1po said:
Hello is that working for Update from 11.0.0.2 to 11.0.2.1 without losing root ?
Click to expand...
Click to collapse
No, this guide Is only for switch from beta firmware to stable without data wipe.
For update firmware without losing root, follow this step (before to start make a BACKUP, BACKUP, BACKUP,
BACKUP, BACKUP ):
Remove all installed magisk module and reboot phone.
Download full firmware 11.0.2.1 and save in phone storage memory.
Install new firmware but DO NOT REBOOT WHEN INSTALLATION IS COMPLETE.
Open Magisk and select "install" in magisk section.
Select "Install to inactive slot (After OTA update)".
When magisk installation end, reboot your phone.
Restore your magisk module.
Finish...latest firmware release installed and rooted .
Regards.
Thank you
My phone is rooted with a modified boot.img
It will work also ?
prad1po said:
Thank you
My phone is rooted with a modified boot.img
It will work also ?
Click to expand...
Click to collapse
Yes, work only with pre-rooted phone, to retain root after a firmware update
thanks for your help
it's worked perfectly
Just used this to rollback from Open Beta 5 to stable, thank you!!
Will it work with a prerooted phone?
I mean I am just on beta build (didn't root). Can I install the stable firmware and use the app to retain the data? Or is root a pre-requisite?
Shubham87 said:
Will it work with a prerooted phone?
I mean I am just on beta build (didn't root). Can I install the stable firmware and use the app to retain the data? Or is root a pre-requisite?
Click to expand...
Click to collapse
Root privileges is not required to perform the firmware change while retaining user data, just ignore the magisk installation step and reboot phone after running the keep_data application
dianoandr said:
Root privileges is not required to perform the firmware change while retaining user data, just ignore the magisk installation step and reboot phone after running the keep_data application
Click to expand...
Click to collapse
Thank you.
I have a new problem now. Local upgrade is not allowing me to install the 11.0.0.2.GM21AA firmware. I am currently running O2_Beta_5.
Local upgrade says "Version of selected package is lower than that of current system, hence downgrading not allowed".
Please help.
Shubham87 said:
Thank you.
I have a new problem now. Local upgrade is not allowing me to install the 11.0.0.2.GM21AA firmware. I am currently running O2_Beta_5.
Local upgrade says "Version of selected package is lower than that of current system, hence downgrading not allowed".
Please help.
Click to expand...
Click to collapse
You cannot update with "Local upgrade" feature, if the new firmware is older than the firmware installed on the phone.
If you currently have Openbeta 5 firmware, you can install the stable 11.0.2.1 or the latest 11.0.3.1.
The downgrade is still possible but requires a specific firmware package and the complete data wipe.
Thread closed on request of OP @dianoandr as the OP doesn't possess the device any longer!
For those with the bootloader locked and are not beta testers, there is a way to update to newest MIUI 13 (android 12) without losing data. I got the European (EEA) version of Redmi Note 10 Pro, so the links will be for EEA version of ROMS.
Here are the steps to do it:
1. Go to settings - about phone - MIUI version and tap on MIUI 12 6 or 7 times until "additional update futures are on" will pop up
2. Download your current version of MIUI 12 ROM https://bigota.d.miui.com/V12.5.7.0...AGlobal_V12.5.7.0.RKFEUXM_03d5ef5aec_11.0.zip. Download it using a browser, do not download it with MIUI updater! It would be recommended to have the last version of MIUI 12, in my case is MIUI 12.5.7.0
3. Download MIUI 13 https://bigota.d.miui.com/V13.0.3.0...AGlobal_V13.0.3.0.SKFEUXM_73299ee316_12.0.zip
4. Put the 2 downloaded ROMS in the same folder, on the internal storage of the phone - for example: internal storage/download/downloaded_rom
5. Go to settings - about phone - MIUI version and tap on the three dots on the right upper side of the screen and select Choose update package, go to folder where your downloaded ROMS are, choose V12.5.7.0.RKFEUXM/miui_SWEETEEAGlobal_V12.5.7.0.RKFEUXM_03d5ef5aec_11.0.zip and wait until the notification " Your device will reboot automatically to update to MIUI version V12.5.7.0.RKFEUXM " appears, DO NOT HIT "REBOOT AND UPDATE" OR CLOSE THE WINDOW!! Simply go to home screen.
6. Go to folder you downloaded the ROMS using file manager and rename miui_SWEETEEAGlobal_V13.0.3.0.SKFEUXM_73299ee316_12.0.zip to miui_SWEETEEAGlobal_V12.5.7.0.RKFEUXM_03d5ef5aec_11.0.zip, all you have to do is change the name of MIUI 13 ROM with the name of MIUI 12 ROM you have selected in the update of step 5. TO be able to do that you should change something in the name of MIUI 12 ROM name, you can delete the last letters or add some numbers or letters.
7. After changing the name of MIUI ROM go back to update present on recent and press on "Reboot and Update", the update process has started by decrypting the update zip, after decrypt is finished phone will reboot. Now all you have to do is wait for your beloved Redmi Note 10 Pro to apply the new update.
First boot after update will take some time, don`t panic just wait. I did update my Redmi Note 10 Pro by using this method because I have a locked bootloader and I didn`t joined the beta tester program.
This method can be used on all versions of Xiaomi, Redmi phones and all regions (TR, ID, RU, IN, EEA, GLOBAL, TW) by downloading and using the correct ROMS. If your download a wrong version rom, for example if your Redmi Note 10 is using Indonesian version of rom and you have downloaded the global rom updater won`t let you to do the update, a message like Unable to flash Custom ROM will appear.
If YOU choosing to follow this guide, I am not responsible for bricked devices.
This is perfect, just installed it. However it still has old style quick settings, they might change some design in first official build...
Did anyone noticed that it changed the boot up screen? It no longer says Redmi when turning on but rather just the Mi logo. Same goes for the booting process, goes back to the Mi icon with the 3 dots instead of MIUI's letters boot up.
Yes boot up screen logo is new.
Also to anyone considering doing this, it's still in beta as it shows.
It's jittery, laggy and not at all optimized, you won't be able to downgrade unless you have your bootloader unlocked (which I don't because the phone is new so I have to wait 162 hours).
So flasher beware.
Would anyone be able to provide an answer to the problem that I expose below ?
According to what I read on the following French site https://www.nextpit.fr/xiaomi-miui-13-mise-a-jour-smartphones-compatibles, MIUI13 would be based on Android 11 and not on Android 12 ???
It seems to me really curious, even impossible.
Thank you in advance for your opinion.
cocopipou said:
Would anyone be able to provide an answer to the problem that I expose below ?
According to what I read on the following French site https://www.nextpit.fr/xiaomi-miui-13-mise-a-jour-smartphones-compatibles, MIUI13 would be based on Android 11 and not on Android 12 ???
It seems to me really curious, even impossible.
Thank you in advance for your opinion.
Click to expand...
Click to collapse
On some lower end phones yes. But Note 10 Pro MIUI comes with Android 12.
Marvin.the.Martian said:
On some lower end phones yes. But Note 10 Pro MIUI comes with Android 12.
Click to expand...
Click to collapse
Thanks for your quick answer
Theres any way to roll back to 12.5.7?
NoName126 said:
Theres any way to roll back to 12.5.7?
Click to expand...
Click to collapse
I don't think you can downgrade, unless you have unlocked bootloader.
I'm running this beta for a few days now without a problem. There should also be official update this month and i'm sure most of the bugs will be fixed.
Hello,
Thank you, thanks to you I installed https://bigota.d.miui.com/V13.0.3.0...AGlobal_V13.0.3.0.SKFEUXM_73299ee316_12.0.zip, and it works very well,
then I installed TWRP twrp-3.6.0_11-0-sweet.img,
then magisk
and finally SystemRW/SuperRW (feat. MakeRW) v1.32.
everything is OK even the RW partition.
1000 times THANK YOU
Marvin.the.Martian said:
This is perfect, just installed it. However it still has old style quick settings, they might change some design in first official build...View attachment 5523895View attachment 5523897View attachment 5523899
Click to expand...
Click to collapse
Actualizado a miui 13 siguiendo el tutorial, sin problemas, ya tengo miui 13, todo operativo junto con android 12
If I install the beta version this way, then when the stable comes, I will be able to install it normally?
Bro I install miui 13 Eea Beta version 13.0.2.0 from recovery ROM . Now I want to go back to miui 13 Eea stable version is there to go to stable ROM without pc
Can confirm this is working. Tricked MIUI to update from 13.0.6.0.SJDEUXM to 13.0.7.0.SJDEUXM. Trying by updater app said "This rom is intended for internal testers". This is f*cking genius xD
Hi ,
I have 13.0.1 installed already on my phone and i want to install it again but get an error "the rom is intended for "internal testers" make sure your account has the required permission" , how can i bypass this ?
theres an easier way, in the updates section just tick the box for receiving updates sooner than everyone else, i had it ticked and it updated a couple week back to 13.0.13 EEA. Much easier than flashing. personally i wouldnt recommend it, my phone came brand new from Xiaomi already loaded with 13.0.3, everything worked great, but since it updated to a Beta the battery life is worse, and the phone gets extremely hot when charging and it does seem slower and laggier. i havent managed to downgrade because bootloader is locked and i really dont want to unlock it and ive never flashed a xiaomi so im not 100% on the process. If i had the choice i would stay away from anything above 13.0.3 until the issues are resolved.
NoName126 said:
Theres any way to roll back to 12.5.7?
Click to expand...
Click to collapse
Yes, plenty of videos online and posts regarding downgrading, however it can only be done officially and safely by unlocking the bootloader and flashing the rom you want to go back to and will wipe all your data. that is the only official way, you can upgrade without unlocking, but to downgrade you need to unlock it.
gazza35 said:
Yes, plenty of videos online and posts regarding downgrading, however it can only be done officially and safely by unlocking the bootloader and flashing the rom you want to go back to and will wipe all your data. that is the only official way, you can upgrade without unlocking, but to downgrade you need to unlock it.
Click to expand...
Click to collapse
True. But afterwards you can relock it
Doesn't work for me.
Hey guys! When trying to update to A16, I get this error, same issue I had before with A14, any tips on what I should do to get my phone updated to the latest fw? Happens every time I try to update to the latest.
I would recommend you to download Oxygen Updater and install the full image from them.
This should solve your issue and if not after update from the full image, just reset your device and set it up as new. That's what did the trick for me.
There's no full image unfortunately NE2215 is weird.
Local upgrade fails at 99% too, even after disabling or straight up uninstalling modules.
@dladz any tips?
same here . tried updater app also. fails at 99%
dasche said:
same here . tried updater app also. fails at 99%
Click to expand...
Click to collapse
Switching to NE2213 or reseting the device is not an option ?
zopostyle said:
Switching to NE2213 or reseting the device is not an option ?
Click to expand...
Click to collapse
I switched to NE2211, did not check the system update. now i am back on NE2215 and saw this.
resetting wont make any difference.. are you boot loader unlocked? mine is unlocked.
dasche said:
I switched to NE2211, did not check the system update. now i am back on NE2215 and saw this.
Click to expand...
Click to collapse
For me when I switched to NE2213 I had to reset the device and then the updates started to install.
when switching from one to another, it does not boot without factory reset first.
GarnetSunset said:
There's no full image unfortunately NE2215 is weird.
Local upgrade fails at 99% too, even after disabling or straight up uninstalling modules.
@dladz any tips?
Click to expand...
Click to collapse
You'd need the full update, plus you'd need the newest local installer from the OnePlus community guide.
I'm on NE2213 and the updates I install are all full zips never incremental.
The only time I've ever seen a failure at 99% is when I was using the wrong local update APK whilst I was rooted.
My advice is use the rollback zip to switch to ne2213..., you'll probably find your internet improves from doing so too.
I was using the link from oxygen updater, which is a pretty generic url that appears to be "latest" etc.
Are you sure I wont lose some 5G bands for switching to global? I'm in NA and using the NA firmware so I'm just trying to think if I'll lose any signal strength
dladz said:
You'd need the full update, plus you'd need the newest local installer from the OnePlus community guide.
I'm on NE2213 and the updates I install are all full zips never incremental.
The only time I've ever seen a failure at 99% is when I was using the wrong local update APK whilst I was rooted.
My advice is use the rollback zip to switch to ne2213..., you'll probably find your internet improves from doing so too.
Click to expand...
Click to collapse
GarnetSunset said:
I was using the link from oxygen updater, which is a pretty generic url that appears to be "latest" etc.
Are you sure I wont lose some 5G bands for switching to global? I'm in NA and using the NA firmware so I'm just trying to think if I'll lose any signal strength
Click to expand...
Click to collapse
Use the full zip here https://forum.xda-developers.com/t/oneplus-a-15-full-zips-na-in-eu.4482915/#post-87371753 for a.15 then you should be able to update without any problems. Also when rooting the phone it's always best to fastboot boot the patched magisk boot.img then use direct install. Magisk will then back up original boot.img and you will be able to restore it later when update comes then all you have to do everytime you get an update is choose restore images in magisk update but don't reboot then go back in magisk and choose install to inactive slot after ota and reboot and your good to go
GarnetSunset said:
I was using the link from oxygen updater, which is a pretty generic url that appears to be "latest" etc.
Are you sure I wont lose some 5G bands for switching to global? I'm in NA and using the NA firmware so I'm just trying to think if I'll lose any signal strength
Click to expand...
Click to collapse
They're not rollback zips in oxygen updater however you do need to turn on full from there on in..and no you won't lose bands, you'll probably gain a better signal based on previous reports.
Use the rollback zip from the OnePlus community android 13 beta 2 thread.
Once rolled back you should only use the full zips from oxygen updater with the the newest local install APK.
Pic below from oxygen updater, make sure to use the advanced settings.
Thank you!! I moved over to NE2213!
GarnetSunset said:
Thank you!! I moved over to NE2213!
Click to expand...
Click to collapse
Use the button bud
How's your signal doing now that you've shifted over?
dladz said:
Use the button bud
How's your signal doing now that you've shifted over?
Click to expand...
Click to collapse
AFAICT Identical? Not sure. Only been a couple hours and I didn't use my phone much
I was able to flash only full package zips from local upgrade. but
then i install oxygenos 13 via local upgrade. after that did same with rollback to oxygenos 12 and that fixed the issue. now i can upgrade to any OTA which is coming...