Hello guys, sup?
Well im looking for a solution (if it has) about build.prop editing with adb and the conditions for it is:
-no root (obviously since moto one vision does not have it yet)
-no recovery mode installed (obviously since moto one vision does not have it yet)
actually im trying command
adb pull
C:\adb> adb pull /system/build.prop c:\adb\new and i get adb: error: failed to copy '/system/build.prop' to 'c:\adb\new\build.prop': remote open failed: Permission denied
the intention is to edit build.prop with notepad++ and push build.prop back
tried looking into tutorials around web but no sucess , any help is welcome . :fingers-crossed:
No possibility yet, maybe try edit system.img and flash it
Related
Hello Forum!
So i am currently using a Virgin Mobile LG Optimus Elite.
After 2 days of refuge here on the forums i amazingly found a small little program that was intended to root p500 devices and worked for mine.
I did run root checker and all plus i have root access so it is rooted.
My problem is,
1.) I cannot edit my build.prop
2.) Install Xbox Smartglass (which is the whole reason i'm killing myself for all this right now)
I'm running 2.3.7 gingerbread, and the smartglass app requires 4.0 and up.
I am certain this phone can run the app.
From the very beginning i tried to take the easy path out by manually downloading the .apk from an outside source but when i try to install it
i get an error stating that it had a problem "parsing" the info.
Running my little research i found you could edit the build.prop file to make the play store think you were running another device that was compatible. Then realizing my device must be rooted first, began my 2 days long journey to root the stubborn thing.
After root success, I installed ES File Explorer. From there, i went to my build.prop, proceeded to edit it with the ES text editor. Re-wrote the 2 lines required then when i went to save, "Error occurred when trying to save the file. It will not be saved." And just left me hanging after that.
In a quick desperate attempt, i found QtADB, which i thought would allow me to edit the system files. It only allowed me access to a hand full of the root directories. I downloaded the newest android dev kit (obviously you need it to run QtADB) so i don't know what exactly the problem here is.
For my absolute last desperate attempt i decided to do it manually. I took the build.prop and edited it manually through wordpad. (NOTE: i backed up the original) I named it "copy.build.prop" and placed it back in an easy to find directory. I then opened up ES file explorer, located the file and tried to copy it to the original location but no matter what i name it or what i do in general it will not move. It keeps failing and just telling me the file cannot be moved.
I am at my last legs with this to the point where i may just give up.
I dont know what to do and was hoping someone on here would.
If there was another way to install the app? If i could install it manually? Something to get me around all these utterly frustrating and annoying errors. I've ran from error to error, fixing it then coming to another. And at this point i just dont know what to do.
The help and replies would be much appreciated! Thanks in advanced!
The build.prop file is located in the /system partition, which is by default mounted as read-only (and for good reason).
Here are some simple steps to modifying the build.prop file.
1) Fire up an ADB shell ("adb shell" from a command prompt without quotes)
2) Within the ADB shell, execute "mount -o rw,remount /system /system" without quotes. This will remount your /system partition in read-write mode
3) Open a new command prompt and CD to an easily accessible directory (e.g "cd ~/Desktop" if on a Linux box)
4) Execute "adb pull /system/build.prop" without quotes
5) Edit the build.prop file as needed with a good text editor (DO NOT use Wordpad or Notepad, I prefer Notepad++ on Windows and Geany on Linux)
6) Execute "adb push /path/to/your/edited/build.prop /system/build.prop" without quotes. This will copy your modified build.prop back into the /system partition
7) In the ADB shell prompt, execute "mount -o ro,remount /system /system" without quotes. This will remount your /system partition read-only (never leave it read-write that is bad)
8) Reboot your phone
9) Profit!
As far as the Smartglass app goes, there is likely a good reason it requires ICS and above, and simply modifying your build.prop may not be enough. Don't take my word for it though, try the above steps and see what happens.
Cheers!
drewwalton19216801 said:
The build.prop file is located in the /system partition, which is by default mounted as read-only (and for good reason).
Here are some simple steps to modifying the build.prop file.
1) Fire up an ADB shell ("adb shell" from a command prompt without quotes)
2) Within the ADB shell, execute "mount -o rw,remount /system /system" without quotes. This will remount your /system partition in read-write mode
3) Open a new command prompt and CD to an easily accessible directory (e.g "cd ~/Desktop" if on a Linux box)
4) Execute "adb pull /system/build.prop" without quotes
5) Edit the build.prop file as needed with a good text editor (DO NOT use Wordpad or Notepad, I prefer Notepad++ on Windows and Geany on Linux)
6) Execute "adb push /path/to/your/edited/build.prop /system/build.prop" without quotes. This will copy your modified build.prop back into the /system partition
7) In the ADB shell prompt, execute "mount -o ro,remount /system /system" without quotes. This will remount your /system partition read-only (never leave it read-write that is bad)
8) Reboot your phone
9) Profit!
As far as the Smartglass app goes, there is likely a good reason it requires ICS and above, and simply modifying your build.prop may not be enough. Don't take my word for it though, try the above steps and see what happens.
Cheers!
Click to expand...
Click to collapse
I'm having problems setting a custom directory now... im on a windows 7 pc. I'm using the Qtabd shell, and at first it stated to give the CD a home, i've tried a million combinations and i just cant get one to work!!!
Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans
skatehans said:
Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans
Click to expand...
Click to collapse
If you can get root on ADB then just install SuperSU app and its binaries and you are good to go.
Flashing the attached ZIP will install SuperSU app and everything it requires to function.
NOTE: You probably need a custom recovery because the zip isn't signed.
Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?
skatehans said:
Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?
Click to expand...
Click to collapse
You should be able to flash it via fastboot.
Thats the next Problem. I cant boot into fastboot mode. When i execute "adb reboot bootloader" or "adb reboot download" the device boots up like normal, so i guess fastboot is not available on this device.
Do you know any other way?
Hi to everyone,
after two weeks I wrecked my Alcatel Tablet (Telekom Puls).
The Android system recovery 3e offers me among others:
apply update from ADB, sdcard or cache
Root and USB-Debugging are activated.
After starting >adb device< on my windows 7 (USB) I get a correct answer.
The copied file build.porp misses the file permissions I assume.
Any hints and suggestions are welcome.
Thanks in advance.
rfine said:
Hi to everyone,
after two weeks I wrecked my Alcatel Tablet (Telekom Puls).
The Android system recovery 3e offers me among others:
apply update from ADB, sdcard or cache
Root and USB-Debugging are activated.
After starting >adb device< on my windows 7 (USB) I get a correct answer.
The copied file build.porp misses the file permissions I assume.
Any hints and suggestions are welcome.
Thanks in advance.
Click to expand...
Click to collapse
Hello,
If there is a permission issue, You may push your build.prop and give it correct permissions according to these commands.
Code:
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb reboot
-Vatsal
adb sideload
Thank you for your post, Vatsal.
Before I start the adb prompt on the pc the following message I get from the tablet:
Now send the package you want to apply to the device with adb sideload <filename> ...
Can someone who has an Essential Phone (PH-1) upload a zip of the system dump. Run the command below in ADB to pull the dump (no root required):
Code:
adb pull /system PH1_system_dump
The dump will be pulled to a folder called "PH1_system_dump". Zip and upload that folder so we can begin development on this device.
I just tried...it stopped at 18% with the following message:
adb: error: failed to copy '/system/vendor/firmware/msadp' to 'PH1_system_dump/system/vendor/firmware/msadp': remote open failed: Permission denied
cabegol said:
I just tried...it stopped at 18% with the following message:
adb: error: failed to copy '/system/vendor/firmware/msadp' to 'PH1_system_dump/system/vendor/firmware/msadp': remote open failed: Permission denied
Click to expand...
Click to collapse
Try to pull like this:
Code:
adb pull /system/app PH1_system_apps
Code:
adb pull /system/priv-app PH1_system_priv_app
Code:
adb pull /system/framework PH1_system_framework
Code:
adb pull /system/media PH1_system_media
Code:
adb pull /system/etc PH1_system_dump_etc
Shawn5162 said:
Try to pull like this:
Code:
adb pull /system/app PH1_system_apps
Code:
adb pull /system/priv-app PH1_system_priv_app
Code:
adb pull /system/framework PH1_system_framework
Code:
adb pull /system/media PH1_system_media
Code:
adb pull /system/etc PH1_system_dump_etc
Click to expand...
Click to collapse
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure:
Code:
adb: error: cannot create 'PH1_system_etc\firmware\TFA9891.cnt': No such file or directory
I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Code:
adb: error: failed to copy '/system/etc/firmware/wlan/qca_cld/wlan_mac.bin' to 'C:\Users\bmg10\Documents\dump\etc\firmware\wlan\qca_cld\wlan_mac.bin': open failed: Permission denied
DOWNLOAD
bmg1001 said:
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure:
Code:
adb: error: cannot create 'PH1_system_etc\firmware\TFA9891.cnt': No such file or directory
I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Code:
adb: error: failed to copy '/system/etc/firmware/wlan/qca_cld/wlan_mac.bin' to 'C:\Users\bmg10\Documents\dump\etc\firmware\wlan\qca_cld\wlan_mac.bin': open failed: Permission denied
DOWNLOAD
Click to expand...
Click to collapse
Without root and factory images, I think this is the best we'll be able to get via ADB. This should be enough for a starting point though. Thanks for your help
Shawn5162 said:
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure: I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Without root and factory images, I think this is the best we'll be able to get via ADB. This should be enough for a starting point though. Thanks for your help
Click to expand...
Click to collapse
Someone in this thread managed to get the boot.img. I downloaded it and tried rooting it with Magisk but it didn't work. He already has TWRP and Lineage but they're still unreleased as its being worked on. I can't try the boot image anymore since I'm on the newest update and the image posted was for the previous update.
https://forum.xda-developers.com/essential-phone/help/bootloader-root-t3695583/page3
You need root to get actual dumps. Our TWRP is still only usable via adb since they're loading touchscreen firmware in userspace via a daemon that doesn't want to run without the rest of android up, otherwise we'd have released something.
We have dumps of the latest OTA (NMJ20D) already. If anyone is interested in contributing or following development of this device (TWRP/Lineage/etc) here's a link to our discord: https://discord.gg/DTtY2nb
Look on the post below the guy already pulled the zip file already. I pushed it to my device via adb.
invisiblek said:
You need root to get actual dumps. Our TWRP is still only usable via adb since they're loading touchscreen firmware in userspace via a daemon that doesn't want to run without the rest of android up, otherwise we'd have released something.
We have dumps of the latest OTA (NMJ20D) already. If anyone is interested in contributing or following development of this device (TWRP/Lineage/etc) here's a link to our discord: https://discord.gg/DTtY2nb
Click to expand...
Click to collapse
is the touchscreen daemon the last piece of the TWRP puzzle? Can it be manipulated with vol + - and power buttons?
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