I'm trying to edit the build.prop file on the G2 803 model. It's rooted and unlocked on a stock Bell Rom. The phone has the wi-fi forgetting problem. everytime I reboot it I have to reset the wifi password. I've tried editing the build.prop file to change the wifi.lge.patch line to=false but I can't seem to enter more than 4 characters after the = on that line. Am I missing something?
Use build prop editor free on playstore
_____________________________________Read more write less and be smart
siggey said:
Use build prop editor free on playstore
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
Thanks, I tried that but the changes don't appear to stick.
Fraggle_Shamy said:
Thanks, I tried that but the changes don't appear to stick.
Click to expand...
Click to collapse
Reason 1: Some build.prop values get their values from the ramdisk on each boot, so that's why some values wont stick.
Reason 2 (requires root): build.prop is located in /system. Your /system may be read-only, we want it to be read-write to make changes, so.. run the following command in a Terminal Emulator downloaded from the play store. Run the following commands,
Code:
su
mount -o rw,remount /system
Now make your build.prop changes. Once finished run the following command to get your system back to how it was,
Code:
mount -o ro,remount /system
If the app isnt helping you, download a file explorer such as ES and navigate to /system/build.prop, open the file and edit the values you want.
Note: It's nice to hit the "Thanks" button under our posts if you indeed are thankful. Saying thanks and not hitting the thanks button is a slap in the face .
Thanks for the suggestion, but the emulator didn't help. I'm guessing it's because it's locked to the boot rom (your first suggestion)? Any way around this? I have anohter 803 that doesn't have this issue. Can I copy the ROM from that phone to the problematic one?
Fraggle_Shamy said:
Thanks for the suggestion, but the emulator didn't help. I'm guessing it's because it's locked to the boot rom (your first suggestion)? Any way around this? I have anohter 803 that doesn't have this issue. Can I copy the ROM from that phone to the problematic one?
Click to expand...
Click to collapse
Try this. (Pretty much the same as a previous suggestion, doubt it will work)
Get a root capable browser. Jrummy has one that's free, I think it's called Root Browser.
Browse to /system there should be a button to mount it r/w, if not it may prompt you when you go to edit the file... Long click the file, and try to open for editing. (it may be some other combination, I don't have my phone handy right now). Make the a change or two, reboot and see if they stick.
Or the other thing you cna do is:
The other thing you can try is to do is check if they're being set on boot.
adb pull /*.rc
which will pull all of the ramdisk's initialization scripts into your current folder on your computer. Look through them and see if the values are indeed being set by the boot image. If they are, you'll need something like AIK (android image kitchen) to extract the ramdisk, either change or delete those lines, rebuild the boot.img and flash it (using flashify or manually using adb and dd). You have to rebuild them into the boot.img, any changes you make to them directly on the phone will never stay as they get re-created every boot. It's a pretty roundabout way to do it, but it's entirely possible to do.
A much easier, and less likely to cause you issues would simply be to create an init.d script that sets it. This will occur after whatever is setting it in your boot.img so there would be no need to recreate that.
create a file in /etc/init.d called something like... "Set_wifi_pass" set the permissions so that it can be executed and read by everyone.
Then enter the following:
Code:
[B][I]#!/system/bin/sh[/I][/B]
setprop wifi.lge.patch = WifiPassword
You can check that it worked by going through adb shell with
adb shell
getprop wifi.lge.patch
which should return that value you set. Same thing that build.prop is ultimately doing, just in a different way.
Hope that helps.
Related
This is the latest release of my fix (June 14, 2011). This version addresses the Market ID and Moto Blur issue.
I have not had a chance to test the latest version, aside from verifying the awk command works as exptected. The rest is a strong educated guess, mixed with a re-tooling of it to just use Android Debug Bridge to do what I was having scripts do in the past. Should be much more reliable.
IF YOU DECIDE TO USE THESE INSTRUCTIONS: PLEASE, read through this page entirely from top to bottom at least once prior to doing anything. This way, if you are unsure on anything, you can ask the questions you need answers to. I am not liable for anybody messing up their phone because they didn't think to read the F'n manual prior to following these steps.
If you don't read this through completely before starting, and you brick your system, Don't come crying to me. I warned you.
This version makes it close to impossible to brick the system, but I left that bit in to cover my arse.
Earlier today, I wrote instructions on how to root the flipside. Now, I have Unknown Sources enabled. Here's how you can do it.
First, if you don't have root, follow these directions:
http://forum.xda-developers.com/showpost.php?p=9702394&postcount=4
Next, you will need to run a script, but for the script to work you will need to install busybox to your rooted flipside. You can either get it from the market, or download it somewhere on the web. I tried installing it from the market, but it just timed out on download for some reason.
Once you have busybox, you have an environment ready for enabling Unknown Sources. Lets do it:
Latest version installs busybox for you]
I have not tested it, so you may still need to tell it to install, but it installs the apk.
1. Download the attachment located in this post.
Unzip to a folder on your desktop.
PLUG IN YOUR PHONE NOW!!!
Double click on the batch file ("enable_unknown_sources.bat"). You may have to run as administrator, but I don't think so. Built on Windows XP (I'm a linux guy who wrote this at work in a couple minutes)
When it prompts for you to OK the super user for "unknown", look at your phone. It should have a prompt. If not, it may be ok. We will see....
once your phone has rebooted, you phone will have "unknown sources" enabled already. Don't worry about rebooting. The batch file did that for you.
Quite a bit less work than before. Good news: it's done! never to worry about it again...unless you upgrade....
DISCLAIMER:
DO NOT FOLLOW ANY OF MY STEPS IF YOU ARE UNSURE OF WHAT YOU ARE DOING! I have done my best to ensure that the instructions are accurate, but I made mistakes in the first revision, so who's to say that I didn't miss something this go 'round as well? If you decide to follow this walk-through, your actions are an agreement to not hold me liable if your phone becomes a pretty brick. I am not responsible for what you do with this information. If you have no idea how to do any portion of these instructions, you can either walk away (best idea), or ask for help here.
I am also not the 2nd shooter on the grassy knoll, nor am I the cause of all your woes throughout life. I always wanted to say that in a disclaimer.
run_second.sh
i get errors when i attempt to run your run_second
though for the life of me... i can't figure out what's wrong with it?
What error do you get?
on all 4 of the cp commands... i get a return of
cp: (destination directory): Invalid argument
EDIT: tried the run.sh script... got an invalid file/folder error on the mount... on one of the cp's... and on the chmod of the same
EDIT: i manually edited the 2 files in the system directory using notepad++ and droid explorer...
couldn't find the 2 databases anywhere on the phone? hidden?
Odd. I did this:
Code:
ls /data/data/com.motorola.android.providers.settings/databases
and I get this back:
Code:
settings.db
The only time I cannot do that is if I don't have super user.
DOH! just realized the issue. once you type "SU", go to your phone, and tell it to allow application "unknown" super user.
Forgot about that part.
well... here's one for you then... i have nothing in my /data/ directory...
never did...
EDIT: wait... droid explorer lied to me... now if i could just get into that file... i could hard change them without having to deal with all the scripting
script typo
Thanks for the script. I have managed to enable it by following your script.
However there are a few typo in your script that caused errors. I have corrected them. You may check attached script.
jonsjava said:
What error do you get?
Click to expand...
Click to collapse
I get an error when I exicute run.sh
: No such file or directory
monho said:
I get an error when I exicute run.sh
: No such file or directory
Click to expand...
Click to collapse
Did you install busybox? Please, run through what you have done so far. My goal is to get a comprehensive how-to together, and any and all input I can get will assist me to that end.
i'm getting read only file errors on the script now... i assume some file attributes need adjusting... not sure how to do that...
Did you remount /system/ in rw mode, as mentioned in the walkthrough? /system is read only by default, but part of my how-to explains how to re-mount it in read/write
all 5 chmod statements return no file found....
EDIT: even reboot is no found
that sounds like you don't have super user, or busybox isn't installed.
i have super user access... i used z4root... this also installs busybox... or so i'm told...
rignfool said:
i have super user access... i used z4root... this also installs busybox... or so i'm told...
Click to expand...
Click to collapse
That does not install busybox. As stated in my how-to, you will need to either download busybox from the market, or get it from the web.
I know it says it does, but I didn't have busybox features until I installed it manually myself.
root explorer FTW
so... after using root explorer to manually edit the mkitso files... and copy the databases from the /ab/ directory....
i made it work...
Hallo there. Please I would appreciate if you can help me. When you say:
1.Look for the one that says "/system". Mine says "/dev/block/mtdblock7"
- Mine says the same too, is that right? Could it be different? Why sould we care where it says 'system'?
2.'type this in (changing the /dev/ as needed)':
-When you say 'as needed' that means changing the /dev/ is not neccesary? What does ir depends? If it's neccesary, what should I type instead of /dev/?
3. 'Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock7 /system'
-Must that line be typed exactly as it's shown? I've done so and after running the commands:
cd /sdcard/
sh run.sh
-This error message appears:
No such file or directory
I've rooted with z4. I've already installed BusyBox from the market, altought I can see it's not an app that appears like the others: I've just got an Icon named 'busyBox Installer' and after all it says 'busybox is successfully installed'.
Please excuse my bad english and thank you very much in advance for your help
1. I wrote it that way just in case it was different anywhere else. It shouldn't be.
2. when I said "change /dev/..." It was in reference to 1. above
If /system is /dev/block/mtdblock7 as listed, you don't need to change it.
If /system is /dev/block/mtdblock21 (example), you would need to change my command to read:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock21 /system
That's what I mean when I said change /dev as needed. Seeing how yours is the same as mine, that is not necessary.
3. the command to mount /system will not affect the sdcard. Make sure the /sdcard isn't mounted on your computer. In windows, look in "My Computer", or your languages equivelant, and if you see the phone there, right click and tell it to unmount. Wait a few seconds for the phone to access the SD card, and try again.
so, I too have problems running run.sh
I tried both the one in the original post and the typo fix in the other post. Both didn't work. I get file not found errors.
Yeah, I have z4root done and busybox installed no problem.
For some reason it's not seeing the files when I run run.sh.
Here's a copy paste just to prove what I am seeing:
Unable to chmod /system/etc/motorola/com.android.providers.settings/secure.mkitso
: No such file or directory
Unable to chmod /system/etc/motorola/com.android.providers.settings/system.mkitso
: No such file or directory
I verified that my sdcard has /ab/ folder copied over, and all the subfolders and files from the original archive are moved over.
What gives?
Hello!
My main question is: where are the settings stored? I've done some research, and there is apparently supposed to be a file called settings.db on android phones... but mine doesn't have one
I was locked out of my phone because of the pattern lock screen, and it will not accept my gmail user name and password. It immediately fails when I submit the info, and I am positive it is correct. A common solution to this problem is to change some variables in settings.db (for different phones).
To find all .db files, I used: find / -name "*.db" -print
I can boot into clockwork recovery and connect with adb...
Thanks in advance!
Are you running the command as root? The default user doesn't have read access to all directories on the phone, and it's likely the file is in one of those directories.
I believe so. I have a # for the prompt.
Ah, after many hours, I have fixed my problem. Since it's possible someone else may find this thread, I'll explain what I did. Basically, the datadata folder is not auto-mounted. I noticed this when I was doing a nandroid backup... so, I mounted it, and my problems were solved
First, I used adb to pull /etc/fstab. In fstab, you can view the device location that is usually mounted for the datadata folder (open it in notepad or wordpad or something).
After that, I used adb -d shell and mounted the device.
I forget the name of the block file, but the syntax of the command to mount devices is:
Code:
mount <block_device_location> /datadata
Come to think of it, "mount /datadata" might have also worked.
After that, I was able to find the settings.db file in the datadata/databases folder and edit a setting in it to remove the permanent lock using the "sqlite browser". The variable to change is obvious (it has permanent lockout in the name) and it needs to be changed from a 1 to a 0.
**** this **** didnt work, too confusing.
I'm kinda new to android
I've started to delete useless apps through Titanium Backup(acer staff,games etc) , and exidently deleted smth connected with honeycomb stock keyboard.
Now every time when i want to use stock keyboard, pops up a messege "The application Android keyboard (process com.google.android.inputmethod.latin) has stopped unexpectedly. plz try again".
Ive tryied to reset factory data but it wont helped. Is thera any solution for this problem? if there no, plz tell how to completely reset tablet) ive read "system Images " thread but i didn understand some things
here is my recover steps: (for a500 which is bricked)
for a500 is normal:
root it
put the system.img into a500
connect to the computer with adb and follow the codes:
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
then reboot
Click to expand...
Click to collapse
connect to the computer with adb and follow the codes:
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
what that means)
You might very well have ruined your tablet.
I'm not a developer or coder so I can't make any sense of the code you posted but if a reset didn't fix it then you've certainly deleted something important. Hopefully someone has some ideas.
If not, then maybe you can return it? And next time, don't delete something unless you know what it is you're deleting.
ok ive recovered from image, but now wifi is not working , what should i do?
There are posts about having to change file permissions to fix wifi. Search this forum, there are a few.
edit - linked post
http://forum.xda-developers.com/showthread.php?t=1074449&highlight=wifi+permission
yeah ive read this but i dont know how to move that files to system folder on devide, wifi is down , so i cant download any file managing apps from market and theres no any file managers on stock Rom
If you've got the adb working, you can use the command mv to move the file.
I'm not sure of the exact path involved, but for example. the file is in /mnt/sdcard/filetobemoved and needs to go into /sytem/lib/modules
mv /mnt/sdcard/filetobemoved /system/lib/modules
That'd put it in the location you need. To change the permissions, you'd use the command chmod
chmod 655 /system/lib/modules/filetobemoved
The 655 is an octal(0-7) representation of the file's permissions. I'm not sure what permissions it needs, but you could try 655 as a start unless someone else knows for sure.
if you want, hit me up on msn, I can try to walk you through it: [email protected]
Glebaka said:
ok ive recovered from image, but now wifi is not working , what should i do?
Click to expand...
Click to collapse
Ah *phew* Good to hear.
gammaRascal said:
Ah *phew* Good to hear.
Click to expand...
Click to collapse
lol How'd he get in that shape to begin with? Any idea what exactly it was he deleted that bonked his system?
muqali said:
lol How'd he get in that shape to begin with? Any idea what exactly it was he deleted that bonked his system?
Click to expand...
Click to collapse
No clue. I really should start reading up on HC app development and at least familiarize myself with that environment.
I haven't rooted yet cause I'm e'scarded to.
ahh i cant replace that files , somehow installed astro manager(through docsttogo) but i cant remove/replace/rename that files in system/lib/modules it says i dont have permission to do this.
tryed in connectbot type "mv /mnt/sdcard/filetobemoved /system/lib/modules"
got this "failed on '/system/lib/modules/filename' - cross-device link"
im rooted what if
Glebaka said:
ahh i cant replace that files , somehow installed astro manager(through docsttogo) but i cant remove/replace/rename that files in system/lib/modules i dont have permission to do this.
tried connectbot tryied "mv /mnt/sdcard/filetobemoved /system/lib/modules"
got this "failed on '/system/lib/modules/filename' - cross-device link"
im rooted
Click to expand...
Click to collapse
type mount and paste/retype the line that has /system in it. It might be mounted read only.
or try the cp command in place of mv
edit - also, the filetobemoved is just an example. I think one of the filenames is bcm4329.ko but I'm not sure. so /system/lib/modules/bcm4329.ko would be the full path
ah im total noob tried cp instead of mv it said permission denied .
t
ype mount and paste/retype the line that has /system in it. It might be mounted read only.
Click to expand...
Click to collapse
i didnt get that (
edit - also, the filetobemoved is just an example. I think one of the filenames is bcm4329.ko but I'm not sure. so /system/lib/modules/bcm4329.ko would be the full path
Click to expand...
Click to collapse
yeah thats i know)
Are you logged into the tablet using adb's shell? I've only used that once on a different tablet, but iirc the commands are standard Unix/Linux commands. Someone correct me if I'm wrong but aren't you already logged in as superuser like this? You don't need to 'sudo' or 'su' to switch over do you?
I'm not familiar enough with this specific environment to figure out what might be keeping you from placing those files in that location. The command to check the partitions mount options is
mount
It should return a bunch of text, one line of which is gonna be the /system partition. If it's ro(read only) then you can't write to it and would need to remount it.
yeah it looks like it is "ro"
ive got /system ext4 ro
how to remount)
My knowledge of adb is limited as well. All I know is that I can connect to it, type: adb devices (in the command prompt) to make sure it sees my tab then 'adb push filename.extension /directory/structure' to force files... Conversly, I think adb pull filename.extension /directory/structure will grab files on the tab if you know what they are called and where they are located.
Glebaka said:
yeah it looks like it is "ro"
ive got /system ext4 ro
how to remount)
Click to expand...
Click to collapse
what was the /dev/block/mtdblock for /system?
there is a number after it...for example /dev/block/mtdblock1
mount -o rw,remount -t ext4 /dev/block/mtdblock1 /system
would remount it read/write, provided that it is mtdblock1, change the number depending on what your device has.
yeah now /system have "rw", but it anyway refuses to copy using mv(failed on '/system/lib/modules/filename' - cross-device link"
) or astro manager
Glebaka said:
yeah now /system have "rw", but it anyway refuses to copy using mv(failed on '/system/lib/modules/filename' - cross-device link"
) or astro manager
Click to expand...
Click to collapse
If cp won't put it there either, I'm out of ideas. Maybe ask in the other thread how they were able to copy/move the file and set the permissions?
I know it may not be really classy, but how about downloading an .apk That will let you mount the drive, to an sd card in a computer then transfer that to the Acer. (If it's an extreme case and nothing else will work..not condoning piracy, but don't know what would work...)
or is it possible to copy the system data from a Titanium backup and send it over so he can restore the missing files?
This following step I can't be responsible for it's safety. It looks safe to my eyes, but proceed having been forewarned. I did some research and you might be able to use dd to get the file there.
dd if=/mnt/sdcard/filname of=/system/lib/modules/filename
after ROOTING Nougat 32.3.A.0.376 (E6833 E6853 E6883) (E6633 E6653 E6683 ), we will still face ERROR while removing system apps, because GOOGLE has changed file system properties in Android N to READ ONLY
in order to make system directory WRITABLE, install busybox, and terminal,
type these lines and enter one by one in #terminal
Code:
su
mount -o rw,remount /system
ORRR
Code:
su
busybox mount -o rw,remount,rw /system
-----------
What???
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
chinmoy32 said:
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
Click to expand...
Click to collapse
Mee too unable to write on system
download terminal on google play
open terminal
write "su" command and give root permission
then you will see "#"
after that, write this command:
Code:
echo 0 > /sys/kernel/security/sony_ric/enable
then you write this command:
Code:
mount -o rw,remount /system
if you see "#" again, it worked
but if you see "mount: Operation not permitted" it has not, sorry
Credits: https://forum.xda-developers.com/showpost.php?p=70677335&postcount=92
I did what @serajr described here:
https://forum.xda-developers.com/xp...-kernel-dm-t3301605/post70595975#post70595975
works like a charm, system always writable!
Can any of you share here your perfectly rooted working kernel for Z5 E6683 DSDS ????
chinmoy32 said:
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
Click to expand...
Click to collapse
i found a workaround and it goes
installing busybox
installing terminal
and writing following codes
Code:
su
'to give terminal root access
busybox mount -o rw,remount /system
later using ROOT APP REMOVER i manage to remove all bloatware!
toncheee said:
I did what @serajr described here:
https://forum.xda-developers.com/xp...-kernel-dm-t3301605/post70595975#post70595975
works like a charm, system always writable!
Click to expand...
Click to collapse
@serajr workaround was fo when rootkernel4.51 wasn't able to support Nougat kernel
however if you follow carefully, the lines mentioned
Code:
on post-fs
export LD_PRELOAD libNimsWrap.so:libdrmfix.so
and
Code:
write /sys/kernel/security/sony_ric/enable 0
will switchoff SONYRIC and will fix DRM
the issue is NOT sony RIC,
Google in general with or without any security/rootaccess changed the system folder properties from default Writable in <+ 6.01 Android version to READABLE ONLY from android 7.xx
so when i followed the both method of altering file via notepad++ in the ramdisk folder using N kernel and rootkernel version4.5, I ended up having fully root system with READLY ONLY ACCESS to /system partition and i could only switchoff the apps but can't remove!
YasuHamed said:
@serajr workaround was fo when rootkernel4.51 wasn't able to support Nougat kernel
however if you follow carefully, the lines mentioned
Code:
on post-fs
export LD_PRELOAD libNimsWrap.so:libdrmfix.so
and
Code:
write /sys/kernel/security/sony_ric/enable 0
will switchoff SONYRIC and will fix DRM
the issue is NOT sony RIC,
Google in general with or without any security/rootaccess changed the system folder properties from default Writable in <+ 6.01 Android version to READABLE ONLY from android 7.xx
so when i followed the both method of altering file via notepad++ in the ramdisk folder using N kernel and rootkernel version4.5, I ended up having fully root system with READLY ONLY ACCESS to /system partition and i could only switchoff the apps but can't remove!
Click to expand...
Click to collapse
I also think the issue is not the RIC but something to do with the Nougat filesystem itself.
I can delete all the files and folders with any file managers I like but like after 1 sec they all reappear as nothing ever happened to them !!!
How strange is that ??
It shows file sizes when I delete them and take times to delete the folders with , say for 500MB
but they still reappear after just 1 refresh or 1 sec.
I cant figure it out at all for the sake of my sanity --- why the hell this is happening ????
https://www.dropbox.com/sh/2kf8wg3g13pv869/AACB3l8iPJHJnBlpnGorRqrha?dl=0
@bungadudu @chinmoy32
I followed bungadudu-s steps and it worked i can change permissions and prove it with link i provided.
And chenges, yes they stick after reboot and i can rename files allso, but:
after reboot i have to repeat this steps if i want to change something elsewhere, old changes do stick aroind though
I deletet phone to 0 mb in twrp, flashed AU nougat .372 with flashtool, rebooted into twrp, flashed zip file provided in link, then flashed supersu in link and rebooted, no custom kernel used
Next i will try to copy modified thermal files now and see if they stick after reboot and if kernel aduitor uses them, see you later
Observations:
-i changed permissions from file /system/build.prop and changed lcd density to 320 and i have bootloop
working on how to boot it up...
YasuHamed said:
after ROOTING Nougat 32.3.A.0.372 (e6833 e6853 e6883) (E6633 E6653 E6683 ), we will still face ERROR because GOOGLE has changed file system properties in Android N to READ ONLY
in order to make system directory WRITABLE, install busybox, and terminal,
type these lines and enter one by one in terminal
Code:
su
busybox mount -o rw,remount /system
-----------
Click to expand...
Click to collapse
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
https://www.dropbox.com/s/d9ie598b618feiz/recovery.log?dl=0
i managed to get somesort of log from twrp in link from previous post will this sufice?
i am reflashing my phone so i can not look at versions, for now i used:
when i reboot it i can look into busybox version
SR3-SuperSU-v2.79-SR3-20170114223742, on top of that i installed pro:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
busyboxpro
https://play.google.com/store/apps/details?id=stericson.busybox.donate
terminal from romtoolbox pro:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
those are some apps i support so i dot know if it makes a diference from non paid
chinmoy32 said:
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
Click to expand...
Click to collapse
chinmoy32 said:
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
Click to expand...
Click to collapse
I install both of them via play.google.com
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
&
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
later i opened terminal and ran those commands
later i installed System App remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
granted it SU rights and removed HANGOUTS and GOOGLE MOVIES etc
It seems to work to some extend but if you want to go tweak it up, kablaaam
i did not managed to boot it up after bootloop sadly, i need my phone so this is it for me this week
stipi69 said:
https://www.dropbox.com/s/d9ie598b618feiz/recovery.log?dl=0
i managed to get somesort of log from twrp in link from previous post will this sufice?
i am reflashing my phone so i can not look at versions, for now i used:
when i reboot it i can look into busybox version
SR3-SuperSU-v2.79-SR3-20170114223742, on top of that i installed pro:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
busyboxpro
https://play.google.com/store/apps/details?id=stericson.busybox.donate
terminal from romtoolbox pro:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
those are some apps i support so i dot know if it makes a diference from non paid
Click to expand...
Click to collapse
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
I did not manage to delete anny apps as my phone crashed before, i am glad you get commands to work.
oh, by the waj roomtoolbox is great as you can make shortcuts of the commands and then you klik it one after another and you get rid of the typing
example (first shortcut command depends of busybox install folder i think)
1.st shortcut "cd /su"
2.nd shortcut "su"
3.rd shortcut "echo 0 > /sys/kernel/security/sony_ric/enable"
4.th shortcut "mount -o rw,remount /system"
that way some people can do this quick and you dont need to remember commands, and you can experiment quicker.
sorry i dont know howto annything else for now
chinmoy32 said:
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
Click to expand...
Click to collapse
stipi69 said:
I did not manage to delete anny apps as my phone crashed before, i am glad you get commands to work.
oh, by the waj roomtoolbox is great as you can make shortcuts of the commands and then you klik it one after another and you get rid of the typing
example (first shortcut command depends of busybox install folder i think)
1.st shortcut "md /su"
2.nd shortcut "su"
3.rd shortcut "echo 0 > /sys/kernel/security/sony_ric/enable"
4.th shortcut "mount -o rw,remount /system"
that way some people can do this quick and you dont need to remember commands, and you can experiment quicker.
sorry i dont know howto annything else for now
Click to expand...
Click to collapse
I just managed to restart my phone successfully after changing the LCD density to 320 [I also use this value since always ]
But then I carefully just deleted 1 single app and booom--- boot loop
PS. i used root explorer to just click mount as R/W and then do anything to system partition --
Great you magaged it, and yes 320 seems so right.
And i asume there is no way to break bootloop?...other than reflashing?
I had trouble afterwards on downgrading to.253, 3x times error on start, even after reseting " power & + " and couple of full wipes in twrp.
I had to flash lineage from twrp and boot it up and only then flashtool succeeded pushing. 253.
This nougat will be fun i see
If there is something to try tell me i will flash it once more tonight, otherways i can do it on weekends
Oh i did not tell, i managed to copy modified thermal files with no error and then changed lcd density so i can not 100% tell which caused bootlop, since i did not reboot in between...
chinmoy32 said:
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
Click to expand...
Click to collapse
there is another way which i did not try because the busybox commands worked for me
its about flashsing updater script
delete_recursive(
"/system/app/GoogleAnalyticsProxy",
"/system/priv-app/GoogleBackupTransport",
"/system/priv-app/textinput-chn-xxhdpi",
);
https://forum.xda-developers.com/showpost.php?p=70920831&postcount=2015
HI , im new here but i know a long time ago about this community, anyway, someone can help me uploading a build.prop of the moto g5 plus, i modify it and well... :/ i try to fix it whit a adb on the command promp but my phone still stuck on the boot, and i sorry about this topic maybe can help on the future
Which model do you have? What build are you on? Are you running a custom ROM?
It would probably be easier to post your build.prop and see if someone will look at it and give you some advice as to what is wrong.
willclein said:
Which model do you have? What build are you on? Are you running a custom ROM?
It would probably be easier to post your build.prop and see if someone will look at it and give you some advice as to what is wrong.
Click to expand...
Click to collapse
Thanks in advance for the reply, i can solve the problem flashing the firmware beacuse i have some troubles on the console using adb, but this happening beacuse i dont give it the correctly permisons, but i want share the way to fix that problem as well, therefore i bring the solution on the command prompt on windows, the solution is very simply but helpfull
step by step, there are been taked on the siteweb TAS beacuse i'm a new user and i cant post url's of the other sites
///
Setup ADB and Fastboot on your PC.
Boot your Android device into TWRP recovery.
Select Mount » and then select System from the list of partitions to mount the system partition and then go back.
Connect your device to the PC with an authentic USB cable.
Open a command window on the PC and issue the following command to pull build.prop file from the device:
adb pull /system/build.prop
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from.
└ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file.
Download and install Notepad++ software on your PC.
Open the build.prop file on your PC using the Notepad++ program.
Edit the build.prop file as per your requirement and save it on the PC after making the changes.
Once you’ve saved the edits to the build.prop file, push it back to the device using the following command:
adb push build.prop /system/
Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
adb shell
cd system
chmod 644 build.prop
Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option.
thanks and i hope this can help someone else
The number one issue I see with people modifying build.prop (myself included) is forgetting to fix the permissions once you are done. My preferred method for editing it is using BuildProp Editor. It makes editing easy as well as makes setting the permissions extremely easy without having to use ADB. Best part is you can do this on the fly instead of having to use your PC.