Edit build.prop without root. - Android Q&A, Help & Troubleshooting

Is there a way to make an update.zip file that changes the build.prop file that I can flash using stock recovery with adb? I currently can't find a way to root my device for now.

Uttiya Dutta said:
Is there a way to make an update.zip file that changes the build.prop file that I can flash using stock recovery with adb? I currently can't find a way to root my device for now.
Click to expand...
Click to collapse
Edit:I got twrp now.

Related

Simple fix for Wifi error

For anyone who flashed a kernel or ROM and broke Wifi, this fix worked for me. You will need Root Explorer or some other file manager that can R/W /system/. Go into /system/lib/modules and delete bcm4330.ko. Grab the attached bcm4330.zip, extract the .ko file, copy it over to your phone, then use Root Explorer to drop it into /system/lib/modules. Finally, reboot.
Brought my wifi back after flashing Ziggy's kernel using Con247's easy kernel flash method and losing wifi.
bast525 said:
For anyone who flashed a kernel or ROM and broke Wifi, this fix worked for me. You will need Root Explorer or some other file manager that can R/W /system/. Go into /system/lib/modules and delete bcm4330.ko. Grab the attached bcm4330.zip, extract the .ko file, copy it over to your phone, then use Root Explorer to drop it into /system/lib/modules. Finally, reboot.
Brought my wifi back after flashing Ziggy's kernel using Con247's easy kernel flash method and losing wifi.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20990402&postcount=2
Download the non PH98IMG.zip in that post and flash it in recovery. Does the same thing but is automated.
hi,
cant find the zip data. can you upload it? or the file directly. Please
and hope it works for me too
Bessani said:
hi,
cant find the zip data. can you upload it? or the file directly. Please
and hope it works for me too
Click to expand...
Click to collapse
why don't you try looking in the zip for the rom that you use
wifi
con247 said:
http://forum.xda-developers.com/showpost.php?p=20990402&postcount=2
Download the non PH98IMG.zip in that post and flash it in recovery. Does the same thing but is automated.
Click to expand...
Click to collapse
wow am I glad to stumble on this. I flashed cleanrom 4.5 in June and lost Wifi and have been told to flash this same file. I have it on my sd but can't for the life of me get it to load. Can you please provide some step by step so i can see what i'm missing. thanks so much.
What do you mean by "attached .bcm4330.zip", I can't find this file. Was there a file previously attached to this post? If so could someone supply it please
Thanks in advance. :good:
FINIZLE said:
What do you mean by "attached .bcm4330.zip", I can't find this file. Was there a file previously attached to this post? If so could someone supply it please
Thanks in advance. :good:
Click to expand...
Click to collapse
+1

[Q] Upgrading to ICS including other tweaks

Hi,
I'm kinda new to flashing and upgrading my phone.
Therefore I got some questions:
Currently running on my Neo: AOSP 4.0.3 ICS BETA with kernel provided there
Baseband says: 56 as last two digits
I would like to upgrade my baseband to 62. (latest)?
As far as I understood I will have to flash 4.0.2.A.0.62 Baseband using flashtool.
Do I have to flash the kernel again after upgrading baseband or should I flash the 4.0.2.A.0.62 Kernel first and change it afterwards?
fastboot flash boot boot.img
Click to expand...
Click to collapse
Will changing the baseband or kernel delete anything?
When would be the right time to apply the RAISE your NEO userdata space patch? Before or after baseband, kernel flash?
Sometimes they say that a reboot is required after flashing a new ROM before flashing an update.zip in CWM. Do I have to reboot at other times?
Is there a tool or a possibility I missed which can flash anything like baseband, kernel, ROM and updates to it in one step?
If I want to edit a ROM like directly changing bootanimation and ringtones.
How should the zip file be packed? No compression, etc?
Is it a good idea to include updates which I would have flashed in CWM directly into the ROMs zip file?
Do I have to flash the kernel again after upgrading baseband or should I flash the 4.0.2.A.0.62 Kernel first and change it afterwards?
Click to expand...
Click to collapse
Kernel is not related to baseband. Simply flash baseband, no need to flash kernel after or before.
Will changing the baseband or kernel delete anything?
Click to expand...
Click to collapse
Flashing baseband won't delete anything, but flashing kernel might. I see that kernel in that thread have CWM inside, so if you flash stock kernel you will lose that.
When would be the right time to apply the RAISE your NEO userdata space patch? Before or after baseband, kernel flash?
Click to expand...
Click to collapse
Whenever you want. It's not related to kernel or baseband.
Sometimes they say that a reboot is required after flashing a new ROM before flashing an update.zip in CWM. Do I have to reboot at other times?
Click to expand...
Click to collapse
Yes, they say that so that ROM "settles down in it's place" then you can install fixes and stuff.
What other times?
Is there a tool or a possibility I missed which can flash anything like baseband, kernel, ROM and updates to it in one step?
Click to expand...
Click to collapse
There is flashtool, but only for stock rom's. Custom roms are installed as a .zip file via CWM recovery.
If I want to edit a ROM like directly changing bootanimation and ringtones.
Click to expand...
Click to collapse
You can do that with root explorer app(or any app which can access to system), create that bootanimation.zip on pc and upload it to sdcard, then move it to where it needs to be. For bootanimation.zip, yes, it's with no compression. How it's created, check other bootanimation.zip's over the net.
For other zip's which are flashed trough CWM, it's a bit more complicated to explain how to create them.
Is it a good idea to include updates which I would have flashed in CWM directly into the ROMs zip file?
Click to expand...
Click to collapse
Well depends. Most likely yes, but I would still ask creator/porter of each rom if that is advisable
Madfysh said:
seXneo said:
If I want to edit a ROM like directly changing bootanimation and ringtones.
How should the zip file be packed? No compression, etc?
Click to expand...
Click to collapse
You can do that with root explorer app(or any app which can access to system), create that bootanimation.zip on pc and upload it to sdcard, then move it to where it needs to be. For bootanimation.zip, yes, it's with no compression. How it's created, check other bootanimation.zip's over the net.
For other zip's which are flashed trough CWM, it's a bit more complicated to explain how to create them.
Click to expand...
Click to collapse
Thank you very much.
But in this point there was a misunderstanding.
I just wanted to know how the update.zip or rom.zip has to be packed and if it's save to replace bootanimation.zip inside rom.zip. Are there any checksums for apk or other files inside an CWM update.zip I need to change?
Most of the ICS based ROMs use MT15i_Neo_ICS_Kernel_V1.img. Where does it come from and where is it's original thread?
if it's save to replace bootanimation.zip inside rom.zip. Are there any checksums for apk or other files inside an CWM update.zip I need to change?
its safe to change bootanimations.zip and any other apk or file in side the provided update.zip file
but if u extract it n do changes then u will lose the signature of the developer n wont b able to install the update.zip properly
chintu1234 said:
its safe to change bootanimations.zip and any other apk or file in side the provided update.zip file
but if u extract it n do changes then u will lose the signature of the developer n wont b able to install the update.zip properly
Click to expand...
Click to collapse
Yes of course. If original zip file flashed and runs nice it will be my fault if it won't after my edits.
So no checksums in the update.zip directly. Thanks.
Signing of an altered apk file is required. Got it.
And I figured that there is no signing of the bootanimation possible.
Will post my question regarding the kernel in an extra thread.

