Hi all,
I did a search on google and on this forum for signature validation, but came up a little short. There see a lot of "stock" roms running around the web, but I have little trust for them. How can I verify the OEM signatures of the img files contained in the "stock" rom dumps? android.com shows how the signatures are created, and provides a painful looking method of validation: source.android.com/security/verifiedboot/verified-boot.html Is there anything in sdk which makes signature validation a little easier?
Thanks,
Bob
Related
Good day,
I am having difficulty in finding the process for signing update.zip which contains a modified google ion rom/image. Does anyone know how to sign update zips in linux? Any information would be greatly appreciated.
thanks,
Phill
I dont know how to get the update.zip signed, but i know if you flash the engineering 2005 spl onto your phone that you will be able to flash that rom onto it without getting it signed
there is a resign app. (right click choose from context...done)
http://forum.xda-developers.com/showpost.php?p=3175518&postcount=2
Just choose your final update.zip and resign it (the entire package is resigned). This did the magic for me.
Best Regards,
-f
PS: It is intended for Themes but works on entire updates.
To avoid filling the forum with question i'm just going to create this thread and ask all my questions here.
I finally rooted my nexus 7 on my mac and now am hoping to install a USB ROM, i couldnt post a link but it seems to be most popular for in car installs.
I downloaded the file and compressed it to a .zip file then tossed it onto the android. Next i booted into clockwork recovery the selected install zip from sd card>Choose zip from sd card> 0/>cm-10.zip>yes - install cm-10.zip
After this the tablet says
Finding update package...
opening update package...
installing update...
installation aborted...
Can anyone help me and/or tell me what i'm doing wrong? all help is appreciated. Thankyou
Mperkins92 said:
To avoid filling the forum with question i'm just going to create this thread and ask all my questions here.
Click to expand...
Click to collapse
A more acceptable procedure is to find - via SEARCHING - closely related threads first, and post your questions in those threads. That demonstrates to people that you've actually tried to help yourself by searching. If you actually have something unique to say, in that circumstance you start a new thread.
"Help me install a ROM" is not a new idea here on XDA, whether you have a problem with it or not.
Mperkins92 said:
I downloaded the file and compressed it to a .zip file
Click to expand...
Click to collapse
It's already a .zip file to begin with when you download it. Is your Mac uncompressing it automatically when you download it?
If so, use something other means (not Safari?) to download it. FTP. Wget. Firefox for Mac.
Then, if the ROM developer publishes rom file MD5 signatures, validate that you can compute the same checksum on the file downloaded to your computer.
If you then subsequently copy it to something else (such as the tablet), check the file length and/or the MD5 signature of the copied file as well.
Was there not some additional message on the screen besides "installation aborted"? Details are important.
The most probable guess at the moment (from your narrative) is that you borked the download and/or did something else that made the custom recovery unhappy.
BTW, when you install a new ROM for the first time, you generally:
(a) make a full Nandroid backup first (using the custom recovery)
(b) perform a "factory reset" in the custom recovery,
(c) flash of the ROM file.
Attempting the last step without the first two is just begging for trouble.
good luck
hi guys!
First of all : I'm new to the custom rom scene development. I do know how to flash and so..
So i've installed cygwin and the android kitchen. I took the stock rom provided to me by the manufacturer, i was able to set up the working folder. Then I did : "Build ROM from working folder", without making any changes to apk's or something like that.
When i got the update.zip file i tried flashing it with a recovery and using the update.zip in /sdcard method. The first method just stopped after verifying, the second method said it was an invalid package.
I believe there is something wrong with the signing of the rom. Could you guys help me out?
Thx!
Check type of script used in update.zip
tcornelis said:
hi guys!
First of all : I'm new to the custom rom scene development. I do know how to flash and so..
So i've installed cygwin and the android kitchen. I took the stock rom provided to me by the manufacturer, i was able to set up the working folder. Then I did : "Build ROM from working folder", without making any changes to apk's or something like that.
When i got the update.zip file i tried flashing it with a recovery and using the update.zip in /sdcard method. The first method just stopped after verifying, the second method said it was an invalid package.
I believe there is something wrong with the signing of the rom. Could you guys help me out?
Thx!
Click to expand...
Click to collapse
Did u signed the update.zip while exporting rom using cygwin menu. ?
If you didnt sign it will notify that is invalid
But there might be some other kind of issue like
1. Cygwin provides updater_script and update_script in update.zip package it contain all information reguarding flashing
check that your device require which type of script .
let me know your responce.
Press thanks button. if this helped
Hi guys!
Ok. so I'm (really) not a developer, I'm just trying to make a flashable ZIP (+ custom recovery and root) from the latest D80230f_00.kdz (told you, not a dev', but, yeah, everyone should starts with something right?). and I got some difficulties at the end of the process: when trying to flash the zip file, I got a big red error (ok, just red) in TWRP: "E: failed to sysMapFIle /sdcard/rom_name.zip".
Have you ever met this error?
Furthermore, I got a question about the update-binary file (maybe it's link to the error?): I've downloaded @somboons KK_template_new.zip, but their was already an update-binary file in it. I've unziped the archive, write everything I need in the updater-script, and re-zip all (see attachments), I don't do anything except ziped all: should I do something else such as sign the archive or thing like this? 'cause I don't find anything accurate about update-binary file: I don't know if we have to take it from other archive, or if it's create during signing the archive.
Oh, yeah, the recovery.img is TWRP 2.8.7.1.
Anyway, all kind of help will be very appreciate.
Thanks in advance guys !
@casual_kikoo
I would ask a mod to move your post to the Q&A where it belongs
I'm not sure if they move them or delete threads when they're not in the right sub forums.
Lawlrus said:
@casual_kikoo
I would ask a mod to move your post to the Q&A where it belongs
I'm not sure if they move them or delete threads when they're not in the right sub forums.
Click to expand...
Click to collapse
Oh ok so I post in wrong place... I was..sure :crying: ...
Thanks!
casual_kikoo said:
Hi guys!
Ok. so I'm (really) not a developer, I'm just trying to make a flashable ZIP (+ custom recovery and root) from the latest D80230f_00.kdz (told you, not a dev', but, yeah, everyone should starts with something right?). and I got some difficulties at the end of the process: when trying to flash the zip file, I got a big red error (ok, just red) in TWRP: "E: failed to sysMapFIle /sdcard/rom_name.zip".
Have you ever met this error?
Furthermore, I got a question about the update-binary file (maybe it's link to the error?): I've downloaded @somboons KK_template_new.zip, but their was already an update-binary file in it. I've unziped the archive, write everything I need in the updater-script, and re-zip all (see attachments), I don't do anything except ziped all: should I do something else such as sign the archive or thing like this? 'cause I don't find anything accurate about update-binary file: I don't know if we have to take it from other archive, or if it's create during signing the archive.
Oh, yeah, the recovery.img is TWRP 2.8.7.1.
Anyway, all kind of help will be very appreciate.
Thanks in advance guys !
Click to expand...
Click to collapse
Whenever u flash a zip for it needs to be signed, I would check or Ayysir's Android Kitchen, that's where I started my development from, I started just like u, only modifying touchwiz roms and repackaging them in flushable zoos format with android kitchen, if u need help let me know
P.S., Windows is NOT the platform to start development on lol, if I were u I'd start dual booting whatever machine ur using with a Linux OS of ur choice, for someone new like urself, I'd go with Ubuntu
Sent from my Nexus 6 using Tapatalk
soupysoup said:
Whenever u flash a zip for it needs to be signed, I would check or Ayysir's Android Kitchen, that's where I started my development from, I started just like u, only modifying touchwiz roms and repackaging them in flushable zoos format with android kitchen, if u need help let me know
P.S., Windows is NOT the platform to start development on lol, if I were u I'd start dual booting whatever machine ur using with a Linux OS of ur choice, for someone new like urself, I'd go with Ubuntu
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
First of all, thanks you so much for your fast answer. Yeah, I know Windows isn't the easiest platform to start development. Well, I've already have Ubuntu installed on VMWare, I just took screenshots on Windows .
Ok, so if I understood well, update-binary file is created during the signing step? That's why it doesn't work right now, 'cause I don't signed my ZIP.... Yeah ok I start to understand !
I'm gonna download Android Kitchen (this one right?) and start cooking !
Again, thanks you so much dude you make me more and more enthusiast about creating ROMs on Android.
Kinda makes this noob sick. I just got a new Moto G4 X1625 (not Amazon). Next came the steps to unlock the bootloader with Motorola and to install TWRP. Everything had gone so easily by following some how-to steps I jumped to the next step of installing SuperSU without doing a backup – thinking it was simply adding an app. Big mistake! Reboot and now always stuck on the logo boot animation.
Okay, so I found and tried use TWRP to install ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip in an attempt to get back to stock. No luck there since install always aborts with a "Could not find 'META-INF/com/google/android/update-binary' in the zip file."
I checked a couple of other ROMs and that META-INF directory doesn't seem to be included in them either.
What do I need to do just to get back to normal eliminating the effects of that SuperSU install? Help greatly appreciated.
That file you downloaded is not a flashable file.
Instead, read this linky
Thanks for the helpful clue @t0mm13b. I followed the approach at <http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/> and executed the listed commands from my MacOS Terminal. They did the job resulting in a fresh install after bootup.
2-1/2 questions…
1. Are flashable ROM files readily available? The ones I found all seemed missing the META-INF directory. Will they be .img files and not .zip?
2. Is TWRP not useful for these stock ROMs?
The ones I found all seemed missing the META-INF directory. Will they be .img files and not .zip?
Click to expand...
Click to collapse
As a general rule of thumb, read the accompanying text to the link of the download, on a web page where you find one. It will tell you if it's flashable or not.
Factory images, just like what you had to carry out previously, never have, and do not have the `META-INF` directory. They usually contain img files that requires `fastboot flash`.
On the other hand, OTAs and flashable zips will have that in their respective zip file.
Thanks again @t0mm13b for the clarification. I often didn't see info about whether a ROM is flashable in link or web page text, but it may have just been assumed based on being aware of what the zip contains.