Hi all.
I'm working on a custom ROM for the Nexus 10 based on the latest 4.2.1 build.
It's almost finished, but I'm struggling with a few things and though someone might be able to offer some assistance.
1: I'm trying to add the advanced power menu like is found in some other ROMs for the N10, but am hitting dead ends everywhere. I've found a few guides online but none seem to be relevant to this device. My ROM is de-odexed. I have decompiled the framework-res.apk file but can't find any clues.
2: I'm trying to disable OTA updates and hide the "System Update" option from the "About Tablet" menu, but can't seem to figure it out.
Any help would be greatly appreciated, I know both are possible as I have seem both working in other ROMs, but I don't want to rip off someone else's work.
Cheers,
Will
With some help from a fellow forum member I was able to figure out how to remove the "System Update" button from the About Tablet menu.
I modified the device_info_settings.xml inside the settings.apk file and recompiled it, then re-cooked the rom and flashed it and it worked perfectly.
Now I just need to find where the updater.apk or equivilant is hiding!
In the meantime I cooked in fotakiller.apk which seems to do the trick.
Cheers,
Will
Related
Hi everyone,
I picked up a Droid X a few days ago and I have been looking into modifying it ever since. So far I have successfully Rooted, De-Odex'd, and installed custom themes. Being new to the android platform, it has taken some time to learn and there is still more to know. I have started to piece together a guide and I am looking for some input from the community to correct/add/remove tips/tricks/tools/etc as needed.
Please take the time to review and let me know what you thoughts are. Let me know what you encountered when trying to do a specific task. For us n00b's out there, let me know what you were unsure of and how you resolved the issue. My goal is to make one source for the Droid X that gets rid of most confusion.
Look forward to your input.
Thanks!
Update 10/26/2010: Guide Complete, still open for suggestions, just PM me.
Updated attached guide and also posted to wiki.
RLM703 said:
Hi everyone,
I picked up a Droid X a few days ago and I have been looking into modifying it ever since. So far I have successfully Rooted, De-Odex'd, and installed custom themes. Being new to the android platform, it has taken some time to learn and there is still more to know. I have started to piece together a guide and I am looking for some input from the community to correct/add/remove tips/tricks/tools/etc as needed.
Please take the time to review and let me know what you thoughts are. Let me know what you encountered when trying to do a specific task. For us n00b's out there, let me know what you were unsure of and how you resolved the issue. My goal is to make one source for the Droid X that gets rid of most confusion.
Look forward to your input.
Thanks!
Click to expand...
Click to collapse
Looks like you put a lot of time/effort into this.
How about integrating that info into the wiki?
http://forum.xda-developers.com/wiki/index.php?title=File:Motorola_Droid_X.png
Nice work! +1 on zaphod's sug. ping me if you need any help!
Will do, I have some more work I'd like to do on it though. Thanks for the tips and support
Dude...seriously...THANK you. Step-by-step directions are great when you only have a vaguely general idea of what you're supposed to be doing (that's what happens when you still haven't tried to learn though, so it's kinda my fault...).
Hey- this is awesome. Keep up the good work. Don't forget- now that we can overclock - those will be useful instructions since they are pretty confusing for noobs right now.
nice work!
Thanks for taking the time to write this up for all of us trying to hack our Droid X's.
nice guide, i didnt realize the recovery mod was so easy until i read this. nice to have a backup now.
Does anyone have anytips on getting this root to work. Ive installed the drivers and followed the instructions on the guide but for some reason when i hit the root button it gets hung up halfway through it. Then it can find my DroidX. help plzz
Thanks in advance
hadog32 said:
Does anyone have anytips on getting this root to work. Ive installed the drivers and followed the instructions on the guide but for some reason when i hit the root button it gets hung up halfway through it. Then it can find my DroidX. help plzz
Thanks in advance
Click to expand...
Click to collapse
Guide is a bit out dated. A much easier root method is z4root. apk and support page below:
http://forum.xda-developers.com/showthread.php?t=833953
1. Download .apk, copy to SD card.
2. Enable "Unknown sources" (Settings => Applications => check "Unknown sources"
3. Use file manager to navigate to file on SD card, install. I recommend rebooting before install and again after install, prior to running root command from within z4root. <= may help the process run smoother.
4. Open z4root, tap Permanent Root, let it run, once complete your device should restart and you would then be rooted.
Next step, installing ROM's. Many great ROM's out there, I highly recommend Liberty.
Hi All
I have the most recent version of Oxygen which includes a "theme picker" app.
Similar to the one found in the HD ROM's it gives the opportunity to change the entire system theme, without flashing a zip. Which is good news
However, I have been trawling the internet trying to figure out how to create the .apk needed to create my own themes, failing miserably.
Could someone with the required knowledge post a tutorial maybe? Or a link to where the info is so that I can do my own research?
Thanks
i've not installed the test rom so cant check, but does it come with any theme.apk's pre-installed?
if so i'd start by pulling them apart and looking at the .xml and images and change them from there.
str355 said:
i've not installed the test rom so cant check, but does it come with any theme.apk's pre-installed?
if so i'd start by pulling them apart and looking at the .xml and images and change them from there.
Click to expand...
Click to collapse
Do you know I didn't even think of that
I shall do so and see what I can come up with
Well I downloaded the Android SDK and all the tools required, then I installed eclipse and started a tutorial on how to build an app - as I assumed this is what I will need to do... but then my brain started to hurt and I needed sleep!
Hello,
I am using Sacs Custom ROM 4.2.2 Kit-Kat on Sprint (SPH-L720). Software version, Baseband version, and Build number all reflect NAE.
I don't have enough posts to ask my question in the development thread (and maybe this is a more appropriate venue anyway).
When I go to Settings -> My device -> Lock screen -> Screen lock, every option, except for PIN and Password, is greyed-out with the following message under each option:
Code:
Turned off by administrator, encryption policy or credential storage.
Even though I would prefer to use a Pattern (that option is disabled), if I select one of the available options (PIN or Password), I complete the setup but the Swipe method still applies and anyone can unlock the device with a Swipe gesture. For whatever reason, the method I choose is not effective.
I have done quite a bit of searching-around on this issue, both on these forums and elsewhere, and many of the 4.2.2 ROMs have this problem. Negalite, Slim Bean, and Omega, to name a few. So, I am thinking that perhaps Sacs Custom ROM is no exception and this is a "known issue" on which the devs are already working.
Does anybody know this to be the case?
All of the older threads I've found that mention this problem suggest going to Settings -> More -> Security, and choosing Clear credentials from the bottom of the list. I've tried this and it changes nothing. I have also tried a full Factory Reset, and the problem persists. In fact, I have completely wiped the phone and reinstalled the ROM from scratch and this problem is present from the very first power-on.
Thanks to anyone who may be able to confirm whether or not this is a "known issue" with Sacs Custom ROM 4.2.2 Kit-Kat!
DrRichardQuack said:
Hello,
I am using Sacs Custom ROM 4.2.2 Kit-Kat on Sprint (SPH-L720). Software version, Baseband version, and Build number all reflect NAE.
I don't have enough posts to ask my question in the development thread (and maybe this is a more appropriate venue anyway).
When I go to Settings -> My device -> Lock screen -> Screen lock, every option, except for PIN and Password, is greyed-out with the following message under each option:
Code:
Turned off by administrator, encryption policy or credential storage.
Even though I would prefer to use a Pattern (that option is disabled), if I select one of the available options (PIN or Password), I complete the setup but the Swipe method still applies and anyone can unlock the device with a Swipe gesture. For whatever reason, the method I choose is not effective.
I have done quite a bit of searching-around on this issue, both on these forums and elsewhere, and many of the 4.2.2 ROMs have this problem. Negalite, Slim Bean, and Omega, to name a few. So, I am thinking that perhaps Sacs Custom ROM is no exception and this is a "known issue" on which the devs are already working.
Does anybody know this to be the case?
All of the older threads I've found that mention this problem suggest going to Settings -> More -> Security, and choosing Clear credentials from the bottom of the list. I've tried this and it changes nothing. I have also tried a full Factory Reset, and the problem persists. In fact, I have completely wiped the phone and reinstalled the ROM from scratch and this problem is present from the very first power-on.
Thanks to anyone who may be able to confirm whether or not this is a "known issue" with Sacs Custom ROM 4.2.2 Kit-Kat!
Click to expand...
Click to collapse
Yes it is a know issue. If you did read the threads all the way through you's see that. That question is asked and answered daily in the ROM threads and Q&A. It has to do with the 'Secure Android status' (partition)
There is a possible solution for some, also mentioned in many threads - doing a full NAE tar (or OTA) update then flashing. But, again as mentioned hasn't worked on every single bodies phone (though that of course could be user issues).
Thanks, leaderbuilder. I really appreciate your time. It's nice to see confirmation.
I do try to read through the threads in their entirety, but some threads grow incredibly long. I tried searching the relevant Sacs thread for "Turned off by administrator, encryption policy or credential storage" and no results were returned.
In any case, thanks again! I'll just be patient at this point.
UPDATE:
So, it was trivial to fix this, at least in my particular case. I took your good advice, leaderbuilder, and kept my eye on the thread for the next time someone raised this issue. The solution that worked for me was this one:
daniel4653 said:
Search please, you didn't do so since the lock screen is an issue that has been around from the beginning. You need to have taken the NAE OTA and then flash the ROM. [...]
Change the following in build.prop found in system folder using a root explorer app. Es file doesnt seem to work so try another.
security.mdpp=none
To
#security.mdpp=none
Reboot and all options should now be avaliable.
Click to expand...
Click to collapse
I didn't try ES File Explorer -- just went straight to Root Explorer, based on above-cited comments, and it worked perfectly. Now I can select any unlock method I want, and the changes are effective.
UPDATE 2:
I can confirm that this same technique works on Sacs Custom ROM KitKat v3, too.
I am trying to fix this problem as well. After editing the file as you suggest, I am unable to save the edit. I tried text editor and ES File Explorer Editor, both yield an 'error saving file' type message. Thanks for any suggestions!
DrRichardQuack said:
Thanks, leaderbuilder. I really appreciate your time. It's nice to see confirmation.
I do try to read through the threads in their entirety, but some threads grow incredibly long. I tried searching the relevant Sacs thread for "Turned off by administrator, encryption policy or credential storage" and no results were returned.
In any case, thanks again! I'll just be patient at this point.
UPDATE:
So, it was trivial to fix this, at least in my particular case. I took your good advice, leaderbuilder, and kept my eye on the thread for the next time someone raised this issue. The solution that worked for me was this one:
I didn't try ES File Explorer -- just went straight to Root Explorer, based on above-cited comments, and it worked perfectly. Now I can select any unlock method I want, and the changes are effective.
UPDATE 2:
I can confirm that this same technique works on Sacs Custom ROM KitKat v3, too.
Click to expand...
Click to collapse
---------- Post added at 02:20 AM ---------- Previous post was at 01:56 AM ----------
Ok, I played around in ES File Explorer and figured it out. In the side menu a short press will turn 'Root Explorer' option on and a longer press will give you access to Root Explorer's sub-menus. That allows you to mount r/w and select /system, before editing the file.
rubinglen said:
I am trying to fix this problem as well. After editing the file as you suggest, I am unable to save the edit. I tried text editor and ES File Explorer Editor, both yield an 'error saving file' type message. Thanks for any suggestions!
Click to expand...
Click to collapse
Glad you figured it out! Thanks for sharing this alternate solution with the rest of us!
Worked for me. Lock screen back to normal now. thanks.
Has anyone else had the issue where the home button no longer takes you back to "home"? This is driving me crazy and I cant seem to find a fix anywhere. Others have asked but nobody seems to have an answer that i can find.
I am running sacs v3 with KT kernel. Nova launcher.
Re: new "developer's edition" N910V ROM compatability
From the few ROMs I've tried to flash so far, I've gotten a lot of error 7s in TWRP
As far as I can tell from some googling, this means that the updater-script in the ROM isn't allowing it to be installed on the device because it's not one of the ones in it's approved list based on some prop file somewhere
I think the fix to this is to edit the updater-script file by making it a .txt doc, deleting some amount of lines after the "assert," and changing it back to a file before putting it back into the ROM... so I'm trying to learn enough about coding to find out where exactly I should stop the deletion at. Or, alternatively, what I'd have to add.
It's also possible that I'm totally wrong and I'm getting this error for another reason entirely.
If anyone knows what they're doing here, I'd definitely be open to suggestions. If this is what the problem is, I imagine it won't be hard for devs to edit though.
This giude was made as i found a method to enable google assistant in your phone..
Requirements:-
A phone with custom recovery
Three files provided below
Android 7.0 or higher (as for now)
All google apps must be either force closed or uninstalled before flashing the files
For this,you have to download the 3 files from this MOD EDIT: REMOVED.
->After downloading puth these files in your phones storage.
->Then,Reboot into recovery..
-> In recovery mode you will not be able to see the third file(tweak.prop)
First,flash GoogleAssistantVelvet.zip
Then,flash GoogleAssistantBuildProp
->After installing Wipe Cache
You Are done..Enjoy The new Google Assistant in your phone,,
F.A.Q
Supported languages by Assistant?
-> English and German as for now.
Will I get OTA Updates?
->Nope,As phones build.prop will be changed to PIXEl
Will it work on Marshmallow??
->i dont know,But i found this thread..You can try and tell me.. Visit this thread.
Working Devices
Almost all Phones.. Tested on Arm64(Redmi Note 3) Arm(Moto X2) x86(zenfone2)..All working fine..
Good Luck:highfive:
Tell Me if i helped...
Who created these files, where are they from? Are these for 32bit or 64bit? I am not sure I would call this a guide. How about some additional information, like what device you have a working version running on. Also, brief as it may have been, upon a little looking around it would appear there is not a one-size-fits-all solution as different devices require different parts of certain apk's. Have you resolved this?
Are all functions of assistant working?
Is OK Google working?
Not tryingto come off harsh, but this seems off somehow. Maybe I shouldn't have looked at your "How to build a custom ROM beginners guide", not exactly building a ROM, more like a coloring book, everything is already there you just slip a picture into the back and now it's 'Your Custom coloring book".
StevetotheH said:
Who created these files, where are they from? Are these for 32bit or 64bit? I am not sure I would call this a guide. How about some additional information, like what device you have a working version running on. Also, brief as it may have been, upon a little looking around it would appear there is not a one-size-fits-all solution as different devices require different parts of certain apk's. Have you resolved this?
Are all functions of assistant working?
Is OK Google working?
Not tryingto come off harsh, but this seems off somehow. Maybe I shouldn't have looked at your "How to build a custom ROM beginners guide", not exactly building a ROM, more like a coloring book, everything is already there you just slip a picture into the back and now it's 'Your Custom coloring book".
Click to expand...
Click to collapse
yeah sure,iwill
Thread closed as this is a copy of this guide: http://forum.xda-developers.com/showpost.php?p=69074667&postcount=112"
The Flash
Forum Moderator