Obtaining root by modifying default.prop(ro.secure)?

To get a privileged shell you need to modify the following lines to the given values in the default.prop file
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
Click to expand...
Click to collapse
I have the extracted the recovery image of my phone model : So is it possible to modify the following values in the default.prop file, repack the image and flash it using fastboot(bootloader is unlocked) to get a privileged shell, and then copy the su binary after remounting system as read/write?
Do I need to change any other values in any of the files? And will it work, theoretically at least?
What are the chances of it messing up anything?
[I posted this on android.stackexchange but not much activity there]
No chances of bricking at all
Going further I would suggest you to tag in a shell script within init.rc so that it copies superuser apk and binary automatically as you boot
That's great
And is there any way to confirm that the recovery (downloaded) that I have is indeed from my device? Is the data within the prop files such as build and model no. etc enough?
Sent from my A9 using xda app-developers app
It didn't work. Either it wasn't the stock recovery in the first place, or the process isn't that easy. This can be closed now.
Modify boot.img
I think it is only the boot.img which is to be flashed. You don't need to flash recovery as whole.
If you have root access, you could manually edit default.prop. But, the modifications exist only till reboot. Once you reboot, boot.img will reload all the necessary system files to original. So, edit boot.img.
Adriel David said:
Hello I want to modify default.prop to modify it I need root access now I rooted my phone and cwm installed I want to make a flashable zip backup of default.prop can you provide me the script to be flashed by cwm because I am afraid bricking my phone
Click to expand...
Click to collapse
default.prop is on ramdisk or initrd which is part of the boot.img.
I use abootimg to edit boot, some use mkbootimg. Google editing initrd will give you info you need
varun.chitre15 said:
No chances of bricking at all
Going further I would suggest you to tag in a shell script within init.rc so that it copies superuser apk and binary automatically as you boot
Click to expand...
Click to collapse
Sorry to call on such an old post, but wouldnt this mean that on each boot (if modified on boot.img. On each fireup of recovery if on recovery.img) the superuser apk and binaries are reinstalled? Because this /is/ init.rc we're referring to. Please correct me if I am wrong, and also tell me if this is the best way to go about it I'm trying to come up with a way to root my device without using dirtycow haha

Stock My Files

Hello guys. In some custom roms My Files option removed. If anyone want to get back this stock My Files then how I can get back, even with ported My File with cwm or in other way....?
I suppose you would be able to extract it yourself by installing a stock ROM and then copying the APK from /system/app (using some root capable file manager).
At least if nobody else has an easier solution for you.
Good luck!
b9AcE said:
I suppose you would be able to extract it yourself by installing a stock ROM and then copying the APK from /system/app (using some root capable file manager).
At least if nobody else has an easier solution for you.
Good luck!
Click to expand...
Click to collapse
i checked.. there is no my files.apk in system/app. Still i have My files option in my current rom.
mrjoy said:
Hello guys. In some custom roms My Files option removed. If anyone want to get back this stock My Files then how I can get back, even with ported My File with cwm or in other way....?
Click to expand...
Click to collapse
Here you go..MyFile.apk if you are on JB..
Flash it in CWM
zoot1 said:
Here you go..MyFile.apk if you are on JB..
Flash it in CWM
Click to expand...
Click to collapse
up plz

Tweaking system file permissions via TWRP possible?

Is it possible to edit file permissions of voltage_max file located in sys/class/power_supply/battery via TWRP? In TWRP's File Manager I can only get to battery and no further. It's seemingly shown as a file instead of a folder.
And more importantly if its possible will the tweaked file permissions stick after booting into the ROM? I know with root access it's easy just wanted to know if via recovery it can be accomplished w/o root or not?
Thanks.
Bump.
Anyone?

Categories

Resources