Database Develop

Adfree on 3G slide?

Has anyone gotten Adfree android to work on the my touch slide 3G?
I either get a reboot or error about writing to hosts
Sent from my T-Mobile myTouch 3G Slide using XDA App

Faud said:
Has anyone gotten Adfree android to work on the my touch slide 3G?
I either get a reboot or error about writing to hosts
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
See this post:
http://forum.xda-developers.com/showthread.php?t=664532
Ignore the installation commands, you need to boot in to recovery and push the hosts file to /system/etc/ on the phone.

Adfree works fine. The reason it doesn't work on slide has nothing to do with the app. The hosts file goes in /system/etc/ and since we don't have r/w access to /system, the app can't do what's its supposed to do. It works great I used it the whole time I had a G1, its just cus your phone isn't PROPERLY rooted. Neither is anyone elses til we get that SPL...
Til then you gotta adb push the file thru recovery...
I dunno if you know this, but adfree temporarily d/l's the hosts file to your sdcard, then deletes it when its done. But since it couldn't replace the file on my slide, it left it on the sdcard! All you gotta do is run the app and wait for it to error out, then go get the file and put it on your pc and adb push to /system/etc...
-BMFC
Sent from my ROOTED myTouch3G Slide

bmfc187 said:
its just cus your phone isn't PROPERLY rooted. Neither is anyone elses til we get that SPL...
Click to expand...
Click to collapse
Actually, its rooted just fine (you can run anything you want as uid 0). The SPL security has nothing to do with root.
It is like saying you don't have the proper key to a door just because after you open it there is a guard standing there not letting you in to the next room.
Just being picky...

i think what he meant is that with all the other phones most of us have had we had an SPL to flash once we had done the original tweaks(or before on some phones) so as of right now i agree that the phone is not rooted properly yet as i don't have full control over the phone whenever i want, i want to be able to mv stuff to system partition from android terminal
just being picky...

could anyone please post the actual commands? im new to adb and wold really appreciate the help adfree is the entire reason i even rooted
among others but it was the number one

adb push hosts /system/etc
-BMFC
Sent from my ROOTED myTouch3G Slide

thank you so very much

Other than removing a few of the stock apps, this is one of the things I'm looking forward to rooting for, I loved it on my G1.
With all of the folks having so much trouble rooting this sucker though, I may wait awhile.

it said this
' failed to copy 'hosts' to '/system/etc': Permission denied '

and if i type su it asks for a password and if i try to run in root it says that production models wont run in root
but i rooted and have the superuser permissions apk installed and has granted me permission to other things

ParkerOviedo said:
it said this
' failed to copy 'hosts' to '/system/etc': Permission denied '
Click to expand...
Click to collapse
Were you booted in to recovery with /system mounted?

i was able to figure it out
i never tried typing su into the adb shell after i rooted
i got the prompt on my device and accepted it now i have full permissions

well it accepted the command and it pushed the host file to /system/etc but it still isnt disabling ads |:<

ParkerOviedo said:
well it accepted the command and it pushed the host file to /system/etc but it still isnt disabling ads |:<
Click to expand...
Click to collapse
same thing happened to me. but as falken mentioned before, you have to make sure the system is mounted before running the command. so..
boot into recovery.
go to 'partitions'.
select 'mount /system'.
run adb command "adb push hosts /system/etc".
reboot system.
*you might wanna might wanna be sure the comp sees the device in recovery before running the command via "adb devices". i do this before i do any adb'ing.
*be sure the hosts file is in the root of your sdk directory, otherwise your command will vary.

poetik517 said:
same thing happened to me. but as falken mentioned before, you have to make sure the system is mounted before running the command. so..
boot into recovery.
go to 'partitions'.
select 'mount /system'.
run adb command "adb push hosts /system/etc".
reboot system.
*you might wanna might wanna be sure the comp sees the device in recovery before running the command via "adb devices". i do this before i do any adb'ing.
*be sure the hosts file is in the root of your sdk directory, otherwise your command will vary.
Click to expand...
Click to collapse
All I get is "failed to copy 'hosts' to '/system/etc': Permission denied"
And yes my Phone is Rooted..
I did everything above. do I have to be in su or something...
Can you not do this on the stock rom. Do I have to flash one of the other roms to be able to push to System...

