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
Today i want to explain how to update your phone in all cases you can be. The Thread is divided into situations and methods.
CASES
1. I have a stock rom with an unlocked bootloader and without modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
MSM Tool Restore Method
2. I have a stock rom with an unlocked bootloader and I'm rooted or I made some modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
TWRP Update Method
MSM Tool Restore Method
3. I have a stock rom with an unlocked bootloader and I'm unable to boot the stock rom:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
4. I have a stock rom with an unlocked bootloader and I've not the stock rom or a rom stock based:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
5. My Phone is bricked, i can't boot the rom, i can't enter in TWRP:
In this can you can try with:
Fastboot Update Method (Recommended)
MSM Tool Restore Method
METHODS
Local Update Method
With this method you can flash a newer version or the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage in the main folder;
- Go in settings/system/system updates/advanced settings/Local Update and choose your new rom ( Here you can find a video guide for this passage);
- Click on Install and at the end of the process you need to reboot the phone;
- If this is a big update it's better if you wipe your data.
Fastboot Update Method
With this method It's better flash the same version you already have:
The full method is explained in the relative thread:
OnePlus 6T Fastboot ROMS
OnePlus 6 Fastboot ROMS
TWRP Update Method
With this method It's better flash the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage;
- Click on Install;
- Choose the stock rom and flash it.
MSM Tool Restore Method
The full method is explained in the relative thread:
OnePlus 6T T-Mobile Version
OnePlus 6T
OnePlus 6
DONATE LINK
If you want to support the project please consider making a donation, thanks.
[/CENTER]
mauronofrio said:
Today i want to explain how to update your phone in all cases you can be. The Thread is divided into situations and methods.
CASES
I have a stock rom with an unlocked bootloader and without modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
MSM Tool Restore Method
I have a stock rom with an unlocked bootloader and I'm rooted or I made some modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
TWRP Update Method
MSM Tool Restore Method
I have a stock rom with an unlocked bootloader and I'm unable to boot the stock rom:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
I have a stock rom with an unlocked bootloader and I've not the stock rom or a rom stock based:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
My Phone is bricked, i can't boot the rom, i can't enter in TWRP:
In this can you can try with:
Fastboot Update Method (Recommended)
MSM Tool Restore Method
METHODS
Local Update Method
With this method you can flash a newer version or the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage in the main folder;
- Go in settings/system/system updates/advanced settings/Local Update and choose your new rom ( Here you can find a video guide for this passage);
- Click on Install and at the end of the process you need to reboot the phone;
- If this is a big update it's better if you wipe your data.
Fastboot Update Method
With this method It's better flash the same version you already have:
The full method is explained in the relative thread:
OnePlus 6T Fastboot ROMS
OnePlus 6 Fastboot ROMS
TWRP Update Method
With this method It's better flash the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage;
- Click on Install;
- Choose the stock rom and flash it.
MSM Tool Restore Method
The full method is explained in the relative thread:
OnePlus 6T T-Mobile Version
OnePlus 6T
OnePlus 6
Click to expand...
Click to collapse
Great Mauronofrio
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 02:18 PM ---------- Previous post was at 02:01 PM ----------
The second case?..Im rooted with twrp and stock rom on 6t..
so I have to flash the eventually full rom via twrp? !? which twrp?
Sent from my [device_name] using XDA-Developers Legacy app
isoladisegnata said:
Great Mauronofrio
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 02:18 PM ---------- Previous post was at 02:01 PM ----------
The second case?..Im rooted with twrp and stock rom on 6t..
so I have to flash the eventually full rom via twrp? !? which twrp?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, the recommended is the local update
Nice work
Thanks for this. This is my first OnePlus device. I'm coming from a 5-year-old HTC One so updating pretty much meant wiping phone completely and reinstalling the ROM. I watched that video on the local update method. Good to know that even the full ROM installation doesn't wipe my data.
I do need some clarification on some things, though. I'm case 2 - stock ROM, unlocked BL & rooted. I have YouTube Vanced installed via Magisk as well as AdAway. I assume those would be considered modifications. In this guide, https://forum.xda-developers.com/showpost.php?p=78026660&postcount=3, it says that rooted users need to first uninstall Magisk & restore images before installing the update. Then reinstall Magisk after updating. But here it doesn't mention the need to do this. What's the difference between these two processes? I've read lots of posts lately where people get into a soft brick situation after making some modifications. But I'm not seeing any explinations as to why this happens & I'd like to avoid that.
If I use the local update method from this thread, will Magisk survive the update and will I still be rooted? Or will I need to reinstall it & re-root?
sharksfan7 said:
Thanks for this. This is my first OnePlus device. I'm coming from a 5-year-old HTC One so updating pretty much meant wiping phone completely and reinstalling the ROM. I watched that video on the local update method. Good to know that even the full ROM installation doesn't wipe my data.
I do need some clarification on some things, though. I'm case 2 - stock ROM, unlocked BL & rooted. I have YouTube Vanced installed via Magisk as well as AdAway. I assume those would be considered modifications. In this guide, https://forum.xda-developers.com/showpost.php?p=78026660&postcount=3, it says that rooted users need to first uninstall Magisk & restore images before installing the update. Then reinstall Magisk after updating. But here it doesn't mention the need to do this. What's the difference between these two processes? I've read lots of posts lately where people get into a soft brick situation after making some modifications. But I'm not seeing any explinations as to why this happens & I'd like to avoid that.
If I use the local update method from this thread, will Magisk survive the update and will I still be rooted? Or will I need to reinstall it & re-root?
Click to expand...
Click to collapse
If you flash a stock rom you will lose all the mods you already do, root and twrp included. If you want you can keep the root, i will attach a image guide.
mauronofrio said:
If you flash a stock rom you will lose all the mods you already do, root and twrp included. If you want you can keep the root, i will attach a image guide.
Click to expand...
Click to collapse
Those are the instructions that I was referring to that had me a bit confused. Is there any benefit to doing the update that way compared to using the local update method and re-flashing Magisk, the way I did when I rooted the first time? Does one method have less potential for messing something up?
sharksfan7 said:
Those are the instructions that I was referring to that had me a bit confused. Is there any benefit to doing the update that way compared to using the local update method and re-flashing Magisk, the way I did when I rooted the first time? Does one method have less potential for messing something up?
Click to expand...
Click to collapse
It's the same thing...
mauronofrio said:
It's the same thing...
Click to expand...
Click to collapse
Great. Thank you.
I have bricked my new phone. With your flash-all.bat I have restored it in like 2 minutes.
Thanks A LOT mauronofrio! Grazie, Grazie molto!
SOS: please help to restore my oneplus6t to factory condition
mauronofrio said:
Today i want to explain how to update your phone in all cases you can be. The Thread is divided into situations and methods.
CASES
1. I have a stock rom with an unlocked bootloader and without modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
MSM Tool Restore Method
2. I have a stock rom with an unlocked bootloader and I'm rooted or I made some modifications:
You can use:
Local Update Method (Recommended)
Fastboot Update Method
TWRP Update Method
MSM Tool Restore Method
3. I have a stock rom with an unlocked bootloader and I'm unable to boot the stock rom:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
4. I have a stock rom with an unlocked bootloader and I've not the stock rom or a rom stock based:
You can use:
Fastboot Update Method (Recommended)
TWRP Update Method
MSM Tool Restore Method
5. My Phone is bricked, i can't boot the rom, i can't enter in TWRP:
In this can you can try with:
Fastboot Update Method (Recommended)
MSM Tool Restore Method
METHODS
Local Update Method
With this method you can flash a newer version or the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage in the main folder;
- Go in settings/system/system updates/advanced settings/Local Update and choose your new rom ( Here you can find a video guide for this passage);
- Click on Install and at the end of the process you need to reboot the phone;
- If this is a big update it's better if you wipe your data.
Fastboot Update Method
With this method It's better flash the same version you already have:
The full method is explained in the relative thread:
OnePlus 6T Fastboot ROMS
OnePlus 6 Fastboot ROMS
TWRP Update Method
With this method It's better flash the same version you already have
- Download the stock rom you want to flash from Official site or from XDA Thread ( OnePlus 6T or OnePlus 6 );
- Put the stock rom in your internal storage;
- Click on Install;
- Choose the stock rom and flash it.
MSM Tool Restore Method
The full method is explained in the relative thread:
OnePlus 6T T-Mobile Version
OnePlus 6T
OnePlus 6
DONATE LINK
If you want to support the project please consider making a donation, thanks.
[/CENTER]
Click to expand...
Click to collapse
Hey guys,
Re: OnePlus6T, Oxygen OS 9.0.7
SOS: Can anyone give me a Guide for Dummies (lol) kinda tutorial on how to unroot, remove twrp, remove magisk, remove adb+fastboot and everything else that had been done in the process of rooting+modding. (root as per https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6t-with-magisk-0190586/ ) (stereo mod as per https://forum.xda-developers.com/oneplus-6t/themes/magisk-stereo-speaker-mod-oneplus-6t-t3860041)
Actually, i am a total newbie/non-techie. But right after updating to os 9.0.7, i took fancy to having a stereo output through the earpiece, too. But in the end, there was no sound from the earpiece. Also, i found some other complications in other sections of the phone, although i don't know whether they were related/due to the stereo mod or the rooting process. And being a non-techie, I did not want to tinker with my phone any further. So, i decided to roll back and intuitively (1)first uninstalled stereo mod from magisk, (2)then uninstalled magisk from within the magisk itself, (3)then used the case #2 method, illustrated at https://forum.xda-developers.com/oneplus-6t/how-to/how-to-update-return-to-stock-oneplus-6-t3870795 to go back to the stock rom.
But i find that i have still not gone fully back to the factory state. When booting, i find the screen which informs me about the unlocked fastboot status, etc., which shows that twrp etc are still on my system. I would certainly want to go back to the factory condition. Will someone of you guide me step by step (as i am a non-techie) into removing this fastboot, twrp, etc. and bring me back to the factory condition and also (ii)in removing any fastboot/adb related things, if any, from my windows 10 PC? I shall be very grateful, as I am scared as well as left with no further technical skill to delve further into technical misadventure. It was my big mistake to undertake this exercise, without possessing any technical knowhow, i admit.
Anyway, someone please help.
mnbvcxzaq1 said:
Hey guys,
Re: OnePlus6T, Oxygen OS 9.0.7
SOS: Can anyone give me a Guide for Dummies (lol) kinda tutorial on how to unroot, remove twrp, remove magisk, remove adb+fastboot and everything else that had been done in the process of rooting+modding. (root as per https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6t-with-magisk-0190586/ ) (stereo mod as per https://forum.xda-developers.com/oneplus-6t/themes/magisk-stereo-speaker-mod-oneplus-6t-t3860041)
Actually, i am a total newbie/non-techie. But right after updating to os 9.0.7, i took fancy to having a stereo output through the earpiece, too. But in the end, there was no sound from the earpiece. Also, i found some other complications in other sections of the phone, although i don't know whether they were related/due to the stereo mod or the rooting process. And being a non-techie, I did not want to tinker with my phone any further. So, i decided to roll back and intuitively (1)first uninstalled stereo mod from magisk, (2)then uninstalled magisk from within the magisk itself, (3)then used the case #2 method, illustrated at https://forum.xda-developers.com/oneplus-6t/how-to/how-to-update-return-to-stock-oneplus-6-t3870795 to go back to the stock rom.
But i find that i have still not gone fully back to the factory state. When booting, i find the screen which informs me about the unlocked fastboot status, etc., which shows that twrp etc are still on my system. I would certainly want to go back to the factory condition. Will someone of you guide me step by step (as i am a non-techie) into removing this fastboot, twrp, etc. and bring me back to the factory condition and also (ii)in removing any fastboot/adb related things, if any, from my windows 10 PC? I shall be very grateful, as I am scared as well as left with no further technical skill to delve further into technical misadventure. It was my big mistake to undertake this exercise, without possessing any technical knowhow, i admit.
Anyway, someone please help.
Click to expand...
Click to collapse
You can try to use msmtool, it should be fix all these problems
mauronofrio said:
You can try to use msmtool, it should be fix all these problems
Click to expand...
Click to collapse
Can you give more details about "msmtool", what it is, where to find it and how to use it? Thanks.
mnbvcxzaq1 said:
Can you give more details about "msmtool", what it is, where to find it and how to use it? Thanks.
Click to expand...
Click to collapse
As is written in the first post:
MSM Tool Restore Method
The full method is explained in the relative thread:
OnePlus 6T T-Mobile Version
OnePlus 6T
OnePlus 6
mauronofrio said:
As is written in the first post:
MSM Tool Restore Method
The full method is explained in the relative thread:
OnePlus 6T T-Mobile Version
OnePlus 6T
OnePlus 6
Click to expand...
Click to collapse
Ok. Thanks a lot. I am gonna try it.
I have a query tough. That msmtool post relates to 9.0.5. I already am on 9.0.7. Shall i still use it?
mnbvcxzaq1 said:
Ok. Thanks a lot. I am gonna try it.
I have a query tough. That msmtool post relates to 9.0.5. I already am on 9.0.7. Shall i still use it?
Click to expand...
Click to collapse
Yes it's not a problem
mauronofrio said:
Yes it's not a problem
Click to expand...
Click to collapse
Thanks to you and this XDA community, for correctly guiding/directing me to the msmtool. Msmtool saved my life. i can't thank you guys enough.
Cheers.
Hi I need your help, Iwant yo re-lock the bootloader on my OnePlus 6T
I understand that I have to go back everything on factory but I dont know how do it.
I did the ''root'' because I wanted to change the font and improve the sound but tlost quality on Netflix, and I that is important to me because I use it a lot. I want to back to L1
The problem was when I tried to eliminate the ''root'' (magisk) The system did not star and i was afraid because Iam not an expert so i flashed the ''full OTA'' and it works again, Now I want to remove twrp but I dont know how so I need help because i dont want brick my phone
I got the recovery 9.0.7 stock.img if I flash it will work?
I have stock rom with TWRP, Can I relock the bootloader?
MSMTool remove TWRP?
sorry for my english..
ross92 said:
Hi I need your help, Iwant yo re-lock the bootloader on my OnePlus 6T
I understand that I have to go back everything on factory but I dont know how do it.
I did the ''root'' because I wanted to change the font and improve the sound but tlost quality on Netflix, and I that is important to me because I use it a lot. I want to back to L1
The problem was when I tried to eliminate the ''root'' (magisk) The system did not star and i was afraid because Iam not an expert so i flashed the ''full OTA'' and it works again, Now I want to remove twrp but I dont know how so I need help because i dont want brick my phone
I got the recovery 9.0.7 stock.img if I flash it will work?
I have stock rom with TWRP, Can I relock the bootloader?
MSMTool remove TWRP?
sorry for my english..
Click to expand...
Click to collapse
First post is pretty clear. If you don't know what to do go with the fastboot method, the local update method (if that's what you did with full OTA) must have overwritten your recovery anyway. Boot in recovery to see which recovery you have.
Hello,
I used your fastboot guide yesterday to recover my phone but I accidently flashed a newer version (9.0.10) then I had (9.0.7).
Do I need to reflash my device? If so with what method?
Steps I did:
1. Boot TWRP and wiped all except Internal Storage
2. Reboot in to the bootl;oader
3. Unpacked 9.0.10-OnePlus6TOxygen_34_OTA_017_all_1812111237_f52c4612-FASTBOOT.zip
4. Used flash-all.bat
5. Phone rebooted and working
I did not used TWRP because it did not show the correct internal storage??? If antone knows how to fix that please let me know using latest blu_spark TWRP
Can someone link me to a full rooting guide for the sweetin variant? It'll be a big help!
Thanks!
a safe haven said:
Can someone link me to a full rooting guide for the sweetin variant? It'll be a big help!
Thanks!
Click to expand...
Click to collapse
Hi
Rooting the sweetin is pretty straight forward like most Mi phones. I am sure you can google it and iron it out.
But just FYI, below are the steps -
Link Mi Account for unlocking in Developer options.
Unlock Bootloader using Mi Unlock Tool (lengthy, considering 15 days waiting period)
Flash latest TWRP
Install Magisk via TWRP.
Please let me know if you need further details
nkrishna said:
Hi
Rooting the sweetin is pretty straight forward like most Mi phones. I am sure you can google it and iron it out.
But just FYI, below are the steps -
Link Mi Account for unlocking in Developer options.
Unlock Bootloader using Mi Unlock Tool (lengthy, considering 15 days waiting period)
Flash latest TWRP
Install Magisk via TWRP.
Please let me know if you need further details
Click to expand...
Click to collapse
I thought TWRP wasnt available/fully functional yet.
Do you have a link to that?
a safe haven said:
I thought TWRP wasnt available/fully functional yet.
Do you have a link to that?
Click to expand...
Click to collapse
It is in a very good shape now that decryption is enabled, although there are a few bugs like sideload. I expect this will be cleared very soon though. You can find more info on that here -
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
And download the TWRP here-
Downloads for : Xiaomi Redmi Note 10 Pro | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
a safe haven said:
Can someone link me to a full rooting guide for the sweetin variant? It'll be a big help!
Thanks!
Click to expand...
Click to collapse
-Enable developer options
-Apply Mi for unlock
insert the active sim
register mi account using that sim
bind the number, account and phone in developer options for unlock
(you can take away sim, if you are using on another phone)
-Check using mi unlock tool and apply for it
you will get a time to wait of 168 hours(7 days)
-Unlock after the wait period
(device will be erased)
go enable developer options again
enable USB debugging
-TWRP
get the TWRP in this forum, which is very good with decryption and USB OTG/SD card access
use adb, fastboot commands on terminal and flash TWRP as your recovery and boot
(If you only want to boot without flash, you can do that too)
-Root with Magisk
with TWRP, you can flash magisk
(latest magisk will be available as apk, so change to zip and flash)
boot to ROM after flash success
-Update magisk
get magisk canary from magisk github(availabl as debug apk) and install that to update already flashed magisk(can use regular apk also which the magisk by itself will do)
canary magisk has the codes to read safety net pass correctly
-safety net check
enable magisk hide, and hide google play services, gpay or any other app you want to
flash magiskhide props config within magisk
check safety net from magisk(if canary) or by safet net test app or using gpay or any banking app
I assume, finer steps and details you already know.
nkrishna said:
It is in a very good shape now that decryption is enabled, although there are a few bugs like sideload. I expect this will be cleared very soon though. You can find more info on that here -
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
And download the TWRP here-
Downloads for : Xiaomi Redmi Note 10 Pro | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Click to expand...
Click to collapse
Thank you, appreciate it.
rathisarov said:
-Enable developer options
-Apply Mi for unlock
insert the active sim
register mi account using that sim
bind the number, account and phone in developer options for unlock
(you can take away sim, if you are using on another phone)
-Check using mi unlock tool and apply for it
you will get a time to wait of 168 hours(7 days)
-Unlock after the wait period
(device will be erased)
go enable developer options again
enable USB debugging
-TWRP
get the TWRP in this forum, which is very good with decryption and USB OTG/SD card access
use adb, fastboot commands on terminal and flash TWRP as your recovery and boot
(If you only want to boot without flash, you can do that too)
-Root with Magisk
with TWRP, you can flash magisk
(latest magisk will be available as apk, so change to zip and flash)
boot to ROM after flash success
-Update magisk
get magisk canary from magisk github(availabl as debug apk) and install that to update already flashed magisk(can use regular apk also which the magisk by itself will do)
canary magisk has the codes to read safety net pass correctly
-safety net check
enable magisk hide, and hide google play services, gpay or any other app you want to
flash magiskhide props config within magisk
check safety net from magisk(if canary) or by safet net test app or using gpay or any banking app
I assume, finer steps and details you already know.
Click to expand...
Click to collapse
Thanks for the full guide, this really helps a lot.
Also, how do you guys install OTA with twrp?
Will I be able to install OTA's using twrp?
a safe haven said:
Thank you, appreciate it.
Thanks for the full guide, this really helps a lot.
Also, how do you guys install OTA with twrp?
Will I be able to install OTA's using twrp?
Click to expand...
Click to collapse
depends on the rom, i believe
can be as simple as download update and flash(it goes through TWRP) or, you might have to download full ROM package, flash that, and then again flash magisk or even TWRP(esp if it gets replaced) sometimes
it varies
rathisarov said:
depends on the rom, i believe
can be as simple as download update and flash(it goes through TWRP) or, you might have to download full ROM package, flash that, and then again flash magisk or even TWRP(esp if it gets replaced) sometimes
it varies
Click to expand...
Click to collapse
Did you install the latest 12.0.10 update then?
I assume you have a rooted note 10 pro max, what was your procedure?
a safe haven said:
Did you install the latest 12.0.10 update then?
I assume you have a rooted note 10 pro max, what was your procedure?
Click to expand...
Click to collapse
note 10 pro indian version
updated to the latest stable and then rooted.
(but I don't think firmware matters; I mean it is the same procedure)
rathisarov said:
note 10 pro indian version
updated to the latest stable and then rooted.
(but I don't think firmware matters; I mean it is the same procedure)
Click to expand...
Click to collapse
Sorry for not clearing it up, I meant by Xiaomi OTA's.
Do tell me what your procedure is gonna be when the next OTA comes out since you're on TWRP.
It'll be a big help since I don't want to use custom ROMs at the moment.
a safe haven said:
Sorry for not clearing it up, I meant by Xiaomi OTA's.
Do tell me what your procedure is gonna be when the next OTA comes out since you're on TWRP.
It'll be a big help since I don't want to use custom ROMs at the moment.
Click to expand...
Click to collapse
unfortunately, always, I move out of MIUI to AOSP based minimalistic ROMs(I like that way)
I might not be of help to you.
But, earlier, it was like this-
once bootloader unlocked, we won't get incremental MIUI updates
so, got to download full ROM, update
and after update, every time recovery will be replaced
so need to re flash TWRP, re flash Magisk
(i don't think anything much changed, still not very sure)
rathisarov said:
unfortunately, always, I move out of MIUI to AOSP based minimalistic ROMs(I like that way)
I might not be of help to you.
But, earlier, it was like this-
once bootloader unlocked, we won't get incremental MIUI updates
so, got to download full ROM, update
and after update, every time recovery will be replaced
so need to re flash TWRP, re flash Magisk
(i don't think anything much changed, still not very sure)
Click to expand...
Click to collapse
I see, I appreciate your input regardless.
Is it usually a dirty flash? or does it wipe out everything as in factory reset after installing the update?
Also, what custom rom have you been using?
Is it stable? Are all the cameras fully functional while using the aosp based rom?
I haven't unfortunately found a stable gcam that fully works with the note 10 pro yet, therefore I am being hesitant to switch to custom ROMs for now, otherwise, I would've flashed an AOSP rom in a heartbeat, I hate MIUI.
rathisarov said:
unfortunately, always, I move out of MIUI to AOSP based minimalistic ROMs(I like that way)
I might not be of help to you.
But, earlier, it was like this-
once bootloader unlocked, we won't get incremental MIUI updates
so, got to download full ROM, update
and after update, every time recovery will be replaced
so need to re flash TWRP, re flash Magisk
(i don't think anything much changed, still not very sure)
Click to expand...
Click to collapse
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!
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.