Related
i read into his topic in making tar file from 1.2 kernel, since update.zip is only provided from 1.2. i tried but was unable to get results : (
please help a noob out. thank you !!
Why not just install it using rom manager- that's how he designed the package =P
that is an option, which i used (and worked, thank you again for your help) but i like my rom as clean as possible. if i could just have it as tar file, i could flash it with odin along with the pit when building my rom without needing a separate apk to do the process. i make a update.zip with all custom designed apks.
The only thing the ROM manager package does is utilize a thing called "Redbend" to actually flash the kernel while the system is running- it's the same thing as taking an OTA update from Samsung. It doesn't leave any crap behind or make your ROM any messier.
Though if you're insistent, extract the zImage and use tar:
tar --format=ustar -cf zImage.tar zImage
(Thanks to AJerman for that little tidbit)
what program do i use? i downloaded the tool from unhelpful and tried command prompt but that doesn't work.
You'll have to find the command line based tar software somewhere out on the internet. I haven't personally messed with it, but normally when using tar it's assumed you're using a Linux box =P
haha icic. yeah i googled that and i've decided to stick with rom manager. thank you very much : )
There's really no reason not to use ROM Manager for this. The update.zip does not install any files, it only flashes the kernel.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have searched, read, and tested my butt off on this so, I'm not posting without doing my own homework. I promise.
I'm looking for CURRENT documentation on how to create a standard update.zip file that simply copies a file into /system/foo/bar and chmods it.
All the links I've looked at seem to have old deprecated syntax on the update-script file, or the examples given simply do not work.
I do NOT want to download someone else's script-pak, windows app, or any other such thing that makes it for me.
As for signing, I'm completely comfortable signing using the SDK, although I'll probably take the easy route with ZipSigner/Signapktic running on the phone/tab now that I've discovered those.
Can someone please post a very simple howto?
Thanks for posting this -- I'm with you, I'm not a script-kiddie using someone else's tools, I want to learn it for myself, but like you, I've searched, and what I've found -- while probably correct and accurate -- isn't working the way they say it should. I've even followed the directions on android.com itself and they fail, so I'm starting to suspect my recovery or my ROM is at fault, not the signing itself.
I have a bunch of files I want to place in /system/foo/bar and chmod, as you say, and the error I'm getting is "No signature (172 files) Verification Failed". I do indeed have signatures in the file, as when I open them I see CERT.RSA and others that weren't there before signing, so IDK what the deal is with the error I'm getting (obviously something's missing -- maybe a public key verification from a trusted authority like Thawte or VeriSign).
I see you, too, are getting as much help as I am seeing others get. They start threads, get all sorts of praise from script kiddies who have no clue and just see a point-click solution, and then someone asks for real help and everyone shuts up for months until the thread eventually dies.
But kudos to you, sir, for being in the same boat as I!
cj chitwood said:
Thanks for posting this -- I'm with you, I'm not a script-kiddie using someone else's tools, I want to learn it for myself, but like you, I've searched, and what I've found -- while probably correct and accurate -- isn't working the way they say it should. I've even followed the directions on android.com itself and they fail, so I'm starting to suspect my recovery or my ROM is at fault, not the signing itself.
I have a bunch of files I want to place in /system/foo/bar and chmod, as you say, and the error I'm getting is "No signature (172 files) Verification Failed". I do indeed have signatures in the file, as when I open them I see CERT.RSA and others that weren't there before signing, so IDK what the deal is with the error I'm getting (obviously something's missing -- maybe a public key verification from a trusted authority like Thawte or VeriSign).
I see you, too, are getting as much help as I am seeing others get. They start threads, get all sorts of praise from script kiddies who have no clue and just see a point-click solution, and then someone asks for real help and everyone shuts up for months until the thread eventually dies.
But kudos to you, sir, for being in the same boat as I!
Click to expand...
Click to collapse
See my other reply to you in a similar topic.
I may be wrong but dont you have to sign system apps with the same key that the rom was signed with.
You can compile and sign from source and then add system apps or data
From something awesome
killersnowman said:
I may be wrong but dont you have to sign system apps with the same key that the rom was signed with.
You can compile and sign from source and then add system apps or data
From something awesome
Click to expand...
Click to collapse
System apps must be signed using the same key that is used to sign the platform. This has nothing to do with the ZIP signature that may or may not be present on a recovery update. The actual platform public key is stored within the ROM and gets extracted just like any other file in the system image.
If you compile from source, you use the platform key provided in the source; typically: build/target/product/security/platform.x509.pem. If you are an OEM like say HTC, you'll use your own key to compile the platform and sign the system apps.
Gene Poole said:
System apps must be signed using the same key that is used to sign the platform. This has nothing to do with the ZIP signature that may or may not be present on a recovery update. The actual platform public key is stored within the ROM and gets extracted just like any other file in the system image.
If you compile from source, you use the platform key provided in the source; typically: build/target/product/security/platform.x509.pem. If you are an OEM like say HTC, you'll use your own key to compile the platform and sign the system apps.
Click to expand...
Click to collapse
So in order to put ringtones in the appropriate system folder, I have to sign the update.zip with the same key that e.g. Roalex uses to sign the ROM? Of course that won't work, as I don't have his key, and then there are kernels and themes that other people make that work, and surely they don't have Roalex's key.
So I think I'm misunderstanding this still.
But if I compile from source, I sign with the key that's in the source, so if I know Roalex compiles from source, if he signs with the source key, I can sign an update.zip with that key and it will work?
Also, Recovery says there is NO signature in the file, but does that not necessarily mean really what it says?
I don't know who Roalex is. I don't know anything about your device per se. I don't know anything about Amon-Ra recovery. I was hoping some others would jump into this thread to help out with these unknowns. I've always used clockworkmod recovery so that's all I can speak for, but I did D/L an Amon-Ra recovery to analyze it.
As far as custom ROMs go, most are based on some OEM ROM and still contain system files signed by the OEM and the OEM certs are still included with the ROM so no modifications are necessary.
If you have a simple update.zip with just some files to be written to the system partition, then signing the update.zip file is unnecessary. A signed update.zip is only useful when it is distributed by an OEM with an official OEM update since the stock recovery will refuse anything not signed by the OEM. One of the reasons for using a custom recovery on rooted devices is that it gets around this security check to allow you to install custom stuff written by someone other than the OEM.
If you are having trouble installing an update.zip that contains an otherwise valid working "amend" or "edify" script, then I don't know what the issue might be. Clockworkmod recovery (at least all the versions I've run) has an option to toggle signature checks in the "apply update from SD card" sub-menu, but I don't know of any good reason that it is there since it only has one key and it is the same "test" key distributed in official source distributions, and the toggle is off by default.
I've been poking around github and grabbed the current source for amon-ra recovery (https://github.com/packetlss/amonra_bootable_recovery) and interestingly, amon-ra has a signature verifyer that is missing from clockworkmod recovery. It actually parses the zip file for the META information and ensures that the included signing key for the zip is consistent with the manifest and each file's signature.
So, it would seem that your update.zip should be signed the same way an APK is signed, using jarsigner.
Do you have a valid signing certificate and are you signing your update.zip correctly?
After learning to compile cm from source I found it easiest just to edit the .zip and then resigning the zip. I have added a few programs into /system and never had an issue. Perhaps this is because it's cm?
Gene Poole said:
I've been poking around github and grabbed the current source for amon-ra recovery (https://github.com/packetlss/amonra_bootable_recovery) and interestingly, amon-ra has a signature verifyer that is missing from clockworkmod recovery. It actually parses the zip file for the META information and ensures that the included signing key for the zip is consistent with the manifest and each file's signature.
So, it would seem that your update.zip should be signed the same way an APK is signed, using jarsigner.
Do you have a valid signing certificate and are you signing your update.zip correctly?
Click to expand...
Click to collapse
i was just going to conjecture that perhaps the amon-ra recovery is verifying sigs. you however have found proof. thank you
the only way someone would have the valid sig is for it to either be public, or for them to have signed the platform themselves and have there own private key. i ran into this same problem when investigating the android.intent.action.REBOOT intent which can only be broadcast by system apps signed with the same sig as the platform.
Gene Poole said:
I don't know who Roalex is [...]
Click to expand...
Click to collapse
Sorry, he's the guy who put together the COS-DS ROM for G1/HTC Dream based on CyanogenMod and AOSP sources.
Gene Poole said:
As far as custom ROMs go, most are based on some OEM ROM and still contain system files signed by the OEM and the OEM certs are still included with the ROM so no modifications are necessary.
Click to expand...
Click to collapse
Wait... can signing the zip be as easy as including the CERT.MSA and related other two files as found in the other update.zip files I have that work? Seems that would be too easy... I assumed there would be something in the zip file headers that would be modified to reflect a key as well so that they would also have to match. Maybe this is getting too in-depth...
Gene Poole said:
If you have a simple update.zip with just some files to be written to the system partition, then signing the update.zip file is unnecessary.
Click to expand...
Click to collapse
So just put together a common zip file with the update-script and the right folder structure in it, and I'm good? I tried that too and it also failed. Does the NAME of the file have to be update.zip in that case, though? I didn't actually try that. My unsigned one was named "CJ-Audio-Update_unsigned.zip" or something like that.
Gene Poole said:
A signed update.zip is only useful when it is distributed by an OEM with an official OEM update since the stock recovery will refuse anything not signed by the OEM. One of the reasons for using a custom recovery on rooted devices is that it gets around this security check to allow you to install custom stuff written by someone other than the OEM.
If you are having trouble installing an update.zip that contains an otherwise valid working "amend" or "edify" script, then I don't know what the issue might be. Clockworkmod recovery (at least all the versions I've run) has an option to toggle signature checks in the "apply update from SD card" sub-menu, but I don't know of any good reason that it is there since it only has one key and it is the same "test" key distributed in official source distributions, and the toggle is off by default.
Click to expand...
Click to collapse
Okay then. From here it's a lot clearer than a week ago. Thanks for taking the time to explain it so thoroughly... I think so many people understand so little and they're so quick to say "here, just use this other guy's tool LOL!!!111!1 he r0x0r$!!!1!1". I mean, that's great, that there are tools, but I want to understand it, not just be a script kiddie with someone else's tools, blindly trusting that they're doing it right and all that. Not saying the tools are bad or wrong, but by knowing myself, I know whether it's done right, you know? Same reason I learned automotive mechanicals, computers, and electrical wiring. Oh, and plumbing is slowly being added and in a few years roofing
Then it's on to framing as I build a 20-by-20-foot "workshop" in the back yard but I digress...
Thanks again!
Well this is interesting...
I took the MSA and other two files from the COS-DS update, and put them in a new zip containing my other files (not signed) and it didn't complain about no signature... instead, it failed saying some lib file is missing. Stagefright or some such. Progress is still progress though...
EDIT:
Okay, so it looks like there's something in those signats that says, "hey, look for all these other files too", so I'ma try a different tack...
EDIT2:
I guess I'm just gonna have to use Testkeys. They appear to have worked. :/ But if everyone else is doing it that way, I guess there's no harm.
Hello Moto
I've just downloaded Verizon Jelly Bean 4.1.1 by "Firmware Team".
Just to play with it a little, extract apks and test them on Galaxy SII Skyrocket.
The thing is i'm having a hard time opening system.img.
Now i've tried LinuxReader, Unyaffs and ext2explore/read but none of these can open it, they all say that it's an unrecognized image.
Do you guys know how to properly open a stock moto System.img?
lingowistico said:
Hello Moto
I've just downloaded Verizon Jelly Bean 4.1.1 by "Firmware Team".
Just to play with it a little, extract apks and test them on Galaxy SII Skyrocket.
The thing is i'm having a hard time opening system.img.
Now i've tried LinuxReader, Unyaffs and ext2explore/read but none of these can open it, they all say that it's an unrecognized image.
Do you guys know how to properly open a stock moto System.img?
Click to expand...
Click to collapse
Google for a tool called simg2img (I used the python script that appears in get first few results, there should be other versions as well). That will unpack the image into a plain ext4 image that you can mount with any Linux pc (I recommend using a virtual machine if you have windows or mac).
Happy hacking!
Sent from my XT907
aslomagic, did you try this with the firmware lingowistico is talking about? I also tried before to unpack system.img from this package, and system.img.ext4 from ICS package, and another ICS soft for XT897, and all of them give "Bad magic" error in simg2img. All of those softs are published by the same "Firmware Team" - maybe that's the case? I also tried dsixda kitchen (which also uses simg2img, but anyway...) and it also didn't work. Might be also some custom Motorola's approach to system.img....
Could you possibly help? Thanks.
micx_pl said:
aslomagic, did you try this with the firmware lingowistico is talking about? I also tried before to unpack system.img from this package, and system.img.ext4 from ICS package, and another ICS soft for XT897, and all of them give "Bad magic" error in simg2img. All of those softs are published by the same "Firmware Team" - maybe that's the case? I also tried dsixda kitchen (which also uses simg2img, but anyway...) and it also didn't work. Might be also some custom Motorola's approach to system.img....
Could you possibly help? Thanks.
Click to expand...
Click to collapse
Well, I know for a fact that those images are packed ext4, but I haven't tried specifically with that one.
Now that you mention, I think I remember signed images (like those ones) have some additional header, maybe that needs to be removed with an hex editor, or with dd of you like
If I get a chance, I'll try and report back...
Sent from my XT907
aslomagic said:
Well, I know for a fact that those images are packed ext4, but I haven't tried specifically with that one.
Now that you mention, I think I remember signed images (like those ones) have some additional header, maybe that needs to be removed with an hex editor, or with dd of you like
If I get a chance, I'll try and report back...
Click to expand...
Click to collapse
Ok, I tried, and yes, it complains it cannot find the magic (again, I'm using the python script). I modified the script to look for the magic value in the first 50Mb of the file, and if it finds it, it starts unpacking from there. Python scripts are very easy to play with
It seems to work for me, but I don't have a linux vm handy to see if it mounts correctly (I'm currently on a mac). micx_pl, can you give it a try and let me know?
I had to zip the file even though it's very small because the forum won't let me upload a .py file... who knows, just unzip it.
Holy cow! It works! You're the master I was looking for such solution everywhere, and was stunned to see barely few topics with similar problem, and no solution at all. Thanks!
micx_pl said:
Holy cow! It works! You're the master I was looking for such solution everywhere, and was stunned to see barely few topics with similar problem, and no solution at all. Thanks!
Click to expand...
Click to collapse
You're welcome, glad I could help!
Sent from my XT907
aslomagic said:
Ok, I tried, and yes, it complains it cannot find the magic (again, I'm using the python script). I modified the script to look for the magic value in the first 50Mb of the file, and if it finds it, it starts unpacking from there. Python scripts are very easy to play with
It seems to work for me, but I don't have a linux vm handy to see if it mounts correctly (I'm currently on a mac). micx_pl, can you give it a try and let me know?
I had to zip the file even though it's very small because the forum won't let me upload a .py file... who knows, just unzip it.
Click to expand...
Click to collapse
HOLY $#!+ THANKS!!! I've been trying to decompress the moto images for awhile and have never been able to do it until now
Would it be possible to modify make_ext4fs to re-sparse the image and copy the original signature?
Q9Nap said:
Would it be possible to modify make_ext4fs to re-sparse the image and copy the original signature?
Click to expand...
Click to collapse
You're welcome to try ... my guess is that it could be made to work if the image was an official, originally signed image that was unpacked by the script above or equivalent, but if you want to modify it, re-pack it and re-attach the signature, most likely the signature won't match the content. But I may be wrong, so if somebody is willing to try, best of luck to you
If your goal is just to create a packed image, but not necessarily signed (needs bootloader unlock), then I'd say it's definitely possible, search around here.
aslomagic said:
You're welcome to try ... my guess is that it could be made to work if the image was an official, originally signed image that was unpacked by the script above or equivalent, but if you want to modify it, re-pack it and re-attach the signature, most likely the signature won't match the content. But I may be wrong, so if somebody is willing to try, best of luck to you
If your goal is just to create a packed image, but not necessarily signed (needs bootloader unlock), then I'd say it's definitely possible, search around here.
Click to expand...
Click to collapse
i'm sure you're right about the signature not working on a modified image; it was just wishful thinking. the idea of course would be to inject superuser.apk and su, which wouldn't be necessary on a bootloader unlocked device.
for bootloader unlocked devices though, the ability to repack a modified image does give you another way to build custom roms. here's the code to unpack and repack images with simg2img.py and make_ext4fs:
Code:
mkdir system
./simg2img.py system.img.ext4 system.raw
sudo mount -t ext4 -o loop system.raw system/
#make changes, then:
wc -c system.raw #lists size in bytes of system.raw
sudo make_ext4fs -s -l 1234567890 -a system system.img system/ #where 1234567890 is output from wc -c
sudo umount system
rm -rf system
i've used this proecess with samsung system images, should work for moto images now too (bootloader unlocked, of course)
Yep, it's a good cheat sheet reference
Besides, on razr m and hd at least, you can also use this with safestrap without unlocking the bootloader.
aslomagic said:
Besides, on razr m and hd at least, you can also use this with safestrap without unlocking the bootloader.
Click to expand...
Click to collapse
Not sure what you mean by this; do you mean you could mount a modified system.img with safestrap? I guess it's possible since safestrap uses a system.img on the emmc, interesting idea
Q9Nap said:
Not sure what you mean by this; do you mean you could mount a modified system.img with safestrap? I guess it's possible since safestrap uses a system.img on the emmc, interesting idea
Click to expand...
Click to collapse
Yes, that's what I mean, more or less. You don't need safestrap to just mount it (use the terminal and "mount"), but you can use it to boot from it and try it.
I did this to try the Telstra image that pjcons dumped, which is pre-rooted and not signed (there it's no official signed image to date), and with a few tricks it worked without me having to unlock the bootloader.
Sent from my XT907
aslomagic said:
Google for a tool called simg2img (I used the python script that appears in get first few results, there should be other versions as well). That will unpack the image into a plain ext4 image that you can mount with any Linux pc (I recommend using a virtual machine if you have windows or mac).
Happy hacking!
Sent from my XT907
Click to expand...
Click to collapse
hello, i cant find anything on the basics of how this works, could you point me somewhere that explains it step by step or do one here. sorry of the noob question
TheWhiteChallenger said:
hello, i cant find anything on the basics of how this works, could you point me somewhere that explains it step by step or do one here. sorry of the noob question
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1588461
CNexus said:
http://forum.xda-developers.com/showthread.php?t=1588461
Click to expand...
Click to collapse
Thanks for the link I need to go learn Linux now. Lol I dontbgt the virtual machine thing at all. Its basically a Linux emulator right?
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Thanks for the link I need to go learn Linux now. Lol I dontbgt the virtual machine thing at all. Its basically a Linux emulator right?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No need to
http://sourceforge.net/projects/androidicsjbext/
CNexus said:
No need to
http://sourceforge.net/projects/androidicsjbext/
Click to expand...
Click to collapse
oh damn it. ok first i do appreciate the help. but that sucked. that was the frist program i tryed and it gives me "unknown file format" have i just been screwing up from the begining?
I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me
Hi!
is everything works fine after you did this?
I have live demo unit, I'm afraid bricking it.
there is the possibility of making a video demo?
there is the possibility of making a video demo?
QUOTE=Sirus2012;43240081]I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me [/QUOTE]
Pics pleas??
Verstuurd van mijn GT-I9505
Every thing is working fine for me only one prob.
when i reboot it . it stuck into the first logo. i have waited for more than 10 min.
than if i got recvoery and format the data. it boot than normally once.
Again if i had to reboot it. i have to goto recovery and format the data to boot the phone.
how to get rid of this?
br
s4 demo unit
Deduxma said:
there is the possibility of making a video demo?
QUOTE=Sirus2012;43240081]I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me
Click to expand...
Click to collapse
[/QUOTE]
please dose it mean my live s4 live demo unit will now behave like a normal phone and make or receive calls? after intalling this rom?
Help!
Just picked up a i9505x live demo unit.....does this process still work??
Demos don't have imeis do they I know our 3 s4s don't so calls can't be made
Sent from my GT-I9505 using xda app-developers app
s4sajii said:
Every thing is working fine for me only one prob.
when i reboot it . it stuck into the first logo. i have waited for more than 10 min.
than if i got recvoery and format the data. it boot than normally once.
Again if i had to reboot it. i have to goto recovery and format the data to boot the phone.
how to get rid of this?
br
Click to expand...
Click to collapse
Flash edited stock rom
Yes
Already did that. As described in the first post.
Br
Works but...
Everything works as it should but no WiFi.When flash Adam Kernel just get a black screen and that's it
I follow all the steps from the first post but at the end of odin flash i get FAIL . Any ideas?
Sirus2012 said:
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
Click to expand...
Click to collapse
i did it but i got this
Dj [email protected]ib ~
$ tar --delete --file=samrom.tar NON-HLOS.bin
tar: NON-HLOS.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
$ tar --delete --file=samrom.tar modem.bin
tar: modem.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
so sir what to do ???
mastro:° said:
i did it but i got this
Dj [email protected] ~
$ tar --delete --file=samrom.tar NON-HLOS.bin
tar: NON-HLOS.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
$ tar --delete --file=samrom.tar modem.bin
tar: modem.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
so sir what to do ???
Click to expand...
Click to collapse
same problem here.....seems like the command is not written in the right way
EDIT: I noticedd that when you start the program, it creates a folder inside 'cygwin-home' which is your user name and you have to place the samrom.tar in there in order to delete the two files!
btw the command lines are correct! cheers!!
stergios89 said:
same problem here.....seems like the command is not written in the right way
EDIT: I noticedd that when you start the program, it creates a folder inside 'cygwin-home' which is your user name and you have to place the samrom.tar in there in order to delete the two files!
btw the command lines are correct! cheers!!
Click to expand...
Click to collapse
So what`s the status of your phone, I was given an S4 LDU and I`d love to get rid of the demo all together, I`m not to bothered that I won`t be able to use it as a phone.
mloc33 said:
So what`s the status of your phone, I was given an S4 LDU and I`d love to get rid of the demo all together, I`m not to bothered that I won`t be able to use it as a phone.
Click to expand...
Click to collapse
Well, based on the stock ROM I downloaded it (I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5),I deleted the the files sirus2012 was referring to and I am stuck at a point were the Odin says fail while flashing the ROM....
Trying to figure out if I need to delete another more file from the .TAR
After the FAIL status in Odin, I disconnected the phone, removed battery and placed it again and I had an error saying 'Firmware needs to be recovered via Kies'
I, once then, flashed again the stock ROM(without the deleted files) and noticed there was no WiFi....
So I either have a phone with no WIFI, or an error and phone can't boot
Hope I can find a way out of this!
stergios89 said:
Well, based on the stock ROM I downloaded it (I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5),I deleted the the files sirus2012 was referring to and I am stuck at a point were the Odin says fail while flashing the ROM....
Trying to figure out if I need to delete another more file from the .TAR
After the FAIL status in Odin, I disconnected the phone, removed battery and placed it again and I had an error saying 'Firmware needs to be recovered via Kies'
I, once then, flashed again the stock ROM(without the deleted files) and noticed there was no WiFi....
So I either have a phone with no WIFI, or an error and phone can't boot
Hope I can find a way out of this!
Click to expand...
Click to collapse
Seems that there`s no real method or solution, pity, it`s a waste of a phone the way it is..
mloc33 said:
Seems that there`s no real method or solution, pity, it`s a waste of a phone the way it is..
Click to expand...
Click to collapse
Don't give up on that.....I think there will be a solution sooner or later....(I'll try to find it asap) because this 'phone' is really good
Or it could be something really small that we can't see and do it wrong.
stergios89 said:
Don't give up on that.....I think there will be a solution sooner or later....(I'll try to find it asap) because this 'phone' is really good
Or it could be something really small that we can't see and do it wrong.
Click to expand...
Click to collapse
True man, fingers crossed I suppose
mloc33 said:
Seems that there`s no real method or solution, pity, it`s a waste of a phone the way it is..
Click to expand...
Click to collapse
Sirus2012 said:
I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me
Click to expand...
Click to collapse
Well I think I figured it out with my S4 demo unit to make WiFi work.
All the steps were followed BUT...
I DIDN'T delete the two files(modem and NON-hlos) and continued with the procedure
The most important step was .17 which redirects you to another thread about TWRP and Adams Kernel...
Following the steps there where enough to solve my issue.
And now my WiFi works pretty good(so far so good at least for the last 2-3 hours )
Let me know if it worked for you too!
Cheers!
Hey, I noticed while looking through the Stock Firmware AP file, that in meta-data/fota.zip there are .jar files that have to do with package signing. Only issue is that the zip is password protected. If someone has the Compute power and skills to decrypt a zip and look at the jar files and ****, maybe we could find a way to sign our own TWRP recoveries and roms. Just a thought, i'll post a link to the fota.zip file i was talking about in a bit if anyone wants to take a crack at it. (Google drive is taking forever to upload cause of AT&T's ****ty DSL speeds, sorry)
Download Link: htt*ps:/*/drive.*google*.com/file/*d/0B9tb-svjqaVD*b3Y0V0tXR3drSzA/vie*w?usp=sharing (Remove all *'s from link, stupid 10 post until you can post links limitation)
Thanks,
Lavavex
Did you saw this Thread?
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
About fota.zip...
Did you heard about plain text attack?
In few Seconds... minutes done... no password required but you can unpack.
Best Regards
Yesterday I have download this fota.zip... and yes... same password as for instance from my prior test with:
SM-J330F and 1 more...
Here are the 3 keys to decrypt if somebody want try...
Code:
2b4d493c
6142b289
1b7024aa
Code:
Key0
Key1
Key2
I have used Advanced Archive Password Recovery from elcomsoft...
Best Regards
adfree said:
Yesterday I have download this fota.zip... and yes... same password as for instance from my prior test with:
SM-J330F and 1 more...
Here are the 3 keys to decrypt if somebody want try...
Code:
2b4d493c
6142b289
1b7024aa
Code:
Key0
Key1
Key2
I have used Advanced Archive Password Recovery from elcomsoft...
Best Regards
Click to expand...
Click to collapse
Which will allow unpacking of the above zip? I thought it needed a zip password.
osm0sis said:
Which will allow unpacking of the above zip? I thought it needed a zip password.
Click to expand...
Click to collapse
We never found the Password... but for Decryption you need only these 3 Keys...
They can be easily found in few Minutes... with the right Tool...
Code:
2b4d493c
6142b289
1b7024aa
Here Key0 Key1 Key2 for Samsungs fota.zip...
This is really no rocket science...
Simple read about plain-text attack...
You can see all filenames...
You can see all filesizes etc...
Many files are floating around the Internet... to create ZIP for attack...
Then result is in few Minutes possible... :angel:
Use these 3 Keys in Tool:
Code:
Advanced Archive Password Recovery
And try self to unpack...
Best Regards
Edit 1.
Screenshot added...
Then maybe more clear...
Trial Version have mabye limtations... but to see it work... it is enough to play with trial.
@adfree or to anyone who can answer.
Quick question, what are the legal limitations to what is going on here? I may or not have a file from inside the fota.zip, but will sharing it put me in the legal wrong? If it is within the legal boundaries, I'd be happy to upload it for anyone to take a look at, but I don't want to land on the wrong side of the law by doing so. Please do let me know, as this is the most exciting development we've had when it comes to bootloader unlocking in a while. Also, it seems as though we can't view the entirety of the contents of the fota.zip with the trial version of the zip extraction tool mentioned in this thread, so if someone with more knowledge about this can confirm we could unlock our bootloaders with the contents of the zip (based on what is currently known about this), I'd be happy to bite the bullet of paying for the premium version given we can do this within the boundaries of the law.
Thanks.
1.
Maybe you can answer your question self...
Samsung PROTECTED this ZIP with password.
2.
IMHO it is Kernel related...
Yeah I know... Boot is every irritating...
But it is not sboot.bin related...
3.
About decrypting all files...
There are floating around Command Line Tool...
Code:
pkcrack
Try to Google it...
I have not tried...
I am 1 click Button user...
Best Regards
zipdecrypt from the pkcrack package plus those 3 keys worked flawlessly. :good:
Edit: Crazy number of utilities in this zip, but no script to run them all, and a lot of references to external files. No smoking gun like a "sbootimg_signer" binary or anything to make their proprietary footer signature, and no Samsung signature files.
the password for that zip is fotatest1234
Correct. All fota zips passwords are fotatest1234
Drdra3 said:
Correct. All fota zips passwords are fotatest1234
Click to expand...
Click to collapse
@lavavex , @osm0sis
Yes it is, but now the question still to be answered is, do the tools within the fota.zip file, actually work for legitimately repacking the boot/recovery image? Because in the fota.zip I checked from Android Pie's release it mentioned the "user/test-keys" and very much so had all of the compiled tools to actually patch a system and create and ADB flashable zip for stock recovery.
Could we technically make a signed sideloadable update.zip if the the update package was created on the device itself? The scripts included, along with the updated compiled binary tools, really do seem to be the Toolkit we've been looking for but have overlooked. I haven't tested it out fully, but I'm still reading about how to proceed. It isn't just the S7 either. So are the tools customized to the device, the android branch, or the bootloader?
Delgoth said:
@lavavex , @osm0sis
Yes it is, but now the question still to be answered is, do the tools within the fota.zip file, actually work for legitimately repacking the boot/recovery image? Because in the fota.zip I checked from Android Pie's release it mentioned the "user/test-keys" and very much so had all of the compiled tools to actually patch a system and create and ADB flashable zip for stock recovery.
Could we technically make a signed sideloadable update.zip if the the update package was created on the device itself? The scripts included, along with the updated compiled binary tools, really do seem to be the Toolkit we've been looking for but have overlooked. I haven't tested it out fully, but I'm still reading about how to proceed. It isn't just the S7 either. So are the tools customized to the device, the android branch, or the bootloader?
Click to expand...
Click to collapse
Presumably what I previously said still stands:
osm0sis said:
Crazy number of utilities in this zip, but no script to run them all, and a lot of references to external files. No smoking gun like a "sbootimg_signer" binary or anything to make their proprietary footer signature, and no Samsung signature files.
Click to expand...
Click to collapse