Database Info

[Q] CM11 Nightlies Installation Failure

When I try to install the CM11 nightly builds as found through this thread:
http://forum.xda-developers.com/showthread.php?t=2570965
the update process fails. Below a snip ffrom the TWRP log (I've attached the complete log).
minzip: Extracted file "/system/xbin/vim"
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sdcard/ROM/cm-11-20140101-NIGHTLY-tf300t.zip'
Error flashing zip '/external_sdcard/ROM/cm-11-20140101-NIGHTLY-tf300t.zip'
Through creative Googling I found some references to the install failing with TWRP and succeeding with CWM. However, the CWM ROM Manager tells me there is no supported recovery version for the TF300, so I have no idea which version to pick.
I should mention I may have partially broken my partition table when making nvFlash available though. I made another post about that:
http://forum.xda-developers.com/showthread.php?t=2594142
to which I was hoping to get a reply by now.
I'm hoping someone could help me out, I'd really like to try KitKat on this tablet.
Thanks!

Wrong TWRP?!
Orionos said:
When I try to install the CM11 nightly builds as found through this thread:
http://forum.xda-developers.com/showthread.php?t=2570965
t[...]
I'm hoping someone could help me out, I'd really like to try KitKat on this tablet.
Thanks!
Click to expand...
Click to collapse
Hmm, regularly the issue with TWRP for the TF300T is that you need a very specific/modified version, more often than not for the TF300T not the one from the TWRP site.
I can only recommend using this script to update to CM11, as it does all the installation/downloading/flashing for you, inlcuding the correct TWRP and CM/Omni and GAPPS.
http://forum.xda-developers.com/showthread.php?t=2579922
Hope this helps

recovery
Recheck the original post and make sure you are using the correct recovery.

buche,
Your script helped. When using that particular recovery, not only can I install KitKat, but my backups started working as well. Of course, the patched TWRP generates an error when installing CM10. Go figure.
norskyforce,
The post stated:
"To install, you need a recent CWM or other recovery."
I figured I was fine with the TWRP from the TWRP site. Apparently not.
Maybe I'll try the poster's recovery image. I'm still looking for the correct CWM to use, to see if it has more options. I miss 4ext
Thanks for the help.
Unfortunately, CM11/Omni don't appear to support my WiFi's channel 13. Took me a while to figure out why I could see all the neighbors' networks, but not my own.
And I just figured out neither CM10 or 11 supports my ASUS Connect Dock, which I use for the wired ethernet and USB. Grrr...

[Q] How to sign files so that they work in Android System Recovery 3e

Hello Guys
I am new to android so please correct my mistakes and i will try to give every detail as possible.
I am having Genx tablet GX pad 300 (It is rooted). By mistake i left my tablet as home and my small brother tried to unlock it. As it was password protected so after 15 failed failed attempts, it got hard locked and Asked for my Gmail ID and PASSWORD to unlock. BUT my wifi was disabled so i was not able to reset it.
An other method was to use ADB and bypass the Password, but The usb debugging was disabled so it didnt worked either
thirdly I saw a method (on XDA) to use Recovery mode to flash AROMA Filemanager and delete the files that were related to the password.
​Now the real problem begins so please cross your fingers.
First i copied the 'aroma file manager" .zip file in external sd card. the file is in the attachment and here is the link to its XDA page, click here
First i booted my device into the Recovery mode and seleted the the option "Apply update from external sd" and selected the update file (.zip format). It gave me error
E Signature verfication failed
Installation aborted
I had Android System Recovery 3e
I did a five hour research and came to know that it is security in android system recovery 3e to reject unofficial installation, i came to know that if i have to fix these errors the either i have to flash a Custom rom like CWM or a MODDED Android system recovery 3e which allows the installation of unofficial apps. the problem is that there is now Custom CWM for my device and i dont know how to make one from the source code. Secondly they have to be installed by ADB but i cant acess my device locked. I also found that sometimes we try to flash a new recovery form within a recovery it may brick the device. i also found that the updates that can be flashed by android system recovery should be named Update.zip and should be officially signed.
I know that there are many methods and apps to sign the .zip files so that they are accepted by the Android system recovery 3e.
i came across apps like zipsigner and signapktic both of them are available on google play. I also used used manual method to sign the aroma filemanager .zip file but every thing i tried it gave me the E signature verification error installation aborted.
My Question is this that how to Sign files so that they are accepted in the ANDROID STOCK RECOVERY 3e
Please keep it simple as possible.:good::laugh:

Download APKManager (5.1). Extract it, copy your zip to ./other/ folder, run cmd.exe, change directory to ./other/ then sign using following command in cmd.exe:
java -jar signapk.jar -w testkey.x509.pem testkey.pk8 your-rom.zip signed.zip.

~It does not require internet connect connection..you can sign in to google account without internet~

Me too!
I have the same problem and can not find an answer for my life! I really need something that can sign the zip for the stock recovery!

do not recognize the command

[Q] MultiROM installation issues?

After getting Resurrection Remix ROM (which comes with a kexec-hardboot patch kernel) I thought I'd try installing MultiROM. I got MultiROM manager from the Play Store and it detected fine that I had the kexec-hardboot patch kernel. I went ahead with the installation but in the terminal in the app it give me the message:
Code:
preparing downloads
Skipping already downloaded file TWRP_multirom-amami20150201-00.img
Skipping already downloaded file MultiROM-v30x-170115-unofficial-amami.zip
Installing file TWRP_multirom-amami20150201-00.img... SUCCESS
Installing file MultiROM-v30x-170115-unofficial-amami.zip... NEEDS RECOVERY
It then asks me to reboot but doing so does not install MultiROM. I first thought that this may be an issue with my ROM coming with the MultiROM modified TWRP but I have tried installing MultiROM and recovery separately and together multiple times to no avail.
any help would be greatly appreciated. Thanks in advance.

Error during shield update

Hello,
I can update my shield tablet. I get that error:
Code:
Updating partition details …
… done
Full SELinux support is present
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file …
Sskipping MD5 check*: no MD5 file found
Source*: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys
Verifying current system...
Package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys or nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys*; this device has nvidia/sb_na_wf/shieldtablet:6,0:MRA58K/41524_664,1902:user/release-keys.
Update process ended with ERROR*: 7
Error installing installing zip file '@/cache/recovery/block.map'
Done processing script file
MTP Enabled
Can someone help me?

bird12358 said:
Hello,
I can update my shield tablet. I get that error:
Code:
Updating partition details …
… done
Full SELinux support is present
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file …
Sskipping MD5 check*: no MD5 file found
Source*: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys
Verifying current system...
Package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys or nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys*; this device has nvidia/sb_na_wf/shieldtablet:6,0:MRA58K/41524_664,1902:user/release-keys.
Update process ended with ERROR*: 7
Error installing installing zip file '@/cache/recovery/block.map'
Done processing script file
MTP Enabled
Can someone help me?
Click to expand...
Click to collapse
some more information might help people help you mate, are you rooted, do you have a custom recovery installed or are you running a custom rom? things like that help us alot

I user to be as root. But I restore factory setting ans I still have thé error.
Should i made an other thing to suppress thé root settings.?

Yes Mate I thought no so do you have a custom recovery installed
Sent from my HTC One using Tapatalk

I don t think I have that recovery installed. Where could I find this?

bird12358 said:
I don t think I have that recovery installed. Where could I find this?
Click to expand...
Click to collapse
Turn off your tablet then hold volume down and the power button untill you get to the boot loader then use the volume down button to select recovery and press power if you have a custom recovery it will bot to it and it will say team win recovery
Sent from my HTC One using Tapatalk

It seems I don t have a custom recovery. How should I do nos?

Problems after Magisk update - can only enter download mode and recovery

Hey there,
I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).
What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".
What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful
3) Tried to flash BL via Odin --> not successful
At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.
What I also tried next:
4) Tried to delete magisk modules via twrp --> not successful
5) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format (unpacking image format)
What can I do next?
Can anyone please help me, since I have two bricked devices now????

