Hello everyone. Let's see if anybody can help me, because I'm pretty stuck with this.
Note: I've already searched high and low for solutions to the "Signature verification failed", but they either don't work or don't apply here.
I've tried to install the following ROM from xda-developers in a Sanei N10:
Unofficial CyanogenMod 10 for many AllWinner A10 tablets
I've installed it following the usual procedure:
- Press Vol+ and Power to get the Recovery menu
- Select Wipe data/factory reset
- Select Wipe cache
- Install the three ZIP files: "cm10_a10_20120913.zip", "gapps-jb-20120726-signed.zip" & "n10_compatibility_1.2.1.zip"
The problem is, even though the first ZIP with the ROM installs successfully, the second one (the one with Google's apps) refuses to install, showing instead the message "signature verification failed". The same happens with the third ZIP (N10 compatibility).
So the installation doesn't actually finish. If I reboot the tablet, it runs Cyanogenmod 10, but the touchscreen doesn't work (I have to plug a USB mouse to interact with the operating system).
So what do I do to avoid the dreaded "signature verification failed" message? Just in case if it's of any help to identify the problem, I'll mention that I can see the Android bot laying down with a red triangle with an exclamation when entering the Recovery menu.
I've tried to use the ROM Manager which is preinstalled with Cyanogenmod 10, but when choosing "Flash ClockworkMod Recovery" it says that "The SD Card needs to be mounted to use ROM Manager". Of course my MicroSD is properly mounted (I can see its files in the card from console, from the "Terminal Emulator"). I think this happens because the MicroSD is mounted in /storage/sdcard1 instead of in /storage/sdcard0, but I can't change that. I can't download APKs from the browser, either, because it also says something similar about not being able to access the SD (even though it's correctly mounted and can see it mounted from Settings > Storage).
I've also tried the CyanogenMod A10 ROM available in this page, which is more recent (October instead of September):
http://www.slatedroid.com/topic/3870...mod-10-tweaks/
But the same happens.
I've even tried installing the CWM Recovery ROM, but it doesn't let me installing that from the Recovery either (same message about the "signature"), and with Odin3 it doesn't work either because I don't know how to reach the "download mode", which is needed for Odin3. Pressing Vol+ and Power I get the Recovery, but not the Download mode. Does anyone know how do I get to the download mode in the Sanei N10?
Any idea about how to solve this? Right now I have a tablet with no touchscreen and not even Google applications (so I don't even have the Play Store), so it's practically worthless (at least the WiFi works). How can I get this tablet back to being usable?
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
benny6812 said:
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
Click to expand...
Click to collapse
No, unfortunately I still couldn't fix it
There's nobody here in xda-developers who can help me? Surely somebody must know enough to help me find a solution.
I've tried creating a symbolic link from /storage/sdcard1 to /storage/sdcard (it doesn't exist right now), but it just says "link failed Read-only file system" (I was root, by typing "su" and clicking "Allow" in the Superuser window). So, I can't create symbolic links even while being root user? I need this link so ROM Manager can detect my SD Card (it says it's not mounted but it really is, but in "/storage/sdcard1").
Also, the gapps package linked in the ROM page above seems not to be properly signed, even though it has that "-signed" suffix in its name. I always get that "signature verification failed" error message. But now I've tried downloading a more recent gapps package (gapps-jb-20121011-signed.zip) and that package finally worked! BUT, even though it apparently installed successfully, I still can't see any Play Store icon, nor any other Google app (Gmail, etc.). Why? Those icons should appear after installing gapps, shouldn't they? Maybe this newer "gapps" package is somehow incompatible with this tablet? (is this even possible?).
Also, even though I can now install the newer "gapps" package, I still can't install the "n10_compatibility_1.2.1.zip" file (I still get "signature verification failed" for that ZIP), which, I guess, contains the drivers needed for the N10 so the touchscreen works (currently it doesn't, and I have to use a USB mouse to use Android in this tablet). Any ideas? I'm getting tired of trying 9485738489754935627 things with no good result . I guess Android is showing here its Linux roots...
I think the key here is managing to install a new Recovery ROM that doesn't care about signing, but how do I do that? I can't install through ROM Manager because I get that error about the SDCard needing to be mounted to use it (and it's really mounted), and then I can't create the /storage/sdcard symbolic link because I get that "link failed Read-only file system" error. Also, I can't use Odin3 because I can't manage to put this tablet in Download Mode. Aaaargh! There's no good solution
Any ideas?
Bump!
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Yojimbojpr said:
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Click to expand...
Click to collapse
Thanks for replying. If we could find some way to install a new Recovery, then we'd probably by able to get the N10 Compatibility file working. This can't be that hard to do, but I've tried lots of things, and none of them worked...
Anyone?
Please, someone help!
Bump!
No ideas?
Please, I'm getting desperate
sanei
OMA2k said:
No ideas?
Click to expand...
Click to collapse
same problem here....
jamjamjan said:
same problem here....
Click to expand...
Click to collapse
Please let me know if you find a solution to this. Thanks!
I'm having the same issue with [ROM][CM10/10.1][21 Dec] Codename Lungo
Well, at last I could finally solve the problem thanks to chris5s from this forum.
These are the steps that worked for me:
1. Download the latest ClockWorkMod for Allwinner A10 tablets from here:
http://forum.xda-developers.com/showthread.php?t=1802268
2. Put all three files in the ZIP inside the root of a MicroSD card and insert it in the tablet
3. Check from the Terminal app inside the tablet to see if the MicroSD card is mounted in /sdcard (just type "ls /sdcard").
4. If the "ls" command doesn't show anything (that's what happened in my case), then you must modify the "install-recovery.sh" file and replace all instances of "/sdcard" with "/mnt/extsd".
5. With the proper "install-recovery.sh" file, run the commands specified in the above xda link (in my case the card is in "/mnt/extsd" instead of "/mnt/sdcard" as the original example shows):
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
6. The tablet will then reboot to CWM recovery. Then follow the regular steps to install Cyanogenmod (wipe plus install ROM + GApps + Compatibility). This time the Recovery menu won't care about the files being unsigned and will install them right away!
I hope this helps somebody else!
hey i just registered because i have been having the same exact problem i read that you fixed it but how can i get in to the tablet if im not able to do any movements after it boots ???
please any help would be appreciated
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Thatgrass said:
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
i did i just dont know how to get in to the terminal app
ok so im in the terminal app but what do you mean by modify the install sh file ???
Hello "lesanei"
I just noticed your posts. Let's see if I can help you...
The touchscreen doesn't work because the appropriate drivers were not installed (because of the "signature verification failed" issue). So you need to connect a USB mouse (and preferably a keyboard too) to the tablet. The Sanei N10 should come with a USB to micro-USB adapter. If you don't have it, you can buy it for cheap here.
Since there is only the one USB input in the tablet, you can't connect two USB devices at the same time. What I did use is a wireless mouse+keyboard combo which only needed one USB dongle for reception. If you don't have that, you can just connect a USB mouse and type with the on-screen-keyboard using the mouse. It's annoying, but it works
When I say "modify the install-recovery.sh file", I mean the file inside "cwm_recovery_6.0.1.2_a10.zip". You can modify it from your PC if you prefer. You don't have to do it in the tablet if you don't know how to use the "vi" editor (command line editor). Just open the "install-recovery.sh" file in Wordpad (do not use the Notepad, because it doesn't support Unix line endings so it shows the file incorrectly) and replace all instances of "/sdcard" with "/mnt/extsd". So the file contents should look like this:
#!/system/bin/sh
if busybox test ! -f /mnt/extsd/recovery.img; then
echo no /mnt/extsd/recovery.img
exit 1
fi
cat /mnt/extsd/recovery.img > /dev/block/nandg
sync; sync; sync
echo done
Click to expand...
Click to collapse
Then place all three files ("recovery.img", "install-recovery.sh" and "reboot-recovery.sh") into your MicroSD card. Then safely extract it from your PC, insert it in the tablet and type this from the Terminal:
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
Click to expand...
Click to collapse
Then follow the regular steps to install Cyanogenmod and this time all files should install sucessfully, so when rebooting, touchscreen and everything else will work.
Let me know if it works for you.
Hi Guys, long time lurker, first time poster here.
Just a quick question: A friend of mine bricked his Folio and I'm here to clean up the mess. I've managed to get CFW back on and repartitioned the internal SD (and have no clue how he FUBAR'ed it so hard), and now I'm trying to get an update.zip to flash (any one will do, really). However, for some reason each one fails on the assert getprop("ro.product.device") = "Folio100".
If I cat /default.prop I get:
[...]
ro.product.model=Folio100
ro.product.brand=TOSHIBA
ro.product.name=TOSHIBA_FOLIO_AND_A
ro.product.device=FolioX
[...]
So apparently for some reason it's called "FolioX". Can anyone tell me if this is a problem. I know I can just remove the assert from the buildscript, but that might just corrupt the whole thing again.
Thanks!
I have a Lenovo S930 (this is not relevant IMHO) and every time I try to update its ROM with CWM I get an error message like "This package is for S930, this is a w8".
The message comes from the updater-script which for sanity checks that I am attempting the ROM installation on a device that can support it.
The device is rooted so I used ROM Toolbox's Build.prop Editor to check the value of ro.build.product and ro.product.device, and to my big surprise they are correctly set to S930.
I can even use the ROM Toolbox's Terminal Emulator, go to /system and grep for "w8" in all the files, but it's not contained anywhere.
The typical trick I've used so far has been to modify updater-script to look for w8 instead, with this hack all the ROMs I've tried until now were working perfectly fine.
Now my question is: were the hell is CWM recovery taking the value "w8" for ro.product.device from, if I can't find it anywhere when the system is running? And most importantly, is there a way to change it once and for all?
ERROR: "set_perm: some changes failed" when flashing ROM traces back to /system mount
Hi all, I'm hoping that somebody much smarter than myself might happen to read this and know a possible cause for the following observations. I don't think the particular device hardware or version of Android should matter, as this is more of a general question. I installed a ClockworkMOD recovery and booted into it. Then when I attempt to flash a ROM (from external SD) that is known to be intact and working..
observations:
* I see the error message:
set_perm: some changes failed
E:Error in /storage/external_SD/ROMs/AdvancedStock8.zip
(Status 7)
Installation aborted.
* the real culprit has to do with partitions not mounting properly.
the workaround was to manually unmount and then remount: "/system", "/data", "/cache", and "/storage/external_SD".
afterward, both flashing a .zip and restoring from an earlier backup will work;
though it may require a few repeated tries (and a fair bit of cursing).
I have several identical phones and this behavior only occurred on one of them. I was eventually able to install the desired ROM on the suspect device, but I don't know what would cause this mounting issue. Should I be worried that there may be a problem with this device and go through the hassle of returning it? ..which would (of course) mean going through the hassle of trying to flash it back to a stock ROM.
I have Redmi Note 4g with miui 8.0.1 kitkat 4.4.4. I have done foolish thing and have restored data from sd card which origanally belonged to redmi 2 prime working on miui 7.5.3 on Android 5.1.1. Phone worked fine for sometime but after rebooting it got stuck on a screen with error "unfortunately process com.android...." (it doesn't even show the complete message. Though i have restored Redmi Note 4g's backup on Redmi 2 Prime but that's working quite fine. The only problem is with Redmi Note 4g.
Step wise options exhausted:
1. I have Philz touch recovery. So first i wiped cache from recovery. Problem not solved.
2. Factory reset. Problem not solved.
3. Placed MIUI 8.0.1 global ROM in sdcard and tried flashing using recovery. E: can't mount external sdcard.
4. attempted to access internal memory from recovery to install zip. E: cant mount sdcard. That means i can't flash from from external sdcard or pushing zip in internal memory.
5. installed adb & fastboot driver. used miflash to flash ROM but error: remote can't erase partition.
6. Used ADB sideload in recovery using platform tool. Flashed MIUI 8.0.1; 7.0.6; 7.2.3 ROMs but all ended in status 7 error stating failed to extract dir from "system" to "/system". error in /temp/update.zip status 7.
i also flashed MIUI 6.2.29 developer ROM which failed on " ApplyParsedPerms:removexttr of //data//miui/cust_variant to 0 failed: operation not supported on transport endpoint set_metadata_recursive: some changes failed E: error in /temp/update.zip (status 7) installation aborted.
All online solution for status 7 errors points to errors arising due to identifying wrong device in updater script od ROM. But as i checked it, my error arise at commands after it has recognised right device by getprop.
Now i am completely exhausted and frustrated. I am not an expert in flashing, just learnt little while going through above steps. Anyone, please guide me out of this problem. Thanks.
Any expert out there to solve this issue or have i posted the thread in the wrong section ???
Is the problem is on kernels level...as i don't know about kernels much...but if so then i have to study it too...