jnight666 said:
All I get is "failed to copy 'hosts' to '/system/etc': Permission denied"
And yes my Phone is Rooted..
I did everything above. do I have to be in su or something...
Can you not do this on the stock rom. Do I have to flash one of the other roms to be able to push to System...
Click to expand...
Click to collapse
You need to have flashed the engineering rom so you have a root shell in recovery.

Does the Hosts file even block ads?

droctii said:
Does the Hosts file even block ads?
Click to expand...
Click to collapse
Yup, and it makes the internet soo much faster. Adfree works fine as is if you add the rw overlay

dumfuq said:
Yup, and it makes the internet soo much faster. Adfree works fine as is if you add the rw overlay
Click to expand...
Click to collapse
BINGO! Thanks!!!

Temp root for apps required root access (for s-on IS)

Psneuter exploit is working on IS, but because /system is locked on s-on phones, we can't copy su and superuser.apk into /system, apps required root access can't work.
The following procedure uses psenuter exploit to gain adb shell root, and then copy su (without privilege control ) and busybox into /sbin (which is on rootfs and in the global PATH list) to gain root access for apps.
The procedure:
1. Unzip the attached .zip into a directory (like c:\adb)
2. Open a command prompt and cd to the directory where you extracted the .zip (like cd \adb)
3. run pushroot.bat (simply type pushroot)
4. adb shell /data/local/tmp/getroot
5. adb shell
6. you are now in # prompt. Type /data/local/tmp/pushroot
You have to redo steps 4,5,6 once you reboot your phone.
The procedure will have all apps gaining root access.
!!USE ON YOUR OWN RISK!!
Known working programs: Root explorer, Titanium backup, gscript lite, trasproxy 2.04, ...
Some apps check existence of su in /system/xbin , and reject to proceed if the su binary is not exist (like transproxy 3.08). For this kind of apps, this procedure won't help.

Nice but old news mate...
Sent from my HTC Incredible S using XDA Premium App

Good job...thanks

Thanks for writing this up, might quell the thirst for S-OFF a little longer

/system/ is writeable btw, if you remount it, but after reboot everything u done will be changed to the way it were before.
so a temp root in xbin is possible also, only it will be gone afterwards (atleast i never tried this, but should work also...)

Yes. /system could be remount in rw with root. However, the files you wrote will be gone after you remount ro, and then you won't be able to copy the same filename into the same location again before next reboot ( I don't know why, actually!!). This is why I put su in sbin instead of /system/xbin.

thanks to your files 非常感谢你的工作。

Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?

faf said:
Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?
Click to expand...
Click to collapse
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk

pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....

itandy said:
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Definitely, this is the way to go.
Unfortunately, the root exploit I know could run on device itself, including
rageagainstthecage (ratc) and local root exploit (hotplug) both failed on IS.
The solution will be nearly perfect if we can get temp root on IS without a computer link.
Any input will be welcome.

sky1212 said:
pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....
Click to expand...
Click to collapse
Please then type adb shell.
If you see # but not $, do
cd /data/local/tmp
rm ./cp
ln busybox cp
./pushroot
Then you finished the install.
If you see $, please do all over again.

You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work

l0st.prophet said:
You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work
Click to expand...
Click to collapse
Adfree is working for me. Are you getting some type of error message?
MetaMorph, screenshot and MyBackup Root are also working.
I had to mount system, then push su to /system/xbin. Then install BusyBox Installer from Market.

No erro, still got the ads. I've tried rebooting & rerooting, still no luck

l0st.prophet said:
No erro, still got the ads. I've tried rebooting & rerooting, still no luck
Click to expand...
Click to collapse
What site/app are you going to so I can see if I get the ads.

the anti-ads actually tries to modify the current host file... which is not allowed in your state as far as i know
what you can do is replace it by pushin it to the right spot
but after reboot gone,but sure u know

Adfee is working for me, you can also add Droidwall.

@eddycyf, did you test adfree with apps? Since it aint working for prophet...
Sent from my HTC Incredible S using XDA Premium App

Mhm AdFree isnt working for me. The App states that everything is okay, and that my hosts file is up to date, but I see ads everywhere.
But I am kinda happy now, because i can use Titanium Backup

