[APP][2015-01-12][root][GNex/Dev] BootUnlocker for Nexus Devices -- version 1.6.1
NEW: beta version available!
[SIZE="+2"]BootUnlocker for Nexus Devices -- Unlock your bootloader without fastboot.[/SIZE]
This application REQUIRES a Galaxy Nexus (maguro, toro or toroplus), Nexus 4 (mako), Nexus 5 (hammerhead), Nexus 7 2013 (deb or flo), Nexus 10 (manta), OnePlus One (bacon / A0001), OnePlus 2 (OnePlus2), OnePlus X (OnePlus / ONE / E1001), YU Yuphoria (lettuce / YUPHORIA), YU Yureka (tomato / YUREKA), Lenovo Zuk Z1 (ham / Z1), InFocus M810 (VNA), InFocus M812 (VN2), or Yota Phone 2 (yotaphone2), with root.
You've rooted your device, and you are trying to decide between the security of relocking your bootloader (with stock recovery and USB Debugging off), and the flexibility of leaving it unlocked.
You know that in order to prevent an unauthorized user from accessing your data by flashing a custom recovery, "fastboot oem unlock" wipes your data. This also means that if you relock your bootloader, you will need to do a full backup-and-restore whenever you decide to unlock it again.
BootUnlocker for Nexus Devices lets you have the best of both worlds by using root privileges to unlock your bootloader from within Android, without wiping your data. This allows you to keep your bootloader locked for security, with this application safely protected behind your lockscreen password. Whenever you want to unlock or relock your bootloader, just unlock your screen and run BootUnlocker.
License
BootUnlocker for Nexus Devices is Open Source Software, licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0.html.
You can redistribute, reuse, or modify this software as permitted under this license.
Source code is maintained on GitHub.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
For support, please leave a comment on this thread, or open an issue on the GitHub page.
STABLE version: (a) XDA post, (b) XDA download, (c) Google Play download
BETA version: (a) XDA post, (b) XDA download
XDA:DevDB Information
BootUnlocker, App for the Samsung Galaxy Nexus
Contributors
segv11, osm0sis
Source Code: https://github.com/segv11/boot-unlocker
Version Information
Status: Stable
Current Stable Version: 1.6.1
Stable Release Date: 2015-01-12
Current Beta Version: 1.6.3
Beta Release Date: 2017-10-29
Created 2017-07-18
Last Updated 2017-10-29
How it Works
BootUnlocker for Nexus Devices avoids using "fastboot oem unlock", with its associated "userdata" wipe. When fastboot unlocks it updates a lock status flag, stored on a partition of your device's internal storage. Device partitions, positions and state values (locked/unlocked) are as follows:
On the Galaxy Nexus, the bootloader uses position 0x000007C of the "param" partition, stored as 01 / 00.
On the Nexus 10, the bootloader uses position 0x0000224 of the "param" partition, stored as 00 / 01.
On the Nexus 4 and Nexus 5, the bootloaders use position 0x0004010 of the "misc" partition, stored as 00 / 01. The Nexus 4 and Nexus 5 bootloaders also keep a "Tamper" flag at position 0x0004014 of the "misc" partition. It is stored as 00 / 01 (untampered/tampered).
On the Nexus 7 (2013), the bootloader uses position 0x04FFC00 of the "aboot" partition, stored as 00 / 02.
On the OnePlus One, the bootloader uses position 0x000FFE10 of the "aboot" partition, stored as 00 / 01. The OnePlus One has a "Tamper" flag, at position 0x000FFE14 of the "aboot" partition.
On devices with Tamper flag locations listed above, BootUnlocker for Nexus Devices can also set and clear this flag. You can also view this flag using "fastboot oem device-info".
BootUnlocker uses root privileges to write to to the appropriate location directly, bypassing fastboot. This allows you to lock and unlock your bootloader from within Android, without wiping your "userdata" partition.
The technique used was discovered through the efforts of several contributors on http://forum.xda-developers.com/showthread.php?t=1650830&page=13
Special thanks go to those who posted raw images of their device partitions, helped with/conducted the analysis, or put their devices in harm's way to beta test: efrant, osm0sis, iuss, Archpope, AdamOutler, NCguy, Raftysworld, Mach3.2, Meep70, Polarfuchs, and others. This application could not have been written without their contributions.
To learn more about how this app works, and plans for future functionality, follow this project on GitHub, or subscribe the application's XDA thread.
Please note that the Nexus 7 (2012 version) cannot be supported in BootUnlocker. See this XDA thread for an alternative: http://forum.xda-developers.com/showthread.php?t=2068207
Change Log
Version 1.6.1:
Adds support for bacon / A0001 (OnePlus One)
Version 1.5.2:
Updated wording for tamper flag management
Version 1.5.1:
Adds support for flo and deb (Nexus 7 2013)
Adds tamper flag management on mako (Nexus 4) and hammerhead (Nexus 5)
Version 1.5beta2:
Experimental tamper flag management on mako (Nexus 4) and hammerhead (Nexus 5)
Version 1.5beta1:
Experimental support for flo and deb (Nexus 7 2013)
Version 1.4:
Adds support for hammerhead (Nexus 5)
Version 1.3.2 Beta:
Experimental support for hammerhead (Nexus 5)
Version 1.3:
Adds support for mako (Nexus 4)
Version 1.2.5 Beta:
Experimental support for mako (Nexus 4)
Version 1.2:
Adds support for manta (Nexus 10)
Adds status area (bottom-left) to display information about the device and app
Version 1.2 Beta 1:
Adds support for manta (Nexus 10)
Version 1.1:
Adds support for toroplus (Sprint Galaxy Nexus)
Corrects multiple-su-request issue for users of ChainsDD's Superuser app
Version 1.0:
Initial Release on XDA and Play Store
Version 0.9 Beta:
Fixed race conditions from exec()ing su on the main thread
Removed the need for busybox
Version 0.8 Beta:
New launcher icons and screenshots
Version 0.7 Beta:
Device restrictions in the Manifest to prevent installation on many non-Galaxy Nexus devices
Version 0.6 Beta:
Checks that you have a toro or maguro device before doing anything.
Makes diagnostic output to logcat.
Various code cleanups
Version 0.5 ALPHA:
First testing Release on XDA
How to help bring BootUnlocker to new devices
For those of you who are thinking of helping to bring this app to a new device, you should know what is involved. First, it should be a Nexus or similar device, with "fastboot oem unlock" and "fastboot oem lock", and without the 2014 security changes in the bootloader. Second you should know which devices are already supported, and which we probably can't support.
You will want up-to-date nandroids, copied off-device. Backup your /sdcard off-device too, as nandroids don't save this.
The general idea is that we take images of all the partitions, in both the locked and unlocked states. We then compare them to see where the changes were. Once we've figured it out, we test it by flashing back the appropriate images to make sure that they change the lockstate of the device. If we can't figure it out, we will need to unlock your device using "fastboot oem unlock", which will wipe ALL of /data, including /sdcard...
If your device started locked, we would:
run "ls -lR /dev/block" and send me the result
I'll send back a list of "dd" commands to dump all the paritions to /sdcard
dump all the partitions
take md5's of each image for quick change detection
copy the images off-device
reboot bootloader
fastboot oem lock
reboot
dump all the partitions again, to a different directory
take md5's of each new image for quick change detections
copy new the images off-device
If your device started locked, we would:
run "ls -lR /dev/block" and send me the result
I'll send back a list of "dd" commands to dump all the paritions to /sdcard
dump all the partitions
take md5's of each image for quick change detection
copy the images off-device
reboot bootloader
fastboot oem unlock (wipes device!)
reboot
re-enable ADB debugging
dump all the partitions again, to a different directory
take md5's of each new image for quick change detections
copy new the images off-device
restore a nandroid of userdata
At this point, we can use the md5's to check which partitions have changed, which are hopefully only a few. We'll discuss which ones seem "interesting", so you can zip up and send as few images as necessary. I'll run "xxd" to make hexdumps of them, and "diff" and friends to analyze them.
If we have a candidate set of changes, then you would use dd to copy back the relevant image(s) and reboot bootloader, to verify that this does indeed unlock and lock the device. If everything works, then I can change BootUnlocker to recognize the device. If things don't work, and you want an unlocked bootloader, you will need to unlock it with "fastboot oem unlock" and then restore your nandroid.
As you can see, there is a significant risk of data loss. You also need to be comfortable with fastboot, adb, and the adb/linux shell on your device. And of course, you need root.
We've got the Galaxy Nexus, Nexus 4, and Nexus 10 in the bag. The ASUS bootloader in the Nexus 7 (2012 edition) stores the lockstate using device-specific encryption; we cannot support that device. If you've got some other Nexus device and feel like some hacking, PM me and we'll see if we can figure your device out.
On the other hand, I'm not the only one who can do this work; many of us figured out the G-Nex together, on a different XDA thread. If you've already done the relevant hacking on your bootloader and know how it stores the lockstate, send me the info and I'd be happy to add it to BootUnlocker.
Reserved
This post is Reserved.
Reserved
This post is Reserved.
Looks pretty slick. Can't wait to try it out. Thanks.
thanks for this OP. sweet app
Excellent application. But a question:
Does this now also mean that a tech-savvy thief would be able to unlock the bootloader without wiping data? Assuming that my phone is rooted and I don't place a PIN on the lockscreen.
I had to backup my ROM before I jumped in feet first. Tested a lock and a unlock and I can now say it worked without a hitch. Thanks to everyone involved in the production of this APP.
LoveNFC said:
Excellent application. But a question:
Does this now also mean that a tech-savvy thief would be able to unlock the bootloader without wiping data? Assuming that my phone is rooted and I don't place a PIN on the lockscreen.
Click to expand...
Click to collapse
Yes, if your phone was rooted and you had no PIN/password the thief could use this to unlock the bootloader without wiping data. But if you were rooted with no PIN, you've got bigger problems than this app.
For example: a thief (or even a "visitor") could run Titanium Backup and then copy the backup off the device.
LoveNFC said:
Excellent application. But a question:
Does this now also mean that a tech-savvy thief would be able to unlock the bootloader without wiping data? Assuming that my phone is rooted and I don't place a PIN on the lockscreen.
Click to expand...
Click to collapse
If your phone is already rooted and you don't have a pin then the thief doesn't need to unlock, he can just walk in and help himself.
Segv11, congrats!
If the google play GNs use this to relock their bootloaders will a fastboot unlock do a wipe or will the play store devices still fail to wipe?
I don't think it will wipe. We did not even found out why it did not wipe.
Anyway OP, do state that root is requires on Play Store.
Pressed from my Galaxy Nexus.
NCguy said:
Segv11, congrats!
If the google play GNs use this to relock their bootloaders will a fastboot unlock do a wipe or will the play store devices still fail to wipe?
Click to expand...
Click to collapse
Thank you.
I don't have a Play Store GNex so I can't say for sure, but I imagine that they will still fail to wipe. All this app does is change the lock state flag in the param partition; and from our investigations on the other thread, neither the param partition, nor the bootloader, seem to control the no-wipe-on-unlock behavior of the Play Store GNexes. In fact, we weren't able to figure out where the phone stores that flag.
If we can figure out where the phone stores that little gem, I'd be happy to include a way to set/clear it in this app too.
Play Store link is live
The app is finally live on the Google Play store, for those of us who prefer the convenience of automatic updates:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Don't know how realistic this is, but I'll go ahead and request it anyways.
Would it be possible to have an option to remove the application from the app drawer, but to allow it to be launched through the dialer, in the same fashion as Cerberus?
LoveNFC said:
Don't know how realistic this is, but I'll go ahead and request it anyways.
Would it be possible to have an option to remove the application from the app drawer, but to allow it to be launched through the dialer, in the same fashion as Cerberus?
Click to expand...
Click to collapse
I actually had this on my mind
Pressed from my Galaxy Nexus.
LoveNFC said:
Would it be possible to have an option to remove the application from the app drawer, but to allow it to be launched through the dialer, in the same fashion as Cerberus?
Click to expand...
Click to collapse
Mach3.2 said:
I actually had this on my mind .
Click to expand...
Click to collapse
Not sure why it would even matter. Having an unlocked or locked bootloader makes no difference security-wise if you are booted into Android and have root.
Sent from my Galaxy Nexus using Tapatalk 2
LoveNFC said:
Don't know how realistic this is, but I'll go ahead and request it anyways.
Would it be possible to have an option to remove the application from the app drawer, but to allow it to be launched through the dialer, in the same fashion as Cerberus?
Click to expand...
Click to collapse
ChainsDD's Superuser can also do this. I would find it too inconvenient to go through the dialer, however: instead I would just get a shell and issue the same "dd" command that this app makes.
However, I've added it (Issue 27 on Google Code) to my list of desired features: perhaps the user could opt in to this feature in a preference panel.
There are other other little features I'd like to add (like the ability to reboot from within the app), and one big feature: I'd like the app to be able to flash a custom recovery without a USB connection and fastboot.
Edited: Rooted successfully. Not sure what was going wrong earlier but the following post and download links in it are comprehensive and worked for me.
Refer: http://forum.xda-developers.com/showthread.php?t=2220275
------
I have tried all the methods posted here on this site and others but am aunable to root my Lenovo p770.
I can confirm that:
1. I have preloader and USB drivers installed and the device shows up in the device manager.
2. Using SP Flash Tools, I can "read back" partitions on the device and have made backups of the boot, recovery and android.img of the stock ROM.
3. I have tried flashing recovery.img from various sources that were confirmed successful and have also geenrated my own TDRP using Varun Chitre's script but am unable to flash any of them to the device.
4. I am running all programs as administrator.
I suspect that something is preventing me from writing to the device whereas read is fine (as "read back" works). I have used multiple USB cables and running the process on 2 computers and on Win7 and WinXP ... just to be sure that there is no hardware or operating system issue. Also, while using the Bin4ry method, I get the error "permission denied (are you root)", which has been mentioned elsewhere but not resolved properly.
Is it something to do with the sec_ro partition which is preventing flashing of the device?
Please help. Other information from MTK Phone Tools which might be helpful in resolving this problem is below:
Hardware: MT6577
Model: Lenovo P770
Build number: Lenovo P770_ROW_S110_130204
Build date UTC: 20130204-071849
Android v: 4.1.1
Baseband v: P770.W12.22.SP.V15.P14. 2013/01/08 13:44
Kernel v: 3.4.0 ([email protected]) (gcc version 4.6x-google 20120106 (prerelease) (GCC) #1 SMP Mon Feb 4 15:17:37 CST 2013
Thanks in advance for your help.
RK
dear
seems you have upgraded official rom initially.try back to the previous rom then try using super one click root soft. if it helps or not.
you can try this method
http://www.needrom.com/mobile/lenovo-p770-6/
i have exactly the same ROM Lenovo P770_ROW_S110_130204 and i got it rooted using flashtools. Clockworkmod recovery and root by javum.
rk2612 said:
I have tried all the methods posted here on this site and others but am aunable to root my Lenovo p770.
I can confirm that:
1. I have preloader and USB drivers installed and the device shows up in the device manager.
2. Using SP Flash Tools, I can "read back" partitions on the device and have made backups of the boot, recovery and android.img of the stock ROM.
3. I have tried flashing recovery.img from various sources that were confirmed successful and have also geenrated my own TDRP using Varun Chitre's script but am unable to flash any of them to the device.
4. I am running all programs as administrator.
I suspect that something is preventing me from writing to the device whereas read is fine (as "read back" works). I have used multiple USB cables and running the process on 2 computers and on Win7 and WinXP ... just to be sure that there is no hardware or operating system issue. Also, while using the Bin4ry method, I get the error "permission denied (are you root)", which has been mentioned elsewhere but not resolved properly.
Is it something to do with the sec_ro partition which is preventing flashing of the device?
Please help. Other information from MTK Phone Tools which might be helpful in resolving this problem is below:
Hardware: MT6577
Model: Lenovo P770
Build number: Lenovo P770_ROW_S110_130204
Build date UTC: 20130204-071849
Android v: 4.1.1
Baseband v: P770.W12.22.SP.V15.P14. 2013/01/08 13:44
Kernel v: 3.4.0 ([email protected]) (gcc version 4.6x-google 20120106 (prerelease) (GCC) #1 SMP Mon Feb 4 15:17:37 CST 2013
Thanks in advance for your help.
RK
Click to expand...
Click to collapse
I can't even get MTK Phone Tools to read my Lenovo P770i phone
leo5354 said:
I can't even get MTK Phone Tools to read my Lenovo P770i phone
Click to expand...
Click to collapse
with adb drivers installed this should be no problem
vietchecz said:
with adb drivers installed this should be no problem
Click to expand...
Click to collapse
ADB is installed fine though, detected as ADB Interface di Device Manager
s_hri said:
dear
seems you have upgraded official rom initially.try back to the previous rom then try using super one click root soft. if it helps or not.
Click to expand...
Click to collapse
How do go back to the previous rom?
vietchecz said:
i have exactly the same ROM Lenovo P770_ROW_S110_130204 and i got it rooted using flashtools. Clockworkmod recovery and root by javum.
Click to expand...
Click to collapse
Can you please help me with detailed instructions / upload the files which helped you do this?
Thanks,
RK
This works!
http://forum.xda-developers.com/showthread.php?t=2220275
vietchecz said:
with adb drivers installed this should be no problem
Click to expand...
Click to collapse
Are you able to get it connected through ADB?
I installed the Lenovo USB driver and it is showing up us a ADB interface in the Device manager.
But when run the ADB ,the device is not getting listed -
In the phone side I emaned the USB debugging - Not P2P or Camera TP(Not connected as the
rk2612 said:
Edited: Rooted successfully. Not sure what was going wrong earlier but the following post and download links in it are comprehensive and worked for me.
Refer: http://forum.xda-developers.com/showthread.php?t=2220275
------
I have tried all the methods posted here on this site and others but am aunable to root my Lenovo p770.
I can confirm that:
1. I have preloader and USB drivers installed and the device shows up in the device manager.
2. Using SP Flash Tools, I can "read back" partitions on the device and have made backups of the boot, recovery and android.img of the stock ROM.
3. I have tried flashing recovery.img from various sources that were confirmed successful and have also geenrated my own TDRP using Varun Chitre's script but am unable to flash any of them to the device.
4. I am running all programs as administrator.
I suspect that something is preventing me from writing to the device whereas read is fine (as "read back" works). I have used multiple USB cables and running the process on 2 computers and on Win7 and WinXP ... just to be sure that there is no hardware or operating system issue. Also, while using the Bin4ry method, I get the error "permission denied (are you root)", which has been mentioned elsewhere but not resolved properly.
Is it something to do with the sec_ro partition which is preventing flashing of the device?
Please help. Other information from MTK Phone Tools which might be helpful in resolving this problem is below:
Hardware: MT6577
Model: Lenovo P770
Build number: Lenovo P770_ROW_S110_130204
Build date UTC: 20130204-071849
Android v: 4.1.1
Baseband v: P770.W12.22.SP.V15.P14. 2013/01/08 13:44
Kernel v: 3.4.0 ([email protected]) (gcc version 4.6x-google 20120106 (prerelease) (GCC) #1 SMP Mon Feb 4 15:17:37 CST 2013
Thanks in advance for your help.
RK
Click to expand...
Click to collapse
Hello,, can i have a copy of your boot.img please,, shouldve backed up mine before messing around
I use framaroot, easier than other : http://forum.xda-developers.com/showthread.php?t=2130276
Hello guys,
I got a big problem.
A friend of mine came with his Note 2 with MIUI and wanted me to put a stock rom back onto his device.
So I downloaded the lates Kies-compatible Rom for my Country from samfirmware.com and flashed it via Odin.
Everything went alright, but now the IMEI is 0049xxx?
On MIUI the IMEI was alright, but now on the Stock its gone?
Any idea how to fix this?
I didnt think that an odin flash would destroy an imei ever, so we didnt make an extra backup of the efs, and unfortunately there was also none on the sd...
So now I'll try to root and grab a backup of the efs folder now and try to restore it somehow.
Or can this be caused by rom compatibility issues? Like if i flash the "right" original rom that this fixes it?
===========
Last update:
Flashed the latest Stock DBT 4.1.2 Firmware from June 2013 with DME4 Modem and then the phone had its imei back.
Mustve been caused by incompatible modem im sure.
zroice said:
Hello guys,
I got a big problem.
A friend of mine came with his Note 2 with MIUI and wanted me to put a stock rom back onto his device.
So I downloaded the lates Kies-compatible Rom for my Country from samfirmware.com and flashed it via Odin.
Everything went alright, but now the IMEI is 0049xxx?
On MIUI the IMEI was alright, but now on the Stock its gone?
Any idea how to fix this?
I didnt think that an odin flash would destroy an imei ever, so we didnt make an extra backup of the efs, and unfortunately there was also none on the sd...
So now I'll try to root and grab a backup of the efs folder now and try to restore it somehow.
Or can this be caused by rom compatibility issues? Like if i flash the "right" original rom that this fixes it?
Click to expand...
Click to collapse
maybe u must have flashed new modem try rooting it again and installing miui again or try installing older rom 4.1.1
KaranBhoir said:
maybe u must have flashed new modem try rooting it again and installing miui again or try installing older rom 4.1.1
Click to expand...
Click to collapse
argh well so far I tried rooting and getting efs folder backup (even if its now corrupted there are the bak files) and then tried to restore with efspro but without success.
Downgraded to 4.1.1, same procedure, no success.
Then I wanted to use nandroid backup on the phone (of the miui afaik), but its not complete and cant be restored.
Starting to get frustrated and worried.
---
The problem is also that I don't know what original rom was on the phone - I guess 4.1.1, but which?!
Is there any way to find that out? My friend is kinda clueless about all this stuff and can't tell me what he had on.
Only thing he knows that he had 4.1.1 MIUI on before. I guess I try that.
well here i got the nv.log - it doesnt say anything about an error or something (on my searches I found that usually there are errors reported if the efs is corrupted) - so the efs should be actually intact or at least the bak or?
Code:
Sun Jan 1 00:02:03 2012: nv data does not exist
Sun Jan 1 00:02:03 2012: default NV restored
Sun Jan 1 00:02:11 2012: OFFSET_FOR_PRESET2 writing input
Sun Jan 1 00:02:11 2012: 2nd NV built
Sun Jan 1 00:02:12 2012: NV data back-uped
Sun Jan 1 00:08:35 2012: check off
Sun Jan 1 00:00:02 2012: check off
Mon Feb 18 16:11:55 2013: 2nd NV built
Mon Feb 18 16:11:55 2013: NV data back-uped
Mon Feb 18 16:11:55 2013: check on
Sun Jan 1 00:02:50 2012: check off
Sun Jan 1 00:03:14 2012: 2nd NV built
Sun Jan 1 00:03:14 2012: NV data back-uped
Sun Jan 1 00:03:14 2012: check on
Sun Jan 1 00:11:58 2012: fail - no checksum info
Sun Jan 1 00:11:58 2012: NV restored
Sun Jan 1 00:14:41 2012: OFFSET_FOR_PRESET1 writing input
Sun Jan 1 00:14:41 2012: 2nd NV built
Sun Jan 1 00:14:42 2012: NV data back-uped
Sun Jan 1 00:14:56 2012: OFFSET_FOR_PRESET2 writing input
Sun Jan 1 00:14:56 2012: 2nd NV built
Sun Jan 1 00:14:56 2012: NV data back-uped
Sun Jan 1 00:14:59 2012: OFFSET_FOR_PRESET2 writing input
Sun Jan 1 00:15:00 2012: 2nd NV built
Sun Jan 1 00:15:00 2012: NV data back-uped
Tue Jun 18 11:01:01 2013: input from cp
Tue Jun 18 11:01:01 2013: 2nd NV built
Tue Jun 18 11:01:01 2013: NV data back-uped
Mon Jul 22 20:06:21 2013: OFFSET_FOR_PRESET2 writing input
Mon Jul 22 20:06:21 2013: 2nd NV built
Mon Jul 22 20:06:21 2013: NV data back-uped
But why in hell does it not work then lol?
The Mon Jul 22 is my flash attempt of the stock rom, then right after imei was 0049 i rooted and pulled this efs.
Please someone help.
I think it might have to do with wrong modem firmware? But unfornutately I can't figure out what was on that thing originally.
Flashing over MiUI didnt help either.
As much as I love samsung, this efs sh*t really is annoying as hell. (I once tried to unsuccessfully revive a S3 before, and I had to give up frustrated eventually...)
Grmpf
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