Disable Signature Verification - Xiaomi Redmi Note 3 Questions & Answers

as title says...I didnt found any solution and I am on AOSP extended 7.1.1 rom...its rooted,busybox installed and cant make it work with luckypatcher,so can someone please explain?

title doesn't ​say anything. whose signature verification?

I want to install unsigned app but it wont install cuz I cant disable signature verification with lucky patcher...
http://galaxyvarchive.blogspot.ba/2015/07/tutorial-how-to-disable-signature-check.html
cant even get patch to android menu in lucky patcher...

Lol... Never heard about that for Android. I thought u need to disable it for installing drivers with Windows.

Related

[APP] Gingerbread Keyboard

Anyone have tried to install?
http://www.droid-life.com/2010/12/06/download-gingerbread-keyboard-for-rooted-devices/
According with the site:
"*Should work on ALL rooted 2.2 Android devices."
## UPDATE ##
Fixed Version: http://briefmobile.com/guide-install-android-2-3-keyboard
is there new copy paste tool ??
Welp apparently we need thr spanish tts plugin..i got an error flashing it.
I've just tried to flash and received the following message:
E: Missing file:
system/tts/lang_pico/es-ES_ta.bin
E: Verification failed
Installation aborted.
:/
Yea same error like i said its a latin ime therfore it needs some spanish plugin to run... i have google voice search and tts i think..hmm anyone? Input
I can flash this
forum.cyanogenmod.com/topic/2697-nightlies-discussion-of-nightlies/page__view__findpost__p__100053
but it doesnt start, it crashes. Other people say they use it on the G1
forum.cyanogenmod.com/topic/2697-nightlies-discussion-of-nightlies/page__st__5100
If somebody manages to run it, please let me know how... I keep on trying tomorrow.
Greets
i just installed the apps and also encountered the error, but there was a fix...disable verification under custom recovery and run the it again.
Asuma06 said:
i just installed the apps and also encountered the error, but there was a fix...disable verification under custom recovery and run the it again.
Click to expand...
Click to collapse
Please can you describe exactly what you did to get the keyboard running? I tried to toggle verification in 'other' but after installation the keyboard is still crashing.
Thank you!!
Sent from my LG-P500 using XDA App
I tried flashing it with verification off but i still get an error.
"E: Error in /sdcard/update.zip
(Status 0)".
What does this mean? Did I do something wrong? what should I do?
Thanks in advance.
Only to be sure... did you rename the zip file? Because i never saw the keyboard zip with this name. Maybe you mixed something up?
oops. Was i not supposed to rename the zip?
Yes i renamed the zip into update.zip.
I reverted it into its default name but it still gave me that error.
Maybe I need to redownload it.
I've flashed the fixed version without error, but when i reboo, my device freezes on operator screen.
I had to do a Nand Restore.
Fixed version in http://briefmobile.com/guide-install-android-2-3-keyboard
after flashed the fixed keyboard allsalvati posted and disabled verification ..I am running the ginger keyboard finally..and I like ittttttt!!!!!™
Can someone post a working zip / guide ?
Tried flashing fixed version and got stuck at LG logo
better than froyo bus is still small. lg default it is even better
i've got the keyboard running, but i cant switch the correction to another language than english.
anybody has a solution???
can someone please post the updated file to another host or something? The one in the OP is dead
in installed the apk from this thread and work great, no flashing needed. http://forum.xda-developers.com/showthread.php?t=875202
had it a go from the above post..lookin goood!! toooooo responsive or its just me.

[DEV][UPDATED] ota update.zip with root and 'rescue-backroor' builtin! [not-released]