One click root after update: "We have root, but couldn't push busybox. Not sure why!"

One click root after update: "We have root, but couldn't push busybox. Not sure why!"
I just updated .890 which seemed to go fine with no errors (unfroze all bloat, but did not unroot), but I lost root, as expected.. but when I use Pete's one-click root tool (latest version), it gets to step 3 and gives me the error about not being able to push busybox...!? It says I "have root", but none of my apps recognize it.. I've pulled the battery, rebooted and retried like 10 times... still can't get it to re-root. I've made sure Debugging and Unknown Sources is enabled and tried in Charge Mode and Mass Storage mode... Am I going to have to stock flash this thing and re-update & re-root?
I THINK I have some type of root.. maybe... because Root Explorer will let me mount the System directory as R/W and I can TRY to manipulate files, but if I delete something (like su), it appears to delete successfully, but the file comes back if I refresh the directory.. but I also noticed when I go into the System directory, Root Explorer claims I only have 1MB of free space out of 318.00MB... how did that happen? If I try to run Superuser.apk, it force closes on me.
Any help or ideas are greatly appreciated...

there's an app on the android market that will push busybox if you have root. I'd look into that
edit: have you attempted to run the one-click root again? and if that doesn't work you can try to use the adb method if you're comfortable with it. And make sure that all of your drivers and everything are up-to-date

I have done battery pulls and like a dozen+ re-tries at the 1-click root, always get the same error.. I have been into the ADB shell to try and figure this out and I see the ADB Shell starts out by giving me a # prompt... that means writable/root, right? Any instructions on what I have to do from there?
I will look into that push busybox app, thanks.

http://wiki.rootzwiki.com/index.php/Motorola_Droid_3
This is where all the info about the adb and one-click stuff. The tough part about the adb method is manually pushing su to the (i think) system/xbin folder. Then i just used the app on the marketplace to push busybox. But there's a download link for both of those on the website

Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...

Kraxis said:
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Click to expand...
Click to collapse
After temp ADB root, steps 18 and beyond should do it. You may want to check /system/bin and /system/xbin to remove the old su binaries before pushing the new one. Some folks have one in each location for some reason. Put it in xbin, but if it doesn't work, /system/bin will. Superuser wouldn't recognize xbin for me so I moved it to /system/bin and i'm good since.
Anyone have a thought on the xbin not always working? I think this is the 3rd topic i've seen with this issue, not including myself.
Sent from my DROID3 using XDA App

