Hi,
Long time reader, first time poster...
I've got a K1 tablet and I've been trying to flash the rom but I keep getting the same message.
I've tried 4 different ROMS with the same result.
It is limping along with RR ROM but I can't even get stock ROM on it now.
It is a K1 for sure and I've been very careful about the files i'm trying to flash are for the K1.
From the look of the message it seems as though the device description is NULL
Thank You for any help
{
"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"
}
Been trying to fix this myself all day. as long as you're certain you have the right ROM (and it looks like you do) and that you're on the right bootloader, you can simply remove all of the checks in the installer and force it to install even though it thinks it's the wrong device.
using 7zip, open the archive of the zip you're going to edit, find META-INF, com, google, android and right click/edit updater-script.
remove "
assert(getprop("ro.product.device") == "shieldtablet" || getprop("ro.build.product") == "shieldtablet" || getprop("ro.product.name") == "shieldtablet" ||
abort("This package is for \"shieldtablet\" devices; this is a \"" + getprop("ro.product.device") + "\".");"
Also try different TWRP versions. Some of the latest for this device are problematic (stuff like not showing the micro sd card inside TWRP even if it is formated as fat32) and also give strange errors.
If the latest one isn't working, try the previous one from https://dl.twrp.me/shieldtablet/ (twrp-3.5.0_9-0-shieldtablet.img works fine for me, while 3.5.1 does not), or for certain older custom ROMs based on the stock ROM an even older TWRP before that may work better.
When you find a stable TWRP that works with your favourite ROM then you should be fine.
ogremalfeitor said:
Also try different TWRP versions. Some of the latest for this device are problematic (stuff like not showing the micro sd card inside TWRP even if it is formated as fat32) and also give strange errors.
If the latest one isn't working, try the previous one from https://dl.twrp.me/shieldtablet/ (twrp-3.5.0_9-0-shieldtablet.img works fine for me, while 3.5.1 does not), or for certain older custom ROMs based on the stock ROM an even older TWRP before that may work better.
When you find a stable TWRP that works with your favourite ROM then you should be fine.
Click to expand...
Click to collapse
I can confirm that latest versions (3.5.1) does not work properly with our tablets. 3.5.0 does.
@ogremalfeitorThank you.
I had given up on this until today when I found my k1 behind the couch and decided to give it another shot. I remembered/googed the problem and I was psyched to finally see "somebody else" with the same problem.
Then I realized it was my thread.
Goofball. Still laughing at the absurdity.
Anyway, I wanted to immediately thank you for the advice with such an old tablet.
Tune in next week when I exhume my TF101 from under the bureau.
Joeysaur said:
Been trying to fix this myself all day. as long as you're certain you have the right ROM (and it looks like you do) and that you're on the right bootloader, you can simply remove all of the checks in the installer and force it to install even though it thinks it's the wrong device.
using 7zip, open the archive of the zip you're going to edit, find META-INF, com, google, android and right click/edit updater-script.
remove "
assert(getprop("ro.product.device") == "shieldtablet" || getprop("ro.build.product") == "shieldtablet" || getprop("ro.product.name") == "shieldtablet" ||
abort("This package is for \"shieldtablet\" devices; this is a \"" + getprop("ro.product.device") + "\".");"
Click to expand...
Click to collapse
That did the trick.
Related
hey
if you want to install cm11 lets say and the rom is for i9070 only and you want to install the same rom but for i9070p version so read the instructions below how to do it
first download all of these stuff
CWM Recovery http://sh.st/5X0d
Odin http://sh.st/5X0L (if you have rom of samsung dont download this)
stock rom http://sh.st/5Xqg (if you have stock rom of samsung installed on ur phone dont download this too)
gaaps and cm11(or whatever rom ur using) http://sh.st/5XqI
tee flashable folder http://sh.st/5Xq5
Notepad++ http://sh.st/5Xia
okay after you downloaded all the stuff
open the cm-11-20140209-UNOFFICIAL-janice.zip (or whatever rom you want to install on) and go to META-INF/com/google/android/
now try to open the updater-script file with notepad++ (DO NOT OPEN IT WITH ANY OTHER PROGRAM EVEN WITH WINDOWNS NOTEPAD)
and delete the 3 first lines of the text and save it
the lines are (sometimes theyre written only on one line, just delete this text from the file..)
Code:
assert(getprop("ro.product.device") == "janice" || getprop("ro.build.product") == "janice" ||
getprop("ro.product.device") == "i9070" || getprop("ro.build.product") == "i9070" ||
getprop("ro.product.device") == "GT-I9070" || getprop("ro.build.product") == "GT-I9070" || abort("This package is for \"janice,i9070,GT-I9070\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
now put this zips in your phone sd card update.zip,9070PJBlibteefolderCM10.zip,gapps-kk-20140105-signed.zip,(ur rom)cm-11-20140209-UNOFFICIAL-janice.zip
IF YOU DONT HAVE THE STOCK ROM INSTALLED FOLLOW THIS STEPS
go to recovery mode and wipe ur phone
open download mode
extract odin somewhere on ur pc. open odin.exe and select the PDA and extract the stock rom (DTM-I9070PXXLPJ-20130926140749.zip) with the two files .dll and .mp5 then click on PDA, then find the .mp5 file that you have extracted and select him. make sure the auto reboot and reset time is selected like on this screenshot (make sure that everythings the same as in the screenshot only they 0:[COM8] needs to be 0:[COM5] so just ignore it)
{
"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"
}
then click on start and wait until ur phone will reboot and wait for the phone to start working (DONT DISCONNECT THE USB FROM THE PC WHEN UR INSTALLING THE ROM)
IF UR ALREADY GOT THE STOCK INSTALLED ON UR PHONE FOLLOW THIS STEPS (whos just installed the stock follow this steps too)
open recovery and select install zip from external storage and select sd card (I dont remember the name just select the sd card )
select update.zip and choose yes (install cwm)
wipe ur phone(however the rom requires to)
select install zip from sdcard and chose the first option (its select from sdcard i think) and install the cm-11-20140209-UNOFFICIAL-janice.zip(ur rom) and select yes
after its will finish install 9070PJBlibteefolderCM10.zip
reboot ur phone and now go again in to the recovery and install the gapps-kk-20140105-signed.zip
if some thing is goes wrong you can install the stock again with odin and try again
im not responsible for any kind of phone damage
volume 9070p
i installed it for 9070p with your instructions now i have 2 problem about this rom
1. volume is so low (only speaking with phone)
2. battery about 1 day (before 2-3 days)
thansk for your help
fatihakar75 said:
i installed it for 9070p with your instructions now i have 2 problem about this rom
1. volume is so low (only speaking with phone)
2. battery about 1 day (before 2-3 days)
thansk for your help
Click to expand...
Click to collapse
yea.. bump
and i dont know if you still care about it but its aint my problem and ask the rom creator why its like that
Hey,
So this is my first foray into this sort of thing. I have some computer background but I haven't really gotten into this sort of stuff.
I have an Asus Eepad Transformer T101. I was requested to load Android 6.0 on it.
I followed this thread:
http://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496
I had to learn some things my way. User Debugging was on but I couldn't flash recovery. I ended up finally flashing recovery (I forget what step I had to do to use Clockwork Mod Recovery).
Once I was into CWM I had E:\Cannot Mount \sdcard\.
I then found out I had to use a micro SDcard, fine.
I couldn't load anything, and no solutions were working for getting SDcards to work.
I found a thread through google that said to use SD Formatter, to no avail.
Then I found this:
http://www.transformerforums.com/fo...x-bootloops-soft-bricks-all-ics-firmware.html
I have the files and. It was a batch file that loaded ADB then I could flash recovery. I attempted to flash recovery and I got to rogue XM recovery 1.5.0 (CWM - based recovery v5.0.2.8)
I used Nandroid Backup (Note, still could not mount SDcards)to do a backup of everything to the internal storage. I then did a wipe of all user data.
I have a folder called Marshmellow with Katkiss-6.0_025.zip, open_gapps-arm-6.0-pico-20160219.zip and BETA-SuperSU-v2.52.zip.
I attempted to install the KatKiss one, and it failed saying:
"Installing Update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/marshmellow/katkiss-6.0_025.zip
(Status 7)
Installation aborted."
So here's where I'm pretty sure I screwed up.
I loaded the Gapps and SuperSU.
Tried marshmellow again, and no luck.
Now the device boots to the eepad transformer screen, lasts a few seconds (usually no more than 10) and then reboots.
I've tried
http://forum.xda-developers.com/showthread.php?t=1688012
and
http://justanotherdave.ca/?p=351
The latter simply doesn't work. And I don't think I can get into ABX mode for the former.
Are there any resources on how to "unbrick" the device that may still work. Right now it just keeps rebooting at the nvidia eepad screen. I can get into recovery still.
Hello and thank you for using XDA Assist,
Please ask in our Android Q&A section:
Android Q&A, Help & Troubleshooting
Kind regards and good luck
{
"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"
}
Trafalgar Square
XDA Assist
Hi all,
I installed the official OnePlus One Official Lineage OS 15.1 update on my OnePlus One Beacon.
However, when I installed it, I removed that check string from the updater-script to pass the validation there, because I was getting an error: "This package is for device: beacon,A0001; this device is ."
Now, the same error occurs every time when I try to update it via the Lineage OS Update
{
"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"
}
Any ideas how I can resolve this issue?
My TWRP version: 3.1.1-0
edit - I thought it was during the first time flash
superKalo said:
Hi all,
I installed the official OnePlus One Official Lineage OS 15.1 update on my OnePlus One Beacon.
However, when I installed it, I removed that check string from the updater-script to pass the validation there, because I was getting an error: "This package is for device: beacon,A0001; this device is ."
Now, the same error occurs every time when I try to update it via the Lineage OS Update
Any ideas how I can resolve this issue?
My TWRP version: 3.1.1-0
Click to expand...
Click to collapse
you can go into the zip file,
in META-INF/com/google/android/android-script
you will see a in here something like
Code:
assert(getprop("ro.product.device") == "bacon" || getprop("ro.build.product") == "bacon" ||
getprop("ro.product.device") == "A0001" || getprop("ro.build.product") == "A0001" || abort("E3004: This package is for device: bacon,A0001; this device is " + getprop("ro.product.device") + "."););
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109","TZ.BF.2.0-2.0.0123","TZ.BF.2.0-2.0.0134") == "1");
ui_print("Target: oneplus/bacon/A0001:6.0.1/MHC19Q/ZNH2KAS1KN:user/release-keys");
ifelse(is_
remove
Code:
assert(getprop("ro.product.device") == "bacon" || getprop("ro.build.product") == "bacon" ||
getprop("ro.product.device") == "A0001" || getprop("ro.build.product") == "A0001" || abort("E3004: This package is for device: bacon,A0001; this device is " + getprop("ro.product.device") + "."););
this will remove all checks so be careful, make sure its the correct file for correct phone
Fixed for me
https://forum.xda-developers.com/showpost.php?p=78168481&postcount=13
stevieag said:
you can go into the zip file,
in META-INF/com/google/android/android-script
you will see a in here something like
Code:
assert(getprop("ro.product.device") == "bacon" || getprop("ro.build.product") == "bacon" ||
getprop("ro.product.device") == "A0001" || getprop("ro.build.product") == "A0001" || abort("E3004: This package is for device: bacon,A0001; this device is " + getprop("ro.product.device") + "."););
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109","TZ.BF.2.0-2.0.0123","TZ.BF.2.0-2.0.0134") == "1");
ui_print("Target: oneplus/bacon/A0001:6.0.1/MHC19Q/ZNH2KAS1KN:user/release-keys");
ifelse(is_
remove
Code:
assert(getprop("ro.product.device") == "bacon" || getprop("ro.build.product") == "bacon" ||
getprop("ro.product.device") == "A0001" || getprop("ro.build.product") == "A0001" || abort("E3004: This package is for device: bacon,A0001; this device is " + getprop("ro.product.device") + "."););
this will remove all checks so be careful, make sure its the correct file for correct phone
Click to expand...
Click to collapse
Just to be clear - I am encountering this error when I try to update via the LineageOS OTA Updater. You suggest I download the latest .zip and manually install it (via TWRP I guess), right? Does this mean it will wipe out all the data I have on my device?
TWRP identifies your device as null (ie. blank, no name, etc). Have you tried updating TWRP to a newer version?
I had the same issue, but didn't have to do anything listed above as it seems the issue may have been with TWRP as things went so far sideways after updating TWRP eventually the phone wouldn't even boot beyond the OnePlus "splash" screen.
Solution? Reflash the latest version of TWRP via Fastboot, reboot, then the official OTA updates work again and my wonderful OPO is now on today's Lineage 15.1 update with AdAway and Magisk happily churning away in the background.
Edit: Today's update went in smoothly as well, so it looks like the issue may have been with TWRP. It seems it was for me anyway.
technochronic said:
I had the same issue, but didn't have to do anything listed above as it seems the issue may have been with TWRP as things went so far sideways after updating TWRP eventually the phone wouldn't even boot beyond the OnePlus "splash" screen.
Solution? Reflash the latest version of TWRP via Fastboot, reboot, then the official OTA updates work again and my wonderful OPO is now on today's Lineage 15.1 update with AdAway and Magisk happily churning away in the background.
Edit: Today's update went in smoothly as well, so it looks like the issue may have been with TWRP. It seems it was for me anyway.
Click to expand...
Click to collapse
Perfect! Thank you so much!!! That fixed it!
I just reflashed the latest TWRP (v3.2.3-0-bacon) and the issue is resolved!
superKalo said:
Perfect! Thank you so much!!! That fixed it!
I just reflashed the latest TWRP (v3.2.3-0-bacon) and the issue is resolved!
Click to expand...
Click to collapse
You're welcome
Congrats... BTW, you would not have lost your data etc with my solution.
superKalo said:
Perfect! Thank you so much!!! That fixed it!
I just reflashed the latest TWRP (v3.2.3-0-bacon) and the issue is resolved!
Click to expand...
Click to collapse
The same here. After upgraded TWRP to 3.2.1-K2 I get solved the problem.
Thank you.
{
"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"
}
About LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
Join my telegram channel to get latest updatesUMIDIGI A5 Pro Updates
Whats working?
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Access point
Bluetooth
Video Playback
Audio
Sensors
Flash
GPS
Fingerprint
Camera
Offline charging.
Known Issues?
VoLTE does not work (and probably won’t work on any MTK device with custom ROMs any time soon) due to MTK’s proprietary extensions.
Links
LOS - Download
OpenGApps - Download
NikGApps - Download
TWRP - Download
Magisk - Download
Installation
Be sure to be on the latest stock firmware!
Wipe->Wipe Data->yes
Wipe->Advanced Wipe->Wipe System,Cache
Reboot Recovery
Install Zip->SD Card->Lineage-OS-breeze-Unofficial.zip
Install Zip->SD Card->NikGapps-basic-arm64-10-signed.zip or open_gapps-arm64-10.0-pico.zip
Install Zip->SD Card->Magisk.zip
XDAevDB Information
Lineage OS, ROM for the UMIDIGI A5 Pro/breeze
Contributors
Hadenix
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: Lineage OS
Version Information
Status: stable
06.02.2020
NOTE: NEED A CLEAN INSTALL
Adaptation of the status of the bar to the cutout;
Added camera from f2 modified by me, translation into Russian. Wide-angle module works;
New fix for network and incoming calls;
Call recording
Source code update;
Thanks for the very good instructions.
Easy installation exactly as specified. Setup with transfer of data from the gmail address from the cloud was also easy. So far - all good.
Unfortunately after the first reboot or power down and restart I get a loop with the start screen. The TWRP recovery boots again after about 5-6 minutes.
I need help.
PS: Original software was UMIDIGI_A5_Pro.E_V1.6_20200102. I installed the TWRP_3.3.1_20191020_Hadenix-Breeze_E.img.
Tried to take the latest TWRP_3.3.1_20200219_Hadenix-breeze.img, but it doesn't have 4GB RAM / 32 GB ROM, but 4 GB RAM / 8 GB ROM, so back to the old one.
11.04.2020
NOTE: NEED A CLEAN INSTALL
- Update FCamera (updated translation, updated IKO mode: instead of information in Chinese, Russian from Yasha)
- Changed the device name from "breeze" to "A5_Pro" as on the drain now
- Update battery capacity
- Fixed ignoring: framework-res__auto_generated_rro.apk
- Removed DummyOverlay
- Configuration included: PRODUCT_DEXPREOPT_SPEED_APPS
- Updated GMS: Android-Umidigi
- Build libraries from Mediatek (it is better to use the MTK IMS extension instead of the ril-lib fix)
- fixed animation
- Coral Fingerprint Update
- Off charging fixed
- Updated sources, with the April patch
- Advanced network type
16.04.2020
NOTE: NEED A CLEAN INSTALL
* Update source
* New Snap Camera
* Adding “SafailNet”
* Switch to Pixel 4 XL (flame) fingerprint (device certification in the market passes)
* Setting the correct RIL path (for Vendor)
* assembly libRSDriver_mtk
* Add IMS debug details bypassing CarrierConfig restrictions
* IMS: separate ims-ext-common from boot flasks
* New CameraGo instead of Fcamera (can be installed separately)
* overlay: enable a tactile text cursor.
* Build the system version of liveisplay from mtk
* Adding memory optimization
Why its checking two times the same?
Code:
getprop("ro.product.device") == "A5_Pro" || getprop("ro.build.product") == "A5_Pro"
Shouldnt it be?:
Code:
getprop("ro.product.device") == "A5_Pro" || getprop("ro.build.product") == "A5_Pro_E"
Can you make it work with the EU version of the smartphone?
When installing, you get this error message:
"This package is for device A5_Pro this devices is A5_Pro_E"
Hi guys,
first of all I want to thank @Hadenix for the great work.
So, I've been trying to install the rom for a couple of days. First try I messed up and ended installing the stock rom wiht SPFT. Yesterday I thought I finally got it right, no errors in TWRP whatsoever, but when I hit Reboot system the phone goes to fastboot mode. Have any of you guys had this outcome?
Any help would be much appreciated.
Regards!
@estebanj1980 Same issue, it is something to do with the updater-script and should have produced an error 7. Which I think is causing the fastboot loop. I tried deleteing the offending line, and still got an error. Not sure what else it is supposed to read
when I get motivated again, gonna try @Spillunke code.
Oddly, I can install HAVOK perfectly without a hitch. I tried for two days solid (weekend) for hours on end with lineage OS 17.x, and all I could get was a fastboot loop.
anyone else has any suggestions?
finally got it working. Reading closer, I put the stock rom back in, then rewiped LEAVING THE VENDOR alone.
then following instructions by @Hadenix :
Hadenix said:
Be sure to be on the latest stock firmware!
Wipe->Wipe Data->yes
Wipe->Advanced Wipe->Wipe System,Cache
Reboot Recovery <-- I did dnot do this, still installed fine
Install Zip->SD Card->Lineage-OS-breeze-Unofficial.zip <-- make sure you are using the "breeze" version. The others give you fastboot loop
Install Zip->SD Card->NikGapps-basic-arm64-10-signed.zip
Install Zip->SD Card->Magisk.zip
Click to expand...
Click to collapse
However I had bad luck with open gapps, so used NikGapps instead. worked great.
Also, there is an excruciatingly long wait from the title screen, So do not panic, could be as long as 10min the first time.
Perseverance paid off!
Spillunke said:
Why its checking two times the same?
Code:
getprop("ro.product.device") == "A5_Pro" || getprop("ro.build.product") == "A5_Pro"
Shouldnt it be?:
Code:
getprop("ro.product.device") == "A5_Pro" || getprop("ro.build.product") == "A5_Pro_E"
Click to expand...
Click to collapse
Hi spillunke , i have the eu version , will it work by doing that change?
I have add the line below and i was able to flash this rom for my A5 EU edition A5_PRO_E
getprop("ro.product.device") == "a5_pro_e" || getprop("ro.build.product") == "a5_pro_e"
but it looks like the rom is not fully compatible with the EU version , it's unstable on my mobile. the pixel ui and google play keeps crashing
@Hadenix great respect for the amount of work I found there
I have a trouble when I try to connect wifi using lineage OS 17.1 ROM for UMIDIGI A5 Pro (same with crDroid Android 11 ROM). I follow all recommandations, flashing comes good and so on... but wifi connection freezes screen and fails when I try to. Do you have any idea to overpass this issue please?
Note : initial ROM is UMIDIGI A5 Pro (EU) V1.6_20200102 where wifi connects perfectly
when I flash V2.0_20210326 ROM, I get same issue connecting wifi
update errors... 'This package is for "rk3368" devices; this is a "PX5" '
Trying to update my unit from Android 8 to Android 9. Tried the simple and direct update but it failed. But, I didn't get the black screen. So, I made the bootable sdcard and tried that way. SD card runs, does it's thing, says it was successful and tells me to remove it to reboot. When I do, it goes to a black screen and nothing else. Even after leaving it sit for 30min. That SD flash process was waaaay fast for it to have actually flashed the image.
Now, I can't get the unit to do anything without that SD card.
I have found that if I pop the SDcard out between the logo screen and when the flash process starts it errors and takes me to recovery. From there, I've tried many different roms. Hal9k versions, Malaysk versions, stock 8.0, ota 9.0 for my device, and even a 6.1.1 version.
After going to "Installing update..." most give me an error "Warning: No file_contextsE3004: This package is for "rk3368" devices; this is a "px5"" then a couple of other errors before a (Status 7) Installation aborted.
All the roms that didn't do that have some kind of signature error. Likely need to redownload but haven't tried yet.
Not really sure what to try from here...
The device had the MCU of MTCE_GS_V3.01_3 when I started. I was able to update it to MTCE_GS_V3.40
The original build number was px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.201812222.104950 test-keys though I suspect that doesn't really matter.
Couple photo screenshots.
First one is the error.
Second is what it says after the bootable sdcard runs. I see nothing there about installing the update.zip
Last is what I get sometimes if I eject the ad card too soon trying to get to the recovery menu.
{
"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"
}
Sent from my Redmi Note 7 using Tapatalk
And... I fixed it.
Didn't find anything for this error using the search here. Did a search on google and it linked me to a post on this thread https://forum.xda-developers.com/an...5-mtcd-e-head-unit-discussion-thread-t3929597
A reply told the user having the same problem to follow the SD card instructions at the beginning of the thread.
Instructions were the same as what I already followed but the file linked in the first post is different.
So, went through the process again. Installed that recovery and then was able to actually flash Android 9 onto mine.
Now for the fun part of getting everything configured and decide if this custom rom is the rom for me, if I go with the other one, or if I go to a more stock one. Least I can listen to the radio again...