Database Info

[Q] E:Error executing updater binary in zip...

hello, hope you guys can help me out:
everytime i try to flash trickdroid, viperones or zenROMplus i get the same similar error in TWRP which looks like this:
Updating parition details...
Formatting Cache using mke2fs...
Done.
Formatting Data using mke2fs...
Wiping Internall SDcard
Updating parition details...
Installing '/sdcard/TrickDroid_9.0.0.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
=======================
|Welcome to TrickDroid!|
|by torxx |
=======================
Formatting paritions...
E:Error executing updater binary in zip '/sdcard/Trick
Error flashing zip '/sdcard/TrickDroid_9.0.0.zip'
Updating partition details...
i have no problems flashing CM10 or CM10.1 nightly.
whats wrong with that?
Ville (s4) (o2 branding)
unlocked
s-off
hboot 2.13.0000
radio 1.11.50.05.28
TWRP v2.5.0.0

Flashing the Sense ROMs like TrickDroid or zenROM+ doesn't work in TWRP versions above 2.3.3.0.
Don't ask me why, but it doesn't work. You can temporarily flash it in an older recovery
fastboot boot recoveryname.img

Aah ok thanks! Didnt know that this was a well known problem with twrp v2.5+, because i didnt find such an error on google. Could u tell which recovery i should use? CWM or better lower twrp version? Is a twrp version lower than 2.3 buggy or fine?

turnschuh said:
Aah ok thanks! Didnt know that this was a well known problem with twrp v2.5+, because i didnt find such an error on google. Could u tell which recovery i should use? CWM or better lower twrp version? Is a twrp version lower than 2.3 buggy or fine?
Click to expand...
Click to collapse
TWRP 2.3.3.0 is the beat IMO. It works fine for me and is very stable.
Sent from my One S using Tapatalk 2

Ah, that explains the issue I've been having recently. Thanks for the help! I reverted to 2.3.3 and was able to get viper to flash again. I haven't noticed any difference between 2.3.3 and 2.5 on this device. Are there any downsides to keeping 2.3.3 for the foreseeable future?

HOSer_hut said:
Ah, that explains the issue I've been having recently. Thanks for the help! I reverted to 2.3.3 and was able to get viper to flash again. I haven't noticed any difference between 2.3.3 and 2.5 on this device. Are there any downsides to keeping 2.3.3 for the foreseeable future?
Click to expand...
Click to collapse
It's quicker to wipe on the newer one, but other than that it's the same. (Save for a few UI elements)
Sent from my One S using Tapatalk 2

The major change is the addition of otg in versions above 2.4
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2

Thank you guys. i was able to flash it with CWM Now i want twrp 2.3.3.0 but didnt find any download link on the official site nor on trusted sites like this forum. Can someone help me out again? (last question from me in this thread^^) thanks in advance!

turnschuh said:
Thank you guys. i was able to flash it with CWM Now i want twrp 2.3.3.0 but didnt find any download link on the official site nor on trusted sites like this forum. Can someone help me out again? (last question from me in this thread^^) thanks in advance!
Click to expand...
Click to collapse
On the TWRP website, search for Ville and you'll find all the previous versions (not the goo.im app link)

oh lol yea found it thanks, think im blind sometimes..

Yes!! Back in action
Awesome! So glad I stumbled onto this thread. The Google searches were all coming up with nothing until this one. I was using 2.6.1.0 when I initially had this issue then upgraded to 2.6.3.0 hoping that would resolve but nothing. Rolled back to 2.3.3.0 and now I'm good to go :good:
Just FYI, to anyone else that comes after me this fix worked for me and I'm using a T-Mo Galaxy S2 so this fix is not device-specific.

The issue I'm running into is that I can't figure out how to revert to 2.3.3.0. I'm using 2.6.0.0 and in the cmd prompt I type "fastboot erase cache" and then "fastboot flash recovery xxxxxx.zip". But when I do that I'm forever stuck in fastboot until I flash 2.6.0.0 again. It's like my HOX+ is married to that version and can't use anything else. Any help would be greatly appreciated.

aaron79att said:
The issue I'm running into is that I can't figure out how to revert to 2.3.3.0. I'm using 2.6.0.0 and in the cmd prompt I type "fastboot erase cache" and then "fastboot flash recovery xxxxxx.zip". But when I do that I'm forever stuck in fastboot until I flash 2.6.0.0 again. It's like my HOX+ is married to that version and can't use anything else. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Fasboot flashing needs to be .img not .zip
extract your 2.33 zip so that you can flash the .img
fastboot flash recovery recovery.img (typing the name of recovery.img)
or download the img file from twrp website
http://teamw.in/project/twrp2
click on the "get twrp for your device" on the right and follow the links to the version you want for your particular brand of phone.