OK, I got root back! I used steps 18+ for "ADB Method" (after using Pete's temp ADB root) and essentially replaced SU and Superuser.apk, CHMOD'd it rebooted and I had root! Thanks guys!!

Maintain Root from V7 into OTA V8

This is all thanks to djrbliss.. I just followed instructions.
***This method does not root the V8 OTA update rather it will maintain root from V7 LG-Stock firmware and will carry it over into the OTA V8 update. There is no CWM-Recovery or GingerVolt as of yet, that is left to the professionals.. MT This is only if you want to run the V8 OTA Update with stock software.. but with root.
1. Use LGNPST to get back to LG-Stock V7 firmware by flashing the .tot
Files: http://forum.xda-developers.com/showthread.php?t=1466655
Instructions: http://forum.xda-developers.com/showthread.php?t=1337386
2. Use the LG1click from MT to root only.. you need stock recovery to apply the OTA update.
3. Create /data/local.prop and type ro.kernel.qemu=1 then save it. I used root explorer but you can also do it through terminal: echo 'ro.kernel.qemu=1' > /data/local.prop
4. Phone Settings > About Phone > Software Update > Check New and download the update to V8 firmware.
5. After reboot go to whatever directory on your PC, where you have superuser.apk and su and
adb remount
adb push su /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
If not sure use the 'files' from MT's LG1click
If that doesn't work download and run this:
Super1click 2.3.3 will push the files for you
http://dl.dropbox.com/u/50763513/SuperOneClickv2.3.3-ShortFuse.rar
***If nothing above is working*** (operation not permitted or read-only file system)
in adb type "adb shell id" should read "uid=0(root) gid=0(root)"
if not go back to /data/local.prop and make sure the file is still there (If not, just create it again in root explorer or other file manager that can edit files)
then "adb remount" and try to push the files again
then reboot and should be all set
OH, and if you don't want that remote desktop app it is /system/app/Aetherpal.apk I just renamed to Aetherpal.apk.bak rather than deleting it just in case..
Also if for some reason you wipe data (which I accidentally did) you will have to go back to Step 3 before getting the OTA update
And while they did fix some things in the update they left out fixing the touchscreen.. still goes unresponsive then you have to press power button to lock and unlock the screen to resume.

Flashing back to v7 now to test this out.
:::EDIT::::
So far it is failing. I get to step 5 and I am not able to remount. Permissions denied.
Also your rar file has tripped my antivirus software.
Please post a link to any original instructions.
:::EDIT::::
Yep still fails completely at step 5. The root is not carried over at all.

These are original instructions. I emailed Dan (djrbliss). Your anti-virus picked up on one of the exploits contained in the .rar. Once you download even if your anti-virus removes one of the files the rest works fine. This is how I was able to keep root. It does work.
adding the ro.kernel.qemu=1 and the adb commands were from djrbliss.. the rest is all me
Just try the super1click.
in adb type "adb shell id" what is the output?
*Should read "uid=0(root) gid=0(root)" <--- if anything but, go back to /data/local.prop and make sure it is still there.. I might be crazy but think it disappeared once or twice on me..
then the S1C or just the adb commands from OP should work..
(Your anti-virus removed psneuter from the exploit folder.. not needed anyways)

I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
:::EDIT:::
It is working. Seems I typo'd kernel. After running through things again, it worked like a charm.

Haxcid said:
I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
Click to expand...
Click to collapse
if you have any other issues beep me on IRC freenode #lgrevolution

Haxcid said:
I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
:::EDIT:::
It is working. Seems I typo'd kernel. After running through things again, it worked like a charm.
Click to expand...
Click to collapse
Glad to hear.. I was close to starting over from scratch to make sure I didn't miss something.. lol

Hmm, didn't work for me will try again later
Sent from my VS910 4G using Tapatalk
Edit: Got it working, typo for me too it's qemu not qenmu lol

JUST FYI.. I have been experiencing some issues with this method that I didn't know until now. At one time I have lost all sound (speaker, in-call, key beep) and /or Vibration. If this happens to you for short-term until someone much smarter than me figures out a normal root method go into /data/local.prop and just rename local.prop to local.prop.bak so you will have it just in case you need to adb push files. After you rename you should reboot. You will still have root on the phone without the file.
Dan/djr explained that ro.kernel.qemu=1 is what allows adb to run as root. Jcase told me that after you push the files you should remove that because it will cause problems if left, like above.
Like I said, hopefully someone will come up with something better..

Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol

drt054 said:
JUST FYI.. I have been experiencing some issues with this method that I didn't know until now. At one time I have lost all sound (speaker, in-call, key beep) and /or Vibration. If this happens to you for short-term until someone much smarter than me figures out a normal root method go into /data/local.prop and just rename local.prop to local.prop.bak so you will have it just in case you need to adb push files. After you rename you should reboot. You will still have root on the phone without the file.
Dan/djr explained that ro.kernel.qemu=1 is what allows adb to run as root. Jcase told me that after you push the files you should remove that because it will cause problems if left, like above.
Like I said, hopefully someone will come up with something better..
Click to expand...
Click to collapse
+1 to this. No sound. I was an hour late to work because my alarm was silent this morning LOL!
---------- Post added at 10:02 AM ---------- Previous post was at 09:55 AM ----------
dbeauch said:
Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol
Click to expand...
Click to collapse
.
I flashed back using the tot file, rooted then proceeded from there. Once I fixed my ignorant spelling issues everything worked great. Now that I have renamed the prop file and rebooted sound seems to be working.
My issue is now battery. The phone with no use is eating battery like a thunderbolt. It has been off charger for 2 hours with no use and its down to 84%.

dbeauch said:
Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol
Click to expand...
Click to collapse
Yes if you already have the V8 update in order to gain root you have to go back to V7 Stock firmware. If you are on GingerVolt 2.0 you have to flash the V7 Firmware to get back to LG-STock and Stock Recovery. The LG1click does NOT work on the V8 update so there is no CWM-Recovery, or GingerVolt at this time until MT figures out how once again..

Haxcid said:
+1 to this. No sound. I was an hour late to work because my alarm was silent this morning LOL!
SORRY!!!.. like I said didn't realize it until it happened, lost vibration and went to check my voicemail and no sound. But made that /data/local.prop into a .bak file, rebooted and was fixed. MT said has something to do with that entry in place the phone thinks it is a terminal emulator instead of a phone or something like that..lol So hopefully this is only temporary.
There may be a new root out soon.. not by me, like I said by someone much smarter than me may have found a way.
Click to expand...
Click to collapse

Worked like a charm DRT thanks so much!
Here is what I did:
1) Flashed MTs ZV7 Rooted Stock (RevoZV7GBStock.zip)
http://forum.xda-developers.com/showthread.php?t=1348637
2) Created the local.prop file, etc.
3) Used MTs All-in-One tool to flash Stock Recovery (Option 5)
http://forum.xda-developers.com/showthread.php?t=1348557
4) Downloaded and installed the ZV8 update OTA
5) Used ADB to push files per DRT instructions
6) Rebooted
7) Confirmed that I still have root using Root Checked Basic!
A little bit different than DRTs posted method but I wanted to avoid having to use LGNPST, so at least I can confirm that this alternate approach works as well!