Hi guys
Treat it as a small curiosity. Nothing special (I think? )
First custom update.zip done with Sony Tablet S
Its useless for now. We still need a lot of work.
But remember - a small step forward, small progress,
and the target will be achieved
--------------------------
UPDATE
--------------------------
Hi again,
Today I show you capabilities which will be easy to get,
when we will get disable-signature-check in recovery.
We can't do that for now. Method I use is 'little' more
complicated, not easy. Let's wait for ICS release,
then I'm gonna make custom update zip with root incl
Take a look at movie below
br
condi
I LOVE YOU FOR THIS )) Keep up the good work. Fingers crossed.
Trzymam kciuki.
Nicely done!
Was it my PM that motivated you lol. Good stuff Condi!
Nice work!
Well done...
Don't need a complete custom ROM for now, I think that a one line script with set_perm_recursive to 777 on /system should make all the poor #10 kernel build owners very happy!
Keep, the good work thanks
This is incredible news! Bravo!
Hi my friend,
that sounds really good ... what would be the next steps?
Could you explain how you did reach this goal?
It looks very promising ...
Please keep us informed ...
thx condi
Since we now have a SIGNED flashable update.zip, here is a little something I made to install busybox, su, symlinks, etc to root the unrootable kernels. The problem I am running into is signing it so it will pass the signature verification. I attached it for all to use and attempt to get it signed and runable. I only ask that you don't change anything in the flashing script untill you contact me. Thanks...
thomas.raines said:
Since we now have a SIGNED flashable update.zip, here is a little something I made to install busybox, su, symlinks, etc to root the unrootable kernels. The problem I am running into is signing it so it will pass the signature verification. I attached it for all to use and attempt to get it signed and runable. I only ask that you don't change anything in the flashing script untill you contact me. Thanks...
Click to expand...
Click to collapse
We dont have signed update.zip. Who said that its signed zip?
The script is nothing new, i had few updaters with root install,
I've got already my newest ota with root included.
Your script has bad syntax, it will not work.
If i could sign zips with sonys private key, then i would already release root tool,
And also a lot more..
As I wrote in first post, there is a lot of work to do.
Hi Condi,
could you explain a little bit more what and how you did to avoid misunderstandings?
On a first glimpse it looks like a 'faked update.zip' who gives you/us the opportunity to install additional stuff via recovery. If this would be possible, it gives us a lot of possibilities.
obicom said:
Hi Condi,
could you explain a little bit more what and how you did to avoid misunderstandings?
On a first glimpse it looks like a 'faked update.zip' who gives you/us the opportunity to install additional stuff via recovery. If this would be possible, it gives us a lot of possibilities.
Click to expand...
Click to collapse
For now its not useful for 'end-user'. This can't be done without root already.
Everything what can be done via updater-script, can also be done in normal booted device - rooted device.
Until we could manage to modify/decrypt system.img, hidden.img - all the blocks, then its not useful.
I will wait till ICS will be released, this could be our kind of 'OTA-RootKeeper' for ICS
Then I think that I could add this future, as automatic tool in ALLinONE tool.
br
condi
condi said:
We dont have signed update.zip. Who said that its signed zip?
The script is nothing new, i had few updaters with root install,
I've got already my newest ota with root included.
Your script has bad syntax, it will not work.
If i could sign zips with sonys private key, then i would already release root tool,
And also a lot more..
As I wrote in first post, there is a lot of work to do.
Click to expand...
Click to collapse
The zip you flashed is called update-signed.zip, leaving the illusion it's a custom signed zip...
We need to find a way to modify the recovery to bypass the signature verification. After that, no encryption necessary. As for the
syntax error, i will look at it tonight after work...
Sent from my BAMF SGH-T959V!
thomas.raines said:
The zip you flashed is called update-signed.zip, leaving the illusion it's a custom signed zip...
We need to find a way to modify the recovery to bypass the signature verification. After that, no encryption necessary. As for the
syntax error, i will look at it tonight after work...
Sent from my BAMF SGH-T959V!
Click to expand...
Click to collapse
Nope, zip is called update_condi.zip
thomas.raines said:
The zip you flashed is called update-signed.zip, leaving the illusion it's a custom signed zip...
We need to find a way to modify the recovery to bypass the signature verification. After that, no encryption necessary. As for the
syntax error, i will look at it tonight after work...
Sent from my BAMF SGH-T959V!
Click to expand...
Click to collapse
Nobody - in any forum, in any device I know - has bypassed Recovery Mode signature verification. Devs just made custom recoveries (CWM), but the default recovery needs always signed update.zips
We need a custom kernel to include custom recovery.
But to make a kernel we need SOURCES, which we do not have.
Maybe Sony will release ICS souces.
With Honeycomb there were some restrictions...and even Google haven't released sources for Honeycomb, but I hope it will be different for ICS...
@sebarkh
Some hints.
Here you can see that the stock 3e recovery can be modded to disable the sign check.
http://forum.xda-developers.com/showthread.php?t=1091465
http://forum.xda-developers.com/showthread.php?t=909213
In one of the dev toics was the source link posted. I mean the sony website and kernel sources.
here:
http://forum.xda-developers.com/showpost.php?p=22059498&postcount=7
norberto_ said:
@sebarkh
Some hints.
Here you can see that the stock 3e recovery can be modded to disable the sign check.
http://forum.xda-developers.com/showthread.php?t=1091465
http://forum.xda-developers.com/showthread.php?t=909213
In one of the dev toics was the source link posted. I mean the sony website and kernel sources.
here:
http://forum.xda-developers.com/showpost.php?p=22059498&postcount=7
Click to expand...
Click to collapse
That's exactly it. There have been devices that have bypassed the signature verification using 3e recovery without using cwm... Which was the base for the custom recovery i was working on till i got locked out because of kennel 10. I'm not a noob here guys...
With the sgs4g, we had the same issue with sources, kernel, recovery, signature verification, etc. but we had more dev's which made things move along faster.
We need the recovery binary (which i have), root, and the true location of the stock recovery (tried bypassing and using the typical directory) and it will be done. (Hell, I've already got it somewhat working.) Then we can create a zip based cwm that you keep on your sdcard.
Sent from my BAMF SGH-T959V!
you wrote you have the recovery binary.
have you dumped somehow from the tablet or it is from other device?
norberto_ said:
@sebarkh
Some hints.
Here you can see that the stock 3e recovery can be modded to disable the sign check.
http://forum.xda-developers.com/showthread.php?t=1091465
http://forum.xda-developers.com/showthread.php?t=909213
In one of the dev toics was the source link posted. I mean the sony website and kernel sources.
here:
http://forum.xda-developers.com/showpost.php?p=22059498&postcount=7
Click to expand...
Click to collapse
I meant Original recovery... You are linking to MODIFIED recovery...
With original recovery you will never be able to install anything without a key to sign it.
THX for links!!!
So .. if we have sources maybe somebody who "knows how" could build a kernel? Are there some problems with it? Or maybe nobody knows how

trying to OC. E:signature verification failed

specs
droid razor maxx
x912
rooted
3.0.8 kernal
ics 4.0.4
version phone if it matters
ok tryed following this guide
http://forum.xda-developers.com/showthread.php?t=1754888
but it didnt work.i moved ziped(and even tryed unziping files).didnt see unzip.ziped files failed with the E:signature thing
http://www.youtube.com/watch?v=CFV1P1t9FEI
also tried that.but same deal.cant get anywhere.still saying E:sig verification fail
sooo its certainly something im doing wrong.
both i boot into reboot mode.and try to update from sd
now i searched a few similar threads and i noticed alot of people fixing it by booting into reboot.than using the "update from zip" option
well i dont have that....i only have a few options
reboot
update from sd
flash clean
flash cashe
update from cashe
why do people have more options than me
if you watch that youtube video.when that guy goes into reboot he has like a million options too.
maybe its my rom?
im pretty sure im on a stock one.could this be my issue?
Bump
No one
In order to make all those steps you must have a rooted device and a custom recovery i.e BMM; from what you wrote at least you don't have / know how to use a custom recovery
If you have a rooted device and just want to make it easier way to OC/UV just download the tweakerz apk at the end of the 1st post of the thread you took and read it ALL the complete thread to learn what to do the proper way in order to decrease possibilities of messing It bad your device, the hard way is not reading and maybe bricking your phone
Now seriously, I made a thread on another forum but in spanish about what I think is what you're looking for, a short easy tutorial on how to use tweakerz for OC/OV "noobs-proof edition", if you think It could help you let me know and I'll pm you a link to it :good:

[Q] i747M rom signing

The usb port in my samsug i747M S3 is not working on any pc and my phone is stuck in a bootloop. I need to know if there is anyway to flash in a custom recovery via the stock recovery or flash in a new zip flashable rom through stock recovery.
I have used cygwin kitchen to put together a flashable zip from a odin rom i downloaded online but i keep getting esignature verification failed. After researching this i found that only samsung signed zips are allowed to be flashed in stock recovery. How can i sign my zips and make them appear as Samsung signed? If possible!!
narell said:
The usb port in my samsug i747M S3 is not working on any pc and my phone is stuck in a bootloop. I need to know if there is anyway to flash in a custom recovery via the stock recovery or flash in a new zip flashable rom through stock recovery.
I have used cygwin kitchen to put together a flashable zip from a odin rom i downloaded online but i keep getting esignature verification failed. After researching this i found that only samsung signed zips are allowed to be flashed in stock recovery. How can i sign my zips and make them appear as Samsung signed? If possible!!
Click to expand...
Click to collapse
Sorry man, that's pretty much the proverbial rock and a hard place... I'm assuming you already tried the factory reset? There really aren't many options when you are in this situation without getting the USB port fixed (which is soldered, so not the easiest thing to do). You can't flash a custom recovery or rom through the stock 3e recovery. At all. Some phones you can, this isn't one of them. This limits your options to 2 things -
Find an OTA update zip that is the same version or the one that is the next in line of updates such as this:
http://www.androidegis.com/how-to/leaked-jelly-bean-ota-update-for-bell-galaxy-s3-i747m-9-mvlali1/ (but this is older and probably won't work and do not even try if you were 4.3 last and is a leak version - this is just for example purposes only)
or you can try this, though since your boatloader is probably fine, not sure if it will work either:
http://forum.xda-developers.com/showthread.php?t=2549068
Other than that, your options are JTAG service or fixing the port, which if you are gonna spend the $ for a JTAG service, it'd make more sense to just put that towards the repair and then it will be very easy to reload the OS once that is fixed.
es0tericcha0s said:
Sorry man, that's pretty much the proverbial rock and a hard place... I'm assuming you already tried the factory reset? There really aren't many options when you are in this situation without getting the USB port fixed (which is soldered, so not the easiest thing to do). You can't flash a custom recovery or rom through the stock 3e recovery. At all. Some phones you can, this isn't one of them. This limits your options to 2 things -
Find an OTA update zip that is the same version or the one that is the next in line of updates such as this:
http://www.androidegis.com/how-to/leaked-jelly-bean-ota-update-for-bell-galaxy-s3-i747m-9-mvlali1/ (but this is older and probably won't work and do not even try if you were 4.3 last and is a leak version - this is just for example purposes only)
or you can try this, though since your boatloader is probably fine, not sure if it will work either:
http://forum.xda-developers.com/showthread.php?t=2549068
Other than that, your options are JTAG service or fixing the port, which if you are gonna spend the $ for a JTAG service, it'd make more sense to just put that towards the repair and then it will be very easy to reload the OS once that is fixed.
Click to expand...
Click to collapse
Thanks alot for your help...i downloaded the rom from the link u sent..the flash woud have been successfull but it was aborted due to this error
E: Error in /tmp/sideload/package.zip (Status 6). Installation aborted.
What does this mean? Is there anyway i can go into the rom package and fix it?
narell said:
Thanks alot for your help...i downloaded the rom from the link u sent..the flash woud have been successfull but it was aborted due to this error
E: Error in /tmp/sideload/package.zip (Status 6). Installation aborted.
What does this mean? Is there anyway i can go into the rom package and fix it?
Click to expand...
Click to collapse
I specifically said that it probably wouldn't work and was only for the idea. That update was a leaked version of 4.1.1. I'm assuming your system is probably newer than that, hence why it wouldn't work. I don't know what update you are on and not sure if there is an OTA that would be helpful even. Just saying in your current situation, there aren't many options.

Package verification failed - Make it stop!

I unlocked the bootloader and installed TWRP, but have not rooted. I have the OTA install of Android 11. I keep getting this message on my phone. At least once a day!
"Package verification failed - the update package being downloaded is not compatible with the current software version on the device"
Please, someone help me to disable this message. It is driving me nuts. Also I don't know if it is wasting bandwidth downloading an update that it isn't able to install.
Did you change firmware regions?
No, I don't even know how to do that, and I doubt such a thing could be done accidentally by unlocking the bootloader and installing TWRP.
Ok, I see now there is an option in Settings called "System Updates", within which one can disable automatic downloading of new updates. I disabled it so we'll see if I stop seeing the annoying message. Though I'm almost certain that this will work. Yes I know I'm a moron for not having found this obvious setting sooner. Oh well, I hope this post will help other folks out there.
Is there any solution to this. I get the notification daily despite disabling the Settings/System Updates?
boltjuice said:
Is there any solution to this. I get the notification daily despite disabling the Settings/System Updates?
Click to expand...
Click to collapse
I ultimately had to root the device and then install the De-Bloater app. Nothing but rooting ever worked.
danahata said:
I unlocked the bootloader and installed TWRP, but have not rooted. I have the OTA install of Android 11. I keep getting this message on my phone. At least once a day!
"Package verification failed - the update package being downloaded is not compatible with the current software version on the device"
Please, someone help me to disable this message. It is driving me nuts. Also I don't know if it is wasting bandwidth downloading an update that it isn't able to install.
Click to expand...
Click to collapse
Its suppose to fail, if its a signature verification, just make sure you have the exact files needed, see if your device is 64arm or 64 etc I had the same problem before fully educating myself with the whole process, let me know if this helps. Do a factory reset fully, redo every step and apply the ota package then apply any other packages like gapps etc but if you're doing a gapps install do it immediately after the lineage ota. With all this being said I hope you've already booted into the lineage recovery' failure to do so will result as an unsuccessful attempt

Categories

Resources