tivofool said:
Fasboot flashing needs to be .img not .zip
extract your 2.33 zip so that you can flash the .img
fastboot flash recovery recovery.img (typing the name of recovery.img)
or download the img file from twrp website
click on the "get twrp for your device" on the right and follow the links to the version you want for your particular brand of phone.
Click to expand...
Click to collapse
Thanks for the reply, tivo. My mistake on the .zip. I meant .img. I made sure to download the correct version, but still have the same issue. I just get stuck on the white HTC development screen. So, I can get into bootloader and TWRP (2.6.0.0 only), but can't flash ROMs. I'm just stuck with no OS and can't seem to find a work-around. My bootloader says Tampered and Unlocked/S-On. I did, however, use an unlock guide for the One X by accident, instead of the X+. That is the only thing I can think that would cause my troubles...

charliearthur said:
Awesome! So glad I stumbled onto this thread. The Google searches were all coming up with nothing until this one. I was using 2.6.1.0 when I initially had this issue then upgraded to 2.6.3.0 hoping that would resolve but nothing. Rolled back to 2.3.3.0 and now I'm good to go :good:
Just FYI, to anyone else that comes after me this fix worked for me and I'm using a T-Mo Galaxy S2 so this fix is not device-specific.
Click to expand...
Click to collapse
sorry how to revert back? I have TWRP 2.5.0.0
Edit:Nevermind I found out, but that wasn't the case for me I'm trying to flash liquid jb v2.37 and after I downgraded twrp ,I've still got an error (error 7)...

How do i get 2.3.3 when the goo.im page only goes back to 2.5 for my device? Also is this solution still relevant for flashing an AOKP 4.4 kit kat nightly rom on the Sprint HTC One (m7wls/m7spr)

usaff22 said:
TWRP 2.3.3.0 is the beat IMO. It works fine for me and is very stable.
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
tried to find this on the link for a T-Mobile phone, but it only has nexus 7. So I googled it and every carrier seems to have the previous versions on techerrata EXCEPT T-Mobile.
Any help would be appreciated

Learnerspermit said:
tried to find this on the link for a T-Mobile phone, but it only has nexus 7. So I googled it and every carrier seems to have the previous versions on techerrata EXCEPT T-Mobile.
Any help would be appreciated
Click to expand...
Click to collapse
If you just search [ville] on the TWRP website, it should have the One S recovery you need. It doesn't matter if you have the T-Mobile of the International version.

usaff22 said:
If you just search [ville] on the TWRP website, it should have the One S recovery you need. It doesn't matter if you have the T-Mobile of the International version.
Click to expand...
Click to collapse
Sorry for not mentioning that part as well.
Went to the TWRP site and see NO SEARCH ENGINE, nor anything there that says Ville. Nor Googling TWRP ville.

Learnerspermit said:
Sorry for not mentioning that part as well.
Went to the TWRP site and see NO SEARCH ENGINE, nor anything there that says Ville. Nor Googling TWRP ville.
Click to expand...
Click to collapse
On the TWRP site, look for the "Get TWRP for your device" button in the upper right hand corner. Then that should bring up the search function:
{
"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"
}

[TOOL] Lock/Unlock Bootloader + Remove Tampered | Aroma GUI

This tool will allow you remove the Tampered flag from your bootloader. It will also allow you to easily Lock and Unlock your Bootloader directly from recovery.
No root required since it is run in recovery, however you still must be S-OFF.
Before using this tool you need to be sure you are using the latest version of recovery as the M7 U/UL TWRP requires at least version 2.6.3.3 for this package to work. The current downloads for both CWM and TWRP can found below:
The latest M7 U/UL TWRP can be downloaded HERE.
The latest M7 U/UL CWM can be downloaded HERE.
***[UPDATE] - It seems that the latest TWRP 2.6.3.3 has been pulled due to some minor issues. If your TWRP version doesn't work please use CWM for now until a updated TWRP release is made.
This will work for Verizon and Sprint as well, however they have different versions of these recoveries, so please make sure you are using the correct recovery for your device.
Saying this again in case you missed it: YOU MUST BE S-OFF!
To use the tool simply copy the zip file to your phone and then boot to your custom recovery and choose install. Then browse to where you copied the file and select it. The aroma installer will begin. Follow the steps outlined in the pictures below and choose the options you want to run.
{
"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"
}
Now you can just keep this file on your phone and Lock and Unlock at anytime without a PC and without losing data.
***Credits***
S-trace for originally discovering the location of the lock status flag. See this thread.
scotty1223 for his ADB shell commands. Threads HERE and HERE. Scotty was also very helpful to me in understanding some of the default values.
Just to be clear I did not just copy and paste scotty1223's commands into a aroma installer. The echo command can be problematic in aroma, so I developed original code for all four commands. The end result is the same in that the data in the partitions is changed as needed.
***Download***
Guru Bootloader Reset Tool
md5: fdb8264a8f4741bae22939cd7734f7c2
Enjoy!
If this helped you out please consider a small donation or just a thanks would be great.

