I'm trying to covert a thin-client RDP system into a standalone linux system. I'd like to run a lighthttp server on it and auto-boot it to chromium (on start up).
The device comes with a crappy RDP interface and has a method for installing software UPGRADES via FTP. --- Confirmed working.
Doing some research on the web I was able to find an update package for this device. ATTACHED AS TORRENT FILE.
Using CENTOS I've tried to extract the RAMDISK but Linux doesn't seem to know how to extract the file type. I've tried a ton of scripts from xda-devs none seem to work.
I've tried just changing the system dir to see if I can get that work but it seems that the new image doesn't take to the device. I did see that the scripts have checksum info in them but not sure how to repackage or change them to adjust for the new changes.
I do see the build.prop file with a ton of ANDROID stuff and the package is APK signed. Thus I'm thinking it's an ANDROID setup. Also I see that the device is using busybox.
Any help or ideas how to get this doing what I need it?
Thanks!
chavenor said:
I'm trying to covert a thin-client RDP system into a standalone linux system. I'd like to run a lighthttp server on it and auto-boot it to chromium (on start up).
The device comes with a crappy RDP interface and has a method for installing software UPGRADES via FTP. --- Confirmed working.
Doing some research on the web I was able to find an update package for this device. ATTACHED AS TORRENT FILE.
Using CENTOS I've tried to extract the RAMDISK but Linux doesn't seem to know how to extract the file type. I've tried a ton of scripts from xda-devs none seem to work.
I've tried just changing the system dir to see if I can get that work but it seems that the new image doesn't take to the device. I did see that the scripts have checksum info in them but not sure how to repackage or change them to adjust for the new changes.
I do see the build.prop file with a ton of ANDROID stuff and the package is APK signed. Thus I'm thinking it's an ANDROID setup. Also I see that the device is using busybox.
Any help or ideas how to get this doing what I need it?
Thanks!
Click to expand...
Click to collapse
Any ideas out there?
Bump?
Related
Hi all,
I am trying to setup my Mac OSX (Mac Mini) to build and deploy the Cupcake source code and deploy the built images on my ADP1 device.
I must admit - I am no Linux guy, so a bit slow on understanding the various instructions.
My problem - I was somehow able to get the sources down to my Mac, and even run a successful MAKE.
But - got stuck there (could not figure out how to run the built images on the emulator).
So I decided to be brave and compile & install on my ADP1 device.
This is where I am stuck:
In the explanation at the Google site, they claim there should be a ".Repo" directory holding a file called "manifest.xml" in it, and that I should download and add to that directory a file called "local_manifest.xml".
I can not find such a ".Repo" directory, and hence - dont know where to put that file.
Any help would be highly appreciated !
Shimon Shnitzer
TAKEphONE said:
Hi all,
I am trying to setup my Mac OSX (Mac Mini) to build and deploy the Cupcake source code and deploy the built images on my ADP1 device.
I must admit - I am no Linux guy, so a bit slow on understanding the various instructions.
My problem - I was somehow able to get the sources down to my Mac, and even run a successful MAKE.
But - got stuck there (could not figure out how to run the built images on the emulator).
So I decided to be brave and compile & install on my ADP1 device.
This is where I am stuck:
In the explanation at the Google site, they claim there should be a ".Repo" directory holding a file called "manifest.xml" in it, and that I should download and add to that directory a file called "local_manifest.xml".
I can not find such a ".Repo" directory, and hence - dont know where to put that file.
Any help would be highly appreciated !
Shimon Shnitzer
Click to expand...
Click to collapse
".Repo" is a hidden folder any folder with a "." in front of it will be hidden, enable the viewing of hidden folders and you'll find it.
Thanks !
I knew I was probably missing something simple...
Hi All,
I'm still looking for a way to either decrypt or extract an apk from an SEUS signed/encrypted firmware.
I've tried the Sin_Reconstructor and I've tried replacing the JAR file in plugins with the one provided, but this still seems to simply download the same encrypted files it always has.
I tried to use the other plugin that was supposed to do a dump such as dump0.zip and dump1.zip however this didn't work either.
I'm using SEUS and not Pc Companion to try and get this all done.
Is there a guide anywhere out there on the net for decrypting seus firmwares. I've tried and tried and just can't seem to work out how its done.
I want to learn as much as possible, and once I've done the learning I'd love to give back everything I learn, but without understanding the basics it just feels I'm dead in the water.
Any help from anyone would be greatly apreciated.
Just out of curiousity why do you want to extract it from a signed firmware? From what I gather the decrypted roms are no different just without branding. As well I think actually decrypting rom's is for people with some solid experience in the field. If you want to get your feet wet with extracting and modifying apk's go here http://forum.xda-developers.com/showthread.php?t=714288 . I am completely new to programming as well and this is what I have learned so far. Good luck and learning android is a blast!
BTW the link only really covers visual mods. For learning android coding this is a great place to start: http://developer.android.com/index.html
the Android's SDK not contain an Android device emulator ?
If yes, you can mount the Fw on this VM and extract the APK to an sdcard emulated (HD) ...
The System's APK is in /system/app
paid APK : /data/app
Thol said:
the Android's SDK not contain an Android device emulator ?
If yes, you can mount the Fw on this VM and extract the APK to an sdcard emulated (HD) ...
The System's APK is in /system/app
paid APK : /data/app
Click to expand...
Click to collapse
So you can mount SEUS encrypted firmware on the VM now? When did that start?
Hello.
I want to know how can I verify the digital signature of an APK file.
I'm currently downloading what calims to be a leaked Nexus 4 system dump.
When I right click->Properties on an exe file (on Windows), I can see Digital Signatures tab and there I can see certificates etc.
I want to do something similiar to APK files. In my current situation, I want to make sure apps I'll find on the download are actually unmodified, Google-made thing.
This will also come in handy in other situations.
Solutions that work on Windows are great, solutions that work on Android are also OK.
Thanks.
I was looking for a similar topic but I did not find one. Refers to problems with running applications added to "system.img".
I bought UMIDIG S for my father-in-law. It is based on a mediatec chipset. Unfortunately, soft is tragic, and there is no full translation, so I decided to bury it a bit in "system.img".
I can easily install the file in Linux and make changes in it. I can delete applications, I can make changes in configuration files and "buikd.prop".
Unfortunately, all APK files were uploaded to "system.img" even though I set permissions 755 for directories, and 644 for directories. Although the files are root: root, after uploading such "system.img" none of these applications works for the phone. The system sees them and tries to load. Unfortunately, applications hang because of errors. The system informs that the application hangs, and does not load its window. The icons of these applications and the names do not appear either (applications have green robocik as icon, and domain name, e.g. com.android.clock ....)
I am asking for advice. How to add APK files to the unzipped "system.img" so that after packing and uploading to the phone there were no errors ???
Do you have found how add app in system.img?
It's all around, but you can replace apps with others. In the linux system, unpack the img, and mount them. Then you can freely rename files as well as move files within the .img mount point
I chose the applications or other files I did not need, and moved them to the directories (which I named my applications). If the application needed libraries, you also had to get files in a similar way, and place them in arm or arm64 directories.
Then prepared files "stuffed" with data, using the command DD. That is, dd if = (source file) of = (the recipient file at the system.img mount point).
Thanks for reply, so this only on Linux? For Windows there is something?
Markosv76 said:
Thanks for reply, so this only on Linux? For Windows there is something?
Click to expand...
Click to collapse
I do not know, I do not use Windows. Certainly you can in a similar way from BSD systems, probably from Android and MacOS. I read something that Microsoft can somehow support linux shell, but I do not know the details. You can always use some distribution that works with a pendrive.
Thanks, I will try again
Markosv76 said:
Thanks, I will try again
Click to expand...
Click to collapse
You can use Virtual Box to run a Linux distro inside Windows or you can try using Cygwin.
Sent from my LGL84VL using Tapatalk
jaroslawstrauchmann said:
I was looking for a similar topic but I did not find one. Refers to problems with running applications added to "system.img".
I bought UMIDIG S for my father-in-law. It is based on a mediatec chipset. Unfortunately, soft is tragic, and there is no full translation, so I decided to bury it a bit in "system.img".
I can easily install the file in Linux and make changes in it. I can delete applications, I can make changes in configuration files and "buikd.prop".
Unfortunately, all APK files were uploaded to "system.img" even though I set permissions 755 for directories, and 644 for directories. Although the files are root: root, after uploading such "system.img" none of these applications works for the phone. The system sees them and tries to load. Unfortunately, applications hang because of errors. The system informs that the application hangs, and does not load its window. The icons of these applications and the names do not appear either (applications have green robocik as icon, and domain name, e.g. com.android.clock ....)
I am asking for advice. How to add APK files to the unzipped "system.img" so that after packing and uploading to the phone there were no errors ???
Click to expand...
Click to collapse
did you find a solution to this? please reply if yes, I am having the same problem
ROM Explorer
From time to time I need to extract some files from various Android ROMs. So far I downloaded the ROM file and then started to search for further tools to extract files from the downloaded ROM. If all went well I ended up with an image I could open with ext4_unpacker to finally extract the files I needed. This whole procedure took a lot of time, involved tools from unknown sources and often simply didn't work. So I decided to create my own tool.
ROM Explorer can directly open the following files:
zip archives with img or new.dat entries
Samsung md5 archives
Sony ftf archives
Huawei update.app archives
img/ext4 image files
lz4 image files (used by Samsung)
sin fies (used by Sony)
In case you have a file which is not supported let me know. Maybe I find the time to add support. Or simply add it yourself - ROM Explorer is Open Source.
Usage
Download the installer and run it or build your own version with Visual Studio 2017.
Start the executable. You will see a window similar to ext4_unpacker. In the first line you select a file, in the second line you can choose an archive entry if the file is an archive file.
Loading a file or archive entry can take a significant amount of time and disk storage. ROM Explorer may need to create temporary files with several gigabytes. A fast flash disk helps a lot!
You can extract files or folders by dragging and dropping them to Windows Explorer.
Downloads
ROM Explorer 0.9
ROM Explorer 0.9.1
Thanks To
ROM Explorer would not exist without the distributed knowledge of this forum. Especially I want to thank worstenbrood, Androxyde, IgorEisberg for their work.
So I'm waiting for your comments - but be patient it may take some time for me to react
Reserved for whatever purpose...
Wew
Let me try and report you back
Thank you I will try this out. Thanks too for making it open source
Not Running on Windows 7 x64
samidos said:
Not Running on Windows 7 x64
Click to expand...
Click to collapse
0.9.1 should fix this. Be sure to first uninstall before installing 0.9.1.
After hours of google search and downloading countless apps that dont work I found this. This app is legit and works on windows 10 64bit. Thank you for your work.
Your app is GREAT! Thanks for sharing it.
Edit: Answered my own question. Windows 10 tip "Run As Administrator" and dont drag files "to the desktop" but instead to an Explorer window.
Can this program find the differences between compiled ROMs?
I ask this question because Xiaomi on the Mi 9 released an initial kernel with sourcecode that was changed over time without updating the GitHub https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/cepheus-p-oss and because of this change, the ROMs have something different between how they connect to the cameras. The old ROM versions (4/1/2019 and before) connect fine to the cameras, but post that date, a custom kernel built from the GitHub source will fail to connect to the cameras. Since the change has not been made open source on GitHub, there has to be another way to find and patch new kernel builds in order for them to work. Would your software be able to extract these changes? If not, do you have any other ideas which may? Much appreciated.