I am running bamf 1.6.3 remix.. I also am using Handcent sms.. I have synced and redownloaded handcent.. No matter how many times I try the sync won't catch.. The contact images remain little androids.
I Heard of a solution and tried to figure through it..
It appears the ROM Manager fix permissions script messed up the permissions on the thumbnails in the contacts folder. The files were mistakenly permissioned as 771 which meant the jpg thumbnail files were unreadable.
This is what I did to fix it:
1. Boot into clockworkmod recovery
2. Go into the mount/umount section
3. mount /system
4. mount /data
5. Connect usb data cable to computer from phone (I use linux so I don't need anything special in the way of drivers)
6. adb shell
7. mount /datadata
8. The above step may take a few seconds to mount
9. cd /datadata/com.android.providers.contacts
10. chmod og+rx *
11. cd files
12. chmod 664 *.jpg
13. cd /
14. umount /datadata
15. umount /data
16. exit
17. Reboot your phone
I ran into a problem at step 6...
I tried to access the adb shell from the command prompt on the computer I rooted my phone through..
When i typed adb shell into my prompt It could not recognize the device or the command.
-- Am I doing something wrong?? Is there Another solution? I love all the help everyone in forums give, it keeps a community running. I am just such a noob, one word lines never do me any good. A little explanation is GREATLY appreciated.
THANKS ALL.
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
jigz23 said:
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
Click to expand...
Click to collapse
I'm having the same issue. Did you ever get it figured out?
jigz23 said:
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
Click to expand...
Click to collapse
Could be a sign of a degrading internal memory, but is is extremely unlikely that a solid state memory device would fail like that.
You could try reformatting the internal sd via your pc while in CWM, and installing your RUU after that, provided you can see the internal drive.
Sent from my HTC Flyer P510e using XDA Premium HD app
Run these adb commands while in CWM when connected to pc , see if it helps :
adb remount
adb shell rm -rf /system/sd/dalvik-cache
adb shell format DATA:
adb shell format SYSTEM:
adb shell format CACHE:
adb shell format MISC:
Warning: THIS WILL ERASE ALL USER DATA. DO AT YOUR OWN RISK.
Then run your RUU and you should be back in working order.
Sent from my HTC Flyer P510e using XDA Premium HD app
mhkabir98 said:
Run these adb commands while in CWM when connected to pc , see if it helps :
adb remount
adb shell rm -rf /system/sd/dalvik-cache
adb shell format DATA:
adb shell format SYSTEM:
adb shell format CACHE:
adb shell format MISC:
Warning: THIS WILL ERASE ALL USER DATA. DO AT YOUR OWN RISK.
Then run your RUU and you should be back in working order.
Sent from my HTC Flyer P510e using XDA Premium HD app
Click to expand...
Click to collapse
This has been a looong time but I figured it was worth a try. I did all these commands and run into trouble once I get to the adb shell format data:. I get an error message saying "/sbin/sh: format: not found"
jigz23 said:
This has been a looong time but I figured it was worth a try. I did all these commands and run into trouble once I get to the adb shell format data:. I get an error message saying "/sbin/sh: format: not found"
Click to expand...
Click to collapse
I get the same thing
I picked up an Archos G9/80 and immediately came here to root it. Instead I wound up installing SDE and flashing Freezenooks G9 Build8 from tis thread: http://forum.xda-developers.com/showthread.php?t=2171742
I just have one problem. I can't get Dropbear SSH II to install. I tried both from the Play store and adb installing it. I even tried the older version. The apk installs fine but it fails to install the service. They both fail during a step where it says its remounting read-only. This is interesting as I notice that the rootfs is mounted read-write by default. From adb shell I tried to force it read-only with mount -o remount,ro but it fails as the Device is busy. I'm guessing this is the same problem that the installer is encountering and since it can't remount rootfs as read-only it proceeds to remove the binaries it's copied over. I've been trying to find out where it copies them before it deletes them. I assume they would be in /system/bin but I can't ever find them there. I gets to the error step way too fast.
Does anyone have any workarounds? Could / should I "borrow" the binaries from another Android box and copy everything to the correct place?
Hi I was attempted to updating to the newest Venom X+ rom and my phone got stuck in boot loop even after some other fixes, so I wiped the phone and have TWRP v2.4.1.0 on the phone but no rom. So I am trying to ADB sideload the .zip however at around 20% it says "failed to write to protocol (no status).
Anyone know why this is? Happens on multiple ROM's.
--edit--
used
adb shell mount -t tmpfs none /sdcard
adb push ROM.zip /sdcard
Got the Zip onto the device but /system and /cache won't mount *least progress is made*
HTC MTP drivers not installing correctly, maybe related to why I can't ADP all the way
So I've been tinkering around with CM12.1 on this watch for a while (since I switched my phone from the Samsung Galaxy Note 4 to the Xiaomi Mi Max) and yesterday decided to give Android Wear another try (note: I had the LG G Watch back in the really early Android Wear days) and there have been quite a few tweaks that I decided to apply so will share them all here as I remember them.
Android Wear:
Gaining root:
Since we can not use systemless SuperSU (because we can't edit the kernel on the go) like the other watches we need to use a system only root method so I will share how to do that:
You can do this either manually by creating a .supersu containing "SYSTEMLESS=false" file in /system/ before flashing Wear SuperSU or just flash the zip from here before the SuperSU Wear zip: https://forum.xda-developers.com/android/software-hacking/root-disabler-t3370794
Also here is the latest SuperSU Wear zip file: https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Note: you will have a Busybox app installed when you boot AW, you need to connect to Wi-Fi to be able to use it, otherwise it will crash.
Note 2: If you are connected to the phone via Bluetooth the Wi-Fi will automatically disconnect but you can disable this behavior in Developer Options on the watch.
Disabling touch to wake:
This was really annoying for me, I only want the device to wake by pressing the button not when I tilt the watch or touch the screen since that means the watch will be waking up uselessly a lot, tilt to wake can be disabled from the Android Wear app on the phone but for disabling touch to wake you need to edit some system files.
Note: this requires either having root or booting into TWRP and being connected to a PC using either Bluetooth ADB or the watch with the cradle and an USB cable.
AW+root method:
With the watch connected to the computer using either ADB over Bluetooth or the USB cable do the following in a shell:
Code:
adb pull /system/usr/idc/sec_touchscreen.idc
Now you will get the sec_touchscreen.idc file on your PC, open it using Notepad++/gedit/some other Linux EOF format compatible text editor (NOT NORMAL NOTEPAD OR ANY MICROSOFT OFFICE APP!!!!)
The last line should look like:
Code:
touch.wake=1
Just delete that line or set it to 0 and save the file.
Now back to the shell:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push sec_touchscreen.idc /system/usr/idc/
Code:
adb reboot
Done, now touching the screen will no longer wake up the device.
TWRP method:
Boot the watch in TWRP and connect it to the PC using the cradle and an USB cable then do these commands in a shell:
Code:
adb shell "twrp mount system"
Code:
adb pull /system/usr/idc/sec_touchscreen.idc
Now you will get the sec_touchscreen.idc file on your PC, open it using Notepad++/gedit/some other Linux EOF format compatible text editor (NOT NORMAL NOTEPAD OR ANY MICROSOFT OFFICE APP!!!!)
The last line should look like:
Code:
touch.wake=1
Just delete that line or set it to 0 and save the file.
Now back to the shell:
Code:
adb push sec_touchscreen.idc /system/usr/idc/
Code:
adb reboot
Done, now touching the screen will no longer wake up the device.
I am not sure if this is a problem with AW or the AW kernel with TWRP or it was just me but TWRP didn't display properly for me after I switched from CM12.1 to AW (it would only display till I clicked something then screen turns off) so I will post how to flash the zip files without being able to see TWRP:
You will need to be connected to a computer that has ADB setup for this.
The one thing you need to actually do on TWRP on the watch is select the "never ask again" and swipe to allow system modifications on the first run of TWRP. Note that after you click to tick the "never ask again" check box the screen will already go black so remember the layout so that you'll be able to swipe the slider.
Now you will open a shell on the PC and "adb shell" to the watch that is connected with an USB cable and the charging cradle.
Now you are in the TWRP shell so do these commands:
Code:
twrp mount system
Code:
twrp install /sdcard/disable_systemless_root.zip
Code:
twrp install /sdcard/SuperSU-2.78-wear.zip
Code:
twrp wipe cache
Code:
twrp wipe dalvik
Code:
reboot
NOTE: This assumes that you have put the zips from the first post in the internal storage of the device for which /sdcard/ is a mount point.
Will post more stuff soon, just wanted to post the tutorial on how to root AW for now, I'll be leaving home soon so I'll be back to post the rest of the stuff later today.
As a secondary note right now I am trying to port some AW 2.0 apps to work on 1.5 but we'll see how that goes, don't get your hopes up.
When i try push file adb say: read only file system
I write this and now it's ok:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /system
exit
adb push sec_touchscreen.idc /system/usr/idc/
Thesebax4 said:
When i try push file adb say: read only file system
I write this and now it's ok:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /system
exit
adb push sec_touchscreen.idc /system/usr/idc/
Click to expand...
Click to collapse
Why did you add that /dev/block/mmcblk0p25?
The right command is:
Code:
mount - o remount,rw /system
Also did you first root your device?
I never needed to add anything, that's why I'm asking?
I don't have root. TWRP ask me to make system writable, i try to swipe (yes) but screen goes black... Maybe this is fault. I search this in google https://forum.xda-developers.com/showthread.php?t=1749657 (second post) I change the partition from mmcblk0p1 to mmcblk0p25 because gear s have /system under mmcblk0p25. And this working for me.
Thesebax4 said:
I don't have root. TWRP ask me to make system writable, i try to swipe (yes) but screen goes black... Maybe this is fault. I search this in google https://forum.xda-developers.com/showthread.php?t=1749657 (second post) I change the partition from mmcblk0p1 to mmcblk0p25 because gear s have /system under mmcblk0p25. And this working for me.
Click to expand...
Click to collapse
Ah, I was thinking you were in AW not TWRP, as I said in the 2nd post you have to swipe on the black screen, you will feel a vibration, for me both methods work properly without the extra mounting.
I've installed recovery and Android wear os, but due to Heavy battery drainage and no phone audio I'm trying to Go back to stock.
I've tried flashing Stock firmware Using Odin but after flashing when the watch boot up, after Samsung gear s logo screen Goes blank and after few seconds Samsung animation comes Up but doesn't complete the animation anf Goes blank again.
I need help to fix this.
Thanks in advance