Demo and Troubleshooting
Demo Video:
***Troubleshooting***
If the installer stays on this screen fore more than a few seconds, then it means you need to delete/format cache. This can be done within both recoveries. You may need to reboot recovery after clearing cache and begin the installer again. This seems to happen more on CWM than TWRP.
If the installer runs but your bootloader doesn't change, it is proably one of these things:
You are not S-Off
You do not have the latest version of recovery (I recommend TWRP)

+ 1

+1

Worked on int. m7 with hboot version 1.55.
Now have removed my tampered flag :victory:
thx
pOpY

Oh yeah..thanks..a handy tool..
Sent from my HTC One using XDA Premium 4 mobile app

Nice Thanks @crushalot
Quick question (if you have time): why do we need latest recovery? what would happen on an older recovery?

Will this work on Rumrunners custom HBOOT or is a stock HBOOT only recommended?
Sent from my HTC One using Tapatalk

nkk71 said:
Nice Thanks @crushalot
Quick question (if you have time): why do we need latest recovery? what would happen on an older recovery?
Click to expand...
Click to collapse
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.

Evil-Dragon said:
Will this work on Rumrunners custom HBOOT or is a stock HBOOT only recommended?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It will work on any firmware. Hboot is not touched. This only modifies partitions mmcblk0p3 and mmcblk0p7.

crushalot said:
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.
Click to expand...
Click to collapse
Noted. Thanks
Sent from my HTC One using Tapatalk

Awesome!
I was looking for this... it worked great! Thanks man!

crushalot said:
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.
Click to expand...
Click to collapse
Hi crushalot, I just noticed TWRP version 2.6.3.3 was pulled and back to 2.6.3.0, just FYI

Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?

DaringDomino3s said:
Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?
Click to expand...
Click to collapse
. Warranty purposes. Or for example in my case if I decided to upgrade my phone with jump, I can make everything look like never even happened. It's quite useful.
Sent from my HTC One using XDA Premium 4 mobile app

nkk71 said:
Hi crushalot, I just noticed TWRP version 2.6.3.3 was pulled and back to 2.6.3.0, just FYI
Click to expand...
Click to collapse
Yeah, seems like it was pulled because the charging while in recovery doesn't work correctly.
It still works for everything else. Not sure if they will just re-release 2.6.3.3 when fixed or make a new version.
I will update the link and info in the OP.
Thanks

DaringDomino3s said:
Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?
Click to expand...
Click to collapse
Also sometimes a locked bootloader is needed for promotions like the 25 GB of Google Drive space.
There can be a variety of reasons one might need to toggle it.

Looking and unlocking won't wipe data? Like a typical htcdev unlock does?
Sent from my HTC One using xda app-developers app

crushalot said:
Yeah, seems like it was pulled because the charging while in recovery doesn't work correctly.
It still works for everything else. Not sure if they will just re-release 2.6.3.3 when fixed or make a new version.
I will update the link and info in the OP.
Thanks
Click to expand...
Click to collapse
I'm still on CWM 6.....2 (the old one, but with updated ts drivers) gonna test ur tool on friday.
Will let u know.
Btw, thanks for all your guru site, I refer to it a lot; PayPal doesn't work in my country so can't contribute. But thanks !!
Love ur work.
Sent from my HTC One using Tapatalk

joho5 said:
Looking and unlocking won't wipe data? Like a typical htcdev unlock does?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No, my tool doesn't wipe data during a lock or unlock.
It directly modifies the partitions that conatin the bootloader status, without touching /data or /system

What ROM to use?

