[HOW-TO] - Enable GSM phone calls on your S-OFF Flyer :) - HTC Flyer, EVO View 4G

Prerequisite:
1) 3G Flyer
2) S-Off (get yours from Alpharev soon!)
3) Root
Using root explorer or your favorite text editor edit the build.prop file under /system/build.prop and edit the following lines:
Code:
ro.ril.reject.cs.ss.enabled=0
ro.ril.reject.mo.ussd.enabled=0
ro.phone.function=1
To enable Bt Headset profile change the following:
Code:
ro.bt.profiles = 4270403
service.brcm.bt.ag_supported = 1
Save your changes and reboot your device. Look under the programs menu you will see the phone app you will now be able to make and receive calls.
Tested on a 3G UK unlocked flyer using an AT&T SIM.
EDIT: now with full BT support!!
Enjoy!

Aha, i was just looking for that, awesome, thanks!

Now someone please find out to enable the FULL market for us. Changing simply the fingerprint does not work!

Updated post to include full BT support!

Hello clubtech,
Can this be done with just temp-root? Since /system/build.prop is the only file we need to edit.
Thanks.

Nope. I tried it and it didn't catch. must be S-off.

Just out of curiosity, would a modification of this work on the view? I realize that our plans don't include it but it would be nice to mess with.
Sent from my SPH-D700 using XDA App

kokyew said:
Hello clubtech,
Can this be done with just temp-root? Since /system/build.prop is the only file we need to edit.
Thanks.
Click to expand...
Click to collapse
This is unlikely because the changes made in the said config file:
1. Cannot be saved and
2. When you reboot, root is lost.
S-Off is what we now need. Indeed, fingers crossed.

contradude said:
Just out of curiosity, would a modification of this work on the view? I realize that our plans don't include it but it would be nice to mess with.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I am sure that BT part would work the View,a s for call - it might.

works but a little delayed but great find

with temp root:
adb shell cat /system/build.prop > /data/build.prop
adb pull /data/build.prop
open pulled build.prop with notepad++ or whatever text editor you like, make changes suggested by OP. save file
adb push build.prop /data/build.prop
reboot .. and done
theory says that if a different build.prop file is in /data will overwrite the one from /system (same principle applies to apps from /system that when are updated in market new versions are installed to /data and system uses the ones from /data instead of ones from /system)

Did not work for me.
I changed both build.prop in /system and /data but after reboot both of them back to default!
Sent from my HTC Flyer P510e using XDA App

baadnewz said:
with temp root:
adb shell cat /system/build.prop > /data/build.prop
adb pull /data/build.prop
open pulled build.prop with notepad++ or whatever text editor you like, make changes suggested by OP. save file
adb push build.prop /data/build.prop
reboot .. and done
theory says that if a different build.prop file is in /data will overwrite the one from /system (same principle applies to apps from /system that when are updated in market new versions are installed to /data and system uses the ones from /data instead of ones from /system)
Click to expand...
Click to collapse
Did the settings hold/work on your temp root Flyer?

Great work, another reason for me to get the HTC Evo View.. informed mods for portal viewing

Can't edit build.prop this file read only status. how to change to write status?

baadnewz said:
with temp root:
adb shell cat /system/build.prop > /data/build.prop
adb pull /data/build.prop
open pulled build.prop with notepad++ or whatever text editor you like, make changes suggested by OP. save file
adb push build.prop /data/build.prop
reboot .. and done
theory says that if a different build.prop file is in /data will overwrite the one from /system (same principle applies to apps from /system that when are updated in market new versions are installed to /data and system uses the ones from /data instead of ones from /system)
Click to expand...
Click to collapse
What is your answer to my earlier question?

Hi ,
I cant see these files in my HTC Flyer. Can someone help. how to find the build.prop in my device.

gobirahul said:
Hi ,
I cant see these files in my HTC Flyer. Can someone help. how to find the build.prop in my device.
Click to expand...
Click to collapse
Do you have root rights?
Have you installed the SDK on your PC?

YOSEFE said:
What is your answer to my earlier question?
Click to expand...
Click to collapse
Not work for me with temp root as I said.
Sent from my HTC Flyer P510e using XDA App

veria100 said:
Not work for me with temp root as I said.
Click to expand...
Click to collapse
It won't work with temp root only. You need permanent root and s-off. The reason being is that the phone is designed to (when s-on) check on boot if any changes have been made to system files. If they have been made, it will automatically revert them back to the original file. That is why "temp-root" won't persist between reboot, and this is the reason I believe it is not working for you. When you reboot the phone, it is just reverting the changes you made to the build.prop file. Sorry, but I think that you will have to way until AlphaRev releases their s-off method.
Once they release their s-off method it should work.