drt054 said:
This is all thanks to djrbliss.. I just followed instructions.
***This method does not root the V8 OTA update rather it will maintain root from V7 LG-Stock firmware and will carry it over into the OTA V8 update. There is no CWM-Recovery or GingerVolt as of yet, that is left to the professionals.. MT This is only if you want to run the V8 OTA Update with stock software.. but with root.
1. Use LGNPST to get back to LG-Stock V7 firmware by flashing the .tot
Files: http://forum.xda-developers.com/showthread.php?t=1466655
Instructions: http://forum.xda-developers.com/showthread.php?t=1337386
2. Use the LG1click from MT to root only.. you need stock recovery to apply the OTA update.
3. Create /data/local.prop and type ro.kernel.qemu=1 then save it. I used root explorer but you can also do it through terminal: echo 'ro.kernel.qemu=1' > /data/local.prop
4. Phone Settings > About Phone > Software Update > Check New and download the update to V8 firmware.
5. After reboot go to whatever directory on your PC, where you have superuser.apk and su and
adb remount
adb push su /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
If not sure use the 'files' from MT's LG1click
If that doesn't work download and run this:
Super1click 2.3.3 will push the files for you
http://dl.dropbox.com/u/50763513/SuperOneClickv2.3.3-ShortFuse.rar
***If nothing above is working*** (operation not permitted or read-only file system)
in adb type "adb shell id" should read "uid=0(root) gid=0(root)"
if not go back to /data/local.prop and make sure the file is still there (If not, just create it again in root explorer or other file manager that can edit files)
then "adb remount" and try to push the files again
then reboot and should be all set
OH, and if you don't want that remote desktop app it is /system/app/Aetherpal.apk I just renamed to Aetherpal.apk.bak rather than deleting it just in case..
Also if for some reason you wipe data (which I accidentally did) you will have to go back to Step 3 before getting the OTA update
And while they did fix some things in the update they left out fixing the touchscreen.. still goes unresponsive then you have to press power button to lock and unlock the screen to resume.
Click to expand...
Click to collapse
I am having a few challenges with the steps above. For some reason my root explorer is messed up. It won't open and I've tried uninstalling then reinstalling but it won't won't download from the market. I get another error.
Anyway i can't find another program that can create the prop file. Does anyone know another program or does anyone have some more detailed instruction on how to use terminal?
Thanks

Nckmsn said:
I am having a few challenges with the steps above. For some reason my root explorer is messed up. It won't open and I've tried uninstalling then reinstalling but it won't won't download from the market. I get another error.
Anyway i can't find another program that can create the prop file. Does anyone know another program or does anyone have some more detailed instruction on how to use terminal?
Thanks
Click to expand...
Click to collapse
1 open terminal emulator
2 type su, then tap enter
3 type echo 'ro.kernel.qemu=1' > /data/local.prop, then tap enter
4 close terminal emulator
5 profit
Hope this helps
Sent from my VS910 4G using xda premium