I'm pretty happy with stock 5.0 but I miss OnmiRecents from OmniRom and xposed modules.
On my Note 3 I loved Temasek's CM12 because it included both of these, what ROM would you recommend if I want the bare minimum that supports Onmirecents and Xposed?
I tried useing xposed on stock without any FC's unsuccessfully.

if you are getting crashes with xposed then its likely the module might not be lollipop compatible, im running 5.0.2 with xposed and a few modules I use and its solid
you might be better off looking at some of the aosp/cm based roms in the dev section

I want to give aosp a shot since you recommended it and I think it's exactly what I'm looking for, but I'm having trouble flashing the zip I got from the Free Xperia Project site, I'm trying to flash AOPS_L_MR1_150312_leo.zip and all I'm getting is errors from all 3 custom recoveries, using an unlocked bootloader, the md5 is 2c4006757733d7a57997cfb31ba9efe but I can't find a hash on their site, the only error I have is "E: Installation aborted. press any key to continue". My internet is terribly slow and downloading a 200mb file takes hours, so I'll try re-downloading but I'd prefer not to.
Edit: I've tried 2 ROMs I've verified are downloaded correctly and they won't install, one with an unspecified error (AOSP) and the other will report wrong device saying "This rom is intended for D6603 z3, this device is 'leo'" (pac rom), I have no idea where the problem may be

well I never recommended it, I just said that you might be better off looking at aosp roms as that's clearly what you want rather than stock sony rom, what model is your device and are you flashing the boot.img from the rom and using that recovery?

Ok, I got a bit carried away I ment to say that you where right when saying that AOSP suited my needs.
Richy99 said:
what model is your device and are you flashing the boot.img from the rom and using that recovery?
Click to expand...
Click to collapse
I'm not flashing boot.img from the rom, I'm using CWM TeamWin and Philz recoveries I previously flashed while on stock to flash the zip files. Is this wrong? I've been doing this forever on other devices.
Do people that post ROMs provide boot.img to be flashed using flashtool previous to the flashing of their ROMs zip?

what device do you have? is it the 6603 or 6653? no its not wrong but sometimes the recovery is slightly different from the boot.img and I have seen it resolve the issue in the past, the installation aborted should give an error number after it, normally googling this can lead to why it failed

Richy99 said:
what device do you have? is it the 6603 or 6653?
Click to expand...
Click to collapse
I'm using 6603 and the error I get isn't very descriptive "E:Installation aborted" right after selecting the zip, nothing else.
Only in one isntance did I get something different and the error was something along the lines of "this rom is for 6603 and your device is leo".

which rom did you try? as it sounds like the rom isn't for the 6603

You must edit update.binary and erase z3 and replace it with Leo.
Then re-zip and flash it.

Richy99 said:
which rom did you try? as it sounds like the rom isn't for the 6603
Click to expand...
Click to collapse
This has happened with various ROMs that stated they where for 6603, could it be my recovery isn't playing nice with the zipped ROMs making them think my phone is a diferent model?
Edit:
I flashed bootZ3monxtest01.img with fastboot wich i TWRP and I'm getting nowhere
{
"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"
}

E-Chan42 said:
This has happened with various ROMs that stated they where for 6603, could it be my recovery isn't playing nice with the zipped ROMs making them think my phone is a diferent model?
Click to expand...
Click to collapse
LOL
Read my post.

TheTeslaCoil said:
You must edit update.binary and erase z3 and replace it with Leo.
Then re-zip and flash it.
Click to expand...
Click to collapse
For every .zip I try to flash? I'm not confident I could unzip, modify and re-zip without screwing up somehow, isn't there a specific recovery I can flash that will do this correctly?
UPDATE: using Z3_DooMLoRD_AdvStkKernel_v01_FW-93.img I was able to flash only cm-12.1-20150505-UNOFFICIAL-z3 (1).zip all other files gave me the same error, I'm now running Cyanogen but I still want to find a solution so I can flash other ROMs freely

E-Chan42 said:
For every .zip I try to flash? I'm not confident I could unzip, modify and re-zip without screwing up somehow, isn't there a specific recovery I can flash that will do this correctly?
Click to expand...
Click to collapse
Its not hard, open the zip using 7 zip or any winzip or WinRAR
Drag and drop the updater script out, modify it, drag and drop it back in.
Done

