[Q] Anyone know how to perm disable cap lights on lg nitro?

[Q] Anyone know how to perm disable cap lights on lg nitro? - LG Nitro HD

i have a few apps that can disable them but the changes are reset every reboot none of them can make changes stick. i've heard of a few file editing ways to make it stick but most of those say they only work for specific phones and haven't found one for lg nitro yet. my problem is i had to replace a digitizer and the new lights on the new one are too bright and offcentered so i just want the lights off because everything else is working and i dont need the lights anyways. Thanks for any help.

if you're using stock ICS rom, there is an option to disable it in settings and it stays on reboot.
for other roms, try this app, not sure if it works.
https://play.google.com/store/apps/details?id=com.deskangel.kblight&hl=en

ightsrti purpose
arda99 said:
if you're using stock ICS rom, there is an option to disable it in settings and it stays on reboot.
for other roms, try this app, not sure if it works.
https://play.google.com/store/apps/details?id=com.deskangel.kblight&hl=en
Click to expand...
Click to collapse
i have that app its one of the only ones that will turn the lights off, but it doens't stick on boot and after boot i have uncheck recheck the option every time, it is right not he only solution but its not convenient, looking for something more perm. i'm running CM10.0.0 with apex launcher.
by the way thanks for the fast response, it's ironic because i lost my stock rom because of a faulty flash of CWM recovery, my backup rom is the stock AT&T ROM, do you know if this rom has the option? it's gingerbread i think. I'm also wondering if flashing to that rom, disabling the lights, then flashing CM10 again would solve the problem. but i asume when flashing cm10 i would lose the solution and the lights would come back on after booting into cm10 the first time. Any more help on a perm solution would be appreciated. i know there are perm soltuions for other phones but i hvaen't found one that works with p930 yet, i've even seen some for optimus 2x and G but they won't work on LTE, even rootdim doesn't work i've already contacted the developer and told him i can help him with compatibily if he needs anything from my phone to help update rootdim for p930 incase other people are having this problem as well., the problem is mostly that LTE screen is incredibly good and bright, and i dont want to wreck the clarity with my aftermarket digitizers overlight bright cap button lights blaring into my eyes and ruining the beauty of the HD screen on this thing. I mean after all how many of us need lights to tell us where our back/home/menu buttons are... i mean i googled this problem and there are hundreds of people trying to disable them on almost any phone you can think of, with varying success.

KronicSkillz said:
i have that app its one of the only ones that will turn the lights off, but it doens't stick on boot and after boot i have uncheck recheck the option every time, it is right not he only solution but its not convenient, looking for something more perm. i'm running CM10.0.0 with apex launcher.
by the way thanks for the fast response, it's ironic because i lost my stock rom because of a faulty flash of CWM recovery, my backup rom is the stock AT&T ROM, do you know if this rom has the option? it's gingerbread i think. I'm also wondering if flashing to that rom, disabling the lights, then flashing CM10 again would solve the problem. but i asume when flashing cm10 i would lose the solution and the lights would come back on after booting into cm10 the first time. Any more help on a perm solution would be appreciated. i know there are perm soltuions for other phones but i hvaen't found one that works with p930 yet, i've even seen some for optimus 2x and G but they won't work on LTE, even rootdim doesn't work i've already contacted the developer and told him i can help him with compatibily if he needs anything from my phone to help update rootdim for p930 incase other people are having this problem as well., the problem is mostly that LTE screen is incredibly good and bright, and i dont want to wreck the clarity with my aftermarket digitizers overlight bright cap button lights blaring into my eyes and ruining the beauty of the HD screen on this thing. I mean after all how many of us need lights to tell us where our back/home/menu buttons are... i mean i googled this problem and there are hundreds of people trying to disable them on almost any phone you can think of, with varying success.
Click to expand...
Click to collapse
and im not as stupid as i might sound by my rambling way of speaking lol. i was able to get all the mods onto my phone and repair a smashed digitizer by myself (which requires taking the entire phone about and motherboard out of the phone and putting it back together) i just hated english class and it now shows

you can try this one:
http://forum.xda-developers.com/showpost.php?p=30698163&postcount=2
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
the exact path of "max_brightness" might vary and if so,
Code:
find /sys -name max_brightness
Try these commands via rooted adb shell or terminal emulator, if it works then modify init.d to set it on every reboot.

arda99 said:
you can try this one:
http://forum.xda-developers.com/showpost.php?p=30698163&postcount=2
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
the exact path of "max_brightness" might vary and if so,
Code:
find /sys -name max_brightness
Try these commands via rooted adb shell or terminal emulator, if it works then modify init.d to set it on every reboot.
Click to expand...
Click to collapse
how would i go about modifying the init.d to add this, when i executed the command line the lights turn off as desired =P thanks for your help thus far i just haven't modify'd that file before and it's a system file i can see so i'd rather not go trial and error, thanks again so far if you could give me a step by step to add the modifications that would be optimal.
*edit* i gave u a thanks for atleast teaching me where the file is

is it just a text file i open and add the code to? if so does it matter where i add the code (top/bottom)

ok nevermind, i navigated to it out of curiousity and i see that its a folder and obviously not a text file... however im still not sure what to do from here do i drop a text file with that code in it or something ? if so what do i name the file ? if not do i add the code to one of the two files here? the two files i see here are 00banner and 90userinit

