Related
Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:
ZB2016 said:
Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:
Click to expand...
Click to collapse
Restoring the backup is the only solution it seems.
Yes ... hmmm ... backup ... that was what I intended to do that morning when the BAMMMM happened. I really had a bad start with the 7X ...
So in case someone has a backup of a clean or nearly clean system partition, please send me a PN. Tnx in advance!
Normal make a Backup in Twrp before modify the System Partition.
Make not an Official Ota Update with Rooted and Twrp installed Rom
Its not the phones mistake that you mess up and wakeup and take the phone for a spin in half sleep
and bamm, i really dont know what that meant. i would say go to the honor care center and get it to them to work.
the procedure which i know of is tough and things like bamm happening might worsen things like TWRP not starting at all.
i have seen people bricking their phones but its never the phones fault.
i would never recommend doing a "BAMM" thing doing and flashing all the stuff randomly cz i dont think magisk is supported fully yet to our phone and you flashed it without asking anyone.
the other russian forums are flashing chinese stock firmware which is the only original firmware available, but the task to change the settings to work for other variant is a huge stock which i gave link to a few people but for you i wont recommend that cz obviously your situation is totally different so go to the honor center and explain them and they would help you.
good luck! next time verify and be careful before flashing anything at random cause its not the phones fault.
Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.
ZB2016 said:
Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.
Click to expand...
Click to collapse
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release
sid21 said:
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release
Click to expand...
Click to collapse
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!
ZB2016 said:
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!
Click to expand...
Click to collapse
I am in contact with the user who posted the article and tested it himself and requested a proper one in english language but he is busy so it hasnt proceeded.. But soon he ll be free to write one up for me so i will post it on XDA..
I'm in a very similar boat. The Magisk v15 update bricked my L24. I had another one available and have made back ups through twrp to restore on the bricked one. It actually boots, but all I get is a black screen with the menu, home, and back buttons now. Holding power gives me the options to restart and power off. Hope they release the stock rom soon, or custom roms be available soon.
root your son's 7x, make a boot and system backup and restore that in your phone.
reboot
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Sudeep Duhoon said:
root your son's 7x, make a boot and system backup and restore that in your phone.
reboot
Click to expand...
Click to collapse
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.
sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Back to life ... at least about 80%. Rooting leads to corrupt system partition (unable to boot afterwards) and bootloader can only be reached while a USB cable is connected (unusual behaviour). Nevertheless ... got it running. SID ... you are my hero of the day. Will PM you regarding comments for your thread.
ZB2016 said:
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.
Click to expand...
Click to collapse
i think i have to write a guide now. this was the first but more can come soon enough. may be today i'll write a guide to backup your phone (all 48 partitions) and then root so you always have all the necessary files to restore it back to life.
sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Plz give link of custom rom for honor 7x
dhananjay 007 said:
Plz give link of custom rom for honor 7x
Click to expand...
Click to collapse
Who made custom rom for the phone?
sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I have honor 7x.
dhananjay 007 said:
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
I have honor 7x.
Click to expand...
Click to collapse
So why are you even asking me for a custom rom?
If you know no one has made yet
UPDATE ... got it back to life, at least partly. The only thing is, that constantly the android adaptions of Huawei is making it unnecessary complex or is stopping progress at all. This is the log of my actual tasks. Key to progress was the unlocking of the system fs, which has some inconsistencies in the file system. In general, it gives me a 7X, that boots and I can install apps via HiSuite. Nevertheless I have no idea how to deal with Gapps. If I install opengapps, I will not be able to register an account - just hangs for a long period and then comes back (are there any logs written on the device to analyze a bit deeper?). Gapps without an account maks no sense. So I tried it without opengapps but with installing play services via HiSuite, granting rights, rebooting twice, installing Playstore, granting rights, rebooting twice, but starting Playstore after this procedure just tells me, that gms has to be installed (which in fact is already).
Any hint?
- prep like described by SID21 including HiSuite-Installation
- optional: download Nova Launcher, Firefox and Total Commander from "apkmirror.com"
- boot into TWRP
- mount system r/w
- format data
- wipe all partitions besides external SD
- mount vendor
- install image VENDOR.IMG
- reboot to bootloader- USB-connect to PC
- kill HiSuite in case it comes up
- Start MultiTools
- Click on "Unbrick" in upper list
- enter Path to prepared folder in grey field
- Validate: at least 4 checked boxes
- Click on Box labeled "Unbrick"
- Validate messages: "Completed", "All images are flashed successfully"
- Click "Recovery" in upper list
- in frame labeled "Flash custom Recovery/eRecovery":
- Click Button labelde "Select image" and navigate to file twrp_Honor_7x.img and select
- Click button "Flash Recovery"
- in Popup window select "Restart from fastboot" and unplug the phone from USB- Stop Multitools
- Wait for first restart, phone comes up
- Adapt phone settings:
- Security & Privacy/Additional Settings:
- set "Unknown sources"
- set "Allow HiSuite to use HDB" - About phone:
- Click 7 times in a row on "Build number" to activate developer options - Developer options:
- Activate "USB debugging"
- optional: Activate "Allow ADB debugging in charge only mode" - WiFi:
- connect to your WiFi network- USB-connect phone
- Phone popup: set "Allow access to device data?" to "Yes, allow access"
- Phone popup: set "Allow connection in HDB mode?" to "Yes, allow access"
- Phone popup: set "Allow USB debugging?" to "Ok"
- PC HiSuite Popup to inform about installation of services to manage device
- optional: PC HiSuite Apps:
- Install a proper Launcher (e.g. Nova Launcher) and make it the default launcher
- Install a proper file manager (e.g. Total Commander)
- install a browser (e.g. firefox)
- Download opengapps from opengapps.org and save to sd card- USB-disconnect phone
- Restart phone into TWRP
- do not get access to system partition
- Mount: Validate: system is not mounted at all
- Advanced/Terminal:
- enter "ls -l /dev/block/platform/hi_mci.0/by-name/system"
- validate: the filesystem points to /dev/block/mmcblk0p44
- ONLY DO THE FOLLOWING IF YOU KNOW WHAT YOU ARE DOING!!!
- enter "resize2fs /dev/block/mmcblk0p44"
- Validate Message: The Filesystem is now 1200128 blocks long.
- enter "e2fsck /dev/block/mmcblk0p44"
- Validate message: system clean, ... - Mount:
- check "system"
- uncheck "Mount system partition read-only" and swype in next screen to get access to system
- check "system" - Install:
- Select storage: Micro SDCard
- install SuperSU (I've chosen 2.82)
- Wipe Cache/Dalvik - Reboot:
- reboot to system
- do not install TWRP app- Reboot takes long time
- During boot animation another reboot occurs
- Boot animations gets finalized, phones comes up normally
Hi All,
I have a LG G3 (European d855) that was previously running CyanogenMod 13, a long time ago it refused to install future updates either over the air or flashing, I left it a long time as it was only a secondary phone I used for work.
I have since decided to flash a fresh OS (Lineage and also tried AOSCP) as the only important thing on this phone was my contacts. At first TWRP was giving me an error 7 no matter what ROM I downloaded, I read to change the script in META-INF to bypass the security feature to remove the "Asserts" re-package and try again. So I used the adb push command to add the new packaged file to the device and attempted to flash. I now get a new error "could not find META-INF/com/google/android/update-binary" in the zip file (the binary file was never edited).
Also as a side note I can no longer connect with adb when I had no issues before. The phone currently has no OS and refuses to install any package.
Could I possibly have corrupt partitions?
Any help will be much appreciated
Preface:
OnePlus has pushed an incremental rollout to OxygenOS for the OnePlus 8 Pro, 10.5.11 (India / Global) and 10.5.10 (Europe). You can find the changelog issued here.
https://forums.oneplus.com/threads/and-10-5-10-eu-for-the-oneplus-8-pro.1253402/
Many have found that the photochrom filter doesn't work as expected or doesn't work at all after this update, this seems to depend on the region. If you want this feature back, I encourage you to write feedback to OnePlus. There are many great changes in this update and I would love to see them in another update with the photochrom filter restored.
This guide is meant to show you how to restore this filter by downgrading the firmware on your phone, this means you will lose out on the other changes present in the new incremental update, including an Android security update. This is meant to be a temporary solution for those that really love this quirky feature and I don't recommend this guide for most people. Also, if you have root on your phone then this should remove it. Currently, this guide doesn't work for India since there's no downgrade image which brings them to 10.5.8. The infrared camera was disabled for India in version 10.5.9 which is the lowest we can downgrade to at the moment.
WARNING:
Do not proceed with this guide if you lack experience flashing ROMs or have the slightest apprehension about bricking your phone. Be sure to read the guide fully before attempting so that you understand how the procedure works. If you're uncomfortable after reading this, stop and forget about it. Leave feedback to OnePlus and wait for an update. I've only tested this with the global version, but this should work with the other regions as well. That being said, I'm not liable for any damage you cause to your device. STOP if you have a network-branded phone. Proceed at your own RISK!
Phone Backup:
Do not skip this step unless you want to start anew with a wiped device. You can use whatever backup method you wish, but the one I did on my own phone was a OnePlus Switch backup and a Google backup which worked decently well.
I also used Google's Autofill services so that it was easy to sign back into my accounts. You could use any password manager like LastPass just the same, but I think this service works better. You can check if your passwords are saved under Settings > Privacy > Advanced > Autofill services from Google > Passwords.
If you use Two Factor Authentication such as through Authy or Google Authenticator, ensure that you're able to authorize a new device with another such as via another device or SMS.
If you want to use my backup method, follow these basic steps. First, you'll backup with OnePlus Switch.
Open the OnePlus Switch app.
Tap "Backup and Restore".
Select "New Backup".
Check everything that you want backed up, then select "Backup Now".
Once finished, plug your phone into a computer and set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Copy /opbackup/MobileBackup to somewhere safe on your computer. It will be wiped from your phone in the next procedures, so this is extremely important.
Next, you'll backup using Google.
Open Settings, then go to System > Backup > Toggle "Backup to Google Drive" on if it hasn't been turned on already.
Tap "Back up now" and wait for it to finish.
Downgrade Flash:
This is scariest part of the procedure since your device will first be wiped with this type of flashing before installing the initial firmware. If the flashing procedure is interrupted, you may not be able to recover. Therefore, please do the following before proceeding to ensure that doesn't happen.
Ensure your device is charged at least 30%, I recommend higher though.
Make sure your device is plugged in while flashing.
Have a charged battery backup on hand in case the power grid goes out.
Check that the firmware image isn't corrupted before flashing (instructions ahead, step 3)
Alright, so now for the procedure:
Check your phone region. Open Settings > About phone, then look at the Build number. It should be something like 10.5.11.IN11XX. The IN11XX will denote your region.
IN11AA for Global
IN11DA for India
IN11BA for Europe
You can also check the Model:
IN2025 for Global
IN2021 for India
IN2023 for Europe
If you have an Indian model, discontinue this guide unless you have some other reason to downgrade. You won't be able to restore photochrom.
Download the appropriate downgrade firmware. There's a OnePlus post that included these firmware image files used for rolling back a developer preview. Here, we're using it to rollback the official stock image to an older version.
Look for "Download links for OnePlus 8 Pro" here: https://forums.oneplus.com/threads/android-11-beta-developer-preview-for-oneplus-8-series.1233995/
You'll have 3 versions:
NA for Global
IN for India
EU for Europe
You should know what your region is from step 1. It's vital that you choose the correct region, so if you're unsure then GO BACK to step 1!
Compute the SHA1 checksum of the downloaded firmware image. This is to check that it hasn't been corrupted, which can happen when you download files or have a faulty drive. Windows has a built-in utility called CertUtil and Macs have one called shasum.
Windows: Open command prompt (find it by searching "cmd" in the search bar), then enter "CertUtil -hashfile" without quotes followed by a space. Drag the downloaded firmware image onto the prompt, then press enter.
Mac: Open Terminal from Applications > Utilities. Enter "shasum -a 1" without quotes followed by a space. Drag the downloaded firmware image onto the prompt, then press enter.
You'll see a long string of characters, this is the SHA1 checksum. Compare it with the following value according to your region, ensure it matches EXACTLY. If it doesn't then you have a corrupted image or downloaded the wrong region, please go back and download it again.
Global: 96f8ee55a1b8914317c7e24306bb512733530052
Europe: 74a94d4d0b1676a03ddfd40f85635b0036c5b038
Move the downloaded firmware image onto your device. You can do this by plugging in your phone to the computer then set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Make sure your phone is charged at least 30% and plugged in as I warned above.
Open Settings > System > System updates.
Tap the gear cog icon in the top right.
Tap "Local upgrade" and select the package you moved onto the phone in step 4. This will wipe your phone and downgrade. DO NOT unplug or turn off the phone, let it finish the entire process because if you don't then it could brick your phone.
Once the phone boots up, skip through as many prompts as possible since you can set it up later. It will say installing updates during these prompts, don't worry about this, it's normal.
Update to 10.5.10 (Global), 10.5.9 (Europe):
This next step is to get you to the most recent update before photochrom was removed or changed. So hold off on restoring your backup and setting up the device.
Download the previous update that had Photochrom.
https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315
Click the reveal content button under "Signed flashable zips" and then the next reveal content button under the appropriate region. Click the download link for 10.5.10 if your region is Global or India, click the download link for 10.5.9 if your region is Europe.
Check the SHA1 checksum using the instructions in step 3 of the previous section. However, you'll instead be comparing to the following values.
Global: 4a08ebb45aed300e8707aa1dc2cbd07ea69344df
Europe: 1f5b792964312a06eb122f813a33787ccf7d3850
As before, make sure these match exactly with you calculated. If not, you downloaded the wrong file or your download is corrupted. Go back to the post and try to download again. The XDA forum post lists MD5 values which are different than SHA1 so please ignore those.
Move the downloaded firmware image onto your device. You can do this by plugging in your phone to the computer then set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Make sure your phone is charged at least 30% and plugged in as I warned above.
Open Settings > System > System updates.
Tap the gear cog icon in the top right.
Tap "Local upgrade" and select the package you moved onto the phone in step 3. This will update your phone just like the typical OTA update.
Restoring from backup:
If you've come this far then it means you've already restored Photochrom. If you wanted a newly wiped phone then you're done. Otherwise, continue on to restore your backup. This goes over restoring using the backup method I used at the beginning of this guide.
Plug your phone into a computer and set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Copy the /opbackup/MobileBackup folder you saved before back onto the phone. Make sure it has the same path. If you need to then you can create a new opbackup folder.
Back on the phone, open up the OnePlus Switch app.
Select "Backup and Restore" at the bottom.
Select "Restore Backup".
Select and the restore you moved back onto the phone. If you don't see it, it means you didn't move it onto the correct path. It should be in /opbackup/MobileBackup.
Once the OnePlus Switch app has restored your backup, sign into your Google account from Settings > Accounts > + Add account. You should soon see a finish setting up notification from Google, tap this and continue so that it installed all your apps and restores a bunch of settings.
Once finished, double check through your settings to see if it missed anything. For me it got most settings but some weren't set.
Sign back in to all your apps and authorize your 2FA manager if you have one.
Thank you
I hope this has been helpful to some people out there. I put a lot of effort into this and triple-checked everything, but let me know if anything is confusing. I'd be happy to change anything in this guide to help clarify. Ultimately, I'd like to see either OnePlus push out an official update that restores this or see someone create a Stock + Photochrom ROM that only changes code related to that camera to keep the original functionality.
GiveMeAnthony said:
Preface:
OnePlus has pushed an incremental rollout to OxygenOS for the OnePlus 8 Pro, 10.5.11 (India / Global) and 10.5.10 (Europe). You can find the changelog issued here.
https://forums.oneplus.com/threads/...and-10-5-10-eu-for-the-oneplus-8-pro.1253402/
Many have found that the photochrom filter doesn't work as expected or doesn't work at all after this update, this seems to depend on the region. If you want this feature back, I encourage you to write feedback to OnePlus. There are many great changes in this update and I would love to see them in another update with the photochrom filter restored.
This guide is meant to show you how to restore this filter by downgrading the firmware on your phone, this means you will lose out on the other changes present in the new incremental update, including an Android security update. This is meant to be a temporary solution for those that really love this quirky feature and I don't recommend this guide for most people. Also, if you have root on your phone then this should remove it.
WARNING:
Do not proceed with this guide if you lack experience flashing ROMs or have the slightest apprehension about bricking your phone. Be sure to read the guide fully before attempting so that you understand how the procedure works. If you're uncomfortable after reading this, stop and forget about it. Leave feedback to OnePlus and wait for an update. I've only tested this with the global version, but this should work with the other regions as well. That being said, I'm not liable for any damage you cause to your device. STOP if you have a network-branded phone. Proceed at your own RISK!
Phone Backup:
Do not skip this step unless you want to start anew with a wiped device. You can use whatever backup method you wish, but the one I did on my own phone was a OnePlus Switch backup and a Google backup which worked decently well.
I also used Google's Autofill services so that it was easy to sign back into my accounts. You could use any password manager like LastPass just the same, but I think this service works better. You can check if your passwords are saved under Settings > Privacy > Advanced > Autofill services from Google > Passwords.
If you use Two Factor Authentication such as through Authy or Google Authenticator, ensure that you're able to authorize a new device with another such as via another device or SMS.
If you want to use my backup method, follow these basic steps. First, you'll backup with OnePlus Switch.
Open the OnePlus Switch app.
Tap "Backup and Restore".
Select "New Backup".
Check everything that you want backed up, then select "Backup Now".
Once finished, plug your phone into a computer and set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Copy /opbackup/MobileBackup to somewhere safe on your computer. It will be wiped from your phone in the next procedures, so this is extremely important.
Next, you'll backup using Google.
Open Settings, then go to System > Backup > Toggle "Backup to Google Drive" on if it hasn't been turned on already.
Tap "Back up now" and wait for it to finish.
Downgrade Flash:
This is scariest part of the procedure since your device will first be wiped with this type of flashing before installing the initial firmware. If the flashing procedure is interrupted, you may not be able to recover. Therefore, please do the following before proceeding to ensure that doesn't happen.
Ensure your device is charged at least 30%, I recommend higher though.
Make sure your device is plugged in while flashing.
Have a charged battery backup on hand in case the power grid goes out.
Check that the firmware image isn't corrupted before flashing (instructions ahead, step 3)
Alright, so now for the procedure:
Check your phone region. Open Settings > About phone, then look at the Build number. It should be something like 10.5.11.IN11XX. The IN11XX will denote your region.
IN11AA for Global
IN11DA for India
IN11BA for Europe
You can also check the Model:
IN2025 for Global
IN2021 for India
IN2023 for Europe
Download the appropriate downgrade firmware. There's a OnePlus post that included these firmware image files used for rolling back a developer preview. Here, we're using it to rollback the official stock image to an older version.
Look for "Download links for OnePlus 8 Pro" here: https://forums.oneplus.com/threads/android-11-beta-developer-preview-for-oneplus-8-series.1233995/
You'll have 3 versions:
NA for Global
IN for India
EU for Europe
You should know what your region is from step 1. It's vital that you choose the correct region, so if you're unsure then GO BACK to step 1!
Compute the SHA1 checksum of the downloaded firmware image. This is to check that it hasn't been corrupted, which can happen when you download files or have a faulty drive. Windows has a built-in utility called CertUtil and Macs have one called shasum.
Windows: Open command prompt (find it by searching "cmd" in the search bar), then enter "CertUtil -hashfile" without quotes followed by a space. Drag the downloaded firmware image onto the prompt, then press enter.
Mac: Open Terminal from Applications > Utilities. Enter "shasum -a 1" without quotes followed by a space. Drag the downloaded firmware image onto the prompt, then press enter.
You'll see a long string of characters, this is the SHA1 checksum. Compare it with the following value according to your region, ensure it matches EXACTLY. If it doesn't then you have a corrupted image or downloaded the wrong region, please go back and download it again.
Global: 96f8ee55a1b8914317c7e24306bb512733530052
India: 84f1e472d7e5da0e50d0a4e8f135820352e6dd17
Europe: 74a94d4d0b1676a03ddfd40f85635b0036c5b038
Move the downloaded firmware image onto your device. You can do this by plugging in your phone to the computer then set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Make sure your phone is charged at least 30% and plugged in as I warned above.
Open Settings > System > System updates.
Tap the gear cog icon in the top right.
Tap "Local upgrade" and select the package you moved onto the phone in step 4. This will wipe your phone and downgrade. DO NOT unplug or turn off the phone, let it finish the entire process because if you don't then it could brick your phone.
Once the phone boots up, skip through as many prompts as possible since you can set it up later. It will say installing updates during these prompts, don't worry about this, it's normal.
Update to 10.5.10 (Global and India), 10.5.9 (Europe):
This next step is to get you to the most recent update before photochrom was removed or changed. So hold off on restoring your backup and setting up the device.
Download the previous update that had Photochrom.
https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315
Click the reveal content button under "Signed flashable zips" and then the next reveal content button under the appropriate region. Click the download link for 10.5.10 if your region is Global or India, click the download link for 10.5.9 if your region is Europe.
Check the SHA1 checksum using the instructions in step 3 of the previous section. However, you'll instead be comparing to the following values.
Global: 4a08ebb45aed300e8707aa1dc2cbd07ea69344df
India: 07b698e8d071ad794f3bcca38ad728ba646a4a5e
Europe: 1f5b792964312a06eb122f813a33787ccf7d3850
As before, make sure these match exactly with you calculated. If not, you downloaded the wrong file or your download is corrupted. Go back to the post and try to download again. The XDA forum post lists MD5 values which are different than SHA1 so please ignore those.
Move the downloaded firmware image onto your device. You can do this by plugging in your phone to the computer then set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Make sure your phone is charged at least 30% and plugged in as I warned above.
Open Settings > System > System updates.
Tap the gear cog icon in the top right.
Tap "Local upgrade" and select the package you moved onto the phone in step 3. This will update your phone just like the typical OTA update.
Restoring from backup:
If you've come this far then it means you've already restored Photochrom. If you wanted a newly wiped phone then you're done. Otherwise, continue on to restore your backup. This goes over restoring using the backup method I used at the beginning of this guide.
Plug your phone into a computer and set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Copy the /opbackup/MobileBackup folder you saved before back onto the phone. Make sure it has the same path. If you need to then you can create a new opbackup folder.
Back on the phone, open up the OnePlus Switch app.
Select "Backup and Restore" at the bottom.
Select "Restore Backup".
Select and the restore you moved back onto the phone. If you don't see it, it means you didn't move it onto the correct path. It should be in /opbackup/MobileBackup.
Once the OnePlus Switch app has restored your backup, sign into your Google account from Settings > Accounts > + Add account. You should soon see a finish setting up notification from Google, tap this and continue so that it installed all your apps and restores a bunch of settings.
Once finished, double check through your settings to see if it missed anything. For me it got most settings but some weren't set.
Sign back in to all your apps and authorize your 2FA manager if you have one.
Thank you
I hope this has been helpful to some people out there. I put a lot of effort into this and triple-checked everything, but let me know if anything is confusing. I'd be happy to change anything in this guide to help clarify. Ultimately, I'd like to see either OnePlus push out an official update that restores this or see someone create a Stock + Photochrom ROM that only changes code related to that camera to keep the original functionality.
Click to expand...
Click to collapse
can you please tell me after rolling and installing first step
then at this point
Update to 10.5.10 (Global and India), 10.5.9 (Europe):
can we install 10.5.8 also Indian version for me in which it was enabled.
becasue company disabled it on 10.5.10 for me.
MintuBilii said:
can you please tell me after rolling and installing first step
then at this point
Update to 10.5.10 (Global and India), 10.5.9 (Europe):
can we install 10.5.8 also Indian version for me in which it was enabled.
becasue company disabled it on 10.5.10 for me.
Click to expand...
Click to collapse
Yeah, you can use any of the images listed on that XDA page.
https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315
Though I haven't calculated the SHA1 hash for all of those versions. Since I didn't author these files, in order to verify the hashes, I download to multiple devices and then run the checksum on each to compare. So what about 10.5.9 for India? Do you know if the old photochrom works on that?
Here's the SHA1 for 10.5.8 (India): db88d05729c8b235d7d4067ed0b949348f671e61
GiveMeAnthony said:
Yeah, you can use any of the images listed on that XDA page.
https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315
Though I haven't calculated the SHA1 hash for all of those versions. Since I didn't author these files, in order to verify the hashes, I download to multiple devices and then run the checksum on each to compare. So what about 10.5.9 for India? Do you know if the old photochrom works on that?
Here's the SHA1 for 10.5.8 (India): db88d05729c8b235d7d4067ed0b949348f671e61
Click to expand...
Click to collapse
no it was working well on 10.5.8 only.
buti think we will get error message that downgrade is not possible .
Update
Just i downgraded with first post to 10.5.9 now when installing 10.5.8: OnePlus8ProOxygen_15.I.17_GLO_017_2005100301
it gives error that you can't downgrade now what ?
I don't have knowledge of root.
do you know any link of downgrade for 10.5.8 India version
MintuBilii said:
no it was working well on 10.5.8 only.
buti think we will get error message that downgrade is not possible .
Update
Just i downgraded with first post to 10.5.9 now when installing 10.5.8: OnePlus8ProOxygen_15.I.17_GLO_017_2005100301
it gives error that you can't downgrade now what ?
I don't have knowledge of root.
do you know any link of downgrade for 10.5.8 India version
Click to expand...
Click to collapse
That won't work and you shouldn't even attempt to circumvent it. If you were able to flash it then you would end up bricking your phone. The whole point of the downgrade firmware image is to bring you to a lower version than the one before the feature was removed. You cannot update to a lower version, you specifically need a downgrade image. I didn't realize the downgrade image for India didn't go below 10.5.9. For global users, the downgrade image provided by OnePlus goes to 10.5.7. I'll update the guide to reflect that this currently doesn't work for India users. In order to get it to work, you would need a downgrade firmware image which brings you down to at least 10.5.8. It may be possible to create such an image because from what I can tell, the image consists of instructions to wipe the phone and then flash the update. Basically, we would need to modify the image to keep those instructions but change the update.
GiveMeAnthony said:
That won't work and you shouldn't even attempt to circumvent it. If you were able to flash it then you would end up bricking your phone. The whole point of the downgrade firmware image is to bring you to a lower version than the one before the feature was removed. You cannot update to a lower version, you specifically need a downgrade image. I didn't realize the downgrade image for India didn't go below 10.5.9. For global users, the downgrade image provided by OnePlus goes to 10.5.7. I'll update the guide to reflect that this currently doesn't work for India users. In order to get it to work, you would need a downgrade firmware image which brings you down to at least 10.5.8. It may be possible to create such an image because from what I can tell, the image consists of instructions to wipe the phone and then flash the update. Basically, we would need to modify the image to keep those instructions but change the update.
Click to expand...
Click to collapse
yes please, I am waiting for it. because for India it was working and enabled the feature on 10.5.8 let me know if you found downgrade image tested which has enabled photochrom because i am getting an error that I cannot downgrade and i do not wish to root my phone due to I use security apps.
Right now i am on 10.5.9 which has no photochrom but i think its better does not sucks my battery like .11 and more stable.
I will keep it testing if any issues will update to latest version.
MintuBilii said:
yes please, I am waiting for it. because for India it was working and enabled the feature on 10.5.8 let me know if you found downgrade image tested which has enabled photochrom because i am getting an error that I cannot downgrade and i do not wish to root my phone due to I use security apps.
Right now i am on 10.5.9 which has no photochrom but i think its better does not sucks my battery like .11 and more stable.
I will keep it testing if any issues will update to latest version.
Click to expand...
Click to collapse
The error is because those aren't downgrade images and you're trying to "update" to an older version. Don't even attempt flashing update images of older versions, even though the System Update app blocks you, because it would brick the phone if it did allow you. The point of updating in this guide was because the downgrade image goes all the way back to 10.5.7. If there were one for 10.5.10 then global users wouldn't need the updating step. Rooting won't help you in this case either (at least not yet). There's another thread attempting to bring back this functionality with the camera, photo processing, and various services / APIs so that you can have the updates with photochrom.
https://forum.xda-developers.com/on...cussion-how-to-enable-photochrom-int-t4132807
In fact, could you try something for me?
Download and extract Android platform tools on your computer https://developer.android.com/studio/releases/platform-tools
Add the platform-tools directory to your PATH system variable. Here's how to do it on Windows. https://www.computerhope.com/issues/ch000549.htm Let me know if you don't have Windows.
Enable USB debugging on your device. Settings > About Phone > Tap the build number until it says you're a developer. Next, go to Settings > System > Developer Options then toggle USB debugging.
Run the following command in command prompt / terminal
Code:
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Press the switch camera button on the app which should've loaded until you get to Fourth Camera. Let me know the results.
I'll let you know if a 10.5.8 downgrade image is made for India. When I get a chance, I'll run some diffs on the downgrade vs update images and see if I can generate a new image myself. I have no way of testing the image though since I don't have an Indian device.
GiveMeAnthony said:
The error is because those aren't downgrade images and you're trying to "update" to an older version. Don't even attempt flashing update images of older versions, even though the System Update app blocks you, because it would brick the phone if it did allow you. The point of updating in this guide was because the downgrade image goes all the way back to 10.5.7. If there were one for 10.5.10 then global users wouldn't need the updating step. Rooting won't help you in this case either (at least not yet). There's another thread attempting to bring back this functionality with the camera, photo processing, and various services / APIs so that you can have the updates with photochrom.
https://forum.xda-developers.com/on...cussion-how-to-enable-photochrom-int-t4132807
In fact, could you try something for me?
Download and extract Android platform tools on your computer https://developer.android.com/studio/releases/platform-tools
Add the platform-tools directory to your PATH system variable. Here's how to do it on Windows. https://www.computerhope.com/issues/ch000549.htm Let me know if you don't have Windows.
Enable USB debugging on your device. Settings > About Phone > Tap the build number until it says you're a developer. Next, go to Settings > System > Developer Options then toggle USB debugging.
Run the following command in command prompt / terminal
Code:
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Press the switch camera button on the app which should've loaded until you get to Fourth Camera. Let me know the results.
I'll let you know if a 10.5.8 downgrade image is made for India. When I get a chance, I'll run some diffs on the downgrade vs update images and see if I can generate a new image myself. I have no way of testing the image though since I don't have an Indian device.
Click to expand...
Click to collapse
bro no long process needed !
I can still use the camera using factory trick
For wireless adb(require wireless adb debugging to be enabled):
https://github.com/lllsondowlll/OP8_Camera/blob/master/README.md
this works 100% and no root needed.
i am on 10.5.9 right now in which no photochrom but can use with factory mode.
what i do not like is we have to use that factory mode and id not like it however i am feeling battery is more stable right now in my current version that is why not looking to upgrade.
https://forums.oneplus.com/threads/...tochrom-filter-to-work-like-original.1257039/
{
"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 have the Indian version of Oneplus 8 Pro. And I downgraded my phone from 10.5.12 to 10.5.4 using the MSM Tool. (EDL Mode). And the Photochrom works well on that.
rippedd_ggenes said:
I have the Indian version of Oneplus 8 Pro. And I downgraded my phone from 10.5.12 to 10.5.4 using the MSM Tool. (EDL Mode). And the Photochrom works well on that.
Click to expand...
Click to collapse
can you please share the detailed steps to do it will be very thankful to you.
Can we follow this guide even on 11.0.3.3?
Teclast M40 Pro DiscoveriesVarious helpful points of knowledge to unlock your bootloader, to root, and use your tablet.
Problem: Where can I obtain the official firmware?
Solution: Teclast Website
Usage: type M1A3 in search
Problem How can I unpack "pac" files?
Solution: Build C utility divinebird / pacextractor
Solution: Download pre built Linux executable pacextractor.zip
Usage: >./pacextractor Firmware.pac
Bash:
git clone https://github.com/divinebird/pacextractor
cd pacextractor
make
Problem: I need tools to flash my device
Solution: Download the latest SPD Upgrade Flash Tool SPD_Upgrade_Tool
Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools
Solution: Download and install 2010 Visual C++ Distribution
Problem: I want to unlock my bootloader. (Window and Linux kit)
Solution: Download TeclastM40Pro_Unisoc_UnlockTools.zip
Usage: Read readme file.
Problem: How can I remove the dm_verify warning on boot up after unlocking the bootloader?
Untested Solution: digitally sign the vbmeta partition and write it back. See [Tutorial] How to create a custom signed vbmeta.img
Problem: I want to root my device.
Solution: Modify boot.img with Magisk, then sign.
Usage: Upload to your device's download directory, the current boot.img read from your device, or from the same version firmware. Then install Magisk app from here. Use Magisk to patch the boot.img. Sign the partition. Then flash back the signed magisk version of boot.img to "boot_a" partition. Guide to flashing single partition at Hovatek Website
Problem: I need to emergency flash my device?
Solution: Currently only from Windows, use SPD Upgrade Tools to reflash firmware.
Usage: From the tablet powered off, or if boot looping. Hold down the power-button and volume-down for five seconds, release the power-button, and keep the volume-down button still held for another five seconds, then release or release if the detected earlier. Windows and SPD tools should then detect your device to flash.
Problem: I want to improve my Telcast M40 Pro
Solution: List of suggested apps below;
FDroid App Store F-Droid Website
Aurora > via FDroid. App store allowing the direct download from Google Playstore, without your own account.
Lawnchair > via FDroid. Fast open source sophisticated launcher.
AdAway > via FDroid. Removes adverts whilst using apps.
TrackerControl > via FDroid. Manages apps access to internet, and blocks spyware and trackers.
.
Problem: I want root mode without the effort of hacking a rom partition.
Solution: For those with World version Teclast M40 Pro device, here is a signed rooted boot partition I created. Read the readme file inside the zip. You will require an unlocked device, windows setup with USB drivers for Teclast, the complete firmware from Teclast website, and SPD Update Tools installed. If you're successful, then on rooting you will need to install Magisk app to get root active. Magisk will reboot once to finalise.
Download : TeclastM40Pro_ROW__v1p0_signedboot_magiskrooted.zip
Download : TeclastM40Pro_ROW__v1p2_signedboot_magiskrooted.zip
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
laurorual said:
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
Click to expand...
Click to collapse
Sorry for replying late. I got no indication of the response. To the problem, I can only suggest getting a different version of SPD or m aking sure your computer system is properly updated. I hope you've already solved the issue!
Maybe you're experiencing, "Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools" See above for solution.
I've noticed a new ROM for world edition, "M40 Pro(M1A3)_Android 11.0_ROW V1.02_20220525", but not getting any system update options for OTA. People flashing their systems may want the latest firmware!
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Is there any way to install Magisk modules?
Thanks for your post, it helped me a lot to unlock my tablet.
Edit: My version is the M1A1 firmware V1.03_20210804
Edit 2: Finally, when updating my tablet with the root file that is in the post, it did not allow me to install any Magisk module, the solution is to download version 24.3, and update automatically, without changing to a higher version of Magisk
Glad you worked it out Miny !!! Sorry the warning emails for new posts have been going to a gmail account I no longer use.
Also your hardware maybe different and require it's own unique firmware and boot images. It seems the cracking in similar though.
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Hi there.
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked?
Thanks in advance
rubsbcn said:
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked? Thanks in advance
Click to expand...
Click to collapse
To tell you the truth, not sure. Most SoC are impossible or near impossible to brick. They usually allow for an injection or have a read only boot section. Other words you could test. Also research difference in hardware between models, and that may indlicate if something may not work. The kernel/drivers are the improtant aspect.
jorkusjorkus said:
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Click to expand...
Click to collapse
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
minyfriki said:
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Click to expand...
Click to collapse
What I found works, is when using SPD Research Tool, load up the firmware.pac and then go into settings and click "Select All Files" and again to unselect, which leaves the default required items.
Then manually change BOOT to the Magisk img. Then click on all VBMETA types, and UBOOT_LOADER (may not be required though). Then flash.
You should get bootable tablet (no looping). Warning: UserData partition is written over.
I'll share my Magisk image for v1.2
e8hffff said:
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I'm using the same version as you on the same OS. After some research it seems like unlock_bootloader was removed in this commit from 2018. From what I can tell, unlock_critical does something else (unlock_bootloader runs
Code:
fb_queue_download("unlock_message", data, sz); fb_queue_command("flashing unlock_bootloader", "unlocking bootloader");
while unlock_critical runs
Code:
do_oem_command("flashing", "unlock_critical" and doesn't take the signature argument);
)
I'll see if I can compile the older version with the needed command.
What about my other questions?
Issue: Android not starting. I had the infinite restart when plugged in the usb. I tried to reload the installation package (succeeded), but didn't fixed the issue. Battery was not charging yet. When I started the Teclast M40 pro, the logo showed up, but the tablet turned off again.
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
dougcwb said:
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
Click to expand...
Click to collapse
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
e8hffff said:
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
Click to expand...
Click to collapse
I did the installation package process that the Teclast sent me. The last thing they told me to do was keep trying to install the package (wft?). Well, I just open the tablet, unplugged the battery for a while and after that it worked.
Maybe this resolved 2 things:
1-the battery was not properly connected in the first place, so when I plugged the 5 pin to the board it connected as it should.
2- Maybe there is a "memory" in the board attached to the battery that was bricked (or something like that) when I pulled off the plug, this memory was reseted.
BTW, when the tablet came to life again, the battery was at 87%.
Hi,
i have rk3399, px6, max 10 device running on android 10 and when trying to update firmware to latest version, I always end with error 21, wrong footer, signature verification failure (see attached photo). I know that error 21 is related to corrupted file or similar but I tried many times different OTAs and it's always the same. Any tip how to fix that?
1) Format the SD card or usb flash drive to FAT32, or try another SD card or flash drive.
2) Copy update.zip to the root directory
3) Try to perform the update from recovery.
4) If everything failed, just try to reinstall the recovery using IMG and then update using OTA:
[MTCD/E] Android 10 upgrade using official Free tools
To upgrade a MTCD/E PX3, PX5, PX6 from Android 6+ on using official Rockchip free tools - a reminder, bringing together multiple threads. First note - if coming from Android 6 - early versions of Realtek dual BT/WIFI (type 2) are not supported...
forum.xda-developers.com
5) Or install recovery android 11 right away:
Px6 android 10 to 11 update
hi friends Dasaita release android 11 in img file https://www.dropbox.com/s/f94si34riqxsc3o/ha3_11_rk3399_11.0_%E7%83%A7%E5%BD%95%E5%8C%85%2820220316%29.zip?dl=0 M.I.C ANDROID 11 image file ...
forum.xda-developers.com
6) Of course your unit must be MTCE.
7) Last advice, if everything works for you, then leave it as it is. If the applications do not work for you, uninstall the
latest Android System WebView update and disable its updates.
hi @Pavel-71 ,
thanks a lot for your time and help. In fact it turned out to be a faulty USB drive...
I used a different one, which successfully managed to push the update. About the upgrade to android 11, is there anything fascinating or better not risk it?
I haven't personally tested it, read the experience from Bettman66 here:
I did it, A11 on a MTCE device
Hardware: Isudar PX6-VW0907 Software: SDDiskTool_v1.59 ha3_11_rk3399_11.0_烧录包(20220316).zip HCT8 ANDROID 11 OTA UPDATE (20220412 ) I created a bootable SD card using SDDisktool and the image and flashed the A11. After that I had this picture...
forum.xda-developers.com