Related

Deleted build.prop and reboted phone

I got the notice on my Gf's phone that I need to update. after it failed I tried a few things among them replacing the build.prop
Unfortunatilly I removed the build.prop and did not secussfully replace it. I can still use adb but if i try to push the build.prop to the /system folder it says premission denied read only.
I tryed to grand superuser permissions but after the su command the super user permission dialog doesnot come up on my phone. atcually nothing shwes up on the phone but the top information pannel which i can bring down to view notifications. but I cannot acess anything else.
Also the resolution looks to be about half of what it is suposed to be.
PLEASE HELP, my girlfriend is going to have my nutz, and my nexus one.
EDIT:
used the exploit from the first post in this section. then after the ./exploit command I was able to load up the build.prop
Does the $ change to a # when you type su?
porcupineadvocate said:
Does the $ change to a # when you type su?
Click to expand...
Click to collapse
sorry i have not tried using exploid rooting method . why dont you use universal androot. its easy and if you need build.prop then i have attached for you and also universal androot.

(TOOL) Perma-Temp Root with *R/W* & Stable!

Thanks goes to #TeamWin for Temp Root
This is For Windows only, if you wish to make it work for linux or mac help your self...
Remember, This is still a Temp Root & any Changes made will be Rest back to stock on a Reboot
It's stable & works 100%
I Personally have not lost Root with this new Method
Q. I thought RW was Fixed?
A. Caused by Deleting an apk / file that was already deleted. Journaling shows it still there!
Keep Track of what you delete, as trying to delete something off system that you alread di hangs the /system into RO state.
Before Using!!​HTC Sync Must be Turned OFF
Put the Phone into Charge Mode only ( Not Disk Drive )
USB Debugging Must be Turned on
What's Fixed:
Revamped due to new Method:
~ Superuser Apps now Function
~ If you Lose Root, all you have to do is Open terminal & type SU then type fixit! > No More Rebooting & running the exploit again for R/W on system to get Root back in place
~ Fixed R/O Bug!!
~ R/W is now Forced
~ /system is fully editable now! until reboot that is.
~ Busybox is installed to /vendor/bin
~ hex Edited libext4
~ hex edited libfuse.so
~~ This is the Last Update due to it working & Stable ~~
Download for RW HTC Sensation 4G:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Evo 3D:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Flyer 16GB/32GB:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Evo View:
Q. Is this permanent?
A. no, it's a temp root method..
Q. Will I lose SU Access at some point while running the OS?
A. You might, but open terminal & type fixit to get root back!.
Q. What about apps that need a reboot to use superuser?
A. Use Fast Reboot form the market for app that need a reboot..
Q. Can I push & remove items to system & will it work?
A. Yes, but all changes are reset on a reboot.​
Once Downloaded, Unzip & double click on the Run_ME_fre3vo_Root.bat File & Enjoy long lasting Root!
OLD NEWS:
Everyone knows that currently with any temp root, you still lose links to the SU Binary & Busybox links, it's just a matter of time before it happens!!
So after digging around somewhat I found an over sight that HTC might use later for system updates via /vendor/bin, who knows at this point though... Anyways, after amount of time the SU Binary along with busybox links if be in system/bin or /system/xbin gets deleted / removed..
Now, what I did was enable the $Path to /vendor/bin which is in the Sensation export PATH..
Any Calls made from this point either be SU or Busybox don't get deleted nor touched from any App requesting the SU Binary!! I've tested this with alot of apps & the Root sticks in place..
Other than Reboot, it might as well be a Perma-Temp-Root!!
Downloading now!!! Can't wait to test it!
***EDIT***
Rooted perfectly, opened and closed Titanium Backup several times with no force closes or loss of su, Barnacle is perfect, Wireless tether is granted su but the kernel doesn't support it, screenshot gained su also but the screenshots were smeared colors. Drocap2 takes perfect screenies though. Gonna try a few more root apps before bed and play some more when I wake up to verify it lasts.
going to try this now!
Ran the script and no root
script stays on
daemon started successfully :/
eugene373 said:
Thanks goes to #TeamWin for Temp Root!!!
Everyone knows that currently with any temp root, you still lose links to the SU Binary & Busybox links, it's just a matter of time before it happens!!
So after digging around somewhat I found an over sight that HTC might use later for system updates via /vendor/bin, who knows at this point though... Anyways, after amount of time the SU Binary along with busybox links if be in system/bin or /system/xbin gets deleted / removed..
Now, what I did was enable the $Path to /vendor/bin which is in the Sensation & Evo 3D export PATH..
Any Calls made from this point either be SU or Busybox don't get deleted nor touched from any App requesting the SU Binary!! I've tested this with alot of apps & the Root sticks in place..
Other than Reboot, it might as well be a Perma-Temp-Root!!
This is For Windows only, if you wish to make it work for linux or mac help your self...
If you have trouble with the Superuser.apk, uninstall first & reboot then run the .bat file again..
What is installed?
Busybox w/ symlinks
Superuser.apk
SU Binary
Fre3vo
sqlite3
What's Removed?
slackerradio.apk
TMOUS_Navigator.apk
Transfer-pyramid-8.30.0.26-S30.apk
Protips.apk
IdleScreen_Stock.apk
HtcTipWidget.apk
com.htc.TrendsWidget.apk
com.mobitv.client.tmobiletvhd.apk
FusionStockWidget.apk
Stock.apk
So without further ado, the link!
http://www.multiupload.com/LBEYIFVD58
Once Downloaded, Unzip & double click on the Run_ME_fre3vo_Root.bat File & Enjoy long lasting Root!
Last edited by Eugene373; Today at 05:51 AM.
Click to expand...
Click to collapse
Is there any chance u can edit the script or tell me how to edit it so it doesn't remove anything. Thanks.
perfect works great!!! Managed to restore TB! Will try out wifi tethering right now and other su required apps! Thank you! <3
I guess I don't understand.
How is removing anything from /system/app gonna stick?
This worked perfect for me. No problems with it. Wifi tether won't work for me, but barnacle tether works perfectly. Drocap2 is taking perfect screen shots for me as well, where as before the images would be all distorted and what not.
Made some changes to the .bat since I don't necessarily want to disable all of that yet, but it works, this is the longest superuser has worked for me so far on the EVO 3D.
k2buckley said:
This worked perfect for me. No problems with it. Wifi tether won't work for me, but barnacle tether works perfectly. Drocap2 is taking perfect screen shots for me as well, where as before the images would be all distorted and what not.
Click to expand...
Click to collapse
How'd you get Barnacle to work?
EDIT:
Sorry my tablet doesn't read Ad-Hoc >_>
Is anybody able to root the E3D with this method? I tried twice and it failed both times. I will do again by restart my pc and E3D.
urcboss07 said:
Is anybody able to root the E3D with this method? I tried twice and it failed both times. I will do again by restart my pc and E3D.
Click to expand...
Click to collapse
Yeah....First try.
nabbed said:
I guess I don't understand.
How is removing anything from /system/app gonna stick?
Click to expand...
Click to collapse
It won't stick, but after you reboot you run the batch program again and the apps are removed again until your next reboot.
hockeyfamily737 said:
It won't stick, but after you reboot you run the batch program again and the apps are removed again until your next reboot.
Click to expand...
Click to collapse
So, it will not stick as said, right?
Tiffany84 said:
Is there any chance u can edit the script or tell me how to edit it so it doesn't remove anything. Thanks.
Click to expand...
Click to collapse
a .bat file is just a text document that is executed in command prompt. If you are familiar with cmd just open the file in notepad, delete any commands you don't want executed, save.
urcboss07 said:
So, it will not stick as said, right?
Click to expand...
Click to collapse
Not through a full reboot....no you will have to run the batch file again (even says so in the OP). However, the other root methods would crash periodically even without a reboot or would last but not give you access to the majority of your root apps. This is the closest yet to a feasible root solution.
mine doesnt get past daemon started successfully i have usb debugging on
so if i downloaded and installed some apps that require root,
and i reboot, what happens to them ?
they will work after running the bat file again ?
or they will have to be installed again to work properly ?
thanks !
EDIT: i haven't done my due diligence (searching and reading)
but it's 5 am so i'll ask ...
what works for screen capture and for wireless tethering ?
lowetax said:
so if i downloaded and installed some apps that require root,
and i reboot, what happens to them ?
they will work after running the bat file again ?
or they will have to be installed again to work properly ?
thanks !
Click to expand...
Click to collapse
They will work after running the .bat file again. You shouldn't need to uninstall and reinstall them. Super User may need to be uninstalled before running the .bat file again, if it gives you any force closes.
Sent from my PG86100 using XDA App