after stopping to think i would assume that the userinit file would make most sense, if i remember correctly i actually think i can put it anywhere im just being careful and double checking. two things i'm a little hazy on, can i just add it to the end of the userinit file, if so do those commands require ; at the end of them? because everything else in this file except the loop counter has ;
thanks in advance, i also have another question, i read somewhere on these forums that the system/ folder gets reflashed at every boot, if this is true wont that overwrite this file? if that is true if i was to create a custom file and add it, would that get deleted whent he system is reflashed? does it delete the entire directory and rewrite it or just readd the files because if it was copying over the old files i think that would mean i should actually create a new file called something like dislights. just to verify if this is the case would a file with this text in it suffice.
chmod 666 /sys/class/leds/button-backlight/max_brightness
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 444 /sys/class/leds/button-backlight/max_brightness
or do i need some type of header and footer or semicolons at the end like this
{
chmod 666 /sys/class/leds/button-backlight/max_brightness;
echo 0 > /sys/class/leds/button-backlight/max_brightness;
chmod 444 /sys/class/leds/button-backlight/max_brightness;
}
sorry for all the questions im just paranoid about altering system dir when im not 100% sure what im doing.

Download and extract the attachment, put it in /system/etc/init.d, and set permission to rwxr-xr-x, you might need es explorer(enable root options) or root explorer to do so.

thanks for reply, just performed that operation, rebooting fingers crossed.
confirmed works. !!!! yay thanks man i'm going to give you another official forum thank you after im done writing this.
*note* from what i have been reading over the passed few hours, some phones my need to have the init.d activated to work on bootup automatically. the following link will provide a solution for almost all phones (even unrooted) to apply this solution. Although you need root permission to actually write files to the init.d and change permissions. thanks to everyone who contributed to this solution.
edit : adding link i forgot lol
http://forum.xda-developers.com/showthread.php?t=1710980

glad to know it works for you.
init.d is usually missing on stock roms but available on most, if not all 3rd party roms.

Related

[GUIDE] Getting some old features back in Virtuous Sense ROMS

GUIDE: Getting some old features back
INTRO: For those who dislike some of the changes/features made to roms as they are developed and are asking how to get them back, here is a how to. It is usually a simple matter of pushing the old files from previous builds into your current rom. Keep in mind that the devs are building a rom as they see fit. As with any rom that you don't build yourself, there will always be things you want to change.
-If there is a bug, post it in the thread.
-If there is a change that you personally want, then do it yourself. Don't expect the dev, and everyone else who uses the rom, to accommodate your specific needs/wants. You may not have noticed, but you aren't the only one using the rom!
NOTE: This guide and code are meant for the virtuous sense rom, but the concept is universal. For example, if you are using some rom and the new version is posted with, say the amazon mp3 apk removed, and you want it back, refrain from cluttering up the dev's thread with a request to have it back. This is both selfish and a waste of posting space. If you are to the point of installing custom roms, you should first be able to type basic adb/terminal emulator commands to copy/delete files. In this case you would extract the amazon mp3 apk from an old .zip and push/install it into your current one. Now wasn't that easier than waiting and hoping that someone will do it for you?
NOW TO THE GUIDE:
Auto brightness mod - To revert from the auto brightness 'mod', which is far too sensitive, to the original, simply pull the services.jar and framework-res.apk from a rom before the patch, and push them to your framework folder. I've attached them to the second post for ease.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/framework/services.jar
adb shell rm /system/framework/framework-res.apk
adb push [directory of saved file]\services.jar /system/framework
adb push [directory of saved file]\framework-res.apk /system/framework
Reboot
-------------------
Keyboard mapping - The www/com key has been changed to a tab, which is good, as it was non-functional before. However the user keys have been changed too. I've modified a file which keeps the www/com key as TAB but also keeps the user keys as user assignable keys. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/usr/keylayout/vision-keypad.kl
adb push [directory of saved file]\vision-keypad.kl /system/usr/keylayout
Reboot
-------------------
Rosie auto-rotate - If you want to keep it so that rosie will only be in portrait mode with the keyboard closed, but dont want to turn off auto-rotate throughout all apps, just push the old rosie. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/app/com.htc.launcher.apk
adb push [directory of saved file]\com.htc.launcher.apk /system/app
Reboot

Attachments:
You need to rename "services.jar.zip" back to "services.jar" and "vision-keypad.kl.zip" back to "vision-keypad.kl". This is because the forum wont let you upload .kl and .jar extensions as attachments.

Thanks so much for this. I'll definitely be pushing the auto-brightness mod back, and I may do the keyboard, too (might let others do that one first, or see if rmk40/eViL release an update with that first).

Thanks for this!
Sent from my HTC Vision using Tapatalk

Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense

android602 said:
Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense
Click to expand...
Click to collapse
What version of virtuous are you running? Did you rename it and remove the .zip from the end?
I'm using that exact file w/ no issues

calendar/lockscreen
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this

felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
Lockscreen - no.
Calendar - maybe, haven't tried. However I did find these 2 threads by typing in the words "htc calendar" in the search box (which means you didn't search very hard )
http://forum.xda-developers.com/showthread.php?t=795222
http://forum.xda-developers.com/showthread.php?t=723761]
They may help you.

Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).

Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?

felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App

fox-orian said:
Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?
Click to expand...
Click to collapse
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?

Can this be modified to restore ".com/www" to G2's?

the1wingedangel said:
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?
Click to expand...
Click to collapse
Yup, and I have "always show extension" enabled in folder options, so I definitely got rid of the .zip.
Maybe I'll fiddle with it a little more, see if I missed something.

