Database Info

Replaced wrong build.prop and local.prop

I've been stupid enough and replaced my modified build and local.prop files on B310 ROM with the ones I've backed up from my B121SP06 ROM and after I've rebooted the phone it just stays on "Honor, powered by android" logo. Is there some way I can't replace those files with the originals before the intervention ( I have them on my SD card)? I can boot into recovery or in bootloader, also I can flash CWM recovery.

doctorat said:
I've been stupid enough and replaced my modified build and local.prop files on B310 ROM with the ones I've backed up from my B121SP06 ROM and after I've rebooted the phone it just stays on "Honor, powered by android" logo. Is there some way I can't replace those files with the originals before the intervention ( I have them on my SD card)? I can boot into recovery or in bootloader, also I can flash CWM recovery.
Click to expand...
Click to collapse
I had also problems with these two files.
Install cwm on your phone and start your phone in cwm-mode to use adb
in cwm you have to mount system, data and cust
open a command line and use adb as following:
"adb remount"
"adb pull /system/build.prop" --> this will download the build.prop-file to your local folder, where your adb-file is located. At this point you can also download another file like your mentioned backup of the build.prop. for the local.prop-file you have to use: "adb pull /data/cust/prop/local.prop"
When you are ready with changes on the two files or you just want to upload the right ones to your phone back use this command:
"adb push build.prop /system/build.prop" and/or "adb push local.prop /data/cust/prop/local.prop" --> it will copy the file build.prop or local.prop from the local folder, where your adb-file is located to the phone.
After uploading the files to your phone you have to fix permissions:
"adb shell chmod 644 /system/build.prop" and/or "adb shell chmod 644 /data/cust/prop/local.prop"
reboot your phone via cwm.
This is how it worked for me. I hope it will help you too. :fingers-crossed:
By the way, I'm actually looking for a stock local.prop-file for the L04 (from the firmware B109SP1 or B114) or the L12 (from the firmware B118 or B607). Do you have one of these?

Thanks for the reply but I've already succeeded flashing B313. I've been trying with "adb pull" command but it was saying "no device found " or something similar.
My phone is H60-L02 so i don't have the files you're looking for.

[Completed] How can I rename a file via sideload?

In an effort to get a WiFi adapter working I was following instructions on replacing a file called 'linker' in system/bin. Before copying the new linker file you gave I renamed my old one to linker2 because I wanted to be able to revert if needed.
After I renamed linker to linker2 my phone said I didn't have root anymore and I couldn't rename the file back.
I restarted and now am encountering an error that prevents booting. I'm in Android System Recovery with options:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down view
recovery logs
apply update from sdcard
If I select 'apply update via ADB' I can use ADB from my laptop, but seems the only thing I can do is sideload a file. Is it possible for me to sideload and execute a simple script to rename that file back to linker instead of linker2?
Help is greatly appreciated.

I'd be happy to provide payment to someone that's able to help me.

fluidfocus said:
In an effort to get a WiFi adapter working I was following instructions on replacing a file called 'linker' in system/bin. Before copying the new linker file you gave I renamed my old one to linker2 because I wanted to be able to revert if needed.
After I renamed linker to linker2 my phone said I didn't have root anymore and I couldn't rename the file back.
I restarted and now am encountering an error that prevents booting. I'm in Android System Recovery with options:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down view
recovery logs
apply update from sdcard
If I select 'apply update via ADB' I can use ADB from my laptop, but seems the only thing I can do is sideload a file. Is it possible for me to sideload and execute a simple script to rename that file back to linker instead of linker2?
Help is greatly appreciated.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
Please consider posting your question here:
[HELP THREAD] Ask ANY Question. Noob Friendly.
That's a friendly help thread where you'll receive expert advice.
Good luck!

BLU Advance 5.0 HD

It looks to me like the best phone $80 can buy I spent couple hours trying to figure out how to enable Multi User module.
My understanding is that adding this to /system/build.prop would bring users module back:
fw.max_users=3
fw.show_multiuserui=1
None of the commonly used apps can root this phone.
Without root I cannot remount /system to read-write to edit build.prop
Stock recovery can mount /system
There are options in recovery to run update from sd card or to update via adb sideload but the phone does not show in adb devices while in recovery. There is also fastboot option.
I also tried dirty cow exploit but it fails with "only position independent executables (PIE) are supported"
I am into this for only couple hours, so I know I am missing a lot. Any pointers that could get me closer to enabling Users module would be welcome.

So, after some reading, i figured I should be able to apply update form recovery that will replace build.prop with modified one. For start, to test things out, I just want to copy file from update.zip to /system/build.prop.test
I created update.zip with update-script and the file I want to add to /system.
Here is update.zip: www . filedropper.com /update_10
I signed update.zip using this:
www . learn2crack.com /2014/02/sign-android-apk-zip.html
I get error "Signature verification failed". Is the problem that keys are test keys or that they are outdated? Is some special manufacturer key required to sign updates?
I am not looking for someone to do this, I just need to be pointed in the right direction.

