Related
Is there a way to remove this after being rooted?
I would also like to know this.
Sent from my ADR6400L using Tapatalk
I also, its very annoying seeing that pop up.
Jcase, is this something that you might have work on ?
Yes, easy cheesy, using root explorer:
Delete or move or follow file CDROM.ISO
Can be found in /system/etc/CDROM.ISO
More importantly, all of you should also disable usb autoplay on your pcs. That's a popular malware attack vector these days.
Sent from my ADR6400L using XDA App
Gunthermic said:
Yes, easy cheesy, using root explorer:
Delete or move or follow file CDROM.ISO
Can be found in /system/etc/CDROM.ISO
Click to expand...
Click to collapse
This file is nowhere to be found. I searched the whole device and it didn't find anything, any thing else it may be named? There isn't even an ISO file in the etc folder.
Gunthermic said:
Yes, easy cheesy, using root explorer:
Delete or move or follow file CDROM.ISO
Can be found in /system/etc/CDROM.ISO
Click to expand...
Click to collapse
Thnx, this worked for me
Disable Verizon CD Intaller
Here you go:
http://forum.xda-developers.com/gal...ment/guide-how-to-disable-verizon-cd-t2831293
Here is the correct way to use root explorer for manually replacing system files:
1. Mount the system as r/w (read/write) per the top right corner. Navigate to the file that you plan to replace (e.g., system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. For example, in a lot of cases, the permissions will be RW-R-R. In Root Explorer, this would mean checking the first two boxes on the first line and only the first box on the next two lines. In any situation, confirm that the permissions you see after you've changed them (right below the file name) match exactly what you're replacing.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and double check the permissions.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
It may seem like a lot to someone who doesn't do it often but for me, I actually do this method faster than any other and fly through it every time. I got tired of seeing people explain ways to use Root Explorer which result in bootloops, FCs, etc. without fail. So, I decided to put an end to it.
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Audiochild said:
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Toggle "Mount R/W" button at the top.
Audiochild said:
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Sounds like you need to mount \system as read-write. There is a button in the upper right corner of root explorer to mount
Sent from my SGH-I777 using XDA App
Thanks wonner and kbilly70! That was the issue
Awsome. Bookmarked!
thanks for the awesome guide. worked great for me!
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
kZard said:
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
Click to expand...
Click to collapse
Those are only for flashing purposes. Not needed if you're not flashing it. You only need to pull everything besides that folder and place them appropriately.
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Edgarhighman said:
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Click to expand...
Click to collapse
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Simba501 said:
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Click to expand...
Click to collapse
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Edgarhighman said:
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Click to expand...
Click to collapse
If the apk is compatible, it will work. At no point should you get an "application not installed" prompt, unless you attempted to manually install it at some point. If it wouldn't work, it just wouldn't appear in the app drawer: no prompt.
I guess this should be mentioned in the OP, but some times, clearing data of the application may be necessary after finishing. Usually a force stop at the most will allow you to see changes (which is why the steps include a reboot). You've piqued my interest. Post the files of question and I'll see if they work on my device. There was a similar issue someone else was having; I told him to redownload the apk and that was the problem. Some kind of botched file/download.
Sent from my Galaxy S II (i777)
can you edit or create new folders in the /sys directory?
mikoal said:
can you edit or create new folders in the /sys directory?
Click to expand...
Click to collapse
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Simba501 said:
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
dsmboost said:
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
Click to expand...
Click to collapse
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Simba501 said:
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
Ah okay, I was referring to ES file explorer, which can modify other files in that directory.
thanks to you both!
since I can not post directly in the discussion, I have to open a separate thread.
I used the file for dual touch using insmod and it worked.
Now I wanted to make sure that it is fixed with the phone, I read the procedure and tried to follow her, but I do not find any files bulid.prop ....
Where is it?
Please help me.
build.prop is in
root, system folder
tell me if it works for you, I tried this and I couldn't get it to work.
Ray_jai said:
build.prop is in
root, system folder
tell me if it works for you, I tried this and I couldn't get it to work.
Click to expand...
Click to collapse
using it without changing the files, it works QuickPic, Copilot.
In google maps does not work. Not even in browsers like Opera or Ninesky.
But I thought that by modifying these files, worked in the rest.
Thanks! I found the file "build.prop",
Where is the other file "hw_config.sh"? Because what I found I had no voice "insmod" ...
DomusX10 said:
using it without changing the files, it works QuickPic, Copilot.
In google maps does not work. Not even in browsers like Opera or Ninesky.
But I thought that by modifying these files, worked in the rest.
Thanks! I found the file "build.prop",
Where is the other file "hw_config.sh"? Because what I found I had no voice "insmod" ...
Click to expand...
Click to collapse
hw_config.sh is in ur "etc" folder... are you using root explorer???
You do know you can use the search function OF the root editor too...
DomusX10 said:
using it without changing the files, it works QuickPic, Copilot.
In google maps does not work. Not even in browsers like Opera or Ninesky.
But I thought that by modifying these files, worked in the rest.
Click to expand...
Click to collapse
Not sure what ROM you're using, but you may need this file to get the other apps using dualtouch:
http://forum.xda-developers.com/showpost.php?p=13497850&postcount=49
teapea said:
Not sure what ROM you're using, but you may need this file to get the other apps using dualtouch:
http://forum.xda-developers.com/showpost.php?p=13497850&postcount=49
Click to expand...
Click to collapse
this is the problem?? I've Stock ROM 2.1update1 with firmware 2.1.1.A.06
then, I have to create that file and copy it into /system/etc/permissions with rootexplorer...
now I try this...and you know I do!
EDIT: NOT WORKING...I have create that file (copy and paste the code in the frame in a txt file, and renamed android.hardware.touchscreen.multitouch.xml) then I've paste it into /system/etc/permissions and associated it permission rw-r-r
rebooted and not working...single touch.
yet launched from the console does the dual touch working in some applications ... why?
EDIT 2: Please do not send me to hell, but by creating the file and rebooting, if I launch "insmod" from the console, dual touch works in all apps!
How is it possible, however, that the changes to make it start with phone not work?
I want to work "even" when I restart the phone!
Did you try this version?
http://forum.xda-developers.com/showpost.php?p=13498769&postcount=56
I couldn't get it to work when doing it manually. but when I load it from the SD card through adb it works.
I ended up using the AAIS script and replacing the module in the AAIS with the one in the link.
Ray_jai said:
I ended up using the AAIS script and replacing the module in the AAIS with the one in the link.
Click to expand...
Click to collapse
I use that on the first post dedicated at my firmware 2.1.0.A.06
http://forum.xda-developers.com/showthread.php?t=1064558
manually loaded by terminal emulator work in every app. But, the procedure to autorun this module with telephone when start, don't work.
I do not know which is doing a script AAIS, because I'm not well prepared ... I do not know how to do it ...
use this.
http://forum.xda-developers.com/showthread.php?t=951274
Ray_jai said:
use this.
http://forum.xda-developers.com/showthread.php?t=951274
Click to expand...
Click to collapse
thanks!
With this script you can enable and disable a lot of things ... I can just see if it works ...and let you know ...
I wanted to ask, but what is JIT? what does it do?
thank you in advance for availability ..
EDIT: Works!!! without launching the script, I went just to see how the command was written in the file "hw_config.sh" ...
I corrected, and after restarting, it works!
I was wrong because we put the quotes, but no need to write.
The correct lines of code to be included in the file "hw_config.sh" (at bottom) are:
# load multi touch driver
insmod /system/lib/modules/cy8ctma300_ser.ko
sleep 1
After you have copied into system/lib/modules "cy8ctma300_ser.ko" , mounted it as rw-rr , and edit the file "build.prop" as indicated in the post.
works!!!
thanks!!!!
Just rooted my Verizon galaxy S4. Pain in the ars compared to the Droids that I've had for the past 6 years. Maybe just different.Not really interested in changing out Rom, but really need to have tether. I have unlimited and use about 16 gbs per month for business. I know that there's a thread on xda for tehter, but its somewhat old and can't see anyone that's used it or applied it for the MK2 build. Have tried numerous WiFi apps on market and none work. Also the.the thread on xda is somewhat over my head. Anything else out there. Hows this, since I don't do this for a living and don't have the patience to do the tether package ...theres 50.00 bucks to help me get tether and to understand it a little better. Use to change the entitlement on the droids and had tether, but the process on the galaxy is stumping me. let me know
http://forum.xda-developers.com/showthread.php?t=2512981
This thread is updated for MK2. Relatively simple as the primary method is to simply copy and paste in a root explorer.
MK2 tether
AdelosMeansUnknown said:
http://forum.xda-developers.com/showthread.php?t=2512981
This thread is updated for MK2. Relatively simple as the primary method is to simply copy and paste in a root explorer.
Click to expand...
Click to collapse
This is the part that's beyond me. I know it must be frustrating to deal with us out here, but any and all help is very much appreciated.
1.Download the modded framework-res.apk from here for MJ7 or here for MK2 then copy it to /system first then change framework-res.apk's permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk. Then reboot and you should have tethering!
Do I do a direct download to the phone? or or to desktop and than to system. and so on. again any help is appreciated This is why I go to YouTube and have a 8th grader show me how to do it. Kind of embarrassing for a guy that's in his fifties. But than again my work and what I do for a living is beyond allot of people...Thanks
truckerd said:
Just rooted my Verizon galaxy S4. Pain in the ars compared to the Droids that I've had for the past 6 years. Maybe just different.Not really interested in changing out Rom, but really need to have tether. I have unlimited and use about 16 gbs per month for business. I know that there's a thread on xda for tehter, but its somewhat old and can't see anyone that's used it or applied it for the MK2 build. Have tried numerous WiFi apps on market and none work. Also the.the thread on xda is somewhat over my head. Anything else out there. Hows this, since I don't do this for a living and don't have the patience to do the tether package ...theres 50.00 bucks to help me get tether and to understand it a little better. Use to change the entitlement on the droids and had tether, but the process on the galaxy is stumping me. let me know
Click to expand...
Click to collapse
I also have unlimited. Have you tried using PDAnet+? When I upgraded from 4.2.2 MKD to 4.3 MK2 my Foxfi app quit working and then I tried PDAnet+ and it works like a charm.
Sent from my SCH-I545 using Tapatalk
tether pdanet
Terri M said:
I also have unlimited. Have you tried using PDAnet+? When I upgraded from 4.2.2 MKD to 4.3 MK2 my Foxfi app quit working and then I tried PDAnet+ and it works like a charm.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Have used PdaNet in the past. Cant get it to work on this build...Weird
I'm on MK2 with Surge's tether. I found it much easier to unpack the zip on my desktop and move the files to the root of my external SdCard. Once you have all four files in the folder on your external SdCard, download Terminal Emulator to your phone from the play store, open it and type in the commands letter for letter (double check your spelling and spacing). The script runs, the phone reboots, and voila tether works through the hotspot app no problem.
---------- Post added at 05:47 PM ---------- Previous post was at 05:07 PM ----------
In addition if you use the script through Terminal Emulator you have a nice way to return to stock - just type in the commands for the untether script.
I had to undo the tether to accept the OTA from MJ7 to MK2. However, the next OTA should be kitkat, so who knows if this will even be an issue or if we'll still be able to tether this way.
Question on the root on the sd card..Do I make a file, no file on in E'S file mgr.
Sent from my SCH-I545 using xda app-developers app
truckerd said:
This is the part that's beyond me. I know it must be frustrating to deal with us out here, but any and all help is very much appreciated.
1.Download the modded framework-res.apk from here for MJ7 or here for MK2 then copy it to /system first then change framework-res.apk's permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk. Then reboot and you should have tethering!
Do I do a direct download to the phone? or or to desktop and than to system. and so on. again any help is appreciated This is why I go to YouTube and have a 8th grader show me how to do it. Kind of embarrassing for a guy that's in his fifties. But than again my work and what I do for a living is beyond allot of people...Thanks
Click to expand...
Click to collapse
I'd say it doesn't really matter how the file (frameworks-res.apk) gets to the root of your SD card. From there, using a file manager (I usually use File Manager, be sure to check root explorer and system write in the settings) locate where ever you placed the file, highlight it by pressing and holding, there should be an option to copy the file. Select that. Press home (which brings you to the root of your SD card), then press the "Up" button (which essentially begins accessing system files) until you can see the system folder. Paste here. Press and hold the file again and select "Permissions." Check The read and write of the first row, and read only of the next two rows. Move the file. Navigate to the framework folder and drop and overwrite. Reboot.
I use wanam xposed and xposed. There's an option to turn off tethering provisioning their.
Sent from my Nexus 7 using Tapatalk
AdelosMeansUnknown said:
I'd say it doesn't really matter how the file (frameworks-res.apk) gets to the root of your SD card. From there, using a file manager (I usually use File Manager, be sure to check root explorer and system write in the settings) locate where ever you placed the file, highlight it by pressing and holding, there should be an option to copy the file. Select that. Press home (which brings you to the root of your SD card), then press the "Up" button (which essentially begins accessing system files) until you can see the system folder. Paste here. Press and hold the file again and select "Permissions." Check The read and write of the first row, and read only of the next two rows. Move the file. Navigate to the framework folder and drop and overwrite. Reboot.
Click to expand...
Click to collapse
Just to double check where Im putting this file.. Theirs one[ sys file] and one[ system] in Devise, I did check the root explorer but couldn't find system write in the settings.
truckerd said:
Just to double check where Im putting this file.. Theirs one[ sys file] and one[ system] in Devise, I did check the root explorer but couldn't find system write in the settings.
Click to expand...
Click to collapse
The system file. If there is one (depends on file manager used) it should be the option below the root explorer option.
Which file mgr. do you suggest?
Sent from my SCH-I545 using xda app-developers app
AdelosMeansUnknown said:
I'd say it doesn't really matter how the file (frameworks-res.apk) gets to the root of your SD card. From there, using a file manager (I usually use File Manager, be sure to check root explorer and system write in the settings) locate where ever you placed the file, highlight it by pressing and holding, there should be an option to copy the file. Select that. Press home (which brings you to the root of your SD card), then press the "Up" button (which essentially begins accessing system files) until you can see the system folder. Paste here. Press and hold the file again and select "Permissions." Check The read and write of the first row, and read only of the next two rows. Move the file. Navigate to the framework folder and drop and overwrite. Reboot.
Click to expand...
Click to collapse
That's a great explanation.
Sent from my SCH-I545 using XDA Premium 4 mobile app
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)