To start this journal I will begin by stating, I am not actually sure if it will be possible to finish this journal; from what I have read there can be quite a number of obstacles with international versions of the OPPO, some of which can be quite troublesome, but I thought it would be an interesting and hopefully helpful (for my self and anyone else wanting to do the same) way of going through the process with such a modern device.
The device arrives tomorrow, I wanted to get the initial post in without knowing precise details about the device.
I will update this primary post with the journal entries and post into the main thread when I update it going forwards
-- Entry 1 29/01/2022 00:21 (Dellivery today at some point!)
So far I have found out that cpw means car phone warehouse, which used(still is?) a store in the uk, 'EE' a network provider in the UK releases of the Oppo x3 find pro are apparently identical to releases from this store.
I have asked the user who informed me of this if they could possible put any information they are aware of within this thread.
Also, I will be doing the unboxing and initial looking at what it is via youtube I hope this is ok? I could not see a way to embed video onto this platform!
-- Entry 2 29/01/2022 10:53 (Delivery)
This is just a few images of the arrived device, simply unboxed and put on charge nothing has been set on the device what so ever.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also note that this image showing the build number is by @alvydas it is not from my device yet! just some more information to add to the journal, this is believed to be the same as mine should show later on when I decide to video/start the phone up
Also for note the CPH (Possible related to CarPhoneWarehouse) prefix in the build number)
-- Entry 3 29/01/2022 13:11 (Turning on, Bootloader unlock, USB Debugging enabled)
Youtube video:
- May still be processing the HD version in google HQ!
-- Entry 4 30/01/2022 10:53 (Getting sorted)
Ok so we can't root it and we can't change the boot laoder .... however we can get novo launcher to start by default! The pro version at least!
Not exactly an amazing feat but hey its progress, I also removed the gmail mail application as I preffer outlook (mainly because I have 3 email accounts):
And boy .... you can really remove everything including:
130|OP4F57L1:/ $ pm uninstall --user 0 com.oppo.launcher
The coloros launcher its self X_X, so it seems you cannot get root, but there is no protected package, you can remove ANYTHING.
so this bodes the question .... other than wanting lineage OS of course, how thin can we get it ....
-- Entry 3 10/02/2022 10:53 (Hackery and cleaning)
.... So there is no fastboot on the international model, it is simply not there I even got EE them self to confirm this.
However, I have made some progress in discovering a way to get to the qualcomm flashable download mode, that is it will show up as a:
One of those (if you have the Qualcomm drivers installed), some information I put in the forum about this mode was this:
1) Turn the phone off (shutdown)
2) Hold the power button and the Vol up/down (I Forget which) down all the way through the phone starting, you will feel a little Bzzzzz
3) you will be presented with a menu probably in chinese, this is because you held down the power button and it auto selected the first language (its not a biggie), just press the back touch screen button in the top left <--
4) Select english (or chinese if you preffer!)
5) you will be presented with a menu that has 3 options, Format, Reboot, .... something else ...
6) Select none of the options! look to the bottom of the screen you will see a version mine was v12 o3 v1.2 - double tap this
7) you will get a warning you are entering 'customer service mode', and wallah .... you will get the device show up in device manager.
I was going to shoot a video of this, I still might! but its rather redundant at this point as I am now at a brick wall, I need to figure out how to deal with this mode, can I flash something to it .... how?
I am scrubbing the phone of all the bloatware I can and to be honest I have it pretty damn clean .... but still the fastmode is elusive and what else could be loaded onto this lovely phone.
Entry 1 added - nothing really important
Entry 2 added, initial unboxing simply for charging, video to come soon: looking for details!
The CPW in the build number is more of a guess than anything else we all could be wrong
alvydasd2 said:
The CPW in the build number is more of a guess than anything else we all could be wrong
Click to expand...
Click to collapse
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.
PaulGWebster said:
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.
Click to expand...
Click to collapse
Yh that's fine
Entry 3 uploaded, many thanks @alvydasd2 We do have slightly different builds it seems!
So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this
Also have to figure out if all the fancy camera things will work with a custom rom, such as the microscope mode and all the advanced functionalities
Maybe the best initial tangent is to simply root the phone and remove any bloatware as well as installing novolauncher, followed by re-rooting it
That way I will not lose the ability to use the special camera functions and in turn still receive updates, I believe I can actually freeze certain packages too so they are effectively immutable, so they show up but can never run or be changed ... hmmm
PaulGWebster said:
So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this
Click to expand...
Click to collapse
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle
alvydasd2 said:
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle
Click to expand...
Click to collapse
Check the youtube video, I appear to have lol ... though I did notice that going into the recovery menu is all in chinese ... so I assume its the chinese version:
The only problem being ... I have no idea idea what this menu says -_-
I guess that is tomorrows episode though, connecting it via ADB+TWRP
Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that
alvydasd2 said:
Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that
Click to expand...
Click to collapse
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options
PaulGWebster said:
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options
Click to expand...
Click to collapse
Oppo has a weird bootloader cuz it can only be unlocked with an app that only works on Chinese version and to access fastboot u need a unlocked bootloader
just read this .... so there is no way to even fastboot the device https://forum.xda-developers.com/t/...access-for-oppo-phones-starting-2016.3348114/
I wonder if you could flash on the chinese version of the firmware
it seems that the device is really a 'realme gt 5g' .... trying to verify this
PaulGWebster said:
it seems that the device is really a 'realme gt 5g' .... trying to verify this
Click to expand...
Click to collapse
It's not -_-
Related
can someone help? i want to update tot he 4.0 but i need to relock my bootloader to have it work. i dont know how since im pretty noob at this
Provided u still have the folder u used to unlock, boot ur phone into fastboot (vol dn + power) connect it to ur pc with a USB cable, then from the command prompt in the folder where fastboot.exe is, type: "fastboot oem lock" without the quotations. Good luck!
Sent from my HTC Raider X710e using xda premium
ah damn i dont think istill have it
is there another way?
oh nvm i think i do i have it i just need to look for it
thank u so much haha im so happy right now
i have one more question when i did it it said this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so idk if it worked
i tired to update and it still didnt work
anyone have a copy of this fastboot.exe file..
i dont seem to have it anymore.. need to relock also so i can install the file.
---------- Post added at 01:55 AM ---------- Previous post was at 01:27 AM ----------
an4564 said:
i have one more question when i did it it said this
so idk if it worked
i tired to update and it still didnt work
Click to expand...
Click to collapse
Mine just did the same thing...
---------- Post added at 02:01 AM ---------- Previous post was at 01:55 AM ----------
OK, so i went back in to try again, came up saying its locked..
lets see how it go's.
i tired it a few times idk if its gonna work
mine comes up saying locked now, but when i go to install it powers down and then go's into the bootloader.. hmmm
i still havent seen the update yet
i tired it a bunch of times and nothing ever comes up
you need to be more thorough with your explanation of what point you are at and what you are trying to achieve.
an4564, what device do you have, what network are you on, and what exactly are you attempting to achieve, what does "nothing ever comes up" mean to the rest of us who are not mind readers
If you get your bootloader locked just go get the RUU Download and install the ICS Update.Its simple and painless.The directions below.Credit goes to Pirate Ghost,WildChild,Chall80 for the easy directions and whomever else was involved for making this early update possible.All credit goes to them.Im not an any way taking credit but just passing along this info.Enjoy
Originally Posted by Chall80
Ok, so here we go....
First, go to this link and download the RUU(Rom Upgrade Utility) http://goo-inside.me/devs/pirateghost/vivid/RUU/RUU_HOLIDAY_ICS_35_S_CINGULAR_3.26.502.52.zip
Second, you need to use HTC Sync to sync any data that you want saved.
Third, you need to connect your device to your computer, and set it to "charge only". You need to make sure that you have "USB Debugging Enabled".
From the Home screen, press the Menu key.
Tap Settings.
Tap Applications.
Tap Development
Tap to check USB debugging.
Once you've enabled USB Debugging, and connected your device using the "charge only" setting, Double click the RUU file.
From that point on, it will prompt you for a couple things, but there are no options or choices to make. Its bulletproof.
THIS OPERATION WILL COMPLETELY WIPE YOUR ONBOARD DATA, AND RETURN YOUR PHONE TO "OUT OF BOX" CONDITION. It will have Android 4.0.3, and Sense 3.6
This is an AT&T release and does not void your warranty, unlock your bootloader, gain access to the root folder, or remove AT&T bloatware. This is perfectly legit for those who don't wish to mess with root. An RUU is the manufacturers method for upgrading phones.
I have screenshots, and just don't wanna mess with uploading them(too much of a pain). If you wanna see them, PM me and I'll email them to you.
This is painless and so worth it!!!
EDIT: This does not wipe your SD Card
i have the htc vivid for AT&T and am trying to get the ics update. i relocked my bootloader and typed in the *#*#682#*#* code and waited for the notification to come up but it never does. i have tired it multiple times
woodsytattooman said:
If you get your bootloader locked just go get the RUU Download and install the ICS Update.Its simple and painless.The directions below.Credit goes to Pirate Ghost,WildChild,Chall80 for the easy directions and whomever else was involved for making this early update possible.All credit goes to them.Im not an any way taking credit but just passing along this info.Enjoy
Originally Posted by Chall80
Ok, so here we go....
First, go to this link and download the RUU(Rom Upgrade Utility) http://goo-inside.me/devs/pirateghost/vivid/RUU/RUU_HOLIDAY_ICS_35_S_CINGULAR_3.26.502.52.zip
Second, you need to use HTC Sync to sync any data that you want saved.
Third, you need to connect your device to your computer, and set it to "charge only". You need to make sure that you have "USB Debugging Enabled".
From the Home screen, press the Menu key.
Tap Settings.
Tap Applications.
Tap Development
Tap to check USB debugging.
Once you've enabled USB Debugging, and connected your device using the "charge only" setting, Double click the RUU file.
From that point on, it will prompt you for a couple things, but there are no options or choices to make. Its bulletproof.
THIS OPERATION WILL COMPLETELY WIPE YOUR ONBOARD DATA, AND RETURN YOUR PHONE TO "OUT OF BOX" CONDITION. It will have Android 4.0.3, and Sense 3.6
This is an AT&T release and does not void your warranty, unlock your bootloader, gain access to the root folder, or remove AT&T bloatware. This is perfectly legit for those who don't wish to mess with root. An RUU is the manufacturers method for upgrading phones.
I have screenshots, and just don't wanna mess with uploading them(too much of a pain). If you wanna see them, PM me and I'll email them to you.
This is painless and so worth it!!!
EDIT: This does not wipe your SD Card
Click to expand...
Click to collapse
oh is this the update that was put out today?
an4564 said:
oh is this the update that was put out today?
Click to expand...
Click to collapse
No it is not. I don't know if there is a RUU for the newest ics.
davidcampbell said:
you need to be more thorough with your explanation of what point you are at and what you are trying to achieve.
Click to expand...
Click to collapse
i am trying to update my Velocity with the OTA ICS update, i relocked the bootloader, restarted the phone, initiated the install, it gets to the point of restarting and instead of starting the install Fastboot comes up..
Dear, Since I only support Arabic, I will present the necessary files with the pictures
This Files Only For: Lenovo Z6 Pro L78051
Settings > About phone > Technical details > Model > Lenovo L78051
You Can use | Tool All In One | to Force your Device go to Edl
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Files:
Lenovo Z6 Pro L78051 ROM ZUI 11.0.483
Note:
No Need > Unlock the bootloader
https://www.zui.com/iunlock
Thanks. global rom ??
this is the chinese version with no google play but fixed bugs and real benchmark scores close to the top , for me it was easy to remove the bloatwares and install playstore and my apps
i ve already put negative review on the aliexpress seller who provided a hybrid rom claiming this to be a global release....
Guide for Lenovo Z6 Pro CH/ENG ROM flash (BIG PERFORMANCE BOOST COMPARED TO GLOBAL RO
First of all, some info
Okay guys, I’ve been struggling with this a few hours myself. I am by no means a professional. I think it’s safe to say I’m an amateur who had messed around with Android phones in the past.
As all of you may have noticed; the graphical performance and actually the general performance of the global ROM is really horrible for the Lenovo Z6 Pro. I couldn’t live with the fact that my benchmarks sucked and I felt like my phone wasn’t providing its full potential. After opening an official Lenovo forum some amazing people from the community pointed me in the right direction. Thanks Chaina and PcM_2019 for your amazing input!
The reason for this bad performance has to do with the Global ROM itself. It’s simply poorly optimized right now and receives barely any updates. I expect that in the future it will receive updates accordingly but as of right now it’s better to move over to the Chinese / English ROM.
Keep in mind there will be some Chinese apps and no Google Play in this ROM. You can add Google Play and delete most of the apps in case you’d like it better that way.
Time for the tutorial
MAKE SURE TO BACKUP ALL YOUR DATA, THIS IS A TUTORIAL FOR FLASHING DIFFERENT FIRMWARE FOR YOUR DEVICE AND IT WILL RESULT IN LOSING ALL YOUR DATA. Backup all data you wish to keep. Of course I cannot be held responsible for the loss of your data.
You will need a windows computer and a USB-C data cable.
1) Get all the required software for flashing your device to the preferred ROM.
a. First of all, the ROM itself. Because URL’s are not allowed, look on mirrors.lolinet under firmware for Lenovo L78051. It’s about a 3GB file.
b. Secondly; Qualcomm HS-USB driver.exe Boycracked has in his portfolio a a link to the Qualcomm usb driver. Google for it.
c. Lastly; the Qualcomm Flash Image Loader (QFil)
i. Androidbrick lists the latest Qualcomm flasher qfil gpst 2.7.460. Download this one!
2) We start off with the ROM. It’s a ZIP file, get 7zip or other archiving software to extract it.
3) Install the HS-USB driver – keep pressing next, don’t change anything.
4) Exctract and Install QFil. After the installation you can find the program in start by searching for “QFil”.
5) Place the extracted ROM folder in the following installation path of QFil for avoiding potential issues in the flashing process. The path should be: C:\Program Files (x86)\Qualcomm\QPST\bin. Just drop the entire folder in the bin.
6) You’re now ready for the real deal. Time to flash your device! Open QFil (search QFil in start) and follow these steps.
a. Open the configuration tab, click Firehose configuration and change device type from eMMC to UFS. Also “turn Reset After Download” on. Now press “OK”.
b. Now click “load content” Navigate to the path where you placed the new firmware, the path should be: C:\Program Files (x86)\Qualcomm\QPST\bin\L78051_CN_SECURE_USER_Q00745.01_P_ZUI_11.0.483_ST_190511_qpst and open the XML document “contents”. After this the Programmer path should be automatically filled in.
c. Now open developer options on your phone and turn on USB debugging and OEM unlocking. Change default USB configuration to File Transfer.
d. After this you can turn off your phone. When the phone is turned down completely we will now boot it into flash mode. Hold down the two volume buttons together and plug-in your USB-C data cable which is connected to your PC. QFil should now recognize your device as a COM port. The port should be automatically selected. If that’s not the case, then select port manually. You can now press the blue “Download Content” button.
e. That’s it. Your phone should now be flashed with your selected firmware.
Troubleshooting
If you were to run into problems, don’t worry you can always boot your phone normally again by holding down the power button for 10 seconds after having entered the flash mode. No damage will be done.
If QFIL gives Sahara error, go to device manager and update your COMM port drivers. Let Windows select the correct drivers automatically. Enter flash mode again and try the procedure again.
If it turns out the Sahara error is not fixed after a few attempts you could save a lot of time by using another computer, install everything on there again by following this tutorial and try it again.
If something is unclear, or you keep running into problems, let me know and I’ll try to help you to the best of my ability.
Special credits to Chaina
Additional sources that helped me put this tutorial together:
Boycracked
Mirrors.lolinet
Androidbrick
Has anyone figured out, how to fix google assistant issue in chinese rom? (default assist app is switchnig to none after deepsleep or kill process button) Turning off battery optimization or giving more permissions for google home or google services did not help.
China Official
opened a dispute with seller on aliexpress claiming the sale version as global and here is their joke answer here is no actual comparability between the evaluation software and the actual use. It is subject to actual usage. and The global version refers to language packs and channels. if i win i will take back 30usd as this amount i asked back open up all of you the same dispute , we must not tolerate this attitude and lies....
hello to all , how about twrp for this z6 pro ???
i need it bad .
thanks
help please .
i have unlocked bootloader and the global rom provided by phone seller has crashed , i have installed cn rom but no google play and my job depends on playstore apk's.
so please help with global rom for qfill or twrp and a backup of the global rom
here is the latest , i think
L78051_CN_SECURE_USER_Q00745.01_P_ZUI_11.0.542_ST_190610_qpst
https://drive.google.com/open?id=1r2oqL0jrFWO9MDMGMA6J0D-Jxd5rWryx
Background Services Off
Hi all
Firstly thanks for your efforts above! Tut was good and info too.
Since upgrading I received 2x ZUI updates and am now on the newest version.
I'm having so many problems now, my phone is a borderline frisbee!
Managed to install Google apps via Aptoide easy enough and now have everything installed.
Problem I'm having is: when closing apps; they don't run in background which means, WhatsApp's emails, etc. don't come through unless you go into the app. Secondly the settings do not save, so as mentioned above, setting the assistant also changing keyboard etc.
Does anyone know a fix? Is it worth reverting back/updating to the newest global ROM?
Please help!
Thanks
dnick88 said:
Hi all
Firstly thanks for your efforts above! Tut was good and info too.
Since upgrading I received 2x ZUI updates and am now on the newest version.
I'm having so many problems now, my phone is a borderline frisbee!
Managed to install Google apps via Aptoide easy enough and now have everything installed.
Problem I'm having is: when closing apps; they don't run in background which means, WhatsApp's emails, etc. don't come through unless you go into the app. Secondly the settings do not save, so as mentioned above, setting the assistant also changing keyboard etc.
Does anyone know a fix? Is it worth reverting back/updating to the newest global ROM?
Please help!
Thanks
Click to expand...
Click to collapse
You Need to Lock the app
Multitask button box / Lock the app
nakarmkir69 said:
help please .
i have unlocked bootloader and the global rom provided by phone seller has crashed , i have installed cn rom but no google play and my job depends on playstore apk's.
so please help with global rom for qfill or twrp and a backup of the global rom
Click to expand...
Click to collapse
Lock The boot then use this rom or another one
XQ55 said:
Lock The boot then use this rom or another one
Click to expand...
Click to collapse
Thanks for the idea, i have allready installed the latest(the one that i have posted the gdrive link above) without locking the bootloader, all the commands to lock the bootloader do not work.
The phone is working but no google play that is mandatory to install apk's from store
nakarmkir69 said:
Thanks for the idea, i have allready installed the latest(the one that i have posted the gdrive link above) without locking the bootloader, all the commands to lock the bootloader do not work.
The phone is working but no google play that is mandatory to install apk's from store
Click to expand...
Click to collapse
https://mega.nz/#F!WnIASagK!_EZg03ccDdH_BJz0EbvdbQ
XQ55 said:
https://mega.nz/#F!WnIASagK!_EZg03ccDdH_BJz0EbvdbQ
Click to expand...
Click to collapse
Thanks a lot , got all done .
Please help me to get rid of the China default apk's.
Those that are system apk's and maybe how to lock the bootloader.
On Chinese ROM, does everyone experience battery drain? Think I've gone from 35 hours to 12 now
dnick88 said:
On Chinese ROM, does everyone experience battery drain? Think I've gone from 35 hours to 12 now
Click to expand...
Click to collapse
No drain with zui i am looking for global rom "the fake one" as some people call him
Same, I went from global version 11.0.054 ST to the newest CN version 11.0.575 ST and am having so many issues:
No push notifications, unless apps left open
No location on most apps including Google maps
Battery drain
Settings do not save
On the up side, camera quality and performance is now what I paid for!
I'm hoping I can track down a global ROM newer than .054 but seems impossible at the moment..
XQ55 said:
https://mega.nz/#F!WnIASagK!_EZg03ccDdH_BJz0EbvdbQ
Click to expand...
Click to collapse
I have found some problems on zui :
Whatsapp does not notify with sound , only with popup
System default phone apk does not initiate call when touch call from recents or contacts , just increase the number of calls made.if i insert the number manually it make the call just perfect
---------- Post added at 11:01 AM ---------- Previous post was at 10:56 AM ----------
dnick88 said:
Same, I went from global version 11.0.054 ST to the newest CN version 11.0.575 ST and am having so many issues:
No push notifications, unless apps left open
No location on most apps including Google maps
Battery drain
Settings do not save
On the up side, camera quality and performance is now what I paid for!
I'm hoping I can track down a global ROM newer than .054 but seems impossible at the moment..
Click to expand...
Click to collapse
New phone new problems , i just hope that twrp and lineage or mokee will appear soon, for me is the best way allso was the stock global rom that the phone had installed when arrive but it seems that nobody have it.
Maybe someone will have it and posted here
How to Bootloader Unlock (Part 1 of 2):
1. You will need a USB A to USB A cable (Example here)
2. You will need fastboot drivers on your PC
3. Unplug your clock
4. Plug the USB A to A cable into your computer and clock
5. Hold the volume + button and plug in the power cord
6. Keep holding volume + for about 20-30 seconds (It is slow to boot to fastboot)
7. On your computer in a terminal run, fastboot flashing unlock
Part 1 of unlocking is now done
AVB/DM-Verity Unlock (Part 2 of 2)
Unlocking the bootloader really does not give a lot to us because all the partitions are still being verified and the device will not boot if they don't match. Normally doing this on an Android Things device is not possible due to their Private key unlock system. But due to a leak, the private key for the Lenovo Smart Clock is available. Word of warning doing this causes the stock android things not to boot only the factory firmware located on Slot A will boot. Consistently if you don't AVB unlock the factory firmware on Slot A doesn't boot If you have already set up your device once the factory firmware is deleted and currently there is not a way to get it back (Hopefully will change soon).
If you are coming from part 1 you can start right away, if not you need to reboot to fastboot again.
1. Extract the downloaded AVB Unlock zip
2. Run this command in terminal
Code:
at_auth_unlock.exe cube_unlock_credentials_v2.zip
3. Wait till it finishes
4. Keep in mind the stock system does not boot properly with AVB off (It is weird some UI elements work but the boot animation never goes away)
5. To relock AVB in the future run the following command:
Code:
fastboot oem at-lock-vboot!
Downloads:
Stock Shipping fastboot firmware:
Here
AVB Unlock tool:
Here
Factory partition changer (Locale changer):
Here
Google released kernel source:
https://github.com/deadman96385/android_kernel_lenovo_mt8167s
Dump of stock partitions for easy viewing:
https://github.com/deadman96385/things_mt8167s_som_dump
Credit to @deletescape for the leak of the AVB Unlock Key, Stock firmware, region changer
Screenshots of the stock android things on Slot A if you don't setup the device :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP (Coming Soon)
Excited to see what you manage to do with this!
This is great! I have one of these and it felt way too restrictive, looking forward to seeing what comes out of this.
You can also unlock the boot loader simply with what's below... device does boot with this btw
fastboot flashing unlock
Although I've been messing with the device quite a bit. Plug in a usb keyboard, and you can get a web browser to recognize it and go to websites and such using the touch screen as a cursor, but you can't download APK files and install them and such. I've NEVER had the device recognized by ADB, so I can't pass commands from there either.
KaptinBoxxi said:
You can also unlock the boot loader simply with what's below... device does boot with this btw
fastboot flashing unlock
Although I've been messing with the device quite a bit. Plug in a usb keyboard, and you can get a web browser to recognize it and go to websites and such using the touch screen as a cursor, but you can't download APK files and install them and such. I've NEVER had the device recognized by ADB, so I can't pass commands from there either.
Click to expand...
Click to collapse
Just doing step one does not actually get you anything because if you flash something that isn't stock on the verified partitions it will not boot until you flash back the stock one. I have gotten adb to show up but not properly so it is offline. Still hacking away at it trying to get it to go so i can more easily debug TWRP and make edits to the system.
deadman96385 said:
Just doing step one does not actually get you anything because if you flash something that isn't stock on the verified partitions it will not boot until you flash back the stock one. I have gotten adb to show up but not properly so it is offline. Still hacking away at it trying to get it to go so i can more easily debug TWRP and make edits to the system.
Click to expand...
Click to collapse
Ahhhhh got it. I couldn't find anything when I was messing with it like you've found with those commands. I'm kinda new to all this myself at something with nearly zero support, although I have a ton of experience with phones. Had to find my own exploit with my HTC One M7 because the version of android on the phone was the final supported update when I got it, and everyone said "nothing is possible with this android version" as far as rooting... so I figured out my own way lol
I'll continue trying myself though for sure
I also own one of these clocks, so if anyone has anything that I could test out, please share!
I think I'm bit late to party. Anyone who has a backup for those lenovo products, maybe it's a good idea to torrent them.
Honami754 said:
I think I'm bit late to party. Anyone who has a backup for those lenovo products, maybe it's a good idea to torrent them.
Click to expand...
Click to collapse
I don't have the time to test this stuff out for at least a few weeks, but if when I get to it, I'll try to upload my Backups somewhere before I tinker with the system. I'll update this comment when I do.
[/COLOR]
CiriousJoker said:
I don't have the time to test this stuff out for at least a few weeks, but if when I get to it, I'll try to upload my Backups somewhere before I tinker with the system. I'll update this comment when I do.
Click to expand...
Click to collapse
That's not really what I mean... I was referring to some interesting documents from lenovo. Have a few of those hardware but unfortunately didn't grab those files. Anyone also interested in these can PM me maybe we can do something about it.
when will twrp be avable
Interesting as there has a been a few of these turn up to auction of late .
I have gone with the 10' for main room and 8' for bedroom.. love them..
Got the oldies the little 7'
Great for streaming too..
The one I wish it did was announce the time by voice when the internet was down and we said "Hey Google". I am blind without my glasses and often when I am in bed, the internet is down in my area for maintenance period. The clock becomes useless when the internet goes down.
How are people getting the web browser to appear? I'm able to unlock the bootloader but can not boot with the AVB unlocked (well...technically it boots but still shows the spinning circle even though it will let you go to settings). I tried flashing the stock fastboot img and booting with avb unlocked and still get spinning circle. Not trying to get too fancy with this...just want to be able to point to a status page that I can leave it on.
Does anyone try to build a new firmware image and install this instead of stock?
Maybe compiling Android Things from source is possible, but looks like Google has stopped the development. The Lenovo Smart Frame seems to have the same MT8167S and runs on Android 10. Maybe it's possible to compile a LineageOS version?
lenovo.com/us/en/coming-soon/Lenovo-CD-3L501/p/ZZISZSDCD04
Another option might be fuchsia that contains a mt8167s board ref.
fuchsia.googlesource.com/fuchsia/+/master/boards/mt8167s_ref.gni
Googles Coral announced a Dev Board Mini based on MT8167s, maybe they port the Debian-based Mendel Linux to it.
coral.ai/products/dev-board-mini
hugo987 said:
Does anyone try to build a new firmware image and install this instead of stock?
Maybe compiling Android Things from source is possible, but looks like Google has stopped the development. The Lenovo Smart Frame seems to have the same MT8167S and runs on Android 10. Maybe it's possible to compile a LineageOS version?
lenovo.com/us/en/coming-soon/Lenovo-CD-3L501/p/ZZISZSDCD04
Another option might be fuchsia that contains a mt8167s board ref.
fuchsia.googlesource.com/fuchsia/+/master/boards/mt8167s_ref.gni
Googles Coral announced a Dev Board Mini based on MT8167s, maybe they port the Debian-based Mendel Linux to it.
coral.ai/products/dev-board-mini
Click to expand...
Click to collapse
I suppose the smart frame is running android things as well. Compiling android things does make much sense except to prove the drivers are sort of working, this is not designed to let users have fun (ie installing apps).
Google *really* loves mt8167s for some reason. I'd say there's a good chance of we having full android on it but everyone's busy.
They are throwing these things at our head now. 35/40 USD during black fridays.
I don't think you can order the components for that price
Anybody still working on it ? Lenovo claims it's still working on the sound bug - hxxps :// forums.lenovo.com/t5/Lenovo-Smart-Display-Lenovo-Smart-Clock-with-Google-Assistant/Smart-clock-alarm-volume-too-loud-at-first/m-p/5040962?page=4 (latest reply 2020-13-11 from Lenovo) and they did some unanounced pretty good updates in september 2020 - hxxps :// 9to5google.com/2020/09/21/lenovo-smart-clock-night-light/
They also claim the source is on their website hxxps :// smartsupport.lenovo.com/us/en/products/smart/smart-home/smart-clock/za4r/downloads/ds539701
So is this dead ?
deadman96385 said:
How to Bootloader Unlock (Part 1 of 2):
1. You will need a USB A to USB A cable (Example here)
2. You will need fastboot drivers on your PC
3. Unplug your clock
4. Plug the USB A to A cable into your computer and clock
5. Hold the volume + button and plug in the power cord
6. Keep holding volume + for about 20-30 seconds (It is slow to boot to fastboot)
7. On your computer in a terminal run, fastboot flashing unlock
Part 1 of unlocking is now done
AVB/DM-Verity Unlock (Part 2 of 2)
Unlocking the bootloader really does not give a lot to us because all the partitions are still being verified and the device will not boot if they don't match. Normally doing this on an Android Things device is not possible due to their Private key unlock system. But due to a leak, the private key for the Lenovo Smart Clock is available. Word of warning doing this causes the stock android things not to boot only the factory firmware located on Slot A will boot. Consistently if you don't AVB unlock the factory firmware on Slot A doesn't boot If you have already set up your device once the factory firmware is deleted and currently there is not a way to get it back (Hopefully will change soon).
If you are coming from part 1 you can start right away, if not you need to reboot to fastboot again.
1. Extract the downloaded AVB Unlock zip
2. Run this command in terminal
Code:
at_auth_unlock.exe cube_unlock_credentials_v2.zip
3. Wait till it finishes
4. Keep in mind the stock system does not boot properly with AVB off (It is weird some UI elements work but the boot animation never goes away)
5. To relock AVB in the future run the following command:
Code:
fastboot oem at-lock-vboot!
Locale changer instructions:
Coming soon (Need to figure it out)
Downloads:
Stock Shipping fastboot firmware:
Here
AVB Unlock tool:
Here
Factory partition changer (Locale changer):
Here
Google released kernel source:
https://github.com/deadman96385/android_kernel_lenovo_mt8167s
Dump of stock partitions for easy viewing:
https://github.com/deadman96385/things_mt8167s_som_dump
Credit to @deletescape for the leak of the AVB Unlock Key, Stock firmware, region changer
Click to expand...
Click to collapse
how about smart display ,the same way?
jasonzhang1987 said:
how about smart display ,the same way?
Click to expand...
Click to collapse
We do not have the AVB unlock files for the smart displays sadly.
USE UPDATED POST, HERE!
THIS POST IS NOW ONLY REFERENCE ONLY - WILL BE DELETED SOON.
Well I figured I'd make a quick How-To on how I successfully Carrier/Sim unlocked my Samsung Galaxy S21 Ultra 5G running the NEWEST Android update on bootloader 5 (USQU5BULJ)released in January of 2022.
***This does NOT trip Know and does NOT require a root or a paid service. ***
****Also Note - This is the process I took, you may find some of these steps are not needed but for the purpose or recreating my results, I'll be posting my exact process.
****This has ONLY BEEN TESTED ON SNAPDRAGON BASED SAMSUNG GALAXY S21 ULTRA 5G SM-G998 U & U1, if you try it on a different model or phone you may (and likely will) receive different results!!!!
Here's what you'll need:
•ANY (activated or not) Sim from the carrier you wish to switch too.(or a way to replicate the carriers cert from one)
•A computer
•Patched Odin
•BOTH the NEWEST U & U1 ROMs/Firmware - theres a full post on these and how to flash them here on XDA (Reminder for myself or mod to link it) or visit SamFW.com, it has both Odin and the ROM/Firmware files you will need.
•Android ADB platform tools (You can find them on the official Android Developers page here or use any ADB software of your choice, fastboot is not required or used in this process.(Google "Android Developer Platform Tools" to get them from the official Android devs page. )
STEP 1:
So let's presume you have a Verizon or T-Mobile carrier locked phone, if you look at your baseband, which you can find in Settings > About > Software Info, you should see this "SM-G998Uxxxxxxx"
*****IF YOU SEE "SM-G998U1xxxxxxx" STOP - Skip to step 2******
Head over to your preferred site to get stock Samsung Roms (Refer to link above if you don't know where to find) and download the U1 XAA rom and the U rom of the CARRIER YOU WISH TO USE. IMPORTANT! MAKE SURE YOU DOWNLOAD THE "U" ROM FOR BOTH THE CARRIER YOU WISH TO SWITCH TO AND THE U1 UNLOCKED ROM.
Put you device in download mode (Hold Vol up and Vol down and plug in the USB, which should be connected to your PC and now your phone at this point.)
Flash the U1 XAA Rom, place appropriate files in appropriate places in Odin, when you get to CSC, DO NOT use the "HOME_CSC" use the other.
Leave the rest of Odin settings alone and hit Start, wait for it to finish and reboot.
Step 2:
Once the phone boots, return to Settings>About>Software and confirm you are using the XAA rom by looking at Service Provider Software Version and it should say something like "SM-G998U1_XAA blah blah blah" you just want to see the U1 and XAA.
Now put in the Sim from the carrier you desire. A pop-up should appear prompting you to restart your device. Follow the prompt.
!MOST IMPORTANT STEP!
BEFORE the device fully restarts, force it into RECOVERY MODE, I was able to achieve this by holding the power and Vol Down buttons at the same time, starting to hold the directly after the "Samsung" Logo fades away upon initial restart. If you have trouble getting into recovery please comment below.
Once in recovery, use the volume keys to navigate to "Clear Cache" select and execute. Now go to Factory Data Reset/Wipe, select and execute. It should be the option directly above "Clear cache".
Once done, go up to "Reboot to Bootloader", Select, Execute.
AGAIN, Very Important step,you MUST interrupt the boot process again and force the phone BACK into download mode this time, so once the phone attempts to reboot, you need to hold the Vol Down and Vol Up buttons at the same time and the USB MUST be already plugged in.
We should now be back in download mode and be on the U1 rom. We have verified all of this in the steps above.
STEP 3:
Now it's time to flash the ROM from the carrier you wish to use. Make SURE you have a Sim from that carrier inserted during this process. It doesn't need to be a working or activated Sim, just simply one from the carrier you wish to have your S21 work on.
Flash all items as you did earlier, but using the "U" ROM for your desired carrier as described above. Same deal with CSC, DO NOT use the "Home_CSC"
BE SURE that you use the USERDATA file if there is one for your carrier. Very important to have the phone working properly.
Start the Odin flashing process.
Phone will Auto-Reboot.
Done!
You should now be on the carrier you wish to use. This can be (in theory, test at own risk) replicated for ANY carrier supported by Samsung, and, I should soon find out if it will lead to what my original goal was, a bootloader unlock on the QualComm SnapDragon variant of the S21 and future Galaxy devices.
If you have any issues please comment below.
PoC, results after doing above process.
Good luck.
-k0mrade
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There are some parts of my tutorial that are not well expressed and may be misleading. Please don't hesitate to post in comments if you need clarity.
IMPORTANT!!! I LEFT OUT ONE MAJOR STEP! ************ ----- BETWEEN STEP ONE AND STEP 2 - After you do the factory data reset/Wipe cache -> reboot to Bootloader -> force into download, you need to flash the U1 rom BEFORE putting in your desirced carriers SIM, then reboot, let phone fully boot, THEN insert your desired carriers SIM -> restart phone-> interrupt boot by forcing into recovery and repeat factory data wipe and cache wipe and reboot bootloader -> interrupt Boot Process again, but into Download Mode -> Flash your desired "U" carrier Firmware (must be same carrier as the SIM you put in as described above). -> Done.
And when/where does one need to use the required ADB-Tools?
tested and work only on S21 ULTRA 5G SM-G998 U & U1
thank you
OnnoJ said:
And when/where does one need to use the required ADB-Tools?
Click to expand...
Click to collapse
Lol this is likely one of those steps thats unneeded. i cant remeber off the top of my head why exactly i added that in. But it wont hurt to have the drivers, thats for sure.
Ive made a (Slightly) more clear post, hopefully better detailing this, Here. Mods may close this thread as they feel free but i will leave it up as a resource for the time being.
How many different devices have you tested this on?
iBowToAndroid said:
How many different devices have you tested this on?
Click to expand...
Click to collapse
ive just finished doing it on my 6th one device, 4 were Verizon 1 was Tmobile and 1 was ATT. I seem to be able to replicate this process over and over again so far with no issues so far, but i am making sure to update each device manually via odin 1st to latest u1 Firmware first as described above.
K0mraid3 said:
ive just finished doing it on my 6th one device, 4 were Verizon 1 was Tmobile and 1 was ATT. I seem to be able to replicate this process over and over again so far with no issues so far, but i am making sure to update each device manually via odin 1st to latest u1 Firmware first as described above.
Click to expand...
Click to collapse
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
thats essentially the point of going from u to u1 then back to u after you booted atleast once into u1 with the desired carriers sim, somewhere along in the process of interrupting the bootloader and flashing the carriers U Firmware its overwriting the system policy. Theres a hole in here somewhere im positive. still trying to pin point exactly where this weakness lies.
iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
End Game is to find a BL exploit to force enable OEM Unlocking on these qcomm s21s.
K0mraid3 said:
End Game is to find a BL exploit to force enable OEM Unlocking on these qcomm s21s.
Click to expand...
Click to collapse
You're definitely not going to find that, as that's not related to SIM unlocking whatsoever
iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
And sorry to answer your initial question, yes, verfied carrier lock, getting errors like this, see attached.
iBowToAndroid said:
You're definitely not going to find that, as that's not related to SIM unlocking whatsoever
Click to expand...
Click to collapse
I like a challenge
This "temporary" thread is now closed. Main thread is here.
Hi
I bought a new OnePlus 10 PRO from Aliexpress. Its a CH version that the seller installed on it a global rom.
In the first setup of the phone, When I get to setting the fingerprint, I am unable to set it. I get the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried updating the phone, I tried factory reset... its always the same.
Any idea?
Thanks !
Are you sure that he installed the global rom? With model is yours NE2213 ? I bought from them also but I don't have this issue.
Anyway, you can try to use Oxygen Updater, to check if there is an update for your device or since your device is reseted, you can install ColorOS back
Hi,
I am on NE2215. Using Oxygen Updater I see that I have the most up to date version.
Not sure exactly how to install ColorOS.. I do want to have the regular OS that I would have as if I bought the global version (which i guess this is what the global rom mean..)
Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.
ok, and now for someone that have no idea how to do it?
If yours is NE2215 A13 you can download the ota file from this link: https://android.googleapis.com/packages/ota-api/package/7548d30abac02bde85a403bcc3a218df868e1910.zip
Then put it in your phone root and from your device Settings -> About the device -> Click on the option to check for the update -> 3 dots menu -> local installation and chose this package. It will start the installation.
Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
What am I missing?
I think it's obvious that something went wrong during the region change, this issue was prevalent on the 8 pro and was extremely difficult to fix.
Check out the 8 pro threads you'll be sure to see it. It's a partition iirc and if it's borked then it simply will not work..
I can't remember the name of it off hand but have a look and I'm sure you can get an idea of what may be wrong, specifically that partition.
Overall it's difficult to say as you've got a region changed phone, have you asked the seller what they did? If it is indeed as difficult as it was on the 8 pro to fix and seeing as you may be the only person experiencing this (far as I know) then I'd consider returning it.
You could re-flash the entire OS via fastboot enhance but that would also bring with it inherent problem's, if it's new then I guess the question you need to ask yourself is it worth it?
Did you save much money getting that converted variant?
dkaro said:
Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
View attachment 5624305
What am I missing?
Click to expand...
Click to collapse
This page is from android play services. You need to click on the first banner
@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless
If that is the page showing I'm assuming you're on a gsi ROM and not oxygen os.
Now it's better to reinstall OxygenOS completely because it doesn't seem to be the ROM you're running.
Search here on xda to unlock your bootloader and then you need to find the zip with the full ROM for you device and install it from fastboot as mentioned.
OK, i'm trying to unlock my bootloader but as I mentioned:
dkaro said:
and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
Click to expand...
Click to collapse
Any idea what am I doing wrong?
I tried several tutorials online and so far I found no tutorial that will actually give me step by step that each step is actually working..
Maybe it's missing the drivers. Try this https://gsmusbdriver.com/oneplus-10-pro
dkaro said:
@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless
Click to expand...
Click to collapse
I feel you buddy.
You can use the app in my Magisk guide to do local installs.
Unlocking the bootloader you need to type fastboot flashing unlock
I haven't had to change region myself, but I did make a thread for someone else where the process was listed, think I called it changing Chinese firmware iirc.
If it's just a case of a re-flash of the firmware you're on, it's not that difficult.
Just use oxygen updater and grab the full firmware then do the local update using the app I mentioned above (listed in my Magisk/root guide)
I've never done this when not having the bootloader unlocked personally, but you can unlock and that'll wipe your phone with the recovery already on your device.
Only issue I have going down these routes is what else is missing? Do any of these processes stand up if we can't rely on the integrity of the OS that someone has put on and made a balls of it?
Sorry I know you may not agree but 30% is a small price to pay to avoid a brick and bring stability..
But that's me
zopostyle said:
Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.
Click to expand...
Click to collapse
That is a seriously good shout and would explain the fingerprint.
Hi guys, thank you again for helping me.
I tried installing again the uSB drivers, and ran again "fastboot flashing unlock" - it still telling me:
As far as I understand I have to unlock it for next step, right? (either for resetting back to colorOS or reinstalling oxygen)
I will try later tonight the other method (this magisk thing) - is this the link you're talking about?
Can you please also give me a link to download the full most up to date global Oxygen version and the CH Color one? i'll try both
Thanks !
For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585
zopostyle said:
For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585
Click to expand...
Click to collapse
Really is odd about them not being full... They're massive compared to conventional incremental updates. 4.05GB that's a hell of an incremental.
Haven't had to do it myself and it's sightly off topic but is the full version you'd use to recover a phone albeit without a functional MSM?
So fastboot flashing?
Cheers
Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?
dkaro said:
Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
View attachment 5624521
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?
Click to expand...
Click to collapse
As @zopostyle said earlier.. you'd need to use 12 mate. As that's the only full version available...13 won't cut it...you can extract the images using the button that says allow incremental, that's useful for extracting boot images for rooting.
But there's a reason why that's there, it's so you don't go ahead and flash it.... According to @zopostyle 12 is the only full version so that's what you would need.
Again I've not done this myself so perhaps wait for someone else to chime in what to do next.