Looking for a little help here.
In an effort to make some tweaks on my HDX, I somehow managed to delete the actual build.prop while I was in the process of trying to restore from a backup (build.prop.bak). I've tried removing build.prop.bak to build.prop, however Root Explorer keeps telling me that the Renaming Action has Failed.
I'm struggling to get my device to load/recognize on my PC with ADB. I'm looking for solutions to prevent my device from bricking.
Does anyone know if it would be possible to use the "Rollback" method from 4.5.3 to 3.2.8; or will not having a proper build.prop interfere with that?
The most aggravating thing, is I have a fully functioning build.prop backup, I just can't seem to get it to take as the actual build.prop
Any ideas are much appreciated
positivehxcgo said:
Looking for a little help here.
In an effort to make some tweaks on my HDX, I somehow managed to delete the actual build.prop while I was in the process of trying to restore from a backup (build.prop.bak). I've tried removing build.prop.bak to build.prop, however Root Explorer keeps telling me that the Renaming Action has Failed.
I'm struggling to get my device to load/recognize on my PC with ADB. I'm looking for solutions to prevent my device from bricking.
Does anyone know if it would be possible to use the "Rollback" method from 4.5.3 to 3.2.8; or will not having a proper build.prop interfere with that?
The most aggravating thing, is I have a fully functioning build.prop backup, I just can't seem to get it to take as the actual build.prop
Any ideas are much appreciated
Click to expand...
Click to collapse
Sounds like you are on 4.5.3 but lost root. Might try to reroot using Kingroot although I believe that involves a reboot. Pretty sure your device will not restart (effectively brick) without build.prop. You really need to get adb working to expand beyond those options. Keep your device on charge to prevent a shutdown due to low battery.
I absolutely would not attempt a 3.2.8 rollback. There is an outside chance a factory reset from stock recovery would restore a generic build.prop if none is found. It generally will not repair or replace a damaged file and involves a reboot which could be fatal. This becomes an last resort option imo.
If you device was purchased from Amazon it may still be under warranty. Sometimes that is the best/only path. Good luck.
I've managed to get it mounted as ADB, and have pulled the backup, and renamed the file.
I'm now running into a problem pushing the file to /system/ I'm going to assume it's because I've lost my root access (I'm guessing it's because the buildprop manages it?).
So Making advances, just now stuck here. I've tried editing the prop, and it's in read only. I've tried sending it to a different folder and copying it over, but that's also failing.
positivehxcgo said:
I've managed to get it mounted as ADB, and have pulled the backup, and renamed the file.
I'm now running into a problem pushing the file to /system/ I'm going to assume it's because I've lost my root access (I'm guessing it's because the buildprop manages it?).
So Making advances, just now stuck here. I've tried editing the prop, and it's in read only. I've tried sending it to a different folder and copying it over, but that's also failing.
Click to expand...
Click to collapse
You will probably need to root via adb which is challenging and by no means certain. Take a look at this thread for ideas. You may want to reach out to @myotai as he faced a similar problem.
Related
Hi,
I cannot edit /default.prop after update.
To be more accurate, I can edit it, but after reboot it is the way it was before.
I have root, any idea what is happening?
CORRECTION it's 2.3.4
Could be a couple of things,
1. I've read a post on here before about a phone that couldn't be flashed with different firmware at all, possibly due to corrupted nand memory.. Hopefully yours isn't
2. How are you editing the file, are you using something like root explorer or copying the file onto pc then trying to push / paste it back to the phone, because either way you have to make sure you have write access to the system and file.
Hope you get it sussed
Sent via courier pigeon
Thanks for the reply, morg01.
I used for editing a pack of tools, first "super manager" to mount "/" as RW then either "script manager" to edit the file, or Terminal Emulator to add the needed line.
So far I've only found a workaround for the problem, by using ADW launcher, instead of original one. But even though it is very rich in options I prefer the TouchWiz. ADW is kind of lagging I have no idea why
What exactly is nand memory, and how could it get corrupted. I've experienced some problems lately, with a slight pressing of the back cover or if it is removed on the upper end of the battery the phone reboots.
Is it possible to be more than just a battery problem?
Hi there,
I upgraded my Galaxy 551 to Gingerbread 2.3.6. All went well. Unfortunately it seems to be a common side effect that the Z and Y keys (and some others) get swapped. The fix is apparently to modify the file /system/usr/keychars/sec_keypad.kcm.bin. The ideal thing is to put the old file from before the FW update back in, but of course I don't have that anymore! But the existing one can apparently be altered. If I can copy it to the SD card I can alter it in a hex editor and put it back.
So, I rooted my phone with that one click application, and that went OK too. I installed root explorer and found the file. There were also some others in the same folder I may be able to use. But, I cant make the folder R/W (pressing the button does nothing) so cant do anything with the file. I also tried Super Manager with no luck.
I am new to the phone fiddling stuff so noob level instructions would be appreciated!
Think I have it sorted. I installed superuser and then Root Explorer allowed me to select read/write. Now to try sort out this file!
OK, seems that you need to edit the file /system/usr/keylayout/sec_keypad.kl. Did that. DO'H now my keyboard doesn't work at all! Glad it saved a backup for me! Not sure what I did wrong, only edited two characters in a text file! Even the power button doesn't work. Got to pull that battery out LOL!
It seems when the file was saved it was saved with zero size. When I try to delete it to replace it with the backup it says cant delete, read only. So, not sure how I am meant to replace this and fix this problem.
Any ideas, remembering that I cant actually use any buttons on the phone!
I asked this in the general Q&A thread because I feel it is an android issue, not a Note issue...but alas no one even replied, trying it out here. Please help!
RockZors said:
Hello all,
I have a Samsung Galaxy Note i717. I have installed a few ROM's, but recently I installed CM9 unofficial build. After it was installed, I noticed that my default.prop is only like 4 lines long. So I try and add stuff to it (I am rooted, and used RW mode in Root Explorer). I can close the file and save changes successfully, but when I reboot it is back to the way it was with the 4 lines. It is not only that though, any files i add to the "/" get deleted upon reboot.
Things I have tried:
ODIN to stock rom, still did not have a full default.prop
Tried many different ways to change file system (different programs)
Ran fix permissions in CWM and busybox installer script
All with no success. Is there anything else I can try to fix this and be able to edit my "/" and have changes take affect. Or has anyone had this issue before?
Thanks
Click to expand...
Click to collapse
I was wondering if anyone with an i717 could go into cwm, run a backup, and upload that somewhere so I can restore it. Keep in mind your personal data gets backed up also, so preferably someone with a fresh working install. I don't care what rom it is either.
Thanks for reading.
The default.prop should only be 4 lines..
Are you confusing it with the build.prop?
Wow well don't I feel stupid. That's exactly what it was. Thanks for helping me see the way!
You can fix the extsd write lock by using root explorer navigating to etc\platform\permissions.xml
You need to mount as RW and edit the file to match what I'm pasting below.
You can ignore the middle part about syscope info but change your permissions for "write_external_storage" the "access_all_external_storage" and the "write_external_storage"
Don't delete anything from the file or do this without paying attention. Do not alert the syscope permission in between the 2nd and 3rd permissions that relate to storage.
I found this method through Google but it's worked for me so fast with no problems. If you use root explorer and open the file in text editor when you save the modified file, the original file will have .bak appended to it. The guide I used only changed 2 of the 3 permissions I'm saying to edit but the sd lock fix went away after restarting but since I changed the permissions to what I changed below is been working gray even after restarting.
Remember be careful with how you edit the file, only change it in the places I showed to make sure there aren't any complications. If you type it manually make sure to match the formatting and symbols exactly. If you ate going to cut/paste make sure only to change the permissions to exactly how I show it.
I'm not responsible for any damage or issues caused by following this method incorrectly. Remember to save the file with the original name of permissions.xml and then restart the phone to check your now writable ext sd card.
Much easier to use "SDFix: KitKat Writable MicroSD":
https://play.google.com/store/apps/details?id=nextapp.sdfix
Rodger
I haven't tried that one but I've used the xposed framework app that is supposed to enable extsd write but it didn't seem to work properly for me or was at best unreliable when I tried it. I like knowing what patches or fixes are doing behind the scenes in case I need to change them or if there's a problem or an update and it stops working you can do it yourself especially when its add easy as copy and paste
rbird2 said:
Much easier to use "SDFix: KitKat Writable MicroSD":
https://play.google.com/store/apps/details?id=nextapp.sdfix
Rodger
Click to expand...
Click to collapse
This one hasn't worked for me very much on a few ROMs but I did have a little better luck using the Xposed module mentioned above.
Many thanks for the post, OP. I'll add that to my notes and try it on the next ROM that gives me write issues.
Awesome glad to be able to help. .. when I first upgrades yo NG6 I couldn't believe Google could screw up one of the best features in android phones compared to the iphone. At least we're able to workaround it in the current versions at least fornow
nj12nets said:
Awesome glad to be able to help. .. when I first upgrades yo NG6 I couldn't believe Google could screw up one of the best features in android phones compared to the iphone. At least we're able to workaround it in the current versions at least fornow
Click to expand...
Click to collapse
People wonder why Google apps which work fine are still considered "beta." It's because Google isn't done with something until they screw it up completely, preferably also changing the UI a zillion times so it's unusable on more than one level.
rbird2 said:
Much easier to use "SDFix: KitKat Writable MicroSD":
https://play.google.com/store/apps/details?id=nextapp.sdfix
Rodger
Click to expand...
Click to collapse
This one as well...
https://play.google.com/store/apps/details?id=jrummy.sdfix
Thanks for adding the app add an option but can you give an idea of how well or functions and its reliability
I just rooted my phone a few days ago. My phone decided to upgrade to NG6 by itself and it crippled the SD card almost completely. I had some work arounds, but this just made it so much harder. I downgraded to NC5, had a problem, did a full reset and redid my phone. Did Towelroot V3, SuperSU, turned SDM.apk and FWUpgrade.apk into backups. Then I did the SDFix app, rebooted and now the SD card works like it did with MK2. I'm very pleased.
Hi There
I have been a long time Hacker of largely MTK devices. So I wanted to ask a question and see if there's anything I am missing here:
I have an Android 8.1 device, I have rooted it using Magisk no problem and I have successfully changed the bootanimation.zip and also the audio files. I have been able to release the rooted OS, get the OS back to a released state with the changes as I have simply kept the removed dm-verity flags that Magisk uses on the OS.
However, I am unable to change the build.prop at all.
If I copy the build.prop file from the device, edit it on the PC, and save it back it bootloops. If I edit it, roll back all the changes and re-copy it back to the device it is fine.
I noticed the original build.prop permissions are RW (Chmod 600). I tested the above chmodding to 600 and 644 and it makes no difference. If it has changes in it, it fails, if not it works!
So something somewhere is maybe checking the build.prop against an original and not liking it.
Is there anyone on here that could help shed some light on this at all?
Bump...Anyone?
So an update to this is that I have now successfully removed DM-Verity from this device. I have also managed this on many other devices. I prove this by installing all kinds of changes on the device.
So I can pretty much do anything with this device, almost like pre-Android 5.1, however whenever I edit the build.prop at all it bootloops.
What I have tried so far:
I have tried all kinds of permissions on the file
I have duplicated the /vendor/build.prop in an attempt to get round possible build.prop variety issue.
I have removed the /vendor/build.prop
I have replaced system/prop with original build.prop but still edited (and changed back) from my PC and the device boots OK.
So it looks like somethiung is looking up the build.prop file and checking something. Almost like a DM-verity for the build.prop.
Really out of ideas now. i can literally unlock/change anything MTK now except for this issue.
Any help is much appreciated.
Oh i forgot to mention, this is a systemless and not TREBLE OS.
I usually change /system/build.prop and have never had an issue up through Android 10. I know this is elementary and no intention to offend anyone - but are you sure the file is being saved with unix-style line endings.
File-permission must be set to 644.