I have multiple users now :
- downloaded TWRP from bluroms.info
- connected the phone, enabled USB debugging and OEM unlocking in developer options
- run "adb reboot bootloader"
- after phone booted in fastboot mode
fastboot oem unlock (followed instructions on screen / all data wiped)
fastboot boot blutwrp.img (downloaded TWRP)
- twrp started...
- mounted /system
adb pull /system/build.prop
- edited build.prop
adb push build.prop /system/build.prop
adb reboot
- phone got stuck on logo after reboot
removed battery and started the phone again and all seems good

@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.

mrfunnybone said:
@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.
Click to expand...
Click to collapse
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.

sasha_ said:
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.
Click to expand...
Click to collapse
So is getting root access to system like booting recovery TWRP? then pressing the Mount button and checking System? Sorry I'm a newb at this.

I'd love to gain root on this phone I have twrp installed but can't seem to find a root method that works

Just in case you guys are still watching this, I posted my experience with this phone here
https://forum.xda-developers.com/showpost.php?p=75164672&postcount=26

Samsung health error

Guys I need some help !!
I have official firmware in my phone S7 edge ( Android 7.0 G935F ) but once i tried to root it and it was stuck in boot logo so i went to a store for a suppose unroot ,but know e cant use Samsung health app because gives me an error. I already searched this error and just have to change the tima value to 0 in build.prop
My real question is can I edit build.prop to fix this error without root or do i have to root my device again to fix this error ??
Please help
thanksssss, waiting 4 answers

Your phone KNOX is ticked 0X1 that's why not working, you must root your phone and edit built prob, edit line TIMA=0 and will work

so i have to root it again ?? i have some problems (fear) doing it again because i don't know how to do it right

Or othe way to make it work. But need to be Root. Delete v5 restar install v4. Loging abd update. Done

I would recommend you the recovery mode if you don't want root the phone again. You have full access to system files in recovery mode, but only if it is mounted.*
Many stock recoveries don't have option to mount system partition or don't have adb access for commands. You might want a custom recovery for this. And no, you don't need root for custom recovery. So now all you need to do is, boot into recovery (custom preferred), mount system and then using adb, pull the build.prop file:
adb pull /system/build.prop <path to save file>
Now edit the file you just extracted and save it*
Push it back to your phone via adb
adb push <path to your file> /system/build.prop
You're not done yet. You need to set permissions too. So open she'll via terminal
adb shell
Now from shell, set the right permissions
chmod 644 /system/build.prop
And you're done
Reboot your phone and see the changes

Xperia XZS Root

I have been trying to root my Xperia XZs G8232. BL unlocked successfully, flashed TWRP 3.1.1 successfully, just that it wouldn't boot up. Can someone enlighten me which step I have missed out ? Managed to flash SuperSU 2.8.2 and Magisk 19 via TWRP recovery. The phone still wouldn't boot up....
Can anyone share proper comprehensive guide of rooting of G8232 ?

Usually when I offer an answer, the reply is something along the lines of "I found an answer already."
This is a quick guide in case you haven't. I suggest you have a micro-sd card inserted.
First, the stock image you are rooting is signed and verification is still active on the device. You will need to resign the boot.img. I suggest you worry about that after performing a boot into recovery to get ahold of the boot.img. Second, the TWRP you are using really isn't an ideal version. You can safely install this to the recovery parition for rooting and backup too even though it was built for the XZ (chip instruction set and partition table are near identical, it works safely with Keyaki). Go ahead and install the recovery, then once you boot into it comes the somewhat more technical approach.
You need to first mount system and the micro-sd card, by tapping Mount on the main menu and then by checking off System and Micro-SD so they can be accessed (loaded/mounted/whateveryouwannacallit). Now, go back to the main menu and tap Advanced and tap Terminal. From here you will need to copy the boot.img which can be achieved by typing:
dd if=/dev/block/by-name/boot of=sdcard1/boot.sin
You may have to search through the /dev/block directory a bit further, as I cannot recall if it is nested under platform/some number junk/etc... You can safely navigate through the directories with: cd or maybe find -name boot 2> /dev/null until you find the directory by-name that has the partitions you need and fill that path into the dd if= path I presented above. Just make sure the if (input file) is the directory you wish to copy and the of (output file) is where you want it to go.
Once you have successfully copied the boot partition (kernel) to an sd-card you can go ahead and run this tool to unsign it , from my experience you will also need to repack and sign it as AOSP with this to get the stock kernel and system running with root access available.
Both tools work similarly, read through the guides where you download each.
You will need to extract AIK and place the boot.img into the first directory that has the scripts with it. Simply type/choose ./unpackimg.sh and when that completes, choose ./repackimg.sh (depending on which OS you use the commands might be somewhat different, but the above suggestions should guide you through it). You should receive a prompt stating it was completed and packed/signed for AOSP. Copy or cut the new-Image.img out of the AIK directory back to the root directory of your sd-card.
Boot into TWRP (or maybe you attempted this with the mobile version through TWRP, idk?). Select Install, tap install .img (bottom right) and tap the new-Image.img you just created and flash it to boot.
From here you can go ahead and reboot and you should be able to access the stock system with your rooted boot.img. BTW, you don't need Magisk v19. You can install the 25.2 app and patch the new-Image through the app and then repeat the previous step above to have your kernel rooted with the latest Magisk.