How do you know once you boot in, Voodoo is running? Each time I reboot to recovery and go to the Voodoo area in CWM 2.5.1, i see the message that Voodoo is Disable and on next reboot to Enable. Default is set to Enable and Lagfix is set to Enable.
So if next reboot is set to enable, if I reboot to recovery again, the same message above is stated. Does recovery mode auto disable Voodoo?
Using SC2.7, but noticed this since I starting using Voodoo since SC 2.3
Delete the file 'disable_lagfix' in the Voodoo folder on your SDcard (deleting the entire folder is fine), if that file exists Voodoo will automatically be disabled.
You can manually check by opening up terminal emulator and running mount and checking the output to see whether there's any references to rfs (if there are, you don't have Voodoo on, if there's none, you appear to be running Voodoo). If you understand the formatting of mount, you could also check to make sure the various real filesystems (there's also several logical ones listed) are using ext4 as their filesystem.
KitsuneKnight said:
Delete the file 'disable_lagfix' in the Voodoo folder on your SDcard (deleting the entire folder is fine), if that file exists Voodoo will automatically be disabled.
You can manually check by opening up terminal emulator and running mount and checking the output to see whether there's any references to rfs (if there are, you don't have Voodoo on, if there's none, you appear to be running Voodoo). If you understand the formatting of mount, you could also check to make sure the various real filesystems (there's also several logical ones listed) are using ext4 as their filesystem.
Click to expand...
Click to collapse
There is no file disable_lagfix in that folder. Just a subfolder LOGs
smilepak said:
There is no file disable_lagfix in that folder. Just a subfolder LOGs
Click to expand...
Click to collapse
There is a voodoo_history_log.txt file that folder, well there is in mine at least. Click on it and at the bottom it should have a statements that looks something like below. I'm assuming Voodoo is enabled on mine.
2011-03-02 16:45:27 model detected: fascinate
2011-03-02 16:45:27 option: lagfix enabled
2011-03-02 16:45:27 option: lagfix is allowed to convert /system to Ext4
2011-03-02 16:45:27 option: debug mode enabled
My question is. Is debug mode supposed to be enabled?
smilepak said:
There is no file disable_lagfix in that folder. Just a subfolder LOGs
Click to expand...
Click to collapse
Use terminal emulator and try...
su
mount | grep ext4
If no ext4 reported anywhere you are not voodooed. Match you actual state by creating the file "disable-lagfix" in your voodoo folder then reboot into recovery to verify your voodoo status had been corrected.
beray5 said:
Use terminal emulator and try...
su
mount | grep ext4
If no ext4 reported anywhere you are not voodooed. Match you actual state by creating the file "disable-lagfix" in your voodoo folder then reboot into recovery to verify your voodoo status had been corrected.
Click to expand...
Click to collapse
That worked for me. I'm voodoo enabled. Thanks!
beray5 said:
Use terminal emulator and try...
su
mount | grep ext4
If no ext4 reported anywhere you are not voodooed. Match you actual state by creating the file "disable-lagfix" in your voodoo folder then reboot into recovery to verify your voodoo status had been corrected.
Click to expand...
Click to collapse
That gave me result, so I assume I am on voodoo. Thanks.
Run quadrant and check your score. If voodoo is enabled, it will be around 1500. If not, it'll be around 1000.
This may not be the right way but its an easy way to check
mailaliasgar said:
Run quadrant and check your score. If voodoo is enabled, it will be around 1500. If not, it'll be around 1000.
This may not be the right way but its an easy way to check
Click to expand...
Click to collapse
Yeah, that's how I usually do it.
There is an app you can install that will tell you too. And you can enable/disable voodoo with it.
https://market.android.com/details?id=com.zennmaster.rebootButton&feature=search_result
beray5 said:
Use terminal emulator and try...
su
mount | grep ext4
If no ext4 reported anywhere you are not voodooed. Match you actual state by creating the file "disable-lagfix" in your voodoo folder then reboot into recovery to verify your voodoo status had been corrected.
Click to expand...
Click to collapse
I have this same problem. I don't see rfs reported anywhere and I see ext4 so I am guessing voodoo is enabled. But I don't see the correct status on cwr. So when you create the disable-lagfix file, there is no extension on that file? It's just blank file with no extension?????
pcpark87 said:
I have this same problem. I don't see rfs reported anywhere and I see ext4 so I am guessing voodoo is enabled. But I don't see the correct status on cwr. So when you create the disable-lagfix file, there is no extension on that file? It's just blank file with no extension?????
Click to expand...
Click to collapse
Yes, if you see EXT4, then voodoo is enabled. From everything I've read, both green and red CWR don't correctly show the state of voodoo lagfix. You have to use other methods to determine if voodoo is enabled or not (which you just did).
Thank you. Cleared it all up!
Related
What is the advantage having a kernel that has Voodoo in it, and other kernels that come with the roms.
Voodoo convert your /data to Ext4 which is a much faster and reliable file system than RFS.
However, because it changes your file system, when you flash anything, I meant ANYTHING, you need to disable it first. Otherwise, you will soft brick.
There's a new lag fix that's rising. It's call zMod, and it convert /data /dbcache and some other path I don't remember. But it is a full phone conversion besides /system. Look it up in the dev forum. I am not sure about all its details.
I am actually reading up on it now. It should be realised later on tonight, or tomorrow. So i should wait for that and don't bother with Voodoo at this point.
PaiPiePia said:
Voodoo convert your /data to Ext4 which is a much faster and reliable file system than RFS.
However, because it changes your file system, when you flash anything, I meant ANYTHING, you need to disable it first. Otherwise, you will soft brick.
There's a new lag fix that's rising. It's call zMod, and it convert /data /dbcache and some other path I don't remember. But it is a full phone conversion besides /system. Look it up in the dev forum. I am not sure about all its details.
Click to expand...
Click to collapse
Ahh thanks for the info.
I was hesitant to root my Vibrant but the lag has gotten Extreme and I am about to give up on Samsung and Froyo. After messing with a PSP for years you get tired of having to hack things, but Samsung really has failed with this file system and I just cant keep letting it slug along.
PaiPiePia said:
Voodoo convert your /data to Ext4 which is a much faster and reliable file system than RFS.
However, because it changes your file system, when you flash anything, I meant ANYTHING, you need to disable it first. Otherwise, you will soft brick.
There's a new lag fix that's rising. It's call zMod, and it convert /data /dbcache and some other path I don't remember. But it is a full phone conversion besides /system. Look it up in the dev forum. I am not sure about all its details.
Click to expand...
Click to collapse
z4mod converts
/data to ext4
/dbdata to ext4
/cache to ext2
And if you want
/system to ext4 or ext2
So it converts all of those. You just have to add system to the update script. You can also choose which ext you want to use by editing the update script. So it could be /data to ext2 if you'd like. My current set up is the one above but /system is ext4 for me.
Sent from my SGH-T959 using XDA App
Im using zmod right now and it works really well. Just make sure you get the zip that converts the file system back to rfs when you flash a new rom.
Samsung Vibrant using Bionix Final w/ z4mod
Im on EB01 and i didnt remove voodoo when i was in DL09. and im trying to remove voodoo by doing making disable_lagfix folder in sd/voodoo folder. But it didnt work. and there was way of doing the adb thing and idk how to do it. can anyone tell me or teach me how to disable voodoo step by step? please. because of this i cant download anything. it says my phone memory is 0.00B. thank you. i appriciate it
If its voodoo 5 its a option in cwm.. The red one..then reboot
Rocking dj05 and jt's voodoo 5
[HOWTO] Completely Remove Voodoo Lagfix
I think this is what you are looking for.
[HOWTO] Completely Remove Voodoo Lagfix
You don't create a folder. You need to create a FILE
Sent from my Samsung Fascinate
what do u mean as in file? what kind of file? doc? txt?
There is no file extension when creating the "disable_lagfix".
1) Create a new txt document.
2) Name it "disable_lagfix". It will tell you that it will no longer be useable, blah blah. Just accept.
3) Then move it in to the voodoo folder on the sd card.
4) Reboot phone. It will take a while at reboot to un-voodoo the phone. This is normal.
Done.
I could be wrong, but I'm pretty sure the filename needs to be .disable_lagfix (notice the dot at the beginning). Oh, and the file is just an empty file, no particular format. You can create one easily with Root Explorer. If you don't have Root Explorer, I suggest buying it, as it makes it much easier to work with files on your rooted phone.
I've been having this problem for a while. The settings do not store and always get the "can't mount /dev/block/stl11" error. I first tried the disable_lagfix file and rebooted. Nothing new. Changed some settings and then rebooted. None of the system settings kept. I then tried the voodoo uninstaller in the referenced thread. The uninstaller seemed to work without error, but still get the mounting error when entering recovery mode.
I just received my new 32gb SD card, and am wondering how to ensure that my ext3 partition is also copied over, not just the fat32 files. I have found some other threads regarding this process but I still have some unanswered questions.
FYI, I am using MIUI 1.11.4 on a rooted Acer Liquid E (and malez-recovery, which is based on CM).
1. The general consensus seems to be to do a nandroid backup, partition the new card with gparted, and restore that backup (and obviously copy the fat32 files to my computer and then transfer back). I'd just like someone to tell me I'm correct before I try it.
2. On every single one of the threads I found, it always says to do a nandroid backup. Do they really mean a nandroid+ext backup?! Will the basic nandroid backup do the trick (I don't see how)? I'm concerned about this because I always get errors when I attempt a nandroid+ext backup. I plan to run nandroid-mobile.sh -b -e via adb once my file transfer is complete (stupid slow old sd card + computer), but I'm not confident that it'll work. If it doesn't, what options do I have for accessing the ext3 partition? **UPDATE: I ran nandroid-mobile.sh, and it eventually said "--ext2 specified but unable to mount the ext2 partition". I'm still Googling but I haven't figured out a solution yet. Ideas?
3. Every thread recommends using gparted but provides no justification as to why. Since I am using Windows, the whole process seems over-complicated. Can I not just use the "partition sd card" available through recovery? Why is it better to use gparted?
Thanks for any help you can give a semi-n00b!
skittleys said:
1. The general consensus seems to be to do a nandroid backup, partition the new card with gparted, and restore that backup (and obviously copy the fat32 files to my computer and then transfer back). I'd just like someone to tell me I'm correct before I try it.
2. On every single one of the threads I found, it always says to do a nandroid backup. Do they really mean a nandroid+ext backup?! Will the basic nandroid backup do the trick (I don't see how)? I'm concerned about this because I always get errors when I attempt a nandroid+ext backup. I plan to run nandroid-mobile.sh -b -e via adb once my file transfer is complete (stupid slow old sd card + computer), but I'm not confident that it'll work. If it doesn't, what options do I have for accessing the ext3 partition?
3. Every thread recommends using gparted but provides no justification as to why. Since I am using Windows, the whole process seems over-complicated. Can I not just use the "partition sd card" available through recovery? Why is it better to use gparted?
Thanks for any help you can give a semi-n00b!
Click to expand...
Click to collapse
1. Do that (just do it ; in case anything goes wrong, you can restore the nandroid backup and have your device up and running easily). If you don't create one (make sure you do) you will have a hard time getting your device to work again (and depending on your device, it may not be fixable).
2. Just make a nandroid backup. Some roms have it enabled by default (access to the partition). See here: http://forum.cyanogenmod.com/topic/19160-modhow-to-apps2ext-for-cm7-updated-03312011/.
3. Using GParted is the easiest method (which is why it is recommended): http://gparted.sourceforge.net/.
Theonew said:
3. Using GParted is the easiest method (which is why it is recommended): .
Click to expand...
Click to collapse
Easier than 3 multiple-choice questions in a recovery I've already installed???
Theonew said:
2. Just make a nandroid backup. Some roms have it enabled by default (access to the partition). See here:.
Click to expand...
Click to collapse
I doubt that my ROM does an ext backup by default.... I have now run nandroid-mobile.sh and eventually got the following message: "Warning: --ext2 specified but unable to mount the ext2 partition". I'm still Googling but I haven't yet figured out a solution for this. In the meantime, I have copied /sd-ext to my computer, which might end up being a decent workaround...but I'd still love to know what's going on!
**UPDATE: Something I've noticed...:
If I access the phone after a "normal" reboot, /sd-ext definitely exists (I can see it using simply ls, and also mount and df), but no scripts are available in /sbin.
When I go into recovery, /sbin contains all the scripts (so I can now run nandroid), but /sd-ext doesn't appear!
I've a strong suspicion this is why the partition can't be mounted during the nandroid backup.
So how do I fix this?!
skittleys said:
Easier than 3 multiple-choice questions in a recovery I've already installed???
Click to expand...
Click to collapse
According to others, yes .
skittleys said:
**UPDATE: Something I've noticed...:
If I access the phone after a "normal" reboot, /sd-ext definitely exists (I can see it using simply ls, and also mount and df), but no scripts are available in /sbin.
When I go into recovery, /sbin contains all the scripts (so I can now run nandroid), but /sd-ext doesn't appear!
I've a strong suspicion this is why the partition can't be mounted during the nandroid backup.
So how do I fix this?!
Click to expand...
Click to collapse
You cannot "fix" it. That is one reason but it also really depends on your device. For example: http://www.jayceooi.com/2011/01/12/...tition-on-sd-card-with-clockworkmod-recovery/ - This device is able to do it from recovery and it is easier than the GParted method (at least on that device).
Theonew said:
You cannot "fix" it. That is one reason but it also really depends on your device. For example: - This device is able to do it from recovery and it is easier than the GParted method (at least on that device).
Click to expand...
Click to collapse
I think we're mixing up 2 different issues now.
Forget the partitioning method, I'll just use gparted.
But now there's a major issue: I can't make a nandroid+ext backup. I've used adb to copy everything from my current ext partition and can load it onto the new card's partition, but that might not be an effective solution -- will it break all the symlinks? I'm trying to figure out whether symlinks ultimately store a path (therefore links won't break because the directory structure is still the same) or an address (which will break the links if I'm just copying + pasting). I'm finding conflicting answers.
So now I'm asking about what this error means (why won't it mount), whether the behaviour I described in the "update" above is normal (no sbin in normal mode, no sd-ext in recovery), and what alternatives I have! (Oh, and also my symlinks Qs) Plenty of people using the same recovery have created nandroid+ext backups without problems, and all the posts I'm finding about the issue relate to older versions of AmonRa.
skittleys said:
I think we're mixing up 2 different issues now.
Forget the partitioning method, I'll just use gparted.
But now there's a major issue: I can't make a nandroid+ext backup. I've used adb to copy everything from my current ext partition and can load it onto the new card's partition, but that might not be an effective solution -- will it break all the symlinks? I'm trying to figure out whether symlinks ultimately store a path (therefore links won't break because the directory structure is still the same) or an address (which will break the links if I'm just copying + pasting). I'm finding conflicting answers.
Click to expand...
Click to collapse
It's quite likely that it will break the symlinks (just like .android_secure issues). Are you able to make a nandroid-only backup?
skittleys said:
So now I'm asking about what this error means (why won't it mount), whether the behaviour I described in the "update" above is normal (no sbin in normal mode, no sd-ext in recovery), and what alternatives I have! (Oh, and also my symlinks Qs) Plenty of people using the same recovery have created nandroid+ext backups without problems, and all the posts I'm finding about the issue relate to older versions of AmonRa.
Click to expand...
Click to collapse
What recovery are you using (include version)? It is a known problem for some recovery not being able to have access to the SD-ext partition (e.g. ClockworkMod Recovery 3.0.0.5 on some if not all devices). So you should be able to access the SD-ext partition in recovery, and you should be able to access sbin normally.
Theonew said:
It's quite likely that it will break the symlinks (just like .android_secure issues). Are you able to make a nandroid-only backup?
Click to expand...
Click to collapse
Yes, I can do a nandroid backup of the internal partitions. Also not sure what issues you're referring to. I did some research on symlinks and posted on a linux forum and concluded that it shouldn't break....
Theonew said:
What recovery are you using (include version)? It is a known problem for some recovery not being able to have access to the SD-ext partition (e.g. ClockworkMod Recovery 3.0.0.5 on some if not all devices). So you should be able to access the SD-ext partition in recovery, and you should be able to access sbin normally.
Click to expand...
Click to collapse
(I don't have enough posts to insert URLs) I am using Malez recovery 0.6.1 (current is 0.6.2, nothing in the changelog suggests any relevant fixes though). I've searched extensively and it seems that I'm the only malez user having this problem.
Also, I can access sbin, but its only contents are adbd and ueventd. /sd-ext just plain doesn't show up in recovery mode.
Question: who is the owner of your /system, /sd-ext, and /system/sd partitions?
And a possibly unrelated question: what's the point of running a command through busybox (e.g., busybox ls instead of just ls)?
skittleys said:
Yes, I can do a nandroid backup of the internal partitions. Also not sure what issues you're referring to. I did some research on symlinks and posted on a linux forum and concluded that it shouldn't break....
Click to expand...
Click to collapse
It shouldn't break, but on some roms it does.
skittleys said:
Question: who is the owner of your /system, /sd-ext, and /system/sd partitions?
Click to expand...
Click to collapse
What do you mean?
skittleys said:
And a possibly unrelated question: what's the point of running a command through busybox (e.g., busybox ls instead of just ls)?
Click to expand...
Click to collapse
Busybox adds additional commands that the normal android command system does not have/understand on it's own (It gives you additional LINUX/UNIX based commands). See here: http://busybox.net/about.html.
Theonew said:
What do you mean?
Click to expand...
Click to collapse
When you run ls -l the 3rd and 4th columns show the 'owner' and 'group', respectively. It'll say things like root, system, etc., or maybe 0, 1000, 500, etc.
Theonew said:
Busybox adds additional commands that the normal android command system does not have/understand on it's own (It gives you additional LINUX/UNIX based commands). See here: http://busybox.net/about.html.
Click to expand...
Click to collapse
So there's no point in running a command like ls through busybox, right?
New question:
All that /system/sd contains is a 0-byte file called 'placeholder'. I can't find much info about this, but it sounds like this is intentional. But I know that this is where the ext partition is supposed to mount to. Does yours look like this (in either normal mode or recovery)? (edit: in recovery mode, the placeholder is gone, replaced with another 0-byte file called 'empty')
Also, do you think you could paste the output of mount when run in recovery?
BTW, A2SD seems to work perfectly otherwise. The only oddity I've noticed is that when I run a2sd forcecheck near the end it tries to unmount the partiton and can't.
Code:
[ ] Launching Apps2SD Start Program with forcecheck
[ ] Starting Darktremor Apps2SD in forcecheck mode
[ ] Creating Force Check Flag File...
[ ] Unmounting /dev/block/mmcblk0p2...
umount: can't umount /sd-ext: Device or resource busy
[ ] Rebooting phone...
Ironic that I can't mount it in recovery yet I can't unmount it normally!
Hi.
First, a disclaimer... I will not be responsible for you messing this up and bricking your device. I am only outlining a guide which I figured out and used to get my TP setup the way I wanted. DO NOT come to me for support, as I am not a dev and really have no time to save anyone from their doom...
I used RootExplorer (Paid App -
https://market.android.com/details?...sImNvbS5zcGVlZHNvZnR3YXJlLnJvb3RleHBsb3JlciJd) to do the steps outlined below. You may use any file manager of your choice, granted that it gives you root access with read/write access to /boot folder. Please make sure you backup anything you plan on changing by making copies and moving them to a safe location... Don't way I did not warn you... ^_^
With that said... I hope this helps some one... ^_^
I have just figured this thing out and soon after noticed that there is a thread with a video showing the methods to remove the extra UImage from the moboot boot menu.
The video shown here http://forum.xda-developers.com/showthread.php?t=1511050 is a great way to remove the redundant UImages from the list except I figured out a easier method and also a way to choose the default OS (WebOS or CM or CN) to load when TP boots, which the video does not get into.
Once I updated to the latest CM9 V2, I rebooted and my TP wanted to boot into the Bricked_Kernel which I did not want. I would, in this case as many of you, scroll (within 3 seconds) to the right entry to boot or else, I would be needing to reboot again.
So here is what I did.
Boot into your Rom (CM9 in my case)
Install RootExplorer from the market.
Launch RootExplorer. You will be asked to grant SU. Press Yes.
Navigate into /boot folder.
Click on the Mount R/W. This will change to Mount R/O. Now you have read and write (important) access to the contents of this folder.
Find the entry UImage.Bricked_Kernel (It might be UImage.ClassicNerd or something else).
Long press the UImage you want to delete (or modify).
Delete (rename, if you want to keep it for some reason) the UImage of the old kernel
Click on the Mount R/O to set the folder for read only access before you exit.
Now when you reboot, you will notice that the MoBoot menu is missing the entry for the extra kernel that was there before. The problem now is that the default boot selection has been set to WebOS. This is because the device is looking for the missing default entry in the boot menu. So it's just going to the top of the list. If this is what you want, you can stop here but if this is not the OS you want to load by default, follow the next few steps.
Launch RootExplorer
Navigate into /boot
Click on the Mount R/W to set write access.
Find the entry moboot.default
Long press moboot.default and choose Open in Test Editor.
The entry in this text file will show the OS that MoBoot will choose to load by default. Mine had an entry "Bricked_Kernel"
Delete the entry in this file and retype the OS of your choice. Mine was "CyanogenMod" (without the "").
Exit. You will be told that RootExplorer made a moboot.default.bak was created for safety. If you are using other file explorers you might not get the automatic backup. So please make a back up of this file before you change the entry.
Click Mount R/O to set the permissions to read only before exiting.
Reboot.
Now you will see that the MoBoot has the right OS as the default OS.
For those of you that desire to make the WebOS as the default OS you can type WebOS in the moboot.default. Well, good luck.
PLEASE DO NOT CHANGE FILES IN THE /BOOT IF YOU ARE NOT SURE WHAT YOU ARE DOING!!! Only follow this guide if you are comfortable doing so!!!
Good stuff, man.
The major difference between my tutorial and yours is that Root Explorer is a paid app, whereas my tutorial uses ES File Explorer which is free.
If you have Root Explorer though, this is definitely easier.
Choosing Default OS
Or plug in the device to computer and type:
adb shell [enter]
mount -o remount,rw /boot [enter]
ls | grep uImage [enter]
sample output:
Code:
uImage-2.6.35-palm-tenderloin
uImage.ClockworkMod
uImage.CyanogenMod
uImage.moboot
uImage.webOS
echo "CyanogenMod" > /boot/moboot.default [enter]
exit [enter]
done
nomadman said:
Choosing Default OS
Or plug in the device to computer and type:
adb shell [enter]
mount -o remount,rw /boot [enter]
ls | grep uImage [enter]
sample output:
Code:
uImage-2.6.35-palm-tenderloin
uImage.ClockworkMod
uImage.CyanogenMod
uImage.moboot
uImage.webOS
echo "CyanogenMod" > /boot/moboot.default [enter]
exit [enter]
done
Click to expand...
Click to collapse
The thing is... even though I am not a total noob when it comes to using ADB commands, it's usually not the most convenient to have to deal with connecting TP to a PC, putting it in USB mode, Command Prompt, etc... a lot of steps... What I described can be done within the TP... which was my case...
cvcduty said:
The thing is... even though I am not a total noob when it comes to using ADB commands, it's usually not the most convenient to have to deal with connecting TP to a PC, putting it in USB mode, Command Prompt, etc... a lot of steps... What I described can be done within the TP... which was my case...
Click to expand...
Click to collapse
well there's more than one way to skin a robot. i personally think it's even easier running the commands in android terminal than plugging into a pc.
what if i dont have the moboot default file?
phonetec said:
what if i dont have the moboot default file?
Click to expand...
Click to collapse
Ok... can you describe your situation with bit more detail?
Are you running CM9? Or any other ICS or GB custom rom?
How did you install your android rom?
I am not aware (since I am not a dev and no where near an expert on the matter) a way to install Android other than the CM7 or CM9 method using MoBoot to push the files to TP...
So if you can outline some details of your situation, I hope someone can shed some light for you...
im running cm9 alpha 2, installed using cwm, after using acmeinstall of cm7, it defaults to webOS when i boot up and I hate it
phonetec said:
im running cm9 alpha 2, installed using cwm, after using acmeinstall of cm7, it defaults to webOS when i boot up and I hate it
Click to expand...
Click to collapse
So if you don't have Moboot in your system anymore, I think you can push it to the TP via cminstall and get the OS chooser back.
How do you get into CWM? Do you see any UImage.Clockworkmod, UImage.Cyanogemod, etc? Are you missing moboot.default? I wonder if you can just create the moboot.default file with the CyanogeMod as it's content and see if MoBoot will read the file...
cvcduty said:
So if you don't have Moboot in your system anymore, I think you can push it to the TP via cminstall and get the OS chooser back.
How do you get into CWM? Do you see any UImage.Clockworkmod, UImage.Cyanogemod, etc? Are you missing moboot.default? I wonder if you can just create the moboot.default file with the CyanogeMod as it's content and see if MoBoot will read the file...
Click to expand...
Click to collapse
i still have moboot injstalled, but when I go in /boot I dont have a file called moboot.default
phonetec said:
i still have moboot injstalled, but when I go in /boot I dont have a file called moboot.default
Click to expand...
Click to collapse
I think if moboot is still installed, it's probably looking for the moboot.default file but since in your case, it's missing, it's booting what ever is on the top of the list of the UImages. I think you can simply create a text file and name it moboot.default in the /boot directory. As the content of the text file put CyanogenMod. Change the permissions of this file once it's placed in the /boot directory to rw_r__r__ (same as other files in the folder). Change the folder to R/O and reboot... I think it will work.
Worst case I guess you will have to push moboot via pc again...
Good luck...
yeah...that did not work....oh well, I have to send it to HP for repair anyway so i'm not going to worry too much about it
phonetec said:
yeah...that did not work....oh well, I have to send it to HP for repair anyway so i'm not going to worry too much about it
Click to expand...
Click to collapse
wait... you said you used the cm7 acmeinstaller? You shouldn't be using that if you installed cm9.
Sent from my HP Touchpad with CM9!
itsDefying said:
wait... you said you used the cm7 acmeinstaller? You shouldn't be using that if you installed cm9.
Sent from my HP Touchpad with CM9!
Click to expand...
Click to collapse
Good catch. I missed that one. He should have used the new moboot. If he used CM7 acmeinstaller he probably meant he also used the old moboot also.
Why not just edit the boot via CyBoot? Just about to try it myself.....
http://www.webosnation.com/cyboot
Well, it works after a fashion. Boot into WebOS, open up PreWare, install CyBoot. Launch it, and change the default boot to Android. Reboot, and the correct CyanogenMod entry is selected by default, but it doesn't autoboot - waits for you to hit the home key. Still, better than scrabbling for the volume key and a relatively quick way to (semi) fix the issue if you don't have RootExplorer.
dirtyfrog said:
Why not just edit the boot via CyBoot? Just about to try it myself.....
http://www.webosnation.com/cyboot
Well, it works after a fashion. Boot into WebOS, open up PreWare, install CyBoot. Launch it, and change the default boot to Android. Reboot, and the correct CyanogenMod entry is selected by default, but it doesn't autoboot - waits for you to hit the home key. Still, better than scrabbling for the volume key and a relatively quick way to (semi) fix the issue if you don't have RootExplorer.
Click to expand...
Click to collapse
Very good point. As some one said, there is more then one way to skin a cat.
I found that if you use terminal emulator and entering the following is the easiest way to set the default.
su
cd /boot
mount -o rw,remount /boot
echo CyanogenMod > moboot.default
Follow this entry exactly with the spaces them reboot, it will set your default to CyanogenMod. If you want to use another default just replace CyanogenMod with whatever you are using.
This is fast and easy.
Thank me if this helps.
travisross69 said:
I found that if you use terminal emulator and entering the following is the easiest way to set the default.
su
cd /boot
mount -o rw,remount /boot
echo CyanogenMod > moboot.default
Follow this entry exactly with the spaces them reboot, it will set your default to CyanogenMod. If you want to use another default just replace CyanogenMod with whatever you are using.
This is fast and easy.
Thank me if this helps.
Click to expand...
Click to collapse
That's perfect! The point is for people to able to fix this easily on the fly. So if you don't have access to Rootexplorer, this method can be used to change the default OS the TP would load at reboot. Thanks.
Hello.
I've installed viper4android on my mido. Everything is ok, but there is a background static sound when music is being played. According to the viper FAQ I need to delete /system/lib/soundfx/libbundlewrapper.so. What did I do:
1. Mount system as rw
adb shell
su
mount -o rw,remount,rw /system
2. try to rename that file
cd /system/lib/soundfx
mv libbundlewrapper.so libbudnlewrapper-2.so.bak
3. No success. Trying to create backup in a file manager and than trying to delete it. Still no luck. Changed system to ro and I'll wait for suggestions.
The file is there like I haven't done anything. The uncharted territory of the system partition still awaits for me. What I can do next to get the thing to work?
Rust3dCor3 said:
Hello.
I've installed viper4android on my mido. Everything is ok, but there is a background static sound when music is being played. According to the viper FAQ I need to delete /system/lib/soundfx/libbundlewrapper.so. What did I do:
1. Mount system as rw
adb shell
su
mount -o rw,remount,rw /system
2. try to rename that file
cd /system/lib/soundfx
mv libbundlewrapper.so libbudnlewrapper-2.so.bak
3. No success. Trying to create backup in a file manager and than trying to delete it. Still no luck. Changed system to ro and I'll wait for suggestions.
The file is there like I haven't done anything. The uncharted territory of the system partition still awaits for me. What I can do next to get the thing to work?
Click to expand...
Click to collapse
What rom do you use? Miui or los/aosp? Also do you use, magisk or super su? Plus, please tell how did u Install viper, that is through recovery or by using magisk?.
MyNameIsRage said:
What rom do you use? Miui or los/aosp? Also do you use, magisk or super su? Plus, please tell how did u Install viper, that is through recovery or by using magisk?.
Click to expand...
Click to collapse
I use Official and final RR
The phone uses magisk and viper was flashed by magisk (should I remove the module and flash as non-system app?)
Rust3dCor3 said:
I use Official and final RR
The phone uses magisk and viper was flashed by magisk (should I remove the module and flash as non-system app?)
Click to expand...
Click to collapse
Why don't you use es file manager? I just tried i was able to do it with es.
MyNameIsRage said:
Why don't you use es file manager? I just tried i was able to do it with es.
Click to expand...
Click to collapse
Still does not work. I have no idea what to do. Again.
Renaming the file does not go despite a Toast is visible "Rename Successful" and while deleting there is "Device or resource busy"
Rust3dCor3 said:
Still does not work. I have no idea what to do. Again.
Renaming the file does not go despite a Toast is visible "Rename Successful" and while deleting there is "Device or resource busy"
Click to expand...
Click to collapse
Why don't you try deleting it from twrp.
MyNameIsRage said:
Why don't you try deleting it from twrp.
Click to expand...
Click to collapse
I tried. The funny part is that I can only see /system/usr. No other folder is in /system. Thats why I've posted this topic. I'm just lost.
Rust3dCor3 said:
I tried. The funny part is that I can only see /system/usr. No other folder is in /system. Thats why I've posted this topic. I'm just lost.
Click to expand...
Click to collapse
Nope, you haven't mounted system in twrp, that's the reason you are only seeing /usr
So do this
From main menu, select "mount" and there select System, also make sure that the "system" box is checked and the box saying "mount system partition as read only" is unchecked(I've attached a screenshot for reference). Now you can easily go to /system and it should list the files and folders., And you can delete the file you want. Quote me if you need more help
MyNameIsRage said:
Nope, you haven't mounted system in twrp, that's the reason you are only seeing /usr
So do this
From main menu, select "mount" and there select System, also make sure that the "system" box is checked and the box saying "mount system partition as read only" is unchecked(I've attached a screenshot for reference). Now you can easily go to /system and it should list the files and folders., And you can delete the file you want. Quote me if you need more help
Click to expand...
Click to collapse
I can't believe how stupid I am. Thank You for Your advice.