All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.

Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.

fox-orian said:
All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.
Click to expand...
Click to collapse
Weird, I have no idea why that won't work for you. Anyway, there is another way around it. Just open up your patch.zip (from 0.7.0 to 0.7.4), go to the framework folder, and remove the services.jar and framework-res.apk from it. Then go about the wipe/install of both zips like normal. That way the patch zip will no longer replace those two files. Anything that you don't want changed in a patch zip can just removed from it.
Snap Jackel Pop said:
Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.
Click to expand...
Click to collapse
Sorry cant help on that one, I haven't run a CM rom since like 1 or 2.0 haha. You may try to see if others are having that problem, or if it is a known issue with the 6.1 and streaming videos. Is it only that site? Maybe a flash player version problem?
rmk40 said:
Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).
Click to expand...
Click to collapse
Yea, I assumed it would be out-dated soon anyway, as changes are made to your roms. I'll adjust it to keep up if the need is there though. It was just a couple of the more simple alterations that I made, and after seeing so many people cluttering up your thread with posts about them, I decided to post this.
Mostly, though, I just wanted to remind people that many simple issues/personal needs (like an app being removed from a rom, or a small change to one or two apps) can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!

the1wingedangel said:
many simple issues/personal needs can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!
Click to expand...
Click to collapse
I really cant emphasise this enough!
Sent from my sweet G2

Do you know if there is anyone to return the power down message. I remember before there being and option to restart the phone, hibernate, power off, or reboot into recovery. I liked having that. Is there anyway to return this feature?
Sent from my sweet G2

felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
ddotpatel said:
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
by chance, did anyone try this? if not, I will try it in a few...

[MOD] Quick & Easy Root Script - HC