[APP] Market v3.3.11 Latest *Requires Root*

*THIS IS FOR UNROOTED/LOCKED/S-ON* EVO 3D Devices.. Should work for any H-BOOT version
First of all,,,
see this thread to gain TEMPORARY ADB ROOT ACCESS
http://forum.xda-developers.com/show....php?t=1329220
*DO NOT REBOOT*
Secondly..
Download attachment and unzip to your ADB folder
*please backup your original Vending.apk first*
go to your ADB folder by command prompt (copy line by line, except the #, this indicates you are in ADB ROOT mode)
adb shell
# chmod 555 /system/app/Vending.apk
# rm /system/app/Vending.apk
# exit
adb push Vending.apk /system/app/
adb shell
# chmod 755 /system/app/Vending.apk
# exit
Try to run new market from your device, if errors, try reboot
Thank me if this helps you... it works for me...
Also, if it reverts back to old market, simply run the Vending.apk and it shall overwrite...
otherwise you can delete the marketupdater.apk from /system/app/ *thanks to j4n87*
Delete marketupdater.apk from /system/app ...then it should stick after restart.
Works fine for me snd it seems a lot more smooth than earlier versions.
(+ dns fix found on the portal)
Edit: new features:
New setting: Auto-update apps (presumably, sets all apps to auto-update mode, woohoo!)
New setting: Update over Wi-Fi only
New setting: Auto-add shortcuts (automatically adds homescreen shortcuts for new apps like Honeycomb)
Smaller font
New app drawer icon
Microphone (voice command) button in search menu
Star rating chart on app pages
Minor UI tweaks
Click to expand...
Click to collapse
Sent from my HTC EVO 3D X515m using xda premium
Didn't Stick for me either... I'll try Deleting the Updater Apk!
There’s already a flashable .zip in this thread: http://forum.xda-developers.com/showthread.php?t=1328883
Just flash via clockwork.. I’ll upload it here too.
I just downloaded and installed over old apk and it works just fine. Phone rooted but no extra steps needed
Sent from my PG86100 using xda premium
cannibalstreet said:
I just downloaded and installed over old apk and it works just fine. Phone rooted but no extra steps needed
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
That's what I did haha
I updated this like I update every system app. Simply replace it in /system/app fix its permissions and reboot. No need for anything else, and it didn't get replaced with an older market either.
freeza said:
I updated this like I update every system app. Simply replace it in /system/app fix its permissions and reboot. No need for anything else, and it didn't get replaced with an older market either.
Click to expand...
Click to collapse
This always works too!
Forgot to mention...
this step is for those who is UNROOTED, LOCKED & S-ON...
You can achieve TEMPORARY ADB ROOT via the 1st step, and follow the steps accordingly..
If you are ROOTED (UNLOCKED), you can install the apk directly...
Cheers

[GUIDE] Get 48 GB Free promotional Dropbox space

I saw a post in this thread about getting the promotional space on AT&T S4 without flashing TMobile roms. I gave it a try, and it worked just fine. So I thought of sharing the files with you. I pulled them out of a deodexed TMobile rom.
Download the attached file. You need to push Dropbox.apk and DropboxOOBE.apk into system/app and fix permission. Then you need to push com.dropboxpartner into system/framework and again fix permission.
Then, you need to modify the build.prop using a root explorer. Find the following lines and modify them as follow:
ro.product.model=SGH-M919
ro.product.name=jfltetmo
ro.product.device=jfltetmo
Reboot your device, open the Dropbox app, and log in with your existing account, or create a new account. You will receive an email, and after fulfilling 5 of the 7 tasks, you will receive the 48 GB promotional space. After fulfilling the tasks, you can restore your build.prop to its original state.
Attached Files:
http://d-h.st/fZJ
smnfriend said:
I saw a post in this thread about getting the promotional space on AT&T S4 without flashing TMobile roms. I gave it a try, and it worked just fine. So I thought of sharing the files with you. I pulled them out of a deodexed TMobile rom.
Download the attached file. You need to push Dropbox.apk and DropboxOOBE.apk into system/app and fix permission. Then you need to push com.dropboxpartner into system/framework and again fix permission.
Then, you need to modify the build.prop using a root explorer. Find the following lines and modify them as follow:
ro.product.model=SGH-M919
ro.product.name=jfltetmo
ro.product.device=jfltetmo
Reboot your device, open the Dropbox app, and log in with your existing account, or create a new account. You will receive an email, and after fulfilling 5 of the 7 tasks, you will receive the 48 GB promotional space. After fulfilling the tasks, you can restore your build.prop to its original state.
Attached Files:
http://d-h.st/fZJ
Click to expand...
Click to collapse
Worked great for me, thanks! I already had 12GB and had completed the 5 Getting Started steps long ago. When I signed into the DropBox app and got it setup, I suddenly had 60GB for 24months and an email from DropBox.
Here's the instructions I followed:
Cleared cache of, cleared data of, and uninstalled the DropBox app I already had.
Reminder: backup your build.prop
I ended up using this build.prop Editor. When you open it, use the menu key to make a backup before touching anything. Then scroll through and make the changes prescribed in the OP.
Downloaded the file attached in OP.
Extracted files using my computer to my internal sdcard. Possible to do this with apps on your phone (various file explorers or unzip programs), but I found it easier to just do it over USB/MTP.
Fired up ADB Shell - could also use a terminal emulator from the device, but do not use the "stop" command below if you are using an emulator on the device.
Performed the following commands (after running "adb shell" from a command line on the computer):
Code:
$ su
# mount -o rw,remount /system
# stop
# cp /sdcard/Dropbox.apk /system/app
# cp /sdcard/DropboxOOBE.apk /system/app
# cp /sdcard/com.dropboxpartner.jar /system/framework
# reboot recovery
Device rebooted into TWRP, where I used the Advanced menu to Fix Permissions.
Rebooted back into the System like normal.
Opened the DropBox app and signed in. Setup the camera sync again of course (awesome feature).
Checked my mail - Woot.
Used the build.prop editor to restore my build.prop
Closed the build.prop editor and re-opened. For some reason after restoring the backup, the restored changes were not reflected until I restarted the editor. Whatever, but it worked.
Worked for me:thumbup: Thanks! Now what to do after the two year promo period ends...
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I'm already up to 50GB on doing something like this before. I'm not sure if it'll work again but I'll give it a whirl sometime today. Will report back if I find myself up to 98GB.
Perfectly working.
Followed general instructions (used FX root explorer instead of Android Terminal for dropping apks in designated locations) and this worked just fine without a hitch. I appreciate the straightforward and simple instructions.
All I did was flash Wicked (T-Mobile ROM) then KTOONSEZ touchjizz kernel. After getting my free dropbox space, I flashed back.
Sent from my SGH-I337 using xda premium
lol same here with GOLD3N3Y3 rom; any non-ATT rom works if you DL and activate it. i have my own server so im letting everyone in my family use it for our stuff.
Slade8525 said:
lol same here with GOLD3N3Y3 rom; any non-ATT rom works if you DL and activate it. i have my own server so im letting everyone in my family use it for our stuff.
Click to expand...
Click to collapse
i can confirm that this works on vzw.
Thanks, worked great on my VZW S4.
Aou said:
Worked great for me, thanks! I already had 12GB and had completed the 5 Getting Started steps long ago. When I signed into the DropBox app and got it setup, I suddenly had 60GB for 24months and an email from DropBox.
Here's the instructions I followed:
Cleared cache of, cleared data of, and uninstalled the DropBox app I already had.
Reminder: backup your build.prop
I ended up using this build.prop Editor. When you open it, use the menu key to make a backup before touching anything. Then scroll through and make the changes prescribed in the OP.
Downloaded the file attached in OP.
Extracted files using my computer to my internal sdcard. Possible to do this with apps on your phone (various file explorers or unzip programs), but I found it easier to just do it over USB/MTP.
Fired up ADB Shell - could also use a terminal emulator from the device...
Performed the following commands:
Code:
$ su
# mount -o rw,remount /system
# stop
# cp /sdcard/Dropbox.apk /system/app
# cp /sdcard/DropboxOOBE.apk /system/app
# cp /sdcard/com.dropboxpartner.jar /system/framework
# reboot recovery
Device rebooted into TWRP, where I used the Advanced menu to Fix Permissions.
Rebooted back into the System like normal.
Opened the DropBox app and signed in. Setup the camera sync again of course (awesome feature).
Checked my mail - Woot.
Used the build.prop editor to restore my build.prop
Closed the build.prop editor and re-opened. For some reason after restoring the backup, the restored changes were not reflected until I restarted the editor. Whatever, but it worked.
Click to expand...
Click to collapse
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Cinosinu said:
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Click to expand...
Click to collapse
You need to do it from your computer terminal/shell using adb shell command through the USB, not using a terminal emulator on the device. Stop does exactly what it says, it stops the device from running I think , or maybe just pauses.
You should be able to copy the files without stop though, it's probably riskier, and then you need to use reboot. You just need to copy the files into the right locations and then fix the permissions.
Cinosinu said:
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Click to expand...
Click to collapse
These are linux commands. Stop, stops your device, and you cannot use it unless you reboot it. You can punch in the commands through your computer (this way, you need to install android sdk. Then, open the installed folder, and go to sdk\platform-tools. Here, you should hold shift, right click and select "open command window here", and punch the commands). Also, you can simply use a root explorer, and manually move the files to their folders and fix permissions
Just pull the battery and reboot. It happened to me also.
Sent from my SGH-M919 using xda premium
smnfriend said:
Also, you can simply use a root explorer, and manually move the files to their folders and fix permissions
Click to expand...
Click to collapse
What does this mean? I have ES fie explorer, trying to move the files I get a rewrite error. Do i need to fix the permissions first? What is the adb command?
thanks
I got it!!! :victory:
Why didn't someone tell me you must use the command 'ADB Shell' to start?
I'm no expert with ADB obviously. Knew it was something trivial. Hope someone else finds my comment helpful. :highfive:
Thank you OP and all! XDA rocks!
Thanks for pointing these things out. Yes, "stop" should only be used if doing this from an ADB shell. I've updated my instructions a tad bit to reflect this.
How can i do this for multiple accounts? I logged out and in and no luck.
Sent from my SGH-M919 using xda premium
kalparker said:
How can i do this for multiple accounts? I logged out and in and no luck.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
did you do a factory reset, re-install of your ROM, then the steps again? that may help by giving you a different device ID (you may have had this warning before in TiBU), which i'm guessing DB is looking for to limit 1 upgrade per device ID.
-rf
xrabbitfootx said:
did you do a factory reset, re-install of your ROM, then the steps again? that may help by giving you a different device ID (you may have had this warning before in TiBU), which i'm guessing DB is looking for to limit 1 upgrade per device ID.
-rf
Click to expand...
Click to collapse
That might work. In TiBu, I have the option to create a new, random device ID - might be a Pro feature only. Check your menu key, and near the bottom you can Manager your Device ID...
I would advise a nandroid backup first - this may screw up some of your other accounts, including Google. I've personally never tried it, but I would imagine it could cause some amount of chaos.
thanks!

Build.prop not editing

Hi , on my HTC one max when I try to edit build.prop it gets saved but when I reset my device for applying changes it returns to stocked any one that can help me .
I am root, S-OFF.
sonu42197 said:
Hi , on my HTC one max when I try to edit build.prop it gets saved but when I reset my device for applying changes it returns to stocked any one that can help me .
I am root, S-OFF.
Click to expand...
Click to collapse
Make sure you are mounting /system as RW first. By default it is RO. If you have root explorer it's just easy as clicking the RW button but if not there is always terminal and a command you enter.
Ƒłƴнαłƒ205 said:
Make sure you are mounting /system as RW first. By default it is RO. If you have root explorer it's just easy as clicking the RW button but if not there is always terminal and a command you enter.
Click to expand...
Click to collapse
My system is RW and I have used each file manager but can you tell how to do this with terminal?
Please.
sonu42197 said:
My system is RW and I have used each file manager but can you tell how to do this with terminal?
Please.
Click to expand...
Click to collapse
Terminal I mentioned to mount your system as RW. Why not edit your build.prop on computer and push it to your device in recovery mode.
Ƒłƴнαłƒ205 said:
Terminal I mentioned to mount your system as RW. Why not edit your build.prop on computer and push it to your device in recovery mode.
Click to expand...
Click to collapse
Tried to do it with adb but it comes back to original one.
i was able to successfully change the build.prop file by using the file manager in twrp recovery.
i kept the modified file on my sd card, went into recovery, fired up the file manager, browsed to my sd card, selected the modded file, chose the copy option, then chose the /system folder as the destination. rebooted and the changed file stayed changed!
my device is rooted, bootloader unlocked, and s-on.
root explorer with r/w mounting didnt work for me...file would revert after reboot.
also tried "cp" command in terminal in recovery...didnt seem to copy successfully.
hope this helps!
Sent from my HTC One max using XDA Free mobile app

Categories

Resources