Related
So I decided to fumble around a bit with my incredible, I read about the hosts file for blocking ads here and noticed that I would get permission denied errors, then when i had the phone with the screen on, did adb shell from a command prompt I got the super user permissions screen on my device.
now I was able to run the mount commands successfully, and as far as testing I was able to do mv /etc/hosts /etc/oldmaid and it took. however when I try to mv the other hosts file i get an error about a cross linked device. so i try doing a cat /sdcard/hosts.for.mobile.txt > /etc/hosts and get an error about the device not having sufficient space.
Anyone have any input on this? I know a cooked rom will already have this hosts file in it, but i'm trying to see if i can't get it going now.
Thanks!
I do not have one yet but what commands are available? Can you "locate hosts" or "find / -name hosts"
nm try this file "/system/etc/hosts" <-- stated in xda forums 3772987&postcount=5 Hope this is what you were looking for.
You are getting that error due to the fact that nand protection is still enabled. We need to flash a boot image with ro.secure=0 to be able to write to everything in /system.
ihtfp69 said:
You are getting that error due to the fact that nand protection is still enabled. We need to flash a boot image with ro.secure=0 to be able to write to everything in /system.
Click to expand...
Click to collapse
Ah, that would explain it. Thanks for the info!
Hello All,
I just updated my ROM to CR_Mod_2.13.531.1_OTA's
And then when I went to reboot into recovery I got the red Triangle exclamation, and thus decided to reflash my recovery image by using the terminal, and even in adb, I get "Flash_image" command not found, and I've tried googling (So please spare me the rude comments about learning to use it) and come with little to luck with finding a method of what went wrong with this. If anyone can shed some light on this, and what I can do to fix it so I can get into my recovery again would be a great help.
-Thanks
soulysephiroth said:
Hello All,
I just updated my ROM to CR_Mod_2.13.531.1_OTA's
And then when I went to reboot into recovery I got the red Triangle exclamation, and thus decided to reflash my recovery image by using the terminal, and even in adb, I get "Flash_image" command not found, and I've tried googling (So please spare me the rude comments about learning to use it) and come with little to luck with finding a method of what went wrong with this. If anyone can shed some light on this, and what I can do to fix it so I can get into my recovery again would be a great help.
-Thanks
Click to expand...
Click to collapse
same here friend when i find teh answer ill be sure to let u know
so when in terminal to try place Flash_image into /system/bin:
cp /sdcard/flash_image /system/bin
I get:
cp: can't create ' /system/bin/flash_image ' cannot allocate memory
When you get to the triangle with the Exclamation point
All you have to do is stay at that screen and click
VOLUME UP and POWER
then it will show you the options.
soulysephiroth said:
so when in terminal to try place Flash_image into /system/bin:
cp /sdcard/flash_image /system/bin
I get:
cp: can't create ' /system/bin/flash_image ' cannot allocate memory
Click to expand...
Click to collapse
You have to have s-off and /system mounted as r/w to do that. Otherwise you have to push it to /system/bin while in clockwork recovery.
@ xologist, I think they're looking to flash the clockwork recovery image, not the update.zip and stock recovery old way.
To mount system r/w within android tyoe mount -o rw,remount /system and try the copy again.
Sent from my T-Mobile myTouch 3G Slide
Well thats problem, I can't even access my recovey, thats why I'm trying to flash a new image. everytime I try I always get
"Error writing recovery: No space left on device"
soulysephiroth said:
Well thats problem, I can't even access my recovey, thats why I'm trying to flash a new image. everytime I try I always get
"Error writing recovery: No space left on device"
Click to expand...
Click to collapse
That means you don't have s-off. There's a stickied thread in the development section, an alpharev live linux CD that you can use to patch your phone's bootloader to allow you to write to protected partitions like /system, recovery, etc.
Hello!
I'm new to this forum so i hope I'm putting my question in the right place on this forum.
I own a HTC Desire that is rooted with Cyanogenmod 7.1.0.-Desire ROM (S-ON) and i can't get AdFree to work - ads and banners in apps are not blocked at all. In Adfree app's Options i pot a 'tick' on all options, including on "Use /data/data/hosts symlink" and the one below that one.
I also tried to make a host file through adb ("cp /sdcard/hosts /data/data/hosts") but i get the message "cp: can't stat 'sdcard/hosts': No such file or directory".
I tried installing AdAway app, but that doesn't work either since the phone has to be S-Off if I'm not mistaking...
So has someone here had similar experience with Desire on Cyanogen and AdFree? Haw can I get it to work? Is the only solution S-Off?
Thanks for help!!
Hi,
did you restart the device? Also you must press the "Download & Install Hosts" button so the hosts file is edited.
I personally have the first two options checked (Check for updates and Autoupdate). Always after tapping the button I get noticed that I may need to restart the device to clear DNS cache. Everything works perfectly for me, no ads at all. But I use Sense ROM.
Yes i did restart several times after tapping "download and install hosts" but after restart nothing changes that's why I'm asking what to do next...
I think there is no "hosts" file on the SD card. Could that be a part of the problem?
With S-ON, Adfree is not working.
Only 2 possibilities
1. Either make S-OFF and retry Adfree
2. Do manual symlink for hosts from system to etc via adb in fastboot mode
2. Do manual symlink for hosts from system to etc via adb in fastboot mode
Click to expand...
Click to collapse
Thanks for the reply. I'll try the 2nd option first. Actually i did try it and i got the error message in cmd: "cp: can't stat 'sdcard/hosts': No such file or directory", as i described in post #1. Why do i get that message?
I followed a guide from a forum where they described the process for AdFree on HTC incredible but to clarify my steps:
I downloaded Adfree from the market, tapped to download and install... then got the message to reboot because i need to clear my DNS cache. Powered down the phone, powered up by holding volume down button, got into clockwork recovery, mounted /system, /data, /sdcard
connected phone via usb, got cmd up, got into adb shell and typed in the command but got the error message...
Am i doing something wrong?
Can someone guide me through the process? thanks!
acimer said:
Thanks for the reply. I'll try the 2nd option first. Actually i did try it and i got the error message in cmd: "cp: can't stat 'sdcard/hosts': No such file or directory", as i described in post #1. Why do i get that message?
I followed a guide from a forum where they described the process for AdFree on HTC incredible but to clarify my steps:
I downloaded Adfree from the market, tapped to download and install... then got the message to reboot because i need to clear my DNS cache. Powered down the phone, powered up by holding volume down button, got into clockwork recovery, mounted /system, /data, /sdcard
connected phone via usb, got cmd up, got into adb shell and typed in the command but got the error message...
Am i doing something wrong?
Can someone guide me through the process? thanks!
Click to expand...
Click to collapse
via adb, copy the hosts file from /system/etc/ to /sdcard.
Then use symlink option.
or you can get the hosts file from the below link
http://forum.xda-developers.com/showthread.php?t=696084
You can see the below thread for more help.
http://forum.xda-developers.com/showpost.php?p=9609932&postcount=10
May be this app help you:
http://adfree.bigtincan.com/adfree.apk
Hello!
I flashed CM9 nightly on my GSM Galaxy Nexus a few days ago, and it has worked like a charm ever since. Until a few hours ago, that is...
I dug around in the CM-specific settings and (unfortunately!) ended up finding the Advanced settings, more specifically the CPU frequency setting. Just to see how it would handle things, I tried setting the max. frequency to 350 MHz (aka the default min. frequency). I was very surprised to see that the game Road Trip worked perfectly, and so I chose to keep it this way to save energy; I ticked "restore on boot". Later on, the phone rebooted during a phone call, but I thought, "oh, it's a nightly, this is to be expected."
What I noticed a few seconds thereafter (what is my real problem) is that the boot animation froze a few cycles in (after running at full fps for about one cycle), and the phone rebooted again, running into the same problem.
I still have this issue, even after factory resetting and reflashing the nightly (which I thought would remove the freq. "lock", but didn't).
Does anyone know how I can fix this? Is it as easy (or hard, because I can't access the actual system) as flashing some CPU-fixing ROM, or do I need to do something more, even send it to repair?
Thank you guys!
Go to revovry.
Go to Mounts and storage.
Format /system.
Format /cache.
Format /data.
Flash rom.
Flash Gapps.
Wipe data/factory reset.
Reboot.
tingen said:
Go to revovry.
Go to Mounts and storage.
Format /system.
Format /cache.
Format /data.
Flash rom.
Flash Gapps.
Wipe data/factory reset.
Reboot.
Click to expand...
Click to collapse
Did that, but the problem persists.
Anything else I can try?
swefse said:
Did that, but the problem persists.
Anything else I can try?
Click to expand...
Click to collapse
You have to wipe the init.d file.. in there is the script that is locking your boot settings...
zapford said:
You have to wipe the init.d file.. in there is the script that is locking your boot settings...
Click to expand...
Click to collapse
How exactly do I do that? From some advanced menu in CWM or somewhere else?
Now I got some help over on Google+:
Adb remount
Adb shell
rm /system/etc/Init.d
Click to expand...
Click to collapse
but the last command gives me a no such file or directory...
Where in the system structure is init.d?
swefse said:
Now I got some help over on Google+:
but the last command gives me a no such file or directory...
Where in the system structure is init.d?
Click to expand...
Click to collapse
'adb shell'
'su'
'rm -rf /system/etc/init.d/' - folder/file names in android (as in Linux) are case-sensitive.
if it still gives you "file or folder not found"
'ls /system/etc/i*'
do you see /system/etc/init.d/ or not? if not, either your current rom hasn't created that folder yet (case of AOPK comes to mind, user had to create dir manually), or it doesn't support init.d scripts at all.
bk201doesntexist said:
'adb shell'
'su'
'rm -rf /system/etc/init.d/' - folder/file names in android (as in Linux) are case-sensitive.
Click to expand...
Click to collapse
'su' might have worked (it said
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
'rm -rf /system/etc/init.d/' returned
rm -rf /system/etc/init.d/
Click to expand...
Click to collapse
Does this mean it worked, and that it is safe to reboot?
EDIT: Rebooted, problem persists...
Can I check to see if init.d is removed from adb?
Should be, give it a try.
BTW, booting a device is cpu intensive, hence the boot loops at low frequency
swefse said:
EDIT: Rebooted, problem persists...
Can I check to see if init.d is removed from adb?
Click to expand...
Click to collapse
@ Tubes6al4v:
Nope, didn't work.
Btw, 'ls /system' returns
bin
Click to expand...
Click to collapse
Is that normal?
My failsafe is to use fastboot to push a stock image over. Just keep in mind it will wipe your sd card.
Tubes6al4v said:
My failsafe is to use fastboot to push a stock image over. Just keep in mind it will wipe your sd card.
Click to expand...
Click to collapse
So I'll follow this guide?
http://forum.xda-developers.com/showthread.php?t=1366806
Just one more n00b question: Can I pick whichever image I want, even though my phone came with 4.0.1?
If not, how do I know if it's ITL4D or ITL4F?
swefse said:
'su' might have worked (it said
'rm -rf /system/etc/init.d/' returned
Does this mean it worked, and that it is safe to reboot?
EDIT: Rebooted, problem persists...
Can I check to see if init.d is removed from adb?
Click to expand...
Click to collapse
if 'su' errors, then you don't have su binary installed. you wouldn't be able to delete /system/etc/init.d even if it was there. you should see a lot more stuff inside /system/ though.
swefse said:
So I'll follow this guide?
http://forum.xda-developers.com/showthread.php?t=1366806
Just one more n00b question: Can I pick whichever image I want, even though my phone came with 4.0.1?
If not, how do I know if it's ITL4D or ITL4F?
Click to expand...
Click to collapse
before you go restoring to stock, go in bootloader and try:
'./fastboot erase cache'
'./fastboot erase userdata'
see if it boots.
'adb logcat >> logcat.txt' would help debugging as to why the device is bootlooping as well.
Or is it easier to use this, and not have to worry about what version it is/was?
http://forum.xda-developers.com/showthread.php?t=1392310
swefse said:
Or is it easier to use this, and not have to worry about what version it is/was?
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
that's your choice. if you do use that toolkit (or any toolkit, for that matter), read instructions well.
I was redirected to this guide to get the fastboot drivers (and fastboot): http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
When I open "install-superboot-windows.bat", though, it says "waiting for device", and stops there.
Should I just have downloaded it and continued with the first guide (linked a few posts above), or should I have clicked "install-superboot-windows.bat"?
Edit: Now when I tried "install-superboot-windows" a second time, it rebooted the phone, but into Android (resulting in the usual freeze-reboot). I'm stuck, please help me!
Now I tried flashing MCR Ir9, which I had laying around on the internal memory, but it screwed up even worse: Now I don't even get past the first "Google" + unlocked boot loader icon screen.
Should I maybe just send it to Samsung, and foot the bill, before I brick it forever (if I haven't already, that is), or do you guys know what to do?
swefse said:
Now I tried flashing MCR Ir9, which I had laying around on the internal memory, but it screwed up even worse: Now I don't even get past the first "Google" + unlocked boot loader icon screen.
Should I maybe just send it to Samsung, and foot the bill, before I brick it forever (if I haven't already, that is), or do you guys know what to do?
Click to expand...
Click to collapse
Pull batery, VOLUP+VOLDOWN+POWER into fastboot/bootloader. Reflash stock with fastboot.
bk201doesntexist said:
Pull batery, VOLUP+VOLDOWN+POWER into fastboot/bootloader. Reflash stock with fastboot.
Click to expand...
Click to collapse
I'll try that, and let you know how it works. Thank you!
Now it was successfully recovered and works again, thanks to fastboot and the wonderful convincing of you, bk201doesntexist!
Thank you!
http://android.clients.google.com/p...ned-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
to update:
Go into a shell on the watch with su and...
mount -o rw,remount /dev/block/mmcblk0p15 /cache
mv /sdcard/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip /cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
Nice ty
See above
abuttino said:
See above
Click to expand...
Click to collapse
I was trying to do it thought ADB I'm just new to this and I ended up re posting in the wrong thread.
Im Not new to flashing via recover on phones but on adb through commands I always feel sketchy about it.
I keep getting permission denied
Ive ran root a few times I have the drivers install right for sure not sure what im doing wrong
NUGZZ420 said:
I keep getting permission denied
Ive ran root a few times I have the drivers install right for sure not sure what im doing wrong
Click to expand...
Click to collapse
Throw an "su" command in the shell before anything else. It will only work if you're rooted.
I don't really get it how to connect via shell to my watch. Is it the same as installing apk's over adb bluetooth debugging bridge?
Could you provide further instructions how to install the update manually?
Thanks!
Kamekazegoldi said:
I don't really get it how to connect via shell to my watch. Is it the same as installing apk's over adb bluetooth debugging bridge?
Could you provide further instructions how to install the update manually?
Thanks!
Click to expand...
Click to collapse
Is your watch rooted? If not, you can't do it
No further questions thanks!
abuttino said:
http://android.clients.google.com/p...ned-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
to update:
Go into a shell on the watch with su and...
mount -o rw,remount /dev/block/mmcblk0p15 /cache
mv /sdcard/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip /cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
Click to expand...
Click to collapse
Worked (almost) perfect! Except, the "mv" command caused it to error out with "Invalid Arguement:Cross-Device Link" (Due to the implementation of blocked cross device linking with the mv command, bypassable by just cp'ing) Just replaced it with "cp" and the problem was solved.
Though this has already been said, the 4.4w1 insecure boot.img no longer roots 5.0.1. Probably due to incompatibilliuies, I'll work up a new rooted boot.img this weekend. Sadly looks like its going to require flashing the boot.img, not just booting it.
How do you go on a shell on your watch?
You have to have the bootloader unlocked and rooted hooked up via Modded USB cable. Then use the super tool script iin the dev section to install drivers for fastboot. Then back out to that folder make sure you not clicked on anything right click anywhere I think but I right click on the fastboot file while holding the SHIFT key and open in command window the type adb devices to make sure you hooked up right and you have accepted it on your phone Witch you must click accept the adb on your phone to accept the computer access. Once you know your hooked up right type adb shell and boom there you go.
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Prfndhatrdofman said:
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Click to expand...
Click to collapse
Try this its what worked for me
coming from KNX01S, but I keep running into "Status 7" with the stock recovery and "Error executing updater script" with TWRP. Anybody have any better luck flashing this?
SOLVED!: I removed the get prop lines in the beginning of the update script and sideloaded in TWRP!
If anybody would like the modified package it can be found here: https://dl.dropboxusercontent.com/u/...360/update.zip
This was not my fix only copied and pasted
NUGZZ420 said:
Try this its what worked for me
coming from KNX01S, but I keep running into "Status 7" with the stock recovery and "Error executing updater script" with TWRP. Anybody have any better luck flashing this?
SOLVED!: I removed the get prop lines in the beginning of the update script and sideloaded in TWRP!
If anybody would like the modified package it can be found here: https://dl.dropboxusercontent.com/u/...360/update.zip
This was not my fix only copied and pasted
Click to expand...
Click to collapse
That Dropbox link seems to be down, do you still have that modified TWRP zip?
Found the original post, here's the original link: https://dl.dropboxusercontent.com/u/9407677/Moto 360/update.zip
Looks like the link text got shortened when copying/pasting, but it's all good now! Thanks for sharing!
Prfndhatrdofman said:
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Click to expand...
Click to collapse
Make sure your using "/cache" instead of "/cache/"
nissanskylinebam said:
That Dropbox link seems to be down, do you still have that modified TWRP zip?
Found the original post, here's the original link: https://dl.dropboxusercontent.com/u/9407677/Moto 360/update.zip
Looks like the link text got shortened when copying/pasting, but it's all good now! Thanks for sharing!
Click to expand...
Click to collapse
Sorry I had been running all day and beat here my own just in case it helps same zip just my own link
5.0.1 update zip Mirror https://www.dropbox.com/s/naliirhnblh6ihg/update.zip?dl=0
npjohnson said:
Worked (almost) perfect! Except, the "mv" command caused it to error out with "Invalid Arguement:Cross-Device Link" (Due to the implementation of blocked cross device linking with the mv command, bypassable by just cp'ing) Just replaced it with "cp" and the problem was solved.
Though this has already been said, the 4.4w1 insecure boot.img no longer roots 5.0.1. Probably due to incompatibilliuies, I'll work up a new rooted boot.img this weekend. Sadly looks like its going to require flashing the boot.img, not just booting it.
Click to expand...
Click to collapse
Look forward to flashing the Rooted boot.img.
Thank you for doing it.
Update Today
In past day i have update to 5.0.1 LWX48P release. Today i have received automatic update on my watch to 5.0.1 LWX48T release. I don't know what is change but in past day I noticed a problem centering of my display; after update now the display is centered
http://shabbypenguin.com/?developer=Tools&folder=Superuser
flash that in TWRP to get root
latest update: https://mega.co.nz/#!dNBnyT7Q!qtPkmgOV-jrajJAAKDLE6cQWVHyDGi3OsEwmTq5jfOU LWX48T-from-LWX48P follow OP's instructions but change teh file names