Hello.
I discovered that the encryption, which I understand comes with ICS, is not available with my cheap D2Pad with ICS 4.0.4. I have looked in Settings/security, and do not find encryption there, or anywhere else. The online documentation points me to Settings/Personal/Security/encryption, but my problem is that Personal and Encryption are missing entirely from my settings interface.
Is it possible to install Encryption through a file obtained here at XDADevelopers? I have downloaded a settings.apk posted by one of your members. Is this what I need to replace? Would I use ADB to push/pull the Settings.apk?
My theory, after doing some reading on this, is that my device has a dumbed-down version of ICS, which has excluded encryption from the settings.apk.
May I ask for your advice?
The NOOB video is wonderful, by the way.
Thanks in advance.
Robert
Related
It's my understanding that there are currently two updated ROMS to download - the Modaco one and the generic HTC update found on the Modaco thread.
My question is, having rooted the phone, why would the Modaco one be a better bet? I feel like I may as well go for the generic one. I am a bit of a noob when it comes to things liked this, so a summary of pros and cons to each would be extremely helpful. For instance, does the generic ROM allow root access?
Also, for anyone in the same position as me, check out the unlockr guide videos on rooting and upgrading the ROM on your phone - http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
So handy!
Thanks.
This is just from what (i think) I know...
1/ Has additional apps that are useful e.g. CustomLocale, Spare Parts, Anycut, Wifi teethering, A2SD etc. You can get these yourself but obviously you would have to do the leg work.
2/ and you get all the stuff listed on the first page of the Modaco ROM thread.
3/ If you use the generic HTC ROM it won't be rooted.
4/ Most of the folders you would want write access to are already mounted by default. If you are a noob this will save you working out how to do this.
For me it was a no brainer to use the MCR.
Thank you for the response! What do you mean by 'write access' ?
simcarloc said:
Thank you for the response! What do you mean by 'write access' ?
Click to expand...
Click to collapse
"Write Access" means you can copy files on to the drive/folder. Android is based on unix so by default you don't have write or even read access to quite a few of the folders you would normally need access to for modding, copying files, deleting files, putting files on your phone etc.
You have to do this via a command prompt either from your computer when the phone is connected or using an emulator on the phone. You may or may not want to do any of these things but it would generally make life easier for you if you wanted to.
Ok. Thanks for breaking that down for me Isim.
All that remains for me to do now is partition my SD card. I have looked at some of the guides and they scare the ****e out of me. What's the simplest way of partitioning? Do I have to enter the world of command-line prompts? Any programs with a GUI?
Hi Isim , just another quick question does this rom support portuguese language, thanks
simcarloc said:
My question is, having rooted the phone, why would the Modaco one be a better bet? I feel like I may as well go for the generic one. I am a bit of a noob when it comes to things liked this, so a summary of pros and cons to each would be extremely helpful. For instance, does the generic ROM allow root access?
Click to expand...
Click to collapse
If you flash to the generic ROM, you'll have to root your device again since the generic ROM won't be rooted (assuming it is the unadulterated WWE release).
Regards,
Dave
I've been playing with the new firmware file for a few hours now, but can't really extract it. I'm really interested in the apps, etc, so could someone tell me if there's any way to extract it? OpenAOS, and other archos AOS extractors didn't work sadly.
If someone could do me a system dump of the 101 G9, it would make this whole extraction unneeded (for me atleast!).
Thanks in advance!
And what do you want to do?
None of the Apps will work as they are for HoneyComp.
They all need a newer OS and all the other things that come with the new tablet.
It would be the same useless try that has been done in the beginning of the year with the HC SDK Binaries.
Stop hurting yourself and wait for ICS Sourcecode and then we will see.
fzelle said:
And what do you want to do?
None of the Apps will work as they are for HoneyComp.
They all need a newer OS and all the other things that come with the new tablet.
It would be the same useless try that has been done in the beginning of the year with the HC SDK Binaries.
Stop hurting yourself and wait for ICS Sourcecode and then we will see.
Click to expand...
Click to collapse
So my Asus Transformer isn't HC? Good to know...
I exactly know what I want to do with the apps, so please, no more non helping posts. I started this thread to find answers, not stupid people commenting on everything without reading.
And where did you state that you want to use them on a Transformer?
Even then, none of the Archos APK will work there, as Archos has also changed some underlying OS Funktions and drivers.
As the Gen9 has a completely different SOC ( Tegra2 vs TI OMAP 4430/4460) none of those needed Drivers are working.
So again, what do you want?
fonix232 said:
I exactly know what I want to do with the apps, so please, no more non helping posts. I started this thread to find answers, not stupid people commenting on everything without reading.
Click to expand...
Click to collapse
To simply answer your question...
I'm not familiar with the gen9 devices, but i assume that archos did not change their basic infrastructure on these devices (using squashfs).
If that's the case there are basically three ways i'm aware of:
1. Gain root access on your device and directly copy the files to an external device. Of course this is not very comfortable and you'll have to take care of symlink's, etc.
2. Make a dump of the partition where androidmerged.squashfs.secure is
included using a dd tool or similar.
After doing so, you'll have to investigate the raw data for squashfs signature and remove the leading header.
Then you might be able to get the raw squashfs file containing all data.
This file could be mounted as loop on a linux machine supporting squashfs files.
As i pointed out, i'm not aware of the internal structure in gen9 devices, so i can't tell you which partition is the right one.
Maybe you could post some output of your device (e.g. cat /proc/partitions or mount)
Anyway i guess you'll have to be root to access the mtd devices in the end.
3. Extract the androidmerged.squashfs.secure file directly from the .aos.
Using this way you'll neet to tweak aos-tools with the correct key for gen9 devices. This key has not been published yet and that's why aos-tools is lacking support for gen9 devices.
To be honest we don't know anything about the security mechanism on gen9 yet.
Some words in common...
Please respect the rules!
Abusing other users is a no go
Regards,
scholbert
fzelle said:
And where did you state that you want to use them on a Transformer?
Even then, none of the Archos APK will work there, as Archos has also changed some underlying OS Funktions and drivers.
As the Gen9 has a completely different SOC ( Tegra2 vs TI OMAP 4430/4460) none of those needed Drivers are working.
So again, what do you want?
Click to expand...
Click to collapse
Please, do check my signature...
I want to check out the apps what aren't stock, etc.
wait the SDE
Hey fonix232,
did you see this:
http://forum.xda-developers.com/showthread.php?t=1349184
With the gen9 keys, the aos-tools could be tweaked to extract gen9 firmware files.
Ask letama for help/code.
He already successfully extracted the firmware!
Regards,
scholbert
Hi there,
Here it is:
extracted 3.6.29 firmware
Almost untouched, just with su+SuperUser.apk added.
LeTama
I'm currently an Android developer and I would like to make an application that will enable and disable logcat.
The purpose would basically be to save battery for the standard user, and to fix logcat not working for developers.
I know of one method to disable/enable logcat which is:
logcat-disable
logcat-enable
Unfortunately, this does not work on all devices since it is based on the kernel.
Also, most (I believe all) devices have a /dev/log/main/ folder in which there is a file that has logs printed into it. I could also possibly attempt to delete the folder (which it will likely be re-created at reboot) or MAYBE change the file permissions for it to prevent the system from writing to it. This option may or may not work.
So, my question is more for kernel developers or those very familiar with kernel development/file structure.
Does anyone have any idea what file is generally modified when a kernel enable/disables logcat?
P.S. I was able to figure out the answer to my question on one kernel, but I doubt if it applies to all.
P.P.S. I'm aware that this is probably a pointless question since every kernel is different, but I'm not sure, so that's why I'm asking.
Thank you!
Folks, I am trying to get the full encryption on my sony xperia mini pro working. This might also be interested for other people...
According to different sources on the internet, full encryption of phone is available (as regards of OS funcionality) as of android version 3/4.
My Xperia phone came with 2.3, so I updated it to 4.0.4. via the sony update tool.
But at Settings/security I still do not see the "Encrypt phone" capability. I checked with a friend who als has an android 4 phone and when he goes to Settings/security, he does have this option.
So I rooted the phone and installed the Android SDK kit. I now have a shell with root access and looked around through some config files but I do not see anything regarding security capabilities anywhere.
So can anyone please tell me where the files are so I can enable encryption capability to come up at settings/security?
I am sure there is some config file somewhere that just needs to be modified, like set "encryption = enabled" or something like that.
If I am wrong please let me know.
Why is this encryption capability not available by default (as on other phones with android 4) anyways?
Thanks for your support!
joha123 said:
Folks, I am trying to get the full encryption on my sony xperia mini pro working. This might also be interested for other people...
According to different sources on the internet, full encryption of phone is available (as regards of OS funcionality) as of android version 3/4.
My Xperia phone came with 2.3, so I updated it to 4.0.4. via the sony update tool.
But at Settings/security I still do not see the "Encrypt phone" capability. I checked with a friend who als has an android 4 phone and when he goes to Settings/security, he does have this option.
So I rooted the phone and installed the Android SDK kit. I now have a shell with root access and looked around through some config files but I do not see anything regarding security capabilities anywhere.
So can anyone please tell me where the files are so I can enable encryption capability to come up at settings/security?
I am sure there is some config file somewhere that just needs to be modified, like set "encryption = enabled" or something like that.
If I am wrong please let me know.
Why is this encryption capability not available by default (as on other phones with android 4) anyways?
Thanks for your support!
Click to expand...
Click to collapse
Encryption is only available on devices which use the newer emmc style of partitioning. I'm going to guess yours uses the old block style YAFFS partitions?
See http://source.android.com/tech/encryption/android_crypto_implementation.html
I suspect that, unfortunately, rooting and changing some config files is way to easy of a solution. For that phone I don't know, but with a pure Android install, and on most retailers phones, encryption is very easy. Not sure why Sony opted out.
The easiest solution is to install a custom ROM like cm10 or something aosp based. But you will lose all of the nice things Sony may have included, and be left with a system that you can encrypt.
You choose
Sent from my Nexus 7 using xda premium
I have a question, and if possible the answer should be as wide as possible to work on as many systems as possible. While I am not fully conversed in Android functions, syntax, and interfaces, I have been programing various computers since the mid 80's and have applied rooting/jailbreaking methods to several systems (if it functions like a computer, I want my Admin rights, much thanks to each and all authors of these). I know that someone somewhere out there may have asked and already found a solution to this very annoying problem.
Thanks to the Google's decision to increase security in the Android OSes (KitKat and higher) by removing write access to the SD Card (as I call it a very 'bonehead' and brute force decision), most of the older apps do not work properly anymore with the user added SD Cards and most are not being updated with some form of support (create a folder on SD Card). The solution for most persons is to root the system then either run an app that corrects the problem or install a new LRAM image (Lockable RAM: 'unlock' the RAM and overwrite its data with a new image then re-lock it. I don't like the term 'ROM' for this as it has been incorrectly used since the late 80's). I have found at least 2 file managers that say they have a (in-app) solution, but these solutions don't extend to all of your other apps (ie "Root Explorer" or "B1" solution doesn't help your File server/uTorrent/Photo Gallery app).
But what of the owners that for one reason or another can't root their system (unable to root, not authorized or allowed to root, etc.) but want/need to have write access to the user added cards (mainly because their internal storage is just too small)? Example, in my case my personal phone has several apps that require it to remain in an unrooted state for certain work related programs (security issues).
So here is my question:
Is it possible, on an unrooted and stock LRAM android device, using ADB to PULL the "platform.xml" file, add the line '<group gid=”media_rw” />' to it, then PUSH the edited file back to the android device?
I realize this may require entering (various name versions) Recovery or Update mode which is specific to each device (I think Samsung calls their ODIN). But I think the ADB commands and computer side instructions should be the same. So if it is possible, please list all ADB instructions (I know the text editor used will depend on the PC/MAC OS used).
Thank you one and all that give any advice or assistance.
Well it looks like there have been a lot of lookers since I first posted this but still no reply by anyone that knows Android OS inside and out. Most of you are probably thinking "tl:dr" to all of it.
I know there has to be a way to update/upgrade system files that doesn't require rooting or a way to find the manufacturer's or cellular vender's access path or password.