A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.

Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
Mohamedkam000 said:
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
Click to expand...
Click to collapse
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Mohamedkam000 said:
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Click to expand...
Click to collapse
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.

capitarider said:
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
Click to expand...
Click to collapse
Glad your tablet revived again.
Magisk creates a backup of the boot.img found just before flashing magisk, it is compressed in gzip format, so you need to pull it, extract it, and push it back to the phone, then flash it.
The file is usually in /data/stock_boot_${SHA1}.img.gz
You can extract it using the built-in terminal of TWRP, if PC is not accessible at the moment by writing and executing the following command:
gunzip {stock-boot-name}.gz
Replace {stock-boot-name} with your backed-up boot name (without the curleybrackets), or you can use the following command:
gunzip *.gz
That'll extract the gzip archive, and the boot.img will be in /data of which you can navigate to it and flash it.
There's another guaranteed method, if you have the file of the ROM you're using right now, you can just open it (it's just a zip archive) and search for the boot.img of your specific phone model and flash it.
Another guaranteed method will be by flashing a custom kernel compatible with your current ROM, like Moro AiO kernel, of which has a wide support for ROMs starting from Oreo, and up to Q, AOSP, or stock-based, just in one file.
Moro's thread: Moro Kernel

you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot

aIecxs said:
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
Click to expand...
Click to collapse
Doesn't seem like he's encrypted, he found the boot backup of his tablet in /data so he has probably searched for a similar file on his S7, but since it is compressed, he won't find it solely.
Also he would've told us that his /data is empty or something.

start from scratch with older magisk, current 22 has bug
https://github.com/topjohnwu/Magisk/issues/4008

Thank you for your help.
I had a n old twrp backup on another external hard drive. I extracted the boot file and repached it with 7zip to boot.img and flashed through twrp. That also didn´t work for various times. TWRP always said "failed".
In the end I didn´t manage it to bring my phone back to live. Anyway, I decided to flash the latest LineageOS (Android 11) and now its running smooth again.
Thanks again.

Try using sp flash tools flashing the boot.img