Since we're using ODIN, atm. I thought we should post a thread regarding ADB for doing basic functions normally accessed via Clockwork. Just make sure you're rooted and have USB Debugging enabled. Also note that you need to be booted into recovery mode.
This is just a couple of basic things I've found via Google. Anyone who knows more... etc... feel free to add or contribute corrections.
Format Partitions:
adb shell
format SYSTEM:
format DATA:
format CACHE:
Wipe Dalvik Cache:
adb shell
mount /data
rm -rf /data/dalvik-cache/*
Get Android SDK here:
http://developer.android.com/sdk/index.html
Get Java SDK here:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
ADB Command Directory here:
http://developer.android.com/guide/developing/tools/adb.html#commandsummary
http://android-dls.com/wiki/index.php?title=ADB
Install to SD card by default
Have the Android Market on Froyo install to the SD card by default for apps which support it.
Code:
adb shell pm setInstallLocation 2
Hi,
i installed Shadow Hawk, but Wifi doesn´t work. It´s because of the Hyperion Kernel. I just don´t know how to "replace the broadcom module inside /system/etc/lib/modules". Because i used HTCDev(il) to unlock, i flash boot.img with fastboot. But how do i replace the broadcom module?
Please help!
Given your handset is S-OFF, either,
- Hard way :
Use android SDK adb to mount system RW and push module file :
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p25 /system
adb pull c:\bcm4329.ko /system/lib/modules/bcm4329.ko
- Easy way :
Just use ES file explorer, enable root R/W mode and copy/paste bcm4329.ko into /system/lib/modules
And then reboot.
dmfr said:
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p25 /system
adb pull c:\bcm4329.ko /system/lib/modules/bcm4329.ko
And then reboot.
Click to expand...
Click to collapse
If you use adb, those are not the commands. Should be:
adb remount
adb push :\bcm4329.ko /system/lib/modules/bcm4329.ko
In your first line you were trying to mount a yaffs2 filesystem, when it's probably a ext4 one. The "remount" option will work regardless of the fs.
Ths second line is fairly obvious, you want to push the file to the rom, not pull it from there.
Also, if you S-ON and flashed the rom, the broadcom module was flashed, it's just boot.img that gets left out. This means that when you manualy flash boot.img with fastboot, you don't need to update anything else.
So: Check in system settings if you actually flashed the kernel. It must say "Hyperion V2.XXX", or whatever version was included. If it is, wifi must work, if not, you messed something up on the fastboot flash procedure.
Cheers
will try later, thank you.
ICS Quattro Rom worked including Wifi..
update:
working now.
"Please follow these steps in the same order (I'm shouting) :
1. Boot into recovery
2. Format System (not wipe option but format option !!!)
3. Format Data
4. Format Cache then Format Boot
5. Wipe Data/Factory reset (1st option in wipe/format menu)
6. Wipe Dalvik Cache
Next if you have some wiping utility like Full Wipe 1.5 Ext4 for Saga.zip...run that by selecting install zip from sd card and installing the zip...
7. Now install zip from sd card and flash the rom
8. If any kernel flash it as well
9. Now reboot (Note don't flash any tweaks like transparent notification except gapps if required)
10. Now setup your phone
11. Reboot into recovery
12. Now go into advanced fix permissions and then any tweaks you want (Note whether mentioned or not always wipe Dalvik Cache before installing tweak zip)
13. Voila everything would work perfect 100%.... "
did follow these instructions.
flashed boot.img
having a fast and stable rom now hopefully. ICS wasnt stable enough. especially browser.
Hi Folks,
By request from a friend i've created a sh script to move all [email protected] dalvik cache files to /cache/dalvik-cache because some roms store [email protected] dalvik files in /data/dalvik-cache. So for those that need or wont to save some space in /system follow this steps:
1 - You need a rooted phone
2 - You need terminal emulator
3 - Download script from here
4 - Open terminal, navigate to where you downloaded the script and run sh dalvik.sh
5 - Reboot
!!Warning!!
Only run script in roms that store [email protected] dalvik files in /data/dalvik-cache otherwise you will experience some bugs in aplications.
Please post your feedback please
Thanks to HeD_pE for testing!
Cheers,
h4ck3dm1nd
Fairly straightforward question. Is it possible to disable ART and re-enable Dalvik other than via the settings dialog, either via ADB, some sort of flashable zip or from a recovery?
I ask for two reasons. Firstly, when I flashed an experimental 4.4 build on my Galaxy Nexus, I made the mistake of enabling ART. When I restarted, because I'd stupidly flashed an incompatible gapps package, apps would force close so frequently that the constant notifications made it extremely difficult to get into the settings and turn it off again.
Secondly, I just saw a thread on Reddit where somebody was claiming that their Nexus 5 went into a bootloop after enabling ART, and they had to do a wipe to fix it.
So it seems to me it would be quite helpful to be able to disable or enable ART without having to be able to boot.
If you've found a way to fix this, I would love to know. I just turned ART on after installing a new rom, and I'm stuck in a boot loop without a recent backup.
+1
I've enabled ART on my Nexus 4 without issue. Stock ROM.
Enabling it on my 2013 Nexus 7 caused it not to boot past the boot animation anymore.
Just reflash the ROM from recovery. Wipe system and flash. Done. Dalvik will be enabled again. If your not rooted that's another matter but the OP seems to be.
theesotericone said:
Just reflash the ROM from recovery. Wipe system and flash. Done. Dalvik will be enabled again. If your not rooted that's another matter but the OP seems to be.
Click to expand...
Click to collapse
I figured flashing wiping would do it but wasn't willing to wipe if there's an easier solution.
In my case it was Xposed. I flashed the disable zip and that did it. Guess I didn't reboot fully after disabling it from in the ROM.
He said wipe system, not data. It is possible to wipe the system information and leave your data intact.
MisterEff said:
He said wipe system, not data. It is possible to wipe the system information and leave your data intact.
Click to expand...
Click to collapse
Ah yes. I mistook system as data..
I don't know if it allow to switch runtime, but it helps me to avoid bootloop after ota 4.4.2 on my Nexus 5.
To check current library
adb shell getprop persist.sys.dalvik.vm.lib
To set art one
adb shell setprop persist.sys.dalvik.vm.lib libart.so
(IRoN) said:
I don't know if it allow to switch runtime, but it helps me to avoid bootloop after ota 4.4.2 on my Nexus 5.
To check current library
adb shell getprop persist.sys.dalvik.vm.lib
To set art one
adb shell setprop persist.sys.dalvik.vm.lib libart.so
Click to expand...
Click to collapse
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
THANK YOU!!!! It worked for me
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
Thanx, it worked for me
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
It worked for me too, and I don't even use Nexus device, And done it from adb but in recovery mode with properly mounted partitions.
Thx again.
Boot into Recovery and Fix Permissions has fixed this for me (Galaxy Nexus)
EDIT: Apparently that switches it back to dalvik?!?
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
Thanks, this help save my day !
Saved my day too! HTCONE on Viper and I was able to use twrp and a USB otg drive. Thanks!
Sent from my HTCONE using Tapatalk
Quicker way to switch back to Dalvik
My phone was stuck in a bootloop because I did not have enough free space to switch to ART, making my device crash on boot. For a quick way to switch back to Dalvik, see below.
Boot into recovery ('adb reboot recovery' if possible), then mount /data and run this command:
Code:
adb shell "echo libdvm.so > /data/property/persist.sys.dalvik.vm.lib"
adb reboot
It will now be in Dalvik. Enjoy
I've just tested ART feature from friend's recommendation. After activating ART in my CM11 ROM, NFC and Themes Provider keep crashing and phone is not usable. So I think it's good idea to share how to revert ART setting without wiping phone or restore from backup.
Instructions to revert ART
1. Boot into recovery.
2. Run adb shell to access terminal.
3. Type 'rm /data/property/persist.sys.dalvik.vm.lib' This will remove setting default VM runtime to ART.
4. Clear Dalvik cache and reboot. Your phone should run normally now.
Instructions to set ART again
1. Boot into recovery.
2. Run adb shell to access terminal.
3. Type 'echo "libart.so" > /data/property/persist.sys.dalvik.vm.lib' This set default VM to art library file.
4. Clear Dalvik cache and reboot. Your phone should run with ART VM now.
Hope this helps.
tested on huawei honor (u8860)
[email protected]:~$ adb shell
~ # echo "libart.so" > /data/property/persist.sys.dalvik.vm.lib
/sbin/sh: can't create /data/property/persist.sys.dalvik.vm.lib: nonexistent directory
any suggestion? thank you.
hi.
the solution to get art fully working was the following one:
replacing dalvik.vm.dexopt-data-only=0 with dalvik.vm.dexopt-data-only=1 and all went fine...(build.prop)
at least it worked for me. hope it would help.
You need to mount the data partition before running the commands mentioned in the first post there...
This saved my ass! Switched to ART and after reboot, settings would only FC. Could not change anything or switch back through Dev Options. Thank you!!!!
Sent from my HTC6525LVW using Tapatalk
Thanks for the instruction. You save me as I don't have PC now and my custom ROM not support ART.
excuse me, i've been try to switch to art with adb shell, and my phone is boot up but can't get into home screen, it just stuck on starting apps? why ya?