You can also flash CM by: flash boot.img from inside the firmware you want to flash. Unzip the CM ROM and extract boot.img and flash it. [via adb]
Then reboot into recovery.
It will bring you to CM recovery, from there apply update from sdcard1. [assuming that the ROM and gapps are there]
Flash CM
Again apply update and flash gapps.
Done.
After that you can flash another recovery if you want, or kernel, there is also a fota kernel, which updates only the recovery and keeps the kernel the same.
This method is without the need of editing update-binary.
Flash original firmware, [exactly as it is when downloaded] because the CM Recovery will check the signature.
Must have unlocked bootloader.
P.S.
If you edit update-binary do it with Notepad++

I had no idea I could extract boot.img from a ROM and flash it individualy using fastboot, this solved my problem 100%, thanks!

[ROM] [7.0] Optimized Stock Shield Tablet Original [5.2] & K1 [5.2] [14/08/17]

Optimized Stock Rom for Shield Tablet
{
"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"
}
Introduction:
I was missing a stock based rom for this device. So I took the nvidia recovery image and made it a flashable zip for TWRP. You cannot use ota to update though, wait for the new version from here if you want to update.
Also, don't flash wrong zip on the wrong Shield Tablet. It's your own responsibilty
Features:
- Latest Stock Factory Image
- Zipaligned apps
- Nothing more
Download:
K1: https://www.androidfilehost.com/?w=files&flid=93930
Original (Wifi & LTE): https://www.androidfilehost.com/?w=files&flid=94437
Also flash blob file of the same version
Enjoy!!

What to do with the blob zip:
Code:
1. Extract blob file from zip
2. Flash blob in fastboot with: fastboot flash staging "name of blob file"

Yup, I vote for original Shield ROM! Thanks!

Nice! Vulcan API goodness!

Zip for the original Shield Tablet (untested):
https://www.androidfilehost.com/?fid=24591000424954195

Thanks for this!
Is there any possibility you remove the Kill-Switch for users who have kept their tablet what has had to be replaced? I guess the Tegra Ota service must be disabled

Thanks! Made backup, flashed rom zip, flashed twrp, su, Xposed, nomoreota, and kernel. Wiped cache and booted system. Looks good so far... Not much immediate difference but we shall see over time. Came from stock so I did not wipe data and all is well.

teachmeluv said:
Thanks for this!
Is there any possibility you remove the Kill-Switch for users who have kept their tablet what has had to be replaced? I guess the Tegra Ota service must be disabled
Click to expand...
Click to collapse
Its better to do that yourself. There are tutorials on how here in the devices forum
Sent from my XT1562 using XDA Labs

GtrCraft said:
Its better to do that yourself. There are tutorials on how here in the devices forum
Sent from my XT1562 using XDA Labs
Click to expand...
Click to collapse
Ok thank you. Previous post says something about the nomoreota file, I remember that one now.
Anyway is this ROM pre-rooted? And is the file for the original tablet compatible with all three versions of it?

So after a few hours this ROM is smoother, cooler and faster then stock... Guess I'll be keeping it for awhile.

teachmeluv said:
Ok thank you. Previous post says something about the nomoreota file, I remember that one now.
Anyway is this ROM pre-rooted? And is the file for the original tablet compatible with all three versions of it?
Click to expand...
Click to collapse
The rom is not prerooted, also I only downloaded the wifi image. So that's the version for the original tablet

ok so after unlocking and rooting, I installed the bliss rom, but realized none of the nvidia apps were there And besides my Phantom I want this tablet for that.
so I wiped and installed this one, ran the nomoreota zip and everything is back to normal, but, I'm not longer rooted.
I just want this rom and rooted. I have twrp recovery and it works fine, but still not rooted.
anyhelp? thanks

Hello,
I tried to install K1 version using twrp, but i'm getting a blkdiscard failed: Invald argement,updater process ended with error 7. Image doesnot get installed.
Any ideas?
Regards,

Good Good! Working fine!!.Thanks.

fastfed said:
ok so after unlocking and rooting, I installed the bliss rom, but realized none of the nvidia apps were there And besides my Phantom I want this tablet for that.
so I wiped and installed this one, ran the nomoreota zip and everything is back to normal, but, I'm not longer rooted.
I just want this rom and rooted. I have twrp recovery and it works fine, but still not rooted.
anyhelp? thanks
Click to expand...
Click to collapse
Flash the latest su.zip in twrp.

rampa99 said:
Hello,
I tried to install K1 version using twrp, but i'm getting a blkdiscard failed: Invald argement,updater process ended with error 7. Image doesnot get installed.
Any ideas?
Regards,
Click to expand...
Click to collapse
Be sure to have the latest twrp and bootloader for K1

