Hey everyone, I have the realme c11, 2021 model.
The new model, by default, comes with the Android 11.
There are many different threads online showing how to unlock the bootloader on realme c11 android 10, but the same is not working with android 11.
The in-depth test apk is also not getting installed on android 11.
is there any other way we can unlock the bootloader on c11?
vikasrg said:
Hey everyone, I have the realme c11, 2021 model.
The new model, by default, comes with the Android 11.
There are many different threads online showing how to unlock the bootloader on realme c11 android 10, but the same is not working with android 11.
The in-depth test apk is also not getting installed on android 11.
is there any other way we can unlock the bootloader on c11?
Click to expand...
Click to collapse
What is the exact version of the firmware on your device? Does the number end in C.06? Have you tried the UI 2.0 In depth test? Here's a link which might help https://forum.xda-developers.com/t/guide-bootloader-unlock-realme-c12.4244957/
I have the same issue.
Build number:
RMX3231EU_11.A.02
Kernel:
4.14.193+-ab99
Update avaiable to:
RMX3231EU_11.A.58
realme UI version:
Go Edition
EDIT:
When I try to install the DeepTest.apk it failed on the Devices... with adb i get this result:
adb install .\DeepTesting.apk
Performing Streamed Install
adb: failed to install .\DeepTesting.apk: Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.coloros.deeptesting has no signatures that match those in shared user android.uid.system; ignoring!]
behri1986 said:
I have the same issue.
Build number:
RMX3231EU_11.A.02
Kernel:
4.14.193+-ab99
Update avaiable to:
RMX3231EU_11.A.58
realme UI version:
Go Edition
EDIT:
When I try to install the DeepTest.apk it failed on the Devices... with adb i get this result:
adb install .\DeepTesting.apk
Performing Streamed Install
adb: failed to install .\DeepTesting.apk: Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.coloros.deeptesting has no signatures that match those in shared user android.uid.system; ignoring!]
Click to expand...
Click to collapse
If ./adb install InDepthTest.apk isn't working, you could try to install it using the file explorer on the phone itself. I have issues installing some apps using ./adb install such as VLC for example. So installing from the phone itself might help.
Also, I think there are 2 versions of the InDepthTest, one for RUI version 1 and one for RUI version 2. Your build number ends in .A02 which I think corresponds to RUI version 1.
Hey thanks for responding... i tried it first with file manager on the device i cant install the RUI1 or RUI2 version. Both installations failed.
behri1986 said:
Hey thanks for responding... i tried it first with file manager on the device i cant install the RUI1 or RUI2 version. Both installations failed.
Click to expand...
Click to collapse
I just noticed your build number is for an RMX3231, I didn't even know that there was a new C11 with that model number. The C11 I'm familiar with is an RMX2185. Looks like there will need to be a separate thread created for the new C11 (2021) RMX3231. Here's a link to Gsm Arena which shows both versions.
After comparing the C11 Mediatek Helio G35 and C11 (2021) Unisoc SC9863A, I was surprised to see that the newer version isn't really technically better.
Thanks for that informations.
I got that phone as a present for some network-traffic tests... but i have to root it...
maybe there is something coming from realme...
thx!
behri1986 said:
Thanks for that informations.
I got that phone as a present for some network-traffic tests... but i have to root it...
maybe there is something coming from realme...
thx!
Click to expand...
Click to collapse
I had a look at Realme, others have asked for a bootloader unlock tool for the new C11. I think it's worth signing up and politely asking on their forum which I just did.
zpunout said:
I had a look at Realme, others have asked for a bootloader unlock tool for the new C11. I think it's worth signing up and politely asking on their forum which I just did.
Click to expand...
Click to collapse
Do you have this forum link?
felvic said:
Do you have this forum link?
Click to expand...
Click to collapse
Yep, here's one of them https://c.realme.com/in/post-details/1465540585430560768
Thanks!
behri1986 said:
I have the same issue.
Build number:
RMX3231EU_11.A.02
Kernel:
4.14.193+-ab99
Update avaiable to:
RMX3231EU_11.A.58
realme UI version:
Go Edition
EDIT:
When I try to install the DeepTest.apk it failed on the Devices... with adb i get this result:
adb install .\DeepTesting.apk
Performing Streamed Install
adb: failed to install .\DeepTesting.apk: Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.coloros.deeptesting has no signatures that match those in shared user android.uid.system; ignoring!]
Click to expand...
Click to collapse
Hi, I have the same specs as you, I must admit that for now it's a bad buy for me since there is no unlocked bootloader for it. I asked in their website forum and they just said it's not a good thing to unlock bootloader bla bla bla. I should have buy mi phone instead
any good news?
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
Note:- Credits To this guide goes to {Diablosss}
GUIDE FOR UNLOCKING BOOTLOADER OF MEIZU PRO 7
(Sorry for the inconvenience, but there are some issues in posting pictures. Therefore requesting you to please check the attached files for images)
This guide can also work with many other Meizu devices. Checked on 15, 16 all options (s, t, x) and on Pro7I post the archive and instructions in pictures.
Step 1: Download. Unpack. Run meizublunlocker.exe
meizublunlocker:-https://drive.google.com/open?id=1yEm_vZo4rsqEtii279AU6l1mBajiSPQ2
See Image 1 in Attachments.
Step 2:-We connect the phone to the computer in fastboot mode (hold down the Vol. Down and power buttons), click refresh. The program must identify the device.
See Image 2 in Attachments.
Step 3ress CheckBL to check bootloader status.
See Image 3 in Attachments.
Step 4:-Click the Create Request button. This will create a file with the end of req.dat in the folder with this program
We send it to the e-mail [email protected] and wait for the response file to unlock the bootloader.
(This takes usually 1 week to receive the unlocked file, but you can donate to get the file within 3 hours)
See Image 4 in Attachments.
Step 5:- After we received the unlock file with the end of res.dat, click UnlockBL and select the resulting file.
See Image 5 in Attachments.
If the file is correct then get this answer
See Image 6 in Attachments.
That's It. We successfully Unlocked the Bootloader.
Now the next thing is to install the TWRP in our Device. ( Further credits goes to{ sergpolov} )
Step 1: Download and install "adb_run"
adb run:-https://drive.google.com/open?id=1y4wdL53-P7mybKsj5XeimHRoMSpokMkQ
Step 2:- Download the required Files.
Stock Recovery Pro 7:-https://drive.google.com/open?id=1e2tRdqLi5jsT8J854RMcIA-jvZyR7xhT
Twrp Pro 7:-https://drive.google.com/open?id=1uYOT9HGractYuoJvRidgAgh8IBLhzFtu
Step 3:-We load the phone into fastboot mode, flash through the fastboot the recovery you need.
Launch the application shortcut
Step 4:-Click "3" - go to fastboot mode
See Image 7 in Attachments.
Step 5:-Click "3" - recovery
See Image 8 in Attachments.
Step 6:-Here we select the recovery file: - in the window that opens, we throw the file itself and close the window with the file and press any button.
See Image 9 in Attachments.
The process has begun.
See Image 10 in Attachments.
Step 7:- Choose "Y" and "Enter"
See Image 11 in Attachments.
The recovery firmware process is over!
Next Few Steps are Extremely Important , so follow with caution!Step 8:-Reboot into Recovery Mode(hold down "Power" and hold, as soon as the screen goes blank, hold down the second button "Volume +" - hold it until vibration and release "Power", and after it release the button "Volume +")
Step 9:-To disable encryption of the "Data" section (who installs TWRP), we immediately flash the zip archive - tool-root_unlock-Testing-Pro7.zip
(disables encryption of the "Data" section, disables Boot and Recovery checks, installs Magisk and disables system root) and reboot into the system.)
tool-root_unlock-Testing-Pro7.zip:-https://drive.google.com/open?id=1a3Gyyuoo2Jv3EN7EWPwj389tXorSwkxT
Attention ! When installing custom recovery (TWRP) on your device, for the full TWRP functionality, you should format the internal memory (Data section) of the device using TWRP itself, since the "Data" section on Meizu smartphones is encrypted, I highly recommend it before installing custom recovery , on creating backups using the internal Flyme firmware (after creating the backup, it is located in the "backup" folder of the internal drive), as well as copying all the necessary data from the phone’s internal memory to the computer!
NOTE:-No One shall be responsible to any damage ocurring to your device
Doubts and queries are welcomed .
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
XRed_CubeX said:
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
Click to expand...
Click to collapse
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
adityadhage said:
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
Click to expand...
Click to collapse
But then for other MTKs like M5C it will never work?
XRed_CubeX said:
But then for other MTKs like M5C it will never work?
Click to expand...
Click to collapse
i know you have already tried this method with your device and it didnt worked. I am not sure that m5c will get another method in future or not. Bcoz we also got lucky with pro 7 that it got successful by the help of guide ported from Meizu 16TH a Qualcomm device.
its now per donation only.
spiramedia said:
its now per donation only.
Click to expand...
Click to collapse
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
cris2d2 said:
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
Click to expand...
Click to collapse
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
adityadhage said:
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
Click to expand...
Click to collapse
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
cris2d2 said:
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
Click to expand...
Click to collapse
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
adityadhage said:
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
Click to expand...
Click to collapse
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
cris2d2 said:
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
Click to expand...
Click to collapse
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
adityadhage said:
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
Click to expand...
Click to collapse
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
cris2d2 said:
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
Click to expand...
Click to collapse
basically you are right
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
deathbreath2010 said:
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
Click to expand...
Click to collapse
this guide is now updated and guranteed to work with x30 also
follow this
https://www.youtube.com/watch?v=Rnuf-uNBnYA&t=319s
adityadhage said:
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
Click to expand...
Click to collapse
its not 5$ its now 15$ its too mutch
sajib_ngage said:
its not 5$ its now 15$ its too mutch
Click to expand...
Click to collapse
try asking them for lower price, they will help u i think. Tell them its for pro 7 bcoz pro 7 requires less work. try ur luck
I have an Asus rog phone 2 tencent version with rom WW-16.0640.1908.12, i can't update to android 10, i don't receive ota update and if i try to install ww-17 rom donwloaded from asus site i receive an error, what can be the problem?
i see that the last ww-16 update on the asus site is WW-16.0631.1910.64, my rom version isn't on the site, is it possible?
if you click the link, it will send you to ebay. clickbait detected
verioananta said:
if you click the link, it will send you to ebay. clickbait detected
Click to expand...
Click to collapse
which link?
I have exactly the same issue, with same version (I bought it via ebay).
I also tried to update android to 10 manually, but the message is "installation failed".
If you find a solution please share, I'll do the same.
bryan1981 said:
I have exactly the same issue, with same version (I bought it via ebay).
I also tried to update android to 10 manually, but the message is "installation failed".
If you find a solution please share, I'll do the same.
Click to expand...
Click to collapse
i bought it via ebay too
i think now the only possibility is to install the update in fastboot mode but I've had some problems in the past with other phones, and I wouldn't want to have any with this too
For me its showing system update failed
Solution
Hi guys,
I solved yesterday this topic and now I run Android 10.
I have followed the tutorial present in xda forum to convert from CN to WW.
Also if the release 16.0631 appear older, after you mount it you will be able to update to Android 10.
Please let me know if you need the links (also YouTube tutorial).
After you complete release installation, go to Asus official site and download the latest official version of v. 16.xxxxx update, locate on internal memory and restart phone. This update will be detected and installed.
After this step, proceed in the same way to download v. 17.xxxx (Android 10) file and install following the same procedure.
bryan1981 said:
Hi guys,
I solved yesterday this topic and now I run Android 10.
I have followed the tutorial present in xda forum to convert from CN to WW.
Also if the release 16.0631 appear older, after you mount it you will be able to update to Android 10.
Please let me know if you need the links (also YouTube tutorial).
After you complete release installation, go to Asus official site and download the latest official version of v. 16.xxxxx update, locate on internal memory and restart phone. This update will be detected and installed.
After this step, proceed in the same way to download v. 17.xxxx (Android 10) file and install following the same procedure.
Click to expand...
Click to collapse
Yes this works also for me
The mistake was trying to update directly to 10
bryan1981 said:
Hi guys,
I solved yesterday this topic and now I run Android 10.
I have followed the tutorial present in xda forum to convert from CN to WW.
Also if the release 16.0631 appear older, after you mount it you will be able to update to Android 10.
Please let me know if you need the links (also YouTube tutorial).
After you complete release installation, go to Asus official site and download the latest official version of v. 16.xxxxx update, locate on internal memory and restart phone. This update will be detected and installed.
After this step, proceed in the same way to download v. 17.xxxx (Android 10) file and install following the same procedure.
Click to expand...
Click to collapse
can you send me the tutorial link? i tried one guide but don't work for me
iAlex5 said:
can you send me the tutorial link? i tried one guide but don't work for me
Click to expand...
Click to collapse
I'm not authorized to post still link.
Go on YouTube, search the video with this name:
"Guide for Asus rog 2 tencent edition to full global rom conversion.....
Duration 24 min and 37 seconds
By: E-Got Tech
bryan1981 said:
I'm not authorized to post still link.
Go on YouTube, search the video with this name:
"Guide for Asus rog 2 tencent edition to full global rom conversion.....
Duration 24 min and 37 seconds
By: E-Got Tech
Click to expand...
Click to collapse
thanks, i will try
bryan1981 said:
I'm not authorized to post still link.
Go on YouTube, search the video with this name:
"Guide for Asus rog 2 tencent edition to full global rom conversion.....
Duration 24 min and 37 seconds
By: E-Got Tech
Click to expand...
Click to collapse
Will you loose data on your phone?
(will it wipe the phone)
Sent from my ASUS_I001DA using Tapatalk
adidasp4 said:
Will you loose data on your phone?
(will it wipe the phone)
Sent from my ASUS_I001DA using Tapatalk
Click to expand...
Click to collapse
Yes. back up online.
bryan1981 said:
I'm not authorized to post still link.
Go on YouTube, search the video with this name:
"Guide for Asus rog 2 tencent edition to full global rom conversion.....
Duration 24 min and 37 seconds
By: E-Got Tech
Click to expand...
Click to collapse
any luck? im wondering if I should do the same thing I have a tencent version I bought used on amazon running WW_16.0631.1910.44_0
can not figure a single way to update.
Nikws said:
Yes this works also for me
The mistake was trying to update directly to 10
Click to expand...
Click to collapse
This also fixed it for me. I updated to 16.0631.1910.64 then to 17.0210.2001.60-1.1.97 and it worked. Trying to update straight to 17.0210.2001.60-1.1.97 did not work (update failed). I have a tencent rog 2 with a WW fingerprint.
Go to latest android 9 THEN android 10
bryan1981 said:
Hi guys,
I solved yesterday this topic and now I run Android 10.
I have followed the tutorial present in xda forum to convert from CN to WW.
Also if the release 16.0631 appear older, after you mount it you will be able to update to Android 10.
Please let me know if you need the links (also YouTube tutorial).
After you complete release installation, go to Asus official site and download the latest official version of v. 16.xxxxx update, locate on internal memory and restart phone. This update will be detected and installed.
After this step, proceed in the same way to download v. 17.xxxx (Android 10) file and install following the same procedure.
Click to expand...
Click to collapse
Thank you very much for this, I couldn't figure out why the update kept failing. I was able to go to the latest WW 9 and now the latest WW 10:good:
Currently I am on Evolution X latest build and today my camera was opened but it won't close.
Now since my phone is under warranty I want to claim it.
How do I revert back to MIUI, unroot the device and remove TWRP. Please help me.
Regards
flash fastboot rom and u will revert back to stock miui unrooted.
^^ Do I need to download MIUI package or simply that command alone will work?
If yes please guide to resources I have Indian variant of K20 Pro.
shashpant said:
^^ Do I need to download MIUI package or simply that command alone will work?
If yes please guide to resources I have Indian variant of K20 Pro.
Click to expand...
Click to collapse
"Flash fastboot rom" was a sentence/direction/hint what you have to do, not a (fastboot) command
I think there is a detailed guide in the Guides section. Otherwise, you need to google about MiFlash, install to the PC, read how to use, find on xiaomifirmwareupdater an appropriate tgz/fastboot rom for your device.
I'm not on Pro, not on Indian, cannot guide you more than as above, where to start googling/reading/learning
^^ Thanks for the clarification.
I downloaded latest rom from https://xiaomifirmwareupdater.com/miui/raphaelin/ I tried both recovery and fastboot version.
I flashed the rom using twrp (is that right?) but nothing happens and devices reboots itsefl into recovery. What am I doing wrong?
I am also unable to locate the guide to revert back. Plus I am on Linux so that windows too might now work.
Edit - The guides mention flashing magisk. But I don't want to root as I have to claim warranty. What do I do now?
Edit 2 - I flashed magisk root but still not able to boot. It reverts back to recovery.
shashpant said:
^^ Thanks for the clarification.
I downloaded latest rom from https://xiaomifirmwareupdater.com/miui/raphaelin/ I tried both recovery and fastboot version.
I flashed the rom using twrp (is that right?) but nothing happens and devices reboots itsefl into recovery. What am I doing wrong?
I am also unable to locate the guide to revert back. Plus I am on Linux so that windows too might now work.
Edit - The guides mention flashing magisk. But I don't want to root as I have to claim warranty. What do I do now?
Click to expand...
Click to collapse
I wrote you to google about and to use Mi Flash, not TWRP.
Besides, I don't know if they have Linux version.
How to Flash Xiaomi Firmware using MIUI Fastboot and Recovery ROM
Ever since the dawn of affordable smartphones in countries like India and China, the demand for more has increased. The consumers now, more than ever, are
www.getdroidtips.com
How to Install MIUI Fastboot ROM - android file box
For some reasons you may want to completely re-install Android OS running on your Xiaomi phone either Mi series or Redmi series. While updating the ROM is simply a one-tap action through...
androidfilebox.com
How-to use Xiaomi Flash Tool to flash or install Firmware
Step-by-Step guidelines to use Xiaomi Flash Tool to Flash Stock Firmware on Xiaomi Smartphone and Tablets.
xiaomiflashtool.com
etc - google for more
shashpant said:
I am also unable to locate the guide to revert back. Plus I am on Linux so that windows too might now work.
Click to expand...
Click to collapse
Actually, consult these guides for Linux:
How to flash MIUI Fastboot ROM from Linux
How to flash MIUI Fastboot ROM from Linux. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
[GUIDE][Linux] Flashing Xiaomi .tgz
Hello everyone, I recently had to flash a stock firmware file from Xiaomi (.tgz) and being primarily a Linux user I was quite disappointed by the fact that the company only provides a flashing tool for Windows. Either way, I booted into Windows...
forum.xda-developers.com
[OTA][FASTBOOT][ROM] Official Stock Fastboot image (V10.0.10.0.PDHMIXM, Android P)
Attention: To be able to flash, the bootloader needs to be unlocked (https://en.miui.com/unlock/). Please be warned though: Xiaomi changed something in the method of unlocking the device from May 2018 security update onwards. Now all data will be...
forum.xda-developers.com
Hello,
I have a Japanese Galaxy S10+ Snapdraon branded for au
CPU-z information: model SCV42_jp_kdi - CPU Qualcomm snapdragon SM8150 8 cores - GPU Adreno 640 - Architecture Kryo 485 - screen 1080x2280 - board msnile - Brand KDDI - model SCV42_jp_kdi
Model number in About phone is SCV42
Model number on box is SM-G975
Bootloader: SCV42KDU1CUD4
Build Number RP1A200720.012.SCV42KDU1CUD4
I have found a matching bootloader here (not sure if this bootloader is needed I have not tried to flash magisk without it) - after flashing the bootloader and patching the official firmware AP with magisk and reinstalling it I get a rooted phone.
The last official rom i could find is dated 2021-04-23.
There are some suspicious sites that claim to have newer firmware that cannot be downloaded without subscribing/paying and then getting taken for a ride throughout links that lead to dead ends.
My first question is can someone who knows this exact model tell me which is the latest official firmware for it? (if available kindly share a link to it)
Edited
The reason I would like the most recent official firmware is to run linux on dex. Currently linux on dex 1.0.51 (which i believe is the last release before it was discontinued - please correct me if I am wrong on this) says it will not run without the latest updates.
Click to expand...
Click to collapse
It turned out linux on dex only runs on devices with Android 9. So a downgrade is needed instead of an upgrade
Which brings me to my second question: is there a way to know if the hardware in my S10+ model is identical to the hardware on some equivalent USA model? The CPU/GPU are the same but is the rest of the hardware the same? Should the answer be yes would it be possible to flash my device with a more recent official firmware from some USA carrier?
On gsmarena only the following model numbers are listed: SM-G975F/DS (Global); SM-G975U (USA); SM-G975W, on sammmobile SCV42 does not exist. Since the box mentioned model as being SM-G975 I am wondering if there is some naming confusion and a way to figure out which letters to add to SM-G975 to find recent matching firmware or if my model is simply not widespread enough to have received the same attention other models did.
Is there a risk of causing irreversible damage (permanent brick) by trying to upload firmware for another model (most likely candidate SM-G975U)?
My last question is about TWRP, After downloading and flashing the latest S10+ snapdragon image pointed at by the TWRP app my device could not boot. Is there TWRP image compatible with my device?
Many thanks for reading so far and any hints/help provided
how do u root your scv42? may i have the file? i use magisk but it failed
Bigboss2233 said:
how do u root your scv42? may i have the file? i use magisk but it failed
Click to expand...
Click to collapse
Simply installing magisk does not work you have to flash a "cracked rom" before (one that matches your current firmware) installing magisk. I used this one Cracked Rom for the latest available SCV42 firmware (the site requires a registration before allowing downloads).
btw thanks for the help, but i've succed to rooted my phone now using stock rom and magisk
Bigboss2233 said:
btw thanks for the help, but i've succed to rooted my phone now using stock rom and magisk
Click to expand...
Click to collapse
sorry to dig an old thread, did you manage to install an international rom on it? currently trying to get rid of the bloated carrier rom.
seb.mfuentes said:
sorry to dig an old thread, did you manage to install an international rom on it? currently trying to get rid of the bloated carrier rom.
Click to expand...
Click to collapse
On the contrary this thread is meant to attract people who want to solve the same issues. I did not try installing an international ROM (too big a task to regain all configurations and apps) , however my uninformed non expert current belief is that trying another country's ROM is not going to wreck the device. Worse case would be it will not work and official ROM will have to be reinstalled (potentially with a nand reset). I settled for using magisk debloater to hide/uninstall apps I did not want (branding on startup remains).
Here is my debloat list in case it helps: (for ROM SCV42KDU1CUD4)
Code:
debloat.import=1
ARZone^=/system/app/ARZone
DictDiotekForSec^=/system/app/DictDiotekForSec
SBrowser_13.0^=/system/app/SBrowser_13.0
FeliCaLock^=/system/app/FeliCaLock
MobileFeliCaSettingApp^=/system/app/MobileFeliCaSettingApp
FeliCaTest^=/system/app/FeliCaTest
MobileFeliCaMenuMainApp^=/system/app/MobileFeliCaMenuMainApp
MobileFeliCaClient^=/system/app/MobileFeliCaClient
JpnDioDict4^=/system/app/JpnDioDict4
SamsungTTS^=/system/app/SamsungTTS
VisionIntelligence3.7^=/system/app/VisionIntelligence3.7
LiveDrawing^=/system/app/LiveDrawing
Weather_SEP12.0^=/system/app/Weather_SEP12.0
ARDrawing^=/system/app/ARDrawing
FeliCaRemoteLockKDI^=/system/app/FeliCaRemoteLockKDI
MobileFeliCaWebPluginBoot^=/system/app/MobileFeliCaWebPluginBoot
DAAgent^=/system/app/DAAgent
KidsHome_Installer^=/system/app/KidsHome_Installer
FeliCaLockTest^=/system/app/FeliCaLockTest
MinusOnePage^=/system/app/MinusOnePage
SystemUIBixby2^=/system/priv-app/SystemUIBixby2
Routines^=/system/priv-app/Routines
KDIDisasterApp^=/system/priv-app/KDIDisasterApp
KDICarNaviSetting^=/system/priv-app/KDICarNaviSetting
KDIAuMarket^=/system/priv-app/KDIAuMarket
PaymentFramework^=/system/priv-app/PaymentFramework
UserDictionaryProvider^=/system/priv-app/UserDictionaryProvider
SamsungBilling^=/system/priv-app/SamsungBilling
SamsungCloudClient^=/system/priv-app/SamsungCloudClient
StickerFaceARAvatar^=/system/priv-app/StickerFaceARAvatar
BixbyAgentStub^=/system/priv-app/BixbyAgentStub
IpsGeofence^=/system/priv-app/IpsGeofence
SPPPushClient^=/system/priv-app/SPPPushClient
KDIAuSettingMenu^=/system/priv-app/KDIAuSettingMenu
KDIMyAu^=/system/priv-app/KDIMyAu
BixbyService^=/system/priv-app/BixbyService
MateAgent^=/system/priv-app/MateAgent
SettingsBixby^=/system/priv-app/SettingsBixby
KDIFacebookInstaller^=/system/priv-app/KDIFacebookInstaller
AREmoji^=/system/priv-app/AREmoji
KDIAuInitialSetting^=/system/priv-app/KDIAuInitialSetting
SamsungExperienceService^=/system/priv-app/SamsungExperienceService
FsDtvApp^=/system/priv-app/FsDtvApp
KDIRepairAndDeliveryService^=/system/priv-app/KDIRepairAndDeliveryService
LiveStickers^=/system/priv-app/LiveStickers
KDIFacebookServices^=/system/priv-app/KDIFacebookServices
KDIFacebookAppManager^=/system/priv-app/KDIFacebookAppManager
KDIAnshinFilter^=/system/priv-app/KDIAnshinFilter
KDIAuSelfcare^=/system/priv-app/KDIAuSelfcare
KDIDataStorageApp^=/system/priv-app/KDIDataStorageApp
KDIAuWifiConnection^=/system/priv-app/KDIAuWifiConnection
KDIRemoteSupportService^=/system/priv-app/KDIRemoteSupportService
SendHelpMessage^=/system/priv-app/SendHelpMessage
techguru97 said:
currently am in SCV-42 s10+ au model android 12 ,i want to flash global rom to remove japan au bloatwares as am not in japan anymore. Is it possible?
Click to expand...
Click to collapse
Yes it is possible. I have the same model running android 11 rooted and unbloated. android 12 should be the same. I have found the rooted boot loader for my model here:
SCV42 U1 Android 12 ROOT (SCV42KDU1DVE4).tar | Halab Tech Support
support.halabtech.com
This is just to download a rooted firmware boot section
For the whole rooting guide you will need to find one on this forum. (the one i used installed magisk)