This should work for any and all a100 Honeycomb builds, you'll need to install an app from the market called terminal emulator. Also, you'll need a file manager like Astro to unzip the file.
This mod should root your tab in a matter of seconds after the script file is launched. I've tested this on my tab from a clean build and it works like a champ.
Here we go!
- Install the following apps from the market:
Terminal Emulator
https://market.android.com/details?id=jackpal.androidterm&hl=en&rdid=jackpal.androidterm&rdot=1
Astro File Manager
https://market.android.com/details?id=com.metago.astro&hl=en
- Download the attached file from this post.
- Extract and put both the root.sh and su in /mnt/sdcard from the root.zip file.
(Using Astro, find the root.zip file it might be in /mnt/sdcard/Downloads or could be else where if your not using the website to view XDA. Copy it from where ever it's at and paste it in /mnt/sdcard. Press your finger on the zip file and tap Extract when the menu pops up. Tap "Extract to This Directory".)
- Next, open terminal emulator and copy / paste the following:
sh /mnt/sdcard/root.sh
Text will fly by, the script will automatically copy the su binary and install it to the proper location.
Once the script finishes running, be sure to install superuser from the market:
Very Important, if you skip this you won't be "officially rooted yet"!!!
https://market.android.com/details?id=com.noshufou.android.su
Open the superuser app once it's installed, click on the wrench in the upper right corner, scroll to the bottom and find "Su binary v... Tap to check for updates" and tap that link. It should bring you to an update screen, click the button at the bottom to update!
Once you have done the above, then install busybox, Titanium, etc.. if needed.
Thanks goes to abliss for origionally coming up with the root commands!
This mod really just automates his work.

permission denied every step of the way. Used both script manager and terminal

ok terminal manager is out, I didn't realize that doing a hard reset wouldn't wipe the /system/xbin directory completely so technically busybox tools were still installed and sh wouldn't normally be there. I'll see if there's another way..

this method work for any build? and if so, is there any problem during the process that could "kill" my a100 or it's safe?

This method should, yes and it's safe.. It's actually more safe (if that's possible) than the method origionally posted in the dev section since there really isn't any room for user error.
Sent from my MB860 using XDA App

Ill give the new method a go around tomorrow and report back for you.

I wasn't expecting it to anyway, but I figured I'd let you know this doesn't work on the A101.
Hoping someone can find a working root method for this model.

Sorry to hear about the a101, that thing sounds like a tough nut to crack!
Sent from my MB860 using XDA App

This working for me i manage to root my a100

It works and its so simple
Thank you so much for this! It was so easy. Though the only problem I had was with the terminal emulator, no fualt of the Dev, but it might help someone. When I was trying to write in the line of code I kept getting errors because I couldnt get the keyboard to write lower case. So copy and paste if your a noon like me to get it through the terminal.

Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...

mvan4310 said:
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
Click to expand...
Click to collapse
You sure you don´t have an a101? what build number are you running?

A100_2.007.04_COM_GEN1
Most definitely an A100...

mvan4310 said:
A100_2.007.04_COM_GEN1
Most definitely an A100...
Click to expand...
Click to collapse
I have no idea then.. the only thing I could say is to try and restore from a "Full" rom, like Acer_A100_1.014.08_COM_GEN1 and try to root it before doing anything else. It wouldn't hurt to try anyway and the worst that could happen is that you'd have to restore all your apps and stuff. If we can ever get this thing to run cwm and a different kernel, you'll definitely be needing root.

Works great!
Thanks so much for the script and instructions. Im enjoying my rooted tab yay!

mvan4310 said:
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
Click to expand...
Click to collapse
Did you check the boxes for USB Debugging and Unknown sources just in case?? (in Settings > development)

I checked them both. Root Checker shows I have root, but other apps cant get root access, and SuperUser cant update because of this issue... I dont know what the hell to do because this has me stuck atm... Im gonna flash back to 1.018 and see if that helps, probably not, but it wont hurt to check.
EDIT:
I reverted back and got root. It seems to be the newest update that stopped it. Im updating back up again to see if I retain root. What a pain...
Edit 2:
Yep, Im rooted now. It unrooted me when updating, ran the script you provided and its working now. Dont know why it didnt take before reverting back, but works wonderfully now. Now that Im rooted, let me know what I can do and peek around at to help out here.

Has anyone tried that on an A500?

A500 has its own rooting methods. You can find info about the A500 here
http://forum.xda-developers.com/forumdisplay.php?f=1136

Thanks alot crossix. Worked like a charm.
Sent from my A100 using Tapatalk

Edit build.prop through updater-script

Hello fellas.
Back in the day, if I wanted to keep my dpi setting of 280 after flashing a new nightly (talking CM now), I just made a local.prop with the modified line and put it in /data.
Since, I think, CM10, though, local.prop doesn't get loaded, so I have to manually change build.prop.
I know a solution to this would be just keeping the same build.prop and flashing it after the rom (I already have a zip with the modifications I like that I flash after each nightly), but I don't really want to keep an old build.prop. What I want is to juat modify the line through my zip, so it stays updated while I don't have to modify the line every single day.
I found very quickly that I can use this line:
sed -i 's/ro.sf.lcd_density=320/ro.sf.lcd_density=280/g' /system/build.prop
to get the job done, and it does indeed work if I run it using the terminal. The problem is, I can't get it to work in recovery.
Having very little experience with programming, I'm just trying stuff to see if it works. I treid directly including the like line in the updater-script, didn't have too much hope for that.
I also tried including another simple file with this code:
#!/sbin/sh
sed -i 's/ro.sf.lcd_density=320/ro.sf.lcd_density=280/g' /system/build.prop
that I then extract and run, as I've seen in threads in the forum, but still doesn't work. The file gets extracted, but it doesn't work
I even tried to do it in a userinit script form, just to see if the rom loaded it on boot, but nope.
This is pretty friggin' simple to do, and I'm sure I'm probably making a silly noob mistake, but I just don't have any experience with this kind of code, so if someone can tell me how to make my zip run that very simple line, I'd much appreciate it.
Thanks.

Ok, after moar and moar and moar search, I finally found a script that does the job.
Problem solved.

yay
yay

Hi,
can you please provide your solution. I'm also trying to edit values in build.prop.
I tried to do via init.d script. The script is fine but / system seems to be read only when executing script at startup.
So it would be great if you can reply how you did it (maybe complete other way).
Thanks in advanced!

This is the post in question.
Swiftkey'd from my GNexus

Perfect, thanks a lot! I already found a workaround via an init.d script but this looks very promissing....
Sent from my XT894 using xda app-developers app

It's very useful.
I just included it in my after-nightly zip, so everything becomes automated with cyandelta.
Swiftkey'd from my GNexus

Hi,
So how do I edit AND add lines to build.prop from recovery ZIP?

Easy solution
Or maybe using just the updater-script and this code (this should also work on every rom)
run_program("/sbin/sh", "-c", "sed -i 's:ro.sf.lcd_density=.*:ro.sf.lcd_density=280:' /system/build.prop");
Click to expand...
Click to collapse
You can change 280 to another value if you want.

..

Molitro said:
Hello fellas.
Back in the day, if I wanted to keep my dpi setting of 280 after flashing a new nightly (talking CM now), I just made a local.prop with the modified line and put it in /data.
Since, I think, CM10, though, local.prop doesn't get loaded, so I have to manually change build.prop.
I know a solution to this would be just keeping the same build.prop and flashing it after the rom (I already have a zip with the modifications I like that I flash after each nightly), but I don't really want to keep an old build.prop. What I want is to juat modify the line through my zip, so it stays updated while I don't have to modify the line every single day.
I found very quickly that I can use this line:
sed -i 's/ro.sf.lcd_density=320/ro.sf.lcd_density=280/g' /system/build.prop
to get the job done, and it does indeed work if I run it using the terminal. The problem is, I can't get it to work in recovery.
Having very little experience with programming, I'm just trying stuff to see if it works. I treid directly including the like line in the updater-script, didn't have too much hope for that.
I also tried including another simple file with this code:
#!/sbin/sh
sed -i 's/ro.sf.lcd_density=320/ro.sf.lcd_density=280/g' /system/build.prop
that I then extract and run, as I've seen in threads in the forum, but still doesn't work. The file gets extracted, but it doesn't work
I even tried to do it in a userinit script form, just to see if the rom loaded it on boot, but nope.
This is pretty friggin' simple to do, and I'm sure I'm probably making a silly noob mistake, but I just don't have any experience with this kind of code, so if someone can tell me how to make my zip run that very simple line, I'd much appreciate it.
Thanks.
Click to expand...
Click to collapse
Sir can you tell me what to do to change ro.product.name if same phone in different regions is having different ro.product.name so that the build.prop for every phone that's installed.

[ROOT HD 10] Enable advanced power menu (global actions) + my other framework mods!

*****ONLY WORKS FOR FIREOS 5.6.2.0 OR LOWER*****
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0 or 5.6.2.0****
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
Code:
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
4. Long press power button. Score. :highfive:
P.S. This framework also contains all previous modifications. References:
How to guide: Enable 'ok Google' to work from ANY screen
[ROOT] [HD 10 2017] FireTabletSettings.apk Rewritten [August 22, 2018]
[FIRMWARE] [STOCK] Pre-rooted, optimized, stock firmware for HD 10 Suez [APRIL 2019]
[Root] [HD 10 Suez] Remove parental control applications/restrictions [May 2019]
[TEST] [Flash Zip] [HD 10] [ROOT] All-in-1: The ultimate hacks, tricks & mods zip
[Root] [App] [All tablets] Disable & replace lock screen - set custom wallpaper
NO ROOT REQUIRED: Working Screen Mirroring
UPDATE (for 5.6.1.0):
June 1, 2019
- Increased default system volumes from -6 db to 8
- Set preference for 5ghz wifi to false. Setting this to true only allows 5ghz connections. 2ghz are ignored if set to true.
- Fixed typo in time server I found in the system logs.
- Extend network attributes (I don't know if these actually work but doesn't hurt either way)
- Wpa_supplicant_scan_interval by default is set to 15000.... milliseconds. Raised value to 150000000. This may have been the cause of disconnects on a constant level.
- preferences prefer dual pane set to true
- Bar separating notifications from system messages was narrow (set to true). Set it to false.
- Low battery warning is now 10% instead of 25%. Extreme low battery warning (almost dead battery) set at 5%

DragonFire1024 said:
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.a
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0*** (5.6.2.0 comes soon. Possibly 5.3.x.x)
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
Code:
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
4. Long press power button. Score. :highfive:
Click to expand...
Click to collapse
I have updated to the latest, 5.6.3.0 (erroneously called 5.3.6.4). I guess it is risky to do this until someone tries it and says it works? I've been using retyre's prerooted installs for the last couple of releases. So if this screws things up, I would have to adb sideload and root again, which I'd like to avoid.
Ignoring that issue, can the file just be copied into the correct folder with a file manager since I'm already rooted?

sga999 said:
The title says it all. I've activated the stock global actions power menu. The options need tweaking a bit still, but this was too good to wait.
For the moment, without an Xposed module, the stock options are: Airplane Mode, Settings, Lock Now, and volume. With Gravitybox, you can add power (might be stock. I noticed this after gravitybox was installed), restart (which leads to soft reboot, reboot, recovery reboot and boot loader reboot).
How?
One minor edit to the framework was all it took. The menu was disabled, the value set to 0. Change the value to 1, and you get the menu. Simply long press the power button for a couple of seconds and it will pop up.
I have been trying for so long to get this to work. I looked at the configuration dozens of times and didn't figure out what it meant until today. This needs a bit more work and can probably be added to my settings.apk, but that's for another day.a
Requirements:
Rooted HD 10 on FireOS ***5.6.1.0*** (5.6.2.0 comes soon. Possibly 5.3.x.x)
Windows PC with ADB
Installation:
1. Download and install adbd insecure.
2. Download and place the attached framework-res.apk in your ADB folder and plug your tablet into your PC.
3. Open adbd insecure and check the top box to make adb insecure. Open an adb window and type the following, hitting enter at the end of each line:
I have updated to the latest, 5.6.3.0 (erroneously called 5.3.6.4). I guess it is risky to do this until someone tries it and says it works? I've been using retyre's prerooted installs for the last couple of releases. So if this screws things up, I would have to adb sideload and root again, which I'd like to avoid.
Ignoring that issue, can the file just be copied into the correct folder with a file manager since I'm already rooted?
Click to expand...
Click to collapse
There was one report of it working a week or two ago. No one has said anything since. If it doesn't work, worst case is you need to flash back to 5.6.x.x

DragonFire1024 said:
There was one report of it working a week or two ago. No one has said anything since. If it doesn't work, worst case is you need to flash back to 5.6.x.x
Click to expand...
Click to collapse
1. If it fails, and I'm unable to boot, I will have to redo the sideload of the bin file. Then I have to reroot. As I said, I've just been using the prerooted version for the last couple of releases which means I don't have to go through extra steps to root. Since I am rooted, I just use Flashfire to flash the new prerooted version by retyre.
2. I was asking about copying the framework file that you put out there. If I ignore the problems of it possibly messing up my system, and I just want to try it anyway, why is it necessary to use Adb insecure and the PC? Since I'm rooted, can't your framework file just be copied to the correct folder?
3. Finally, can you tell me exactly what you changed in the framework? In your other thread about modifying the framework, you give some good instructions on how to decompile and recompile. I might want to try that instead of using the version that you have created here (since I'm on 5.6.3.0). Is it really just one boolean that needs to be changed?

sga999 said:
1. If it fails, and I'm unable to boot, I will have to redo the sideload of the bin file. Then I have to reroot. As I said, I've just been using the prerooted version for the last couple of releases which means I don't have to go through extra steps to root. Since I am rooted, I just use Flashfire to flash the new prerooted version by retyre.
2. I was asking about copying the framework file that you put out there. If I ignore the problems of it possibly messing up my system, and I just want to try it anyway, why is it necessary to use Adb insecure and the PC? Since I'm rooted, can't your framework file just be copied to the correct folder?
3. Finally, can you tell me exactly what you changed in the framework? In your other thread about modifying the framework, you give some good instructions on how to decompile and recompile. I might want to try that instead of using the version that you have created here (since I'm on 5.6.3.0). Is it really just one boolean that needs to be changed?
Click to expand...
Click to collapse
1. Yes
2. With a root explorer yes.
3. For this? An integer was all. Everything else? That's too much to type. Honestly I spend hours and days reading them testing and mostly failing. I can't tell you the amount of bookmarks i have, maybe close to 500 or more. A lot of times I have to mix together old tricks. you spend most time reading than anything.

DragonFire1024 said:
1. Yes
2. With a root explorer yes.
3. For this? An integer was all. Everything else? That's too much to type. Honestly I spend hours and days reading them testing and mostly failing. I can't tell you the amount of bookmarks i have, maybe close to 500 or more. A lot of times I have to mix together old tricks. you spend most time reading than anything.
Click to expand...
Click to collapse
I don't understand your answer to 3. I'm just interested in what you changed in the framework-res to get the advanced power menu. You said it's just an integer. If I decompile framework-res.apk, where is the integer that must be changed? When you said "everything else", maybe you mean all your changes in the thread about hacks, tricks, and mods? I'm not asking about those. I'm only asking about the advanced power menu that you are talking about in this thread.

sga999 said:
I don't understand your answer to 3. I'm just interested in what you changed in the framework-res to get the advanced power menu. You said it's just an integer. If I decompile framework-res.apk, where is the integer that must be changed? When you said "everything else", maybe you mean all your changes in the thread about hacks, tricks, and mods? I'm not asking about those. I'm only asking about the advanced power menu that you are talking about in this thread.
Click to expand...
Click to collapse
If you decompile it, it would be in res/values/integers. The config would be (paraphrasing) 'long_press_on_power'. Since in this AOSP framework the global actions are active, you have a choice of values of 0 or 1. 0 being no action, 1 being the action. It's a few lines away from 'long_press_on_home' which is supposed to be between 0 and 3. 2 would activate the voice assist. But for some reason I haven't figured out, setting that value does nothing one way or the other but gravitybox fixes it.
You can change around the global action menu too I saw, but didn't have time to experiment with that yesterday.

@DragonFire1024
Nice hack! Like your new power menu - always wanted something like that!
Now, given that it'd be such a burden to update this for every FireOS version, any chance you'd take a stab at putting this together as an Xposed module? Other rooted Fire tablets could use it too.
I recall sometime in the past there were modules designed for FireOS - if you find that on XDA, you could start from that one.

DragonFire1024 said:
If you decompile it, it would be in res/values/integers. The config would be (paraphrasing) 'long_press_on_power'. Since in this AOSP framework the global actions are active, you have a choice of values of 0 or 1. 0 being no action, 1 being the action. It's a few lines away from 'long_press_on_home' which is supposed to be between 0 and 3. 2 would activate the voice assist. But for some reason I haven't figured out, setting that value does nothing one way or the other but gravitybox fixes it.
You can change around the global action menu too I saw, but didn't have time to experiment with that yesterday.
Click to expand...
Click to collapse
Here's what is in my integers.xml file for 5.6.3.0. Are you saying I need to change 2 to 1 in the first one? And no changes to the others?
<integer name="config_longPressOnPowerBehavior">2</integer>
<integer name="config_shortPressOnPowerBehavior">1</integer>
<integer name="config_doublePressOnPowerBehavior">0</integer>
<integer name="config_triplePressOnPowerBehavior">0</integer>

@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.

sga999 said:
Here's what is in my integers.xml file for 5.6.3.0. Are you saying I need to change 2 to 1 in the first one? And no changes to the others?
<integer name="config_longPressOnPowerBehavior">2</integer>
<integer name="config_shortPressOnPowerBehavior">1</integer>
<integer name="config_doublePressOnPowerBehavior">0</integer>
<integer name="config_triplePressOnPowerBehavior">0</integer>
Click to expand...
Click to collapse
Correct. First config set to 1 and leave the others as is, unless you want to test them out.

Rortiz2 said:
@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.
Click to expand...
Click to collapse
I have not. I rarely touch that at least not Amazon smali. It doesn't translate well at all. And haven't really had to so far. And the framework is odexed...well the .jar in system/framework is, so they don't have smalis.

bibikalka said:
@DragonFire1024
Nice hack! Like your new power menu - always wanted something like that!
Now, given that it'd be such a burden to update this for every FireOS version, any chance you'd take a stab at putting this together as an Xposed module? Other rooted Fire tablets could use it too.
I recall sometime in the past there were modules designed for FireOS - if you find that on XDA, you could start from that one.
Click to expand...
Click to collapse
I was thinking about that however if gravity box works to bring out the rest (reboot etc) I imagine other power menu modules will also work now.

DragonFire1024 said:
I was thinking about that however if gravity box works to bring out the rest (reboot etc) I imagine other power menu modules will also work now.
Click to expand...
Click to collapse
Gravity box might work - AFTER your framework-res.apk replacement (which needs updating after each OS version). As is, for me Gravity does not bring anything out beyond the stock "Power off" option. It seems a module could simply patch framework with the correct flag, and then Gravity will do its thing. Same logic would apply to other features that Amazon might have chosen to disable.

bibikalka said:
Gravity box might work - AFTER your framework-res.apk replacement (which needs updating after each OS version). As is, for me Gravity does not bring anything out beyond the stock "Power off" option. It seems a module could simply patch framework with the correct flag, and then Gravity will do its thing. Same logic would apply to other features that Amazon might have chosen to disable.
Click to expand...
Click to collapse
Install framework in OP then you need to enable the advanced power menu in gravitybox, power tweaks. Then long press power button, tap restart, then you get your options for reboot.

Rortiz2 said:
@DragonFire1024, Have you edited smalis? It is for do it in the framework-res.apk of another tablet.
Click to expand...
Click to collapse
Also for the most part Amazon just moved configurations around maybe changed a few characters or couple of words. But for the most part a significant portion if not almost all of the Android source for this version was left inside these files. There are very few things I actually had to rebuild. The battery stats is one of those things. Other things are more difficult and require other pieces of software, for example specific apks. That took quite a lot of time to hunt down working versions of certain apks. Remember we are working with what is considered a stone age OS version. So we have to literally search for needles and haystacks just to find the one tiny thing that makes it all work... Well at least some of it

Gosh, I tried for a long time to decompile/recompile framework-res.apk (5.6.3.0)...no luck! I'm using your instructions in post 2 in the 7 wallpaper thread as a guideline. I can decompile successfully. Then, even without making any changes at all, recompile does not work. I won't bother to put the error display here unless you're interested. (systemui.apk fails on the recompile also, but in a different way). A "regular application" will decompile and recompile just fine.
So I have no idea what's wrong. I do have xposed/gravitybox installed, and I wonder if that causes the problem (but it sounds like have those also?). Or some change to 5.6.3.0 that you did not encounter with prior releases. I'm wondering if you can upload your framework-res.apk somewhere so that I can try that. At least that would narrow it down to the new release or my error.
There are lots of posts about this kind of problem, but they mostly talk about wrong paths, etc. That is definitely not my issue.

I had downloaded the most recent apktool, 2.3.4. Just for fun, I just tried 2.2.0. There are 4 warnings, but otherwise, it worked. I haven't tried to install the new framework, so I can't be sure all is okay, but it's certainly a good sign. I will also try more recent versions of apktool, i.e. ones between 2.2.0 and 2.3.4, and see where it went wrong.
EDIT: 2.3.2 and earlier are good, 2.3.3 and 2.3.4 are bad.
---------- Post added at 04:58 PM ---------- Previous post was at 04:55 PM ----------
If it ain't one thing, it's another! After changing the integer, I'm trying to drag and drop with 7zip from the new apk to the old, as you described in your other thread. For resources.arsc, it works as you said, i.e. it asks if I'm sure I want to copy. But for the res folder, it doesn't ask me anything and just starts extracting into the old. I cancel it before it can complete.
Do you recall doing something different for the res folder? I could be on a different 7zip version than you, of course. I've used 7zip, but I'm not that familiar with it.
EDIT2: I don't think a notification is done if my edit gets combined with my prior post. I tried both reply and quick reply, and both ended up combining. Can someone tell me how to make it do a new post? Or maybe I'm wrong and another notification occurs, in which case, ignore this!

sga999 said:
I had downloaded the most recent apktool, 2.3.4. Just for fun, I just tried 2.2.0. There are 4 warnings, but otherwise, it worked. I haven't tired to install the new framework, so I can't be sure all is okay, but it's certainly a good sign. I will also try more recent versions of apktool, i.e. ones between 2.2.0 and 2.3.4, and see where it went wrong.
EDIT: 2.3.2 and earlier are good, 2.3.3 and 2.3.4 are bad.
---------- Post added at 04:58 PM ---------- Previous post was at 04:55 PM ----------
If it ain't one thing, it's another! After changing the integer, I'm trying to drag and drop with 7zip from the new apk to the old, as you described in your other thread. For resources.arsc, it works as you said, i.e. it asks if I'm sure I want to copy. But for the res folder, it doesn't ask me anything and just starts extracting into the old. I cancel it before it can complete.
Do you recall doing something different for the res folder? I could be on a different 7zip version than you, of course. I've used 7zip, but I'm not that familiar with it.
EDIT2: I don't think a notification is done if my edit gets combined with my prior post. I tried both reply and quick reply, and both ended up combining. Can someone tell me how to make it do a new post? Or maybe I'm wrong and another notification occurs, in which case, ignore this!
Click to expand...
Click to collapse
Lol it's going to take a bit to get used to everything. I actually had messed around with apktool when I first started all this and got so frustrated I just stopped trying. 6 months after that I tried again and it took me a week or so before I successfully compiled and installed a system apk. My initial goal was to use this method to try and trick a non rooted tablet into thinking it was installing an update to a system app. Though it worked on rooted devices, I could never get it to work for non rooted ones. Don't give up,keep trying and re check everything, especially make sure your PATH to the proper tools is correct. I'll look at the latest fireOS framework tomorrow.
P.S. without any further modifications, I tested APM+ Xposed module and it works too. You can add and remove all the optioions plus add different ones depending on the module. No further tweaking needed on my end.

Okay, when dragging and dropping res, it does finally ask if I really want to copy AFTER it takes quite a while "extracting". I was confusing extracting with unzipping or unpacking...or some other term that would imply it was changing the format. I'm still not sure if it's doing it properly, but I'll keep trying. And I'd still like to know how to make these combined posts cause a notification, and if not, how can I force it to.

No Mobile Data on Treble Roms

I've tried over 5+ different treble ROMs and the mobile data will not work. My friend @Spaceminer had helped me try to solve it by finding an apns-conf.xml as well as a flashable zip but no luck.
I'm using the Moto G6 Play XT1922-7 Boost Mobile Variant.
I'm sorry I haven't provided much detail to the issue but this basically sums it up.
Thank you for any help.

Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie

Alphita said:
Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie
Click to expand...
Click to collapse
Did you try to flash the vendor.img on TWRP?

sinkoo1979 said:
Did you try to flash the vendor.img on TWRP?
Click to expand...
Click to collapse
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks

Alphita said:
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks
Click to expand...
Click to collapse
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.

Spaceminer said:
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.
Click to expand...
Click to collapse
How do i set those permissions? Thanks in advance

Alphita said:
How do i set those permissions? Thanks in advance
Click to expand...
Click to collapse
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot

Spaceminer said:
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot
Click to expand...
Click to collapse
Thanks! I will try this the next time i flash a rom

Would someone be so kind enough to share their BOOST apn.config.xml that the replaced the one on with that does NOT work on these GSI's?? If you do I'll follow you and hit thanks all day. ??

Here's (see screenshot) the closest I've ever gotten far as having data on a gsi. I must have the wrong xml file. I am fully aware of the process described above and have even done it multiple ways after I knew the way described and how I was adding the apn xml was correct and I have zero data.
If someone will attach their apn.config.xml, the one that they acquired data from using the boost Mobile network I'll be extremely thrilled and forever greatful to add it to the thread I made over in guides section so that in the future people can solve this issue fast and get her running and have a jolly day. ? I made that thread (I'll change the name later today) initially to consolidate as much info as I could and put it all in the op so we can be a bit more organized. I just haven't figured out anything else so I can't add to it just yet. ? This would be a great addition if someone would be so cool enough to kick me down some knowledge far as what's the correct apn.config.xml to replace the og one in gsi to get data working. I've deleted the current apn xml and replaced it with the one I have, I've overwritten it, I've tried countless times messing with the telephony.db and I obviously can't do it. Please pleeeaasee post the proper apn xml so I can get this phone going and add to op over there. @Starkiller2
I hope everyone is having a good day. It hot as **** where I'm at today. ??

I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight

Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.

Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Vague and unhelpful. Need better directions on that I messed with sqlite editor for days on end swapping out telephony.db things and never did get it going.
Did you swap both of them??
Did you swap other files in telephony.db too?
Details...?
What files exactly did you extract in telephony.db?
Vague comments never help anyone. Better to not post at all then post some two word comment with a link.

I apologise, I'm driving across country and was making an effort to help in the little time I had, but you're right, better to not try at all. Which may be why you aren't getting any answers to your questions. Some info is usually better than none and can sometimes lead you in the right direction, but you won't even get that much snapping at everyone who doesn't immediately solve the problem you have and then rage quitting when you can't do it yourself. It makes people not want to put in any effort. You have 4000 posts I assumed you could figure out how to edit apns with an app from the play store. You're right. I should absolutely stop offering any input at all, but rather I should just start *****ing and whining when I'm not spoon fed like I see so much here.
And as I have posted directions in multiple other threads, I assumed you had done at least a cursory search for your answer(as per forum rules) which would've found those posts but I was apparently wrong there as well.
---------- Post added at 07:00 PM ---------- Previous post was at 06:45 PM ----------
Spaceminer said:
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.
Click to expand...
Click to collapse
Thank you. That's good to know

hi, there is in the web a file apns-conf.xml to download? or sombody take us a backup? Thanks

Hey gang, I too am having issues trying to simply get mobile data working on GSI's. I have a Pixel 3a, and have tried multiple Android 10 GSI's, all of them don't allow me to use mobile data. I have not tried the apns-conf.xml trick yet, as I am unsure if that's the answer if it hasn't worked for others. Android 11 does not use an apns-conf.xml in system/etc/ so I couldn't extract it from my current setup unfortunately. Wish you all luck, post back if you get something working.

not working, moist do you have rooted phone? because only on rooted phones you can do this trick

doid1 said:
not working, moist do you have rooted phone? because only on rooted phones you can do this trick
Click to expand...
Click to collapse
I'll probably flash a ROM this weekend and pull my xml to test this. I have Telus so I unfortunately can't help with the Boost users, but can at least help confirm whether this method works or not.

ok thanks i wait, my phone seems to be dead on 4g.. says: no registration..
I tried everything imaginable and perhaps even the unimaginable .. heheheh .. but the result is always the same: no recording on the 4g, so I'm more and more inclined that it is a hardware failure or even a damage to the eeprom memory because 'I have formatted everything and the mobile phone has recharged everything correctly but it was useless ..
I tried to see that maybe it has a sim locked, but I didn't manage to enter meta mode and try to force it also because only with miracle box there is a guide ... umh ... and I do not stop until I succeed in the objective, and then the next step will be to take a complete image of another mobile phone identical to mine and copy it over it (but it is almost impractical because I cannot find anyone who gives me a full backup of this phone) and then I will brutally try to put another image of another working smartphone on it, leaving only the crucial sectors intact (system, boot, vendor, recovery, preloader, everything else I format it hehehehh) I will know..

Well I have a ROM flashed and found the apns-conf.xml, which is not included on my stock ROMs (10 or 11). Now going to flash a GSI or two and do some tests to see if I can get any data working.
Edit: Couldn't get the apns-conf.xml to work. However, I did find out the some GSI's work right out of the box for my Pixel 3A, those included AOSP 10 / 11 by Phh, and the CAOS R build. Bless, qidroid, havoc booted fine but did not have mobile data working.

Develop Bugs

welcome