I setup my touchpad to dual boot webOS or CynogenMod7. Now I've replaced CM7 with MIUI. And regardless, 'cynogenmod' and 'miui' are Greek to my wife. Is there a way that I can change the 'cynogenmod' menu option in moboot so that it says 'Android' instead?
I don't know about changing the labels, but I know the package called cyboot in preware will let you change the default and timeout.
cu_shane said:
I setup my touchpad to dual boot webOS or CynogenMod7. Now I've replaced CM7 with MIUI. And regardless, 'cynogenmod' and 'miui' are Greek to my wife. Is there a way that I can change the 'cynogenmod' menu option in moboot so that it says 'Android' instead?
Click to expand...
Click to collapse
using either webos (xecutah) or android (term emulator) mount (boot partition is partition 13 in dev/block/ in android) or remount ( webos using xterm the command is mount -o remount,rw /boot)
once you mounted boot with rw privs just rename uImage extension (uImage.cyanogenmod to uImage.Android) then unmount (using umount) or remount ro (mount -o remount,ro /boot)
moboot will the show the differences,just remember to change your moboot.default to whatever name you chose)
quarlow said:
I don't know about changing the labels, but I know the package called cyboot in preware will let you change the default and timeout.
Click to expand...
Click to collapse
Thanks!!! This helped me out a ton!
Tagging this one for later, I will be doing the same.
In my case just for myself as I like to customize the device a bit more than most people probably care about.
Know this is an old thread, but I thought I could mention you can change the labels easily in webOS, instead of with terminal commands in android. Using Internalz Pro (preware package) with master mode enabled you can just rename them. Navigate to /boot/ and rename the file extension. Wit TWRP and a solid CM9 build I went to revisit this, and thought I would share.
Be Advised: if you use CyBoot Preware to set the next boot option to Andriod, CM9 a0 and a0.5 doesn't clear the /Boot/moboot.next file on sucsessful launch. The result is you cannot get MoBoot options back as it keeps going straight to CM9.
In one case, reinstall of MoBoot from ACMEinstaller2 couldn't clear the file either.
Related
OK, so I decided to try the modified build.prop (as described on modaco) on my 2.1 O2 Streak (build 8105). It's rooted and engineering mode is activated.
Downloaded from the link, removed the html bits (checked against the standard build.prop for where it should start and finish), saved as build.prop
copied it to sd card then used root explorer to copy and paste it into the system folder, after choosing "mount R/W". chose "replace existing file" when asked.
restarted and it hangs at the "Dell" boot screen. Fires up, shows Dell logo, goes blank and then shows the logo again kinda permanently
Sooo I'm guessing i've done something wrong with the build.prop? Can anyone put me right with what it SHOULD be (the modified version that speeds things up etc) or what I should have done differently?
Can't do anything now til I get home (I KNOW I KNOW trying it at work was a bit daft, but I have my backup Sony X1 in the car so it's not a total disaster! )
I've also got the pdf of "things you need to know about the streak". Armed with this and the correct build.prop will I be able to fix it or do i need to do a recovery with an update.pkg?
thanks in advance for any help!!
get the proper build.prop
there shouldn't be a need to clear off html stuff unless its been grabbed wrong.
get your original build.prop (or another one) such as http://android.modaco.com/index.php?act=attach&type=post&id=62881 which is the original 8105
connect adb
Code:
adb push build.prop /sdcard/build.prop
adb shell
su
mount -o remount,rw /etc
cp /sdcard/build.prop /etc/
mount -o remount,ro /etc
exit
adb reboot
tbh you don't need the entire build.prop from steve, just change
debug.sf.hw=1
and the dalvik cache to 64m
using root explorer (there's a built in text editor)
thanks for that - much appreciated!
i don't think the PC suite has been recognising the streak since the 2.1 update. will adb work ok with it, assuming i've done all the other bits (downloading drivers etc)
fortunately i did back up my original build.prop (renamed copy_build.prop) to the sd card so I can recover that through a card reader at home...
gotcha re: the mods using root explorer. Will try that once i've recovered it (assuming i can of course!!)
thank you again for the assistance!
woohoo!
recovered (reinstall tho, but it's kept my contacts?!).
build.prop modified using root explorer's text editor. not sure if it's any different yet as i fell asleep before I could test it
thanks for the tips, fards!
Update: Ahh yes it DOES improve it! Videos are much smoother (ie if a shot "pans" it now does it smoothly and not with jerking like it was doing. Wasn't BAD before but is definitely improved). Seems a bit snappier too. I'm probably hoping for too much now but does it help psx4droid at all?
kept the dalvik cache set to 40mb. no issues yet.
triondave said:
snip..
recovered (reinstall tho, but it's kept my contacts?!).
Click to expand...
Click to collapse
yep because if you were singed into google it syncs contacts to google and retrieves them when you log back in
Ahh that makes sense - thanks!
btw lovin it after the mod. videos really are fantastic now. no major increase in psx4droid but i presume that's using 3d rather than 2D? and it really needs updating to utilise the graphics hardware, from what i've read..
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.
I went from bricked kernel(I forget which version) to cm9 alpha 2 and it put two versions of android on my tablet.
At moboot it gives me webos,cyanogenmod,and bricked-kernel...
How do I get rid of the bricked-kernel rom and have it boot into cm9 alpha 2 instead?
got into WEBOS...usinf preware to download Internalz pro....then in setting go into master mode...and in /boot folder, delete uimage for Bricked kernal...
What is preware?
Does it internalz cost money?
I've booted into webOS like once so I am not familiar with any of this stuff.
Ignore that post. Not only is that possible in android, but that would just permanently break your Wi-Fi until you do it the proper way, by following the instructions in the OP of the bricked kernel thread.
This thread details how to get rid of the extra boot option: http://forum.xda-developers.com/showthread.php?t=1511747
I actually just did this. I used to use File Expert (free version) but they started requiring an upgrade for the root permissions, and every other root-explorer app would cause crashes & restarts. If they work for you, go ahead and use that, following the steps from the link above. I couldn't figure out why, so what I did to fix this was:
Download & Install Remount from the market https://market.android.com/details?id=com.stericson.remount
Then, run that, and choose to remount /boot as r,w
Once that was done, I used Terminal Emulator to go to /boot, change to su (to get root), and edited moboot.default (vi moboot.default), changing the contents of this file to "CyanogenMod" (it was set to the old bricked kernel entry). This will set the default to boot into CM. You can stop here if that's all you want.
I finally just went ahead and deleted /boot/uImage.CM_Bricked_Kernel as well since I wasn't going to use this anymore and it was messed up anyway.
Basically on my moboot, I have the option to boot into about 6 different things and that's unnecessary.
I have the options to boot into:
WebOS
Cyanogenmod
AOKP
CM Bricked Kernel
Clockworkmod
WebOS Recovery
How I got it this way, I'm not entirely sure because the way the TP works is different than anything else I've used.
How can I delete all the extra boot options besides WebOS, AOKP, CWM, and Recovery?
Do I have literally like 6 partitions going on or what?
A bit lost here.
Go into /boot and delete the uimage.* for the boot that you want to remove for example uImage.AKOP that should do the trick.
I would use the Terminal emulator, and issued the following commands:
Code:
- su
- mount -o rw,remount /boot
- cd /boot
- rm uImage.CM*
- rm uImage.Cyano*
- echo "AOKP" > moboot.default
- cd /sdcard
- umount /boot
- reboot
Then you'll have those two images removed, and be back to booting by default to AOKP.
haxin said:
Go into /boot and delete the uimage.* for the boot that you want to remove for example uImage.AKOP that should do the trick.
Click to expand...
Click to collapse
You should be able to do this from a root explorer in Android. This is what I do, but generally in IntrnalzPro in webOS (make sure to enable master mode). When I get too many boot items they usually fail to boot android. It might be because I have CWM and TWRP. There is only so much space for those uImage files, when that space is full they don't get created right and it won't boot. Since CM9, this has been my only reason to boot into webOS.
Sent from my Galaxy S II (i777)
So all I have to do is go delete the .image in /boot?
I had messed around in there before and didn't know it was that simple.
I Am Marino said:
So all I have to do is go delete the .image in /boot?
I had messed around in there before and didn't know it was that simple.
Click to expand...
Click to collapse
Yep, that hard part is getting r/w access to the folder.
The files will be uImage.[ROM name] not *.image
Sent from my Galaxy S II (i777)
I have Root Explorer so it shouldn't be too hard I'd imagine.
I got it fixed, so thanks everyone.
moboot uimage and tga cleaner
download the moboot uimage and tga cleaner under beta on classicnerd.net then flash that. It should clean it up.
Yes, it's possible, and yes, it's pretty much exactly the same process as on your phone. If you've done it there, you can do it on Wear.
Oh, apologies if this is old news to you, but I couldn't find threads on this particular topic, and I'm quite satisfied that it worked, so why not share.
Now, the stock Wear boot animation is great. I personally love it, at least -- so why change it? Well, why do we do most things on XDA? Because we can. Do at your own risk, I take no responsibility if you screw up. Take these notes as suggestions. I mean, they work, but you know. Backups are always a good idea.
tl;dr for people who don't need help with adb:
push the bootanimation.zip to /system/media (back up the original!), then
chmod 644 bootanimation.zip
reboot
done.
Stuff you'll need:
1. An Android Wear device (any should do, I have a Sony Smartwatch 3) that has root access and ADB debugging enabled
2. A custom kernel that has adbd insecure (I used this)
3. ADB drivers on your computer
4. A boot animation. Duh. I used this for testing purposes because the resolution is meh x close enough.
Optional: a file explorer that works on Wear. I use ES.
How to do it (the way I did, I know there are other ways):
1. On your computer: move the .zip file your animation comes in to the folder where you have ADB installed. It's probably something like "C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools".
2. Open a command window in that location by shift+right clicking on the folder and selecting "Open command window here".
3. Connect your watch to your computer no later than now. If prompted, allow debugging (note that if it's your first time, the prompt should show. If not, check developer settings again).
4. In the command prompt, type
Code:
adb devices
This lists the devices that are connected to your computer. You should see the text "List of devices attached", your watch's serial number, and the text "device" next to it. If you don't, check your drivers.
5. Copy the .zip onto your watch:
Code:
adb push bootanimation.zip /sdcard/
The directory doesn't actually matter, just make sure it's not /system and somewhere you can remember.
6. Why not /system? Because it's, by default, a read-only partition we can't access via normal adb commands. Yet that's where that zip is headed. This is where the adbd insecure kernel comes in: with it, you can remount /system as read-write. For that, enter the adb shell:
Code:
adb shell
It'll show (don't write this!)
Code:
[email protected]:/ $
To get the root privileges you'll need, type
Code:
su
What you should get is
Code:
[email protected]:/ $ su
[email protected]:/ #
The # means you're rooted. If it shows without typing "su," great.
7. Remount /system as read-write by typing the following:
Code:
mount -o rw,remount /system
8. We can now alter the partition, and we'll start by backing up your stock boot animation. To do that, we need to "move" the file to an identical file with a different name. If that sounds like it doesn't make sense, that's because it doesn't -- it's stupid, but adb shell doesn't have a rename command. This is to avoid the stock animation from getting overwritten by the new one if anything goes wrong. Anyway, to accomplish that, type
Code:
mv /system/media/bootanimation.zip bootanimation.zip1
This changes the animation's extension to .zip1, which doesn't exist. The point of this is that Android looks for /system/media/bootanimation.zip when booting up, so "bootanimation.zip1" gets ignored and is out of our way. If you'd reboot the watch now, there would be no boot animation, just a plain "Android" text (or as is the case with my 320x320 SW3, "NDROI")
9. Now we'll need to move our new animation to replace the old one. To accomplish that, use the aforementioned "move" command:
Code:
mv /sdcard/bootanimation.zip /system/media/
10. Finally, to make the animation actually display, we'll need to give it proper permissions, which are rw-r-r. "chmod" is the command that alters permissions, rw is represented by a six, and r by a four.
Code:
chmod 644 /system/media/bootanimation.zip
11. Close down /system
Code:
mount -o ro,remount /system
12. Done! Reboot your watch and enjoy your new boot animation!
Worked thanks
Gave this a try on the train on my way home from work and it worked a treat thanks now off to find some more suitable boot anims to play around with
Smackedgnome said:
Gave this a try on the train on my way home from work and it worked a treat thanks now off to find some more suitable boot anims to play around with
Click to expand...
Click to collapse
Good to hear! Now all we need is that the artistically inclined among us make some awesome-looking animations for our itty-bitty screens.
If you find any, please post them here so I can add them to the OP.
[NUMINIT] said:
Now all we need ... some awesome-looking animations for our itty-bitty screens.
If you find any, please post them here so I can add them to the OP.
Click to expand...
Click to collapse
Went looking for them and found a few, thought that I would share.
There appears to be a size limit to what boot animation can be used (at least with my Sony Smartwatch 3), the biggest file used being ~3000KB.
Watchdogs
view here
https://www.youtube.com/watch?v=ZhH-4zsMB5w
This is the one I currently use
Cyanogenmod12
(sorry dont have a link/ gif - it looks good trust me )
Nexus 7 boot animation
(no link either sorry and tbh havent tried it yet - theoretically works)
I made none of these myself, they belong to the original owners. (I just cant remember where from lol)
Files are aptly named, dont forget to rename to bootanimation.zip
Enjoy
On my aw2 huawei 2 sport 4g sawshark, the time shows during the boot process. Any way to remove for aw2 or add for aw1?
Sent from my amami using XDA Labs