Hi Folks,
Have search my head off but cannot find a understandable reply or fix.
My TABLET android is an Aishuo A816/Herotab M816 and can flash Aishuo roms no problem also roms from Slatedroid Aishuo forum but when I try to flash other custom roms e.g.
Vestineous
Vestineous A816 1.1.2
Volcano Beta13
Thunderstorm_Alpha 4
Slatedroid Singularity A816
I get the following
--Install /sdcard/external_tfcard ...
Finding update package...
Opening update package...
Verifying update package...
e:signature verification failed
Installation aborted
I am completely lost as to where to go next. I have looked at Rom Manager but need Clockworkmod recovery but it says that it is only for phones not tablets.
Any answers/ideas please folks
Keith
No one ?
Very surprised 5months and no replies
Keith
kaybee327 said:
e:signature verification failed
Click to expand...
Click to collapse
You get this because your tablets boot loader is locked. This is the default behaviour, protecting you from yourself. Unlock the boot loader, and the device will accept unsigned images as well, allowing you to make a mess of it in no time!
kuisma said:
You get this because your tablets boot loader is locked. This is the default behaviour, protecting you from yourself. Unlock the boot loader, and the device will accept unsigned images as well, allowing you to make a mess of it in no time!
Click to expand...
Click to collapse
Apologies for the delay have had PC problems.
Have to say if anyone can make a mess of anything I can but hey life is for living (or something like that) :laugh::laugh:
Keith
Related
I'm an ol' windows geek and an Android noob. I rooted my Evo 3D and had a few bumps during the root process (still during beta) and got S-off and able to run all my rooted apps no errors - but, every time I try to apply any zip (using CRM v4.0.1.5 ), I now get:
Installing: /sdcard/download/zipnamehere.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
The first time I saw it was when I was trying to add SU to my phone -but - SU was on there and I was able to update it so I ignored the error.
Now, I'm trying to apply radios, etc and none will work.
I have tried downloading to Win7 x64 workstation, XP netbook and copying - have tried downloading directly - have tried praying and downloading - all (so far) to no avail
I was able to apply the latest deodexed ROM no problem (THANK YOU!) but i'm stuck and since i'm in the short-stack near-side of the bell-curve, I'm hoping maybe someone smarter than I can give me some things to check an' try...
As always, I'm very grateful for all the time and assistance!
(yes, i'm selecting zip, yes, i've verified checksum)
Cheers!
Try using TWRP recovery from TeamWin. I think the clockwork recovery is a port and may have some bugs. I believe most of the bugs have been worked out in TWRP. Worth a try anyway. It's a bit different than CW but I think as you get used to it you may like it better. I advise to never use Rom Manager app and flash everything manually from recovery anyway.
Sent from my Transformer TF101 using XDA Premium App
housry23 -
TWRP, eh? - It's something new to try tonight... I'll post back either way once I've got the kids to sleep and have a moment to focus
Many thanks for the quick reply and the information!
Cheers!
Okay - one more piece of the puzzle: installed TWRP and told it to doa signature verification... the md5 check is fine but even so, it's telling me the signature check is failing - for the sake of argument - if i assume the file is good, what would cause my phone to be unable to correctly verify file signatures?
and so far - very impressed with TWRP - thanks for pointing me in a proper direction!
Would really like to know how to root my Samsung Galaxy Appeal SGH-i827.
The following guide does not work
redigua.
com/how-to-root-samsung-galaxy-
appeal.html
Nor does Universal Gingerbread Root & Unroot 2.3.3 -> 2.3.7+
I have tried several other that require command inputs via the command prompt on my PC which for some reason do not work either.
This is driving my absolutely nuts.
Any help would be appreciated
P.S bare in mind i have downloaded and tried nearly 20 root packages and all returned this error
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
install_package = (2)
Installation aborted.
Bump.
You've probably googled and landed here:
http://www.youtube.com/watch?v=R3bD-urXNm0
3 comments look promising (but maybe they're faked somehow)
Video shows only link.
Link shows only download button
Download button requires selecting offer
Offer requires providing email.
I stopped at that point.... sounds like a scam.
If you're desperate you might leave a secondary email (that you set up for spam) and see if there's anything there.
Please report back any progress.
electricpete1 said:
You've probably googled and landed here:
*Thatyoutubelinkyouposted*
3 comments look promising (but maybe they're faked somehow)
Video shows only link.
Link shows only download button
Download button requires selecting offer
Offer requires providing email.
I stopped at that point.... sounds like a scam.
If you're desperate you might leave a secondary email (that you set up for spam) and see if there's anything there.
Please report back any progress.
Click to expand...
Click to collapse
Yup it's fake. if there was a root package for the i827 then i'm sure it would downloadable elswhere and most likely on this site or one similar to it. probably a generic rooting tool that does'nt work or is outdated.
Bump
Really want to root this phone and get the most out of it. has no one managed to root a phone on gingerbread 2.3.6 yet ?.
bump
Bump
Bump
Bump
:crying:
bump
cwm and root now available for the appeal
http://forum.xda-developers.com/showthread.php?t=1772503&page=2
Root with poot. Apk... Find it on 4shared.Com.. I uploaded it there
Poot. Apk on 4 shared.. Needs ministro!
Unless they've updated poot, it will not root a galaxy appeal... but feel free to try and post with your results.
Sent from my SAMSUNG-SGH-I827 using Xparent Red Tapatalk 2
I was able to root my samsung galaxy appeal with poot, I don't know why, but it took many trys before it worked...
Sent from my SAMSUNG-SGH-I827 using xda app-developers app
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.
Hello,
I recently got an Smartisan Nut Pro (U2) and really love it. Unfortunate the seller put a modified rom unto it and changed the device name making it impossible to flash the device to the most recent version. When flashing i get an error: E3004: This package is for "odin" devices; this is a "Odin_haiwai".
I tried to change this but because i don't have root access i cannot. I tried editing the updater.script file in the update zip but got an error saying: E:failed to verify whole-file signature E:signature verification failed installation aborted
Tried KingOroot to root device but that failed as well..
In the current rom they removed system apps which make some features unusable. :crying:
Any idea would be much appreciated.
If there are questions please ask and i will answer asap.
Hi. I'm in the same situation like you.
This is the response of the phone seller about this problem:
Me: The phone comes with modified ROM. Is impossible to install official system. Can you help me, please?
The seller: Hello, friend. the phone can no install any other system. if not, it may can not work. ling
Resolve
Go to bbs.smartisan(dot)com/forum.php?mod=viewthread&tid=799739&highlight=%E5%88%B7
akudja said:
Go to bbs.smartisan(dot)com/forum.php?mod=viewthread&tid=799739&highlight=%E5%88%B7
Click to expand...
Click to collapse
Thanks but that is for the nut pro 2. I got the first one. Unfortunately there is no option to fix this for the Nut pro. :crying:
redman.4757 said:
Hi. I'm in the same situation like you.
This is the response of the phone seller about this problem:
Me: The phone comes with modified ROM. Is impossible to install official system. Can you help me, please?
The seller: Hello, friend. the phone can no install any other system. if not, it may can not work. ling
Click to expand...
Click to collapse
I returned the device and bought it from a different seller with the correct software. Got it and it works great!
I did the same. The shipper told me that there's no way to solve this. I'll buy again.
did you fix it?
Rubixcube92 said:
Hello,
I recently got an Smartisan Nut Pro (U2) and really love it. Unfortunate the seller put a modified rom unto it and changed the device name making it impossible to flash the device to the most recent version. When flashing i get an error: E3004: This package is for "odin" devices; this is a "Odin_haiwai".
I tried to change this but because i don't have root access i cannot. I tried editing the updater.script file in the update zip but got an error saying: E:failed to verify whole-file signature E:signature verification failed installation aborted
Tried KingOroot to root device but that failed as well..
In the current rom they removed system apps which make some features unusable. :crying:
Any idea would be much appreciated.
If there are questions please ask and i will answer asap.
Click to expand...
Click to collapse
you can go to weibo to follow”xinger”.he had buy Pro2s and he maybe have thoughts to root this phone.my phone smartisan Pro is rooted by his way.
We have a kiosk application that needs to be able to periodically do OTA updates using our self-made OTA update .zip files.
Our custom OTA update .zip file have the following files:
/data/misc/adb/
adb_keys
/system
/priv-app/
MyApp.apk
/vendor/
build.prop
/META-INF/com/google/android/
update-binary
updater-script
We have used many different tablets like Galaxy Tab 3, Galaxy Tab 4 and Yoga 3, the only thing we have had to do is to replace the `mount` command arguments inside `updater-script` with the right ones for each tablet.
Of couse, since we do not have the release keys of each of these tablets, we have had to replace every Recovery with its own TWRP Recovery replacement, in order to be able to flash our custom OTA update file. All this worked like a charm every time.
Now we bought new tablets from a chinese manufacturer and when we tried to flash our OTA update package we got the following error:
Verifying update package...
E:footer is wrong
E:signature verification failed
Restarting adbd...
Installation aborted.
From that message is clear that error occurred because the OTA update .zip file was not signed. So, I asked from the manufacturer the release keys and the instructions in order to sign our OTA update .zip file and being able to flash it.
The problem is that the manufacturer's engineers have no clue of how to do this (signing OTA update files so they don't get rejected by their Recovery), which seems like a very common problem because we asked in multiple manufacturers and nobody knows how to do this.
So, I would like to ask for your help since I cannot find the instructions on how to sign it. Anybody knows how to do it?
sebastiantoro84 said:
We have a kiosk application that needs to be able to periodically do OTA updates using our self-made OTA update .zip files.
Our custom OTA update .zip file have the following files:
/data/misc/adb/
adb_keys
/system
/priv-app/
MyApp.apk
/vendor/
build.prop
/META-INF/com/google/android/
update-binary
updater-script
We have used many different tablets like Galaxy Tab 3, Galaxy Tab 4 and Yoga 3, the only thing we have had to do is to replace the `mount` command arguments inside `updater-script` with the right ones for each tablet.
Of couse, since we do not have the release keys of each of these tablets, we have had to replace every Recovery with its own TWRP Recovery replacement, in order to be able to flash our custom OTA update file. All this worked like a charm every time.
Now we bought new tablets from a chinese manufacturer and when we tried to flash our OTA update package we got the following error:
Verifying update package...
E:footer is wrong
E:signature verification failed
Restarting adbd...
Installation aborted.
From that message is clear that error occurred because the OTA update .zip file was not signed. So, I asked from the manufacturer the release keys and the instructions in order to sign our OTA update .zip file and being able to flash it.
The problem is that the manufacturer's engineers have no clue of how to do this (signing OTA update files so they don't get rejected by their Recovery), which seems like a very common problem because we asked in multiple manufacturers and nobody knows how to do this.
So, I would like to ask for your help since I cannot find the instructions on how to sign it. Anybody knows how to do it?
Click to expand...
Click to collapse
Got any answers?
Skrappy187 said:
Got any answers?
Click to expand...
Click to collapse
The answer is simple:
If you want to provide self-made OTA update you also have to use your own custom ROM. Then you are able to sign OS and OTA update using the same key.
To use testkeys at least the keys file must be changed in the recovery...