GtrCraft said:
Tell me if you guys want the same zip for the original shield tablet. Or a version without zipaligned apps
Click to expand...
Click to collapse
any chance for original 32GB European LTE flashable version, please?

SnowiiSnowii said:
any chance for original 32GB European LTE flashable version, please?
Click to expand...
Click to collapse
which recovery image is that?

That'd be LTE RoW 4.2... thank you!

SnowiiSnowii said:
That'd be LTE RoW 4.2... thank you!
Click to expand...
Click to collapse
Here you go:
https://www.androidfilehost.com/?fid=24591000424955372

How to verify flashed firmware version (when on custom ROM)?

I just flashed a custom ROM (Pixel Experience A11) originally starting from MIUI Global 12.0.4
Then I flashed the Global 12.0.7 firmware via TWRP (found here https://xiaomifirmwareupdater.com/firmware/surya/).
However, I forgot to check version numbers of anything before flashing, so I don't know what to look for to verify the new firmware is flashed properly?
Thanks!

@uddinf you could also switch to Orange Fox recovery, after you reboot to recovery on startup screen you will see several info about your device including actual fw number...
{
"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"
}

jeryll said:
@uddinf you could also switch to Orange Fox recovery, after you reboot to recovery on startup screen you will see several info about your device including actual fw number...
Click to expand...
Click to collapse
Thanks for the reply. I've switched and booted into Orange Fox version 6 (from here) but don't know exactly what to press to get to the firmware info.

uddinf said:
Thanks for the reply. I've switched and booted into Orange Fox version 6 (from here) but don't know exactly what to press to get to the firmware info.
Click to expand...
Click to collapse
please if you stick with the Orange fox recovery install the latest version, enjoy

jeryll said:
please if you stick with the Orange fox recovery install the latest version, enjoy
Click to expand...
Click to collapse
Thank you for that version update. It's been a while since I've flashed roms so I'm still feeling my way around the new tools/methods.
Unfortunately I don't see what version I have

uddinf said:
Thank you for that version update. It's been a while since I've flashed roms so I'm still feeling my way around the new tools/methods.
Unfortunately I don't see what version I have
Click to expand...
Click to collapse
look for the release row, it's there

jeryll said:
look for the release row, it's there
Click to expand...
Click to collapse
I was meaning the Xiaomi FW version. It doesn't show for some reason.

uddinf said:
I was meaning the Xiaomi FW version. It doesn't show for some reason.
Click to expand...
Click to collapse
interesting, I reread your original post and found that you only flashed fw (without vendor), i suggest you read this post, where are at the beginning links to the whole fw+vendor (mind you it's big around 2 GB archive needed to be flashed before flashing custom ROM)...
I suppose that is the reason why is it not showing fw version. If you will flash that and will still not show fw version, then we'll have a new mystery here... Hm, just flash that fw+vendor archive, reboot recovery and check the info screen again and report here, thanks...

jeryll said:
interesting, I reread your original post and found that you only flashed fw (without vendor), i suggest you read this post, where are at the beginning links to the whole fw+vendor (mind you it's big around 2 GB archive needed to be flashed before flashing custom ROM)...
I suppose that is the reason why is it not showing fw version. If you will flash that and will still not show fw version, then we'll have a new mystery here... Hm, just flash that fw+vendor archive, reboot recovery and check the info screen again and report here, thanks...
Click to expand...
Click to collapse
I appreciate all the input
Correct, I did not flash vendor so that is likely my problem.
I will follow your post and flash the MIUI.eu archive
One question though, you say "needed to be flashed before flashing custom ROM"...
Does that mean I have to go back to original ROM via Miflash first or do I just flash the 2gb archive from your post straight away via orange fox?

uddinf said:
Does that mean I have to go back to original ROM via Miflash first or do I just flash the 2gb archive from your post straight away via orange fox?
Click to expand...
Click to collapse
yep, you can flash it directly in , but since it's a whole usable ROM, it will also overwrite your currently flashed ROM, so if you want to use customized MIUI, don't flash anything else and just boot it, or flash whatever custom ROM you want to use directly after + necessary steps like GAPPS and after boot magisk...

jeryll said:
yep, you can flash it directly in , but since it's a whole usable ROM, it will also overwrite your currently flashed ROM, so if you want to use customized MIUI, don't flash anything else and just boot it, or flash whatever custom ROM you want to use directly after + necessary steps like GAPPS and after boot magisk...
Click to expand...
Click to collapse
Everything seems to be up and running. thanks for all the help!

How to check after getting to oragr fox mane page