elreydotcom said:
1 open terminal emulator
2 type su, then tap enter
3 type echo 'ro.kernel.qemu=1' > /data/local.prop, then tap enter
4 close terminal emulator
5 profit
Hope this helps
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Don't forget to rename the prop file to local.prop.bak when you are completely done and on zv8 rooted or you will experience issues like no sound at all. Once you rename the file and reboot everything should return to normal. I would also give it a few days to work out any kinks, like battery drain and the likes.
H.

Haxcid said:
Don't forget to rename the prop file to local.prop.bak when you are completely done and on zv8 rooted or you will experience issues like no sound at all. Once you rename the file and reboot everything should return to normal. I would also give it a few days to work out any kinks, like battery drain and the likes.
H.
Click to expand...
Click to collapse
Ive been unable to get the adb part to work. I can't get the adb command line to come up on my pc. Anyway, so I'm on v7 unrooted with no sound. I have change the name of the prop file and even removed it but my sound wont come back. Do i need to complete the whole process for the sound to come back?

If you are unrooted you can't create the file, you need to get rooted first. Use the all in one package to root.
Sent from my VS910 4G using xda premium

Once I was able to finsh the entire process, I managed to rename the prop file and all sound came back. success!
Thanks

Made a post in another thread but any word yet I how we get CWM recovery from rooted zv8?
edit: MT let me know that I needed to recreate the prop file, reboot, and then choose the root option in his new all in one package for ZV8...worked like a charm!
Sent from my VS910 4G using xda premium

Now What?

Now that we have root, what things are we going to be focusing on next? Probably Safestrap and ROMs. What cool things have you guys found with root?

Vlasp said:
Now that we have root, what things are we going to be focusing on next? Probably Safestrap and ROMs. What cool things have you guys found with root?
Click to expand...
Click to collapse
Well for one thing if you disabled/uninstall Unified Search, it allows google search to work correctly in the launcher, also without root you can replace the amazon keyboard with the google keyboard and get voice search.
Edit: We need to probably install Google play services properly to get Google Play Games to work correctly but I am not sure.

The ability to install apps depending on root is awesome.
If you are asking for wishes, then I wish I could use CyanogenMod on this device.

I have de-amazonified my tablet a bit. Cant wait to get a custom rom installed on it though.

we need a safe list with what apps can we delete... i did the same but i don't know for sure what to delete and what to keep... i mention that i don't use amazon apps nor i logged in..
Sent from my KFFOWI using XDA Forums

balanigga said:
we need a safe list with what apps can we delete... i did the same but i don't know for sure what to delete and what to keep... i mention that i don't use amazon apps nor i logged in..
Sent from my KFFOWI using XDA Forums
Click to expand...
Click to collapse
For the moment......
http://forum.xda-developers.com/showpost.php?p=63605889&postcount=77
If wants to remove more can give chmod 000 to apk & reboot before delete

What about reassigning the home button to a different launcher?

xT29c said:
What about reassigning the home button to a different launcher?
Click to expand...
Click to collapse
Just install another launcher and remove FireLauncher from system.

csolanol said:
Just install another launcher and remove FireLauncher from system.
Click to expand...
Click to collapse
Oh, nice. Okay, thanks!

csolanol said:
Just install another launcher and remove FireLauncher from system.
Click to expand...
Click to collapse
how can i do this? thanks in advance
Edit: nevermind I found it, thanks anyway

joelwylde said:
how can i do this? thanks in advance
Click to expand...
Click to collapse
You can use titanium backup, and remove it like that. I would make a backup firs though just in-case.
Also, I need help trying to unhide the firelauncher process. I have the command here "adb shell pm unhide [package:com.amazon.firelauncher]"
But I need the other command first so ADB can talk to my tablet. Because I ran the command, and it just says "true" when it should say "false".

joelwylde said:
how can i do this? thanks in advance
Click to expand...
Click to collapse
Working Launcher replacement thanks to @diegocr and @Awesomeslayerg ! Here's the steps:
1. See @diegocr post at http://forum.xda-developers.com/showpost.php?p=63599598&postcount=23 and download "boot-firelauncher.img"
2. Enable USB debugging
3. Install your launcher of choice!
4. On your computer, run
adb reboot bootloader
Click to expand...
Click to collapse
5. Once your tablet reboots in to fastboot, run on your computer (if you are not in the same directory as boot-firelauncher.img, put the full path):
fastboot boot boot-firelauncher.img
Click to expand...
Click to collapse
6. Tablet will reboot
7. Once booted open an adb shell:
adb shell
Click to expand...
Click to collapse
8. To back up the existing app, run:
cp /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk /sdcard/Download/com.amazon.firelauncher.apk
Click to expand...
Click to collapse
9. Then nuke it!
rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk
Click to expand...
Click to collapse
10. Now, run to restart your device:
reboot
Click to expand...
Click to collapse
Confirmed working on my tablet with FireOS 5.0.1.
Enjoy!
Forget all the formatting problems
Sent from my KFFOWI using Tapatalk

If you are already rooted you don't need to do all that stuff.
Just adb shell
su
mount -o remount,rw /system
rm -r /system/priv-app/com.amazon.firelauncher or whatever the package is called.
Reboot and it's done.
Remember to install a launcher before this.

csolanol said:
If you are already rooted you don't need to do all that stuff.
Just adb shell
su
mount -o remount,rw /system
rm -r /system/priv-app/com.amazon.firelauncher or whatever the package is called.
Reboot and it's done.
Remember to install a launcher before this.
Click to expand...
Click to collapse
Will this work if I hid the process with ADB before hand? If not, how do I unhide it? What command would I use before "adb shell pm unhide [package:com.amazon.firelauncher]"

Don't know, try if it works hiding, but I doubt it.

I want to replace the hosts file with the one of my Lenovo S660 (China phone). The S660 hosts file is about a mile long and has entries like "0.0.0.0 bad.ad.server" - a very basic but effective way to avoid a lot ads, even at apps. I have not yet took a closer look but I think I would create a mix of both files for the fire.
So, what are the steps?
I have done similar things to my rooted Sony Experia Tipo concerning modifying files at /system, which is mounted RO as default. So I remounted it RW with ES-Explorer, modified what I had to and mounted RO with ES-Explorer again.
I wonder, if this is ok, because of the security means the fire/android has.

I took a chance and I was successfull.
I attached the unchanged hosts file from my Lenovo S660 /system/etc/ as hosts.lenovo.zip file. The fire hosts has just 1 line: 127.0.0.1 localhost. The lenovo's hosts has 25858 lines.
Code:
- unzip hosts.lenovo.zip -> you get host.lenovo
- rename hosts.lenovo to hosts
- connect fire
- adb push hosts /data
- adb shell
- $ su -
- # cd /data
- # chmod 644 hosts
- # exit
- $ exit
- ES Explorer
- Enable root explorer
- remount /system rw
- go to /data
- mark hosts
- cut hosts (to memory)
- go to /system/etc
- mark hosts
- rename hosts to hosts.old
- insert hosts from memory
- remount /system ro
- exit ES Explorer
done.
should work, use at own risk.
Note: You cannot chmod 644 at /mnt/sdcard1 because it is vfat there, that's why you use /data.
Note: You cannot write to /system/etc while at adb shell, even if it is mounted RW, that's why you have to use ES Explorer which will ask you to choose the path with android overlay window - which makes it work (at least my experience).
If you have apps which showed ads before, then you might keep on seeing the very last forever. Or a broken link sign. Or even a popop with broken link sign. Or your ads hosts is missing at the lenovo hosts file and you keep on seeing ads. There even my be websites you cannot visit anymore - which I have not yet experienced, but the risk exists, or will come.
If interested, take a look at http://winhelp2002.mvps.org/hosts.htm for more information and use for your windows or linux pc.
If you don't like it you can go back, you have a copy of your old hosts file.

I want to replace the hosts file with the one of my Lenovo S660 (China phone). The S660 hosts file is about a mile long and has entries like "0.0.0.0 bad.ad.server" - a very basic but effective way to avoid a lot ads, even at apps.
Click to expand...
Click to collapse
Check out the adaway app (open source). It blocks ads through the host file just like you're doing except it puts the host file in place for you, combines host files from a couple different sources (running de-duplication on them) & auto updates your host file as new ad severs are added or removed. Absolutely beats rolling your own host file manually.

That is new information to me, thanks.