yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ikjadoon:
Got it. I'll write up my issues...but, I've been having some trouble with adb and think that might be a bigger issue, haha:

I'm trying to allow adb to run as root. I decompiled boot.img, changed ro.secure to 0, recompiled boot.img, and pushed. Default.prop now shows ro.secure=0. But, I tried running adb remount and I still get permission denied? Someone said there may be other edits required, but I can't seem to find any.

Here's what I changed it to:

Here's what ADB is telling me:

shell@android:/ $ getprop ro.secure
getprop ro.secure
0
shell@android:/ $ exit
exit
adb remount
[B]remount failed: Operation not permitted[/B]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Try this in terminal...

adb root

Then

adb remount

That should do it for ya. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ikjadoon:
Thanks for the reply! Right: I should probably be root before I try that command. ;) Unfortunately, I tried "adb root" and it said: "adbd cannot run as root in production builds." I did some Google'ing and a few threads said that I should have changed ro.debuggable to 1 as well in default.prop.

So, I changed ro.debuggable=1 and, right, ro.secure=0 still. Then the oddest thing happened: I typed "adb root" into terminal and it went to a new line, no message. And then it disconnected my phone from ADB (I heard the little "ding ding" noise of disconnection). Unfettered, I typed in "adb remount," but of course then it complained that no devices were attached! I thought it was a fluke, so I tried it a few more times. It happened again and again. :(

In an ostensibly unrelated problem, I couldn't get SecSettings.apk to push back (even though android.policy.jar pushed fine), so I tried a Nandroid. TWRP seemingly did not like my changes to default.prop, as it went crazy (froze a few times) saying "cannot unmount /system" every time I tried a restore and then "Restore failed." Hmm...I pushed back my backed up boot.img and it restored fine.

I'm messing up somehow. So, I'm using VTS to unpack and repack the image. I saw that the output boot.img's are about 6MB, while the default ones I pulled are 10.1MB. Dev said it was probably just compression? Also, I'm pulling the boot.img via adb dd if=/dev/mnt/mmcblk0p7 of=/sdcard/boot.img. Are either of these too weird/wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
Are you running adb shell as superuser?

Try:

adb shell

su

adb remount

After typing su you will need to grant superuser permission on your device.

Things to check when pushing with adb:

System, app, and framework folders are mounted r/w in root explorer.

USB debugging is enabled.

I am lazy so I use Eclipse for pushing and pulling files.

Repacked boot images are almost always smaller than the original (sometimes a lot smaller).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ikjadoon:
EDIT: I gave up, haha. Thank you guys, though. I just copied and pasted both files onto /sdcard and then used the good 'ole adb shell mount -o remount,rw /system and then busybox cp of the files over. Copy worked. And the mod worked. And, honestly, I don't flash enough to make adb root worth it. It's a few extra seconds of my life to type the extra commands instead of taking 2 days to figure out this boot.img....

----

I re-did the ro.secure=0 edit in the boot.img through dsixda's kitchen, just to be sure it wasn't VTS. I also "flashed" it via adb dd in recovery this time instead of in Android. I also left ro.debuggable=0 as that does not seem pertinent to allowing adb to run as root, but simply to debug system apps, etc. Does anyone know any actual information on whether ro.debuggable=0 is required to allow adbd to run as root?

1) ADB shell as superuser: um, I didn't think about that! I thought adb root and adb remount were ADB commands, not shell commands? But, I tried it anyways, but it simply said "error: device not found". See http://prntscr.com/wvjmq

2) Right, ADB shell has SU rights as "always grant" per the SuperSU app.

3) Pushing with ADB: oh, huh! So, adb remount or mount -o remount,rw /system are not recursive? Meaning they only apply to the top-level directory? I think that's what you're saying, but that has never been a problem in the past...I think. And, technically, that doesn't explain why when I didn't mount /system/framework specifically android.policy.jar pushed fine. Pushing SecSettings.apk to /system/app causes a "Permission denied" error. :( Can Android reject apks? I did a few minor edits to SecSettings.apk, from this mod: http://xdaforums.com/showthread.php?t=2002620

4) Thanks for the boot.img size clarification; got a little worried after having "lost" 40% of the image, haha! :D

tl;dr:

1) Using either VTS or dsixda's kitchen to modify boot.img to ro.secure=0 and running "adb root" = "adbd cannot run as root in production builds." Pulled and flashed boot.img via adb dd.

2) Unrelated to issue 1 (I think): after mounting system via adb shell (mount -o remount,rw /system), I cannot push SecSettings.apk into /system/app ("Permission denied"), while android.policy.jar pushes just fine /system/framework.

I appreciate everyone's help here. I think it's something really little that I've missed and I just can't figure it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If you post the kernel (untouched) for me. I will go through the process myself. That when when/if it works I can tell you my exact steps so that you can try it out for yourself. Let me know exactly what you are trying to accomplish also. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ikjadoon:
You guys are too kind. I feel like you have more important things to do than help a sucker like me. :D If you're very bored, go ahead. :)

Attached is my stock, unadulterated boot.img inside a zip. What I am trying to accomplish: push system files from ADB (without going into the shell). I think you need adbd to run as root to do that, right? So, an "insecure" kernel. Thus, I should be able to type "adb root" and then "adb remount" to make /system rw instead of ro and then type "adb push SystemUI.apk /system/app/SystemUI.apk" and it work. I thought I just needed to make ro.secure=0 in the boot.img's default.prop, but it looks like that is not enough.

But, honestly, if it looks like it takes too much time (I'm serious; I honestly think Samsung sent me a borked phone), it's all good. :D ADB shell and Busybox cp will suffice. :D I'm just more curious of what I am doing wrong here.

~Ibrahim~
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
Interesting. I am getting the same error (yes, ro.secure=0 and ro.debuggable=1).

As soon as I am finished with the update I am working on I will look in to this - unless Task figures it out first. If for no other reason, just because I want to know.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Me>cd c:\android

c:\Android>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
041b9c2b device

c:\Android>adb shell
shell@android:/ $ adb root
adb root
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|shell@android:/ $ su
su
root@android:/ # adb remount
adb remount
error: device not found
1|root@android:/ # adb root
adb root
error: device not found
1|root@android:/ #WTF?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
You shouldn't be running adb root inside of a shell. You're running two instances of adb and only need the first connection. The reason you're getting device not found is because you're running an instance of adb on the device and it's looking for other devices. Try it again without running adb shell.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm guessing this is a TW boot.img and I do not want to put TW on my device to check and see if this works and is what you are looking for. Will you test this and report back. Thanks. :D

P.S- This isn't a flashable.zip. its just the boot.img inside. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ikjadoon:
Wow, thanks! You're quick. :D Ah, yes, definitely a TW boot.img. :D I'll give it a shot tomorrow and will report back.

P.S. Thanks for the heads up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No problem. Just remember. You don't need to adb shell in to mount. Just open terminal, type adb root, then adb remount. Then you can push. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
I tried that. I just didn't post that session. Adb has been acting weird lately. I am going to see if a newer version is available. Mine might be a little old.

This is what I got when I tried it again just now.

Edit:

Please do me a favor. If you have an insecure kernel in your ROM, give this a try.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Me>cd c:\android

c:\Android>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
041b9c2b device

c:\Android>adb root

c:\Android>adb remount
error: device not found

c:\Android>adb devices
List of devices attached

c:\Android>adb kill-server

c:\Android>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached

c:\Android>
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ikjadoon:
Hmmm...it didn't work. :( I appreciate you putting it together, though. Same error upndwn4par:

C:\Users\Ibrahim Jadoon\AppData\Local\Android\android-sdk\platform-tools>adb root

C:\Users\Ibrahim Jadoon\AppData\Local\Android\android-sdk\platform-tools>adb remount
error: device not found

C:\Users\Ibrahim Jadoon\AppData\Local\Android\android-sdk\platform-tools>adb push android.policy.jar /system/framework/a
ndroid.policy.jar
failed to copy 'android.policy.jar' to '/system/framework/android.policy.jar': Read-only file system

C:\Users\Ibrahim Jadoon\AppData\Local\Android\android-sdk\platform-tools>

Not to jump over anyone's head, but I took a look at ktoonsez's TW kernel with "unsecured root ADB.." His default prop is a little different, with this service.adb.root=1 line,

Maybe that's it? I'll try it in a few days... :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stratatak7:
I noticed you guys had some issues with adb. I'm going to upload an insecure stock kernel soon with changes, and you tell me if it fixes adb for you. Keep an eye out, I'll upload it as soon as I get to a computer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stratatak7:
Try this: https://www.dropbox.com/s/7q9eb8y5ir3jain/boot.img

Let me know if this fixes you guys' adb error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
ADB Root

Ok, Good catch on the adb root.

Here is the insecure UCKLK3 Kernel all fixed up init.d support.

Tested and working.

Includes all modules. Install script will recover you from other kernel installs, deleting and replacing all necessary files

http://d-h.st/KAB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stratatak7:
Cool. What did you do differently than me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Awesome thread....Hope to learn as my issue always seems to be recompiling. It has been month or two and forgot exactly what the error what was but I was using APK tool and was able to place the apk in projects and decompile. I then modded the file and then tried to recompile but when I look at the error log, it gives me a failed to find (yml) I believe and never recompiles. I've tried APKtool and APKmultitool but no luck. Running windows 8 if that is of any concern. I'm not much into adb but I'm needing to learn anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
So here is my issue. Did the how-to by Wanam for the toggles and got a few issues so pulled another debs apart and saw I have to change v13 to v9, v14 to v10. Got it all to compile and boot but here's my issue my brightness bar is extremely huge. Any idea on this one why it would have done that ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
Verify your tw status bar expanded.xml. most likely something in there. I'd diff it with another and make sure.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
When someone says "diff" it is there a way to compare two files pulled up in notepad++ ? Other than just looking line by line ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
I'm assuming you're running Windows, if so there's a program called WinMerge

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ikjadoon:
You can do it in NPP (Notepad++): Plugins -> Plugin Manager -> Show Plugin Manager -> Check "Compare" -> Install -> restart NPP -> Plugins-> Compare! :)

I prefer WinMerge (http://winmerge.org/), as it comes included with Virtuous Ten Studio.

Also, I am not dead! :D I still am going to get that kernel--but, two more weeks of classes until I'm free! :D

~Ibrahim~
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stratatak7:
Nun and I use Beyond Compare. It works wonderfully. http://download.cnet.com/Beyond-Compare/3000-2242_4-10015731.html
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
You put your toggles in the wrong place.

Look at this line in yours compared to the other two.

<com.wanam.systemui.quickpanel.PowerWidget android:id="@id/exp_power_stat" android:layout_width="wrap_content" android:layout_height="@dimen/quick_setting_button_height" android:layout_marginTop="@dimen/tw_notification_panel_header_height" />
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
Thanks up !

It was so freaking obvious... I guess I just needed someone else eyes to see the difference....and putting it up here made sense.

Well rom will go up tomorrow. Been testing it for about 5 days and it's been really stable for me. This is the one mod (toggles) that's taken me forever to get and it's the easiest...go figure

One more thing. TWRP always asks me to fix root permissions after I flash my rom...What's that all about ? The base I used from verizon said "root through adb"

You base I used for learning had "install busybox" and didn't require this. Am I missing something ?

EDIT: Did not work for anything.... I've seen this issues that others had and posted about it but no solutions...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
Help with default APN's

Ok, I am going nuts here! A couple of weeks ago, I decided to start working on my first stock-based rom for my SGH-i747. I have built CM9/10/10.1, and Task650's AOKP as well. I am pretty comfortable with building and modifying kernels. However, this has been my first foray into decompiling APK's and working with smali. Every mod I have made to my rom base has worked perfectly (eventually, lol) except for one. I am trying to change the default list of APN's, and it is driving me insane!

When I first started with my rom, going to Settings > More settings (under Wireless and network) > Mobile networks > Access Point Names displayed one entry: ATT phone. Currently, I have the ATT phone and ATT entitlement APN's available by default, thanks to some edits to the CSC files. However, I want to add at least one more APN as a default: my Straight Talk apn. I know that I can simply tap menu, add a new apn, and put in my straight talk info. I have done that and it does work. However, if I wipe data, I will have to re-add my apn. So far, I have modified /system/etc/apns-conf.xml, removed every reference to hidden apns in every csc file, and decompiled SecSettings.apk, SecSettingsProvider.apk, framework-res.apk, and twframework-res.apk to look for references to default apns. I have also searched xda, Google, and the AOSP tree to attempt to figure out where the rom loads the default apns from. I am completely stumped on this one!

If anyone has any information on changing the default apns, or even a point in the right direction, it would be hugely appreciated!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stratatak7:
Never apologize for asking questions. This is Q&A, a place to ask questions and learning. Your question is 100% valid for this thread as well.

This might sound like a silly question, but did you set your dependencies and install framework-res.apk, systemUI.apk, and twframework.apk to apktool first?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
Yep and as crazy as it may seem I re-add it every time I do a new mod. Delete from the framwork folder and "apktool if XXXX.apk". I was just trying another small mod and had no issue with it compiling on the same framework

I was on a roll last week in figuring out stuff but this week it's been trying my patience haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
You're error is what's keeping it from compiling.

C:\Users\usheadni\apktool\SecSettings\res\xml\settings_headers.xml:19: error: Er
ror: No resource found that matches the given name (at 'title' with value '@stri
ng/xposed_installer').

It has nothing to do with androidmanifest.xml. It shows that whenever there are issues with resources.

Post your settings_headers.xml

It looks like you didn't add "xposed_installer" to your strings.xml.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stratatak7:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
oh Hednik...its always the small things. I kept trying over and over last night I didn't see it until you mentioned that. Thanks guys ! If I want to ad more apps would I need to just add (names changed of course) :

<string name="xposedinstaller">Xposed Installer</string>

At the bottom of the strings.xml, and on settings_header.xml just put more under the:

<header android:title=

BTW I'd like to get rid of the TW clear all button and I can't find anything that seems to point out how it is done. I always get it in the wrong place. Somedays the order in tw_status_bar_expanded.xml makes sense and other days it makes none ha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
Ah then I bet I need to add it to the tw_status_bar_header. Thats makes sense now. I was wondering why it was being added to the drawer and not the header. Makes sense to me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
I did that mod for CSROM. I will post a guide soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
Awesome. Looking forward to it. I'm going to try to see if incan figure it out first. I made a lot of headway today. Next t-motion update will be a big one !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crashpsycho:
why did this thread show up earlier

sorry guys i just made a thread cuz i couldnt find this one would anyone mind checking out my post i dont know if i can move all tha stuff over if can please let me know

http://xdaforums.com/showthread.php?t=2303829
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
I actually explained this on the thread from which you downloaded the base ROM. ;)

http://xdaforums.com/showpost.php?p=40186137&postcount=21

There is an error in your updater-script or you are using the updater-binary from the kitchen (they never seem to work correctly). Just use the updater-script and updater-binary from my base and you'll be fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crashpsycho:
thanks i really apreciate it another question

should i replace both the binary and updater or just the binary because when i did the binary it still failed but i noticed that re uplinkedafter i download this base awhile back?

would it be best to use android Kitchen to enable the data/app and bootanimation or do you have sometype of alternate method
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stratatak7:
The only thing you can really use the kitchen for now is unpacking the kernel and zipaligning/signing/de-odexing your ROM. Yes you can use it for /data/app and also init.d support, however you can't use it to add custom boot animations or adb support. Download the stock ROM from upndwn4par (double check the MD5) and that should be flashable out of the box with no extra work needed. From there, all you have to do is mod away and if you really want, run it through the kitchen when you're done to re-sign and zipalign everything. For boot animations, see the random SGS3 mods thread in the development section. I have a post there explaining what you need to do to add custom boot animation support. Oh and when you're done with the kitchen, don't use the updater-script they provide...it never works.

Updater-scripts are tricky at first but make more sense as you start developing more. Be REALLY careful and study the scripts of others. If you write the wrong thing to the wrong partition you end up with a crispy fried phone. Feel free to PM me or post in my ROM thread if you want more help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crashpsycho:
s3 devs are awesome ive honestly been on xda forever and have never seen so many mods and helpful people thanks to you all
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
You are correct. The S3 has a great community. :good:

I agree with what Stratatak7 said about the boot animation. I use smokin1337's mod in my ROM.

As for the data/app, I would suggest using my updater-script and pasting the data/app portion from the kitchen updater-script.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crashpsycho:
Never folks found my fix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crashpsycho:
removing brightness toggle

hey guys need some help here.

as mentioned before im trying to make my own Rom with your guys help with bootAni and kitchen i now have Debloat Lite Rom.Thanks now for the more tricky stuff

1st: remove brightness toggle without a buffer Space(dont want option to toggle it in setting)

Im using this mod that has already been Generated (just because i cant find a How to on Wanam toggle for 4.1.1 and the other one 4.1.2 there sections of that mod i cant find(anybody else have a more specific guide would be nice)

Im using these steps to decompile and recompile the mod best and most specific i found(Decomp/Recomp Guide)

now im using this guide to remove the slider permenantly(remove slider)

now i decomp'd and recomp'd&zipalignd no Errors and i made the neccessary changes in Post #6

then re added to the original zip it came with but since i recomp'd and flashed the WHOLE mod didnt flash??? im just stuck

(now i copied and pasted the ENTIRE apktool folder(incase you guys notice i have an outdated tool or somethin)

Link to folder and mod

thanks for the help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
Where is this located ?

In perusing the twstatusbar.xml and twstatusbarheader.xml I have been unable to find if this is a PNG or a HEX color edit in there. How would I go about getting rid of this ugly blue in sec settings and the notifications drawer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
There is a how-to for the 23 toggle mod for 4.1.1 (it also works for 4.1.2) by wanam for the Note.

I am not sure what you mean by "the whole mod didn't flash".

You need to edit color hex codes in status_bar_expanded.

There is a great thread for theming here:

http://xdaforums.com/showthread.php?t=1811750