I have a touch pad that runs cm9 more or less without issue. However I used to rum a kernel known as bricked and it boots to that build automatically, even though it isn't there anymore. How can I set moboot to automatically run cm9 stock without having to hold the buttons, reset the tab and manually select it?
richard head said:
I have a touch pad that runs cm9 more or less without issue. However I used to rum a kernel known as bricked and it boots to that build automatically, even though it isn't there anymore. How can I set moboot to automatically run cm9 stock without having to hold the buttons, reset the tab and manually select it?
Click to expand...
Click to collapse
In webos, in pre ware, download cyboot. You can set the order of booting, and you can even set the time to first boot using this.
richard head said:
I have a touch pad that runs cm9 more or less without issue. However I used to rum a kernel known as bricked and it boots to that build automatically, even though it isn't there anymore. How can I set moboot to automatically run cm9 stock without having to hold the buttons, reset the tab and manually select it?
Click to expand...
Click to collapse
like above, install Cyboot from preware in Webos.
You can set all the defaults for moboot including time out and which os to boot by default
i tried it without issues.
Or, if you're comfortable, you can edit the moboot.default file in the /boot folder.
Using a file explorer with root privileges, make sure you are in r/w mode, long press on the file and select edit/open in text editor. Change the name to your current rom, guessing it's CyanogenMod (caps matter), double check that name though, you want it to be the same as it appears on your moboot menu.
Save the changes and you're done
Sent from my ThunderBolt using xda premium
you also should delete the uImage.* for the the old Bricked rom that you dont have installed anymore. it will be in the /boot directory.
chicle_11 said:
In webos, in pre ware, download cyboot. You can set the order of booting, and you can even set the time to first boot using this.
Click to expand...
Click to collapse
Where is this? I am having a tough time with this instruction. Are you referring to the Preware Homebrew Documentation app?
apicia said:
Where is this? I am having a tough time with this instruction. Are you referring to the Preware Homebrew Documentation app?
Click to expand...
Click to collapse
You have to install preware if you haven't already done so using webos quick install. ,after installing preware you will see it as an app that allows you to install lots of custom apps and tweaks..
https://www.box.com/s/4fe8d60f353300d91e2a
webos quick install
Related
Hey sorry if this has been posted, but I couldn't find it.
I installed CM9 nightly after installing classicnerd, but classicnerd is still listed on the moboot screen. is there a way to remove it from the launch screen?
Also, I get an error that says increase icf setting [s3e] when i run draw something. any way to fix that?
I don't know about the draw something error. It plays fine on my touchpad.
For the moboot you need to delete the uImage.classicnerd file in the /boot/ directory. Any root explorer should do it, just mount with r/w permission. You can also do it in webOS with internalz pro, with master mode on. Sometimes when I flash a rom with a different name I get boot failures with multiple entries. In that case you have to boot into webOS to fix it. That's probably the only reason I have booted webOS since the A0.5 dropped.
Sent from my Galaxy S II (i777)
Thanks for the reply! Will try it out when I get a chance.
Yeah the draw something error only happens when I try to create more games via facebook. I wonder if I have too many games at once or what, but it only recently started doing it.
Hi there
new to the touchpad and moboot and such but not new to hacking etc etc
i have searched and havent seem to find anything that is related to what i did....
i have successfully got android and such on my touchpad...
now my issue is i booted back into webOS and downloaded preware and cyboot... in cyboot i set it to default to boot into android. and the time out of moboot i set to 1 sec... the issue i am having is i cannot get into moboot anymore... its there but because its set to go into android right away there is no way for me to get into recovery or moboot at all
anyone know how i can reset moboot and get the timeout back to 5 secs or longer so i can choose my boot method, ex so i can get into recovery or webOS again...
thanks in advance everyone!
I think the cyboot app in PreWare will let you change the moboot settings from within WebOS.
Not sure if the timeout is one of the settings available though.
Edit: Sorry - didn't read original post properly. Now see you have used Cyboot but can't get back into it.
dmarchant said:
I think the cyboot app in PreWare will let you change the moboot settings from within WebOS.
Not sure if the timeout is one of the settings available though.
Edit: Sorry - didn't read original post properly. Now see you have used Cyboot but can't get back into it.
Click to expand...
Click to collapse
correct... i cant get into moboot...
i hit reboot or power down, and it just cycles right back into android... no way for me to get into moboot... thats my issue... i need to reset it in a way so i can get back into moboot
I recall there are some posts around on how to edit the moboot settings directly in android. One option may be reinstall moboot using ACMEInstaller?
dmarchant said:
I recall there are some posts around on how to edit the moboot settings directly in android. One option may be reinstall moboot using ACMEInstaller?
Click to expand...
Click to collapse
everything i have read, they say that reinstalling moboot and ACMEinstaller doesnt solve the issue
got a link to how to edit the files/settings on android?
This thread may give some pointers, but it looks like it is fairly advanced - http://forum.xda-developers.com/showthread.php?t=1399566&highlight=moboot+edit
I just did a search for 'moboot edit' - that may give you some more threads to follow.
Ok got it working now!
So what i needed to do was use root explorer to delete the moboot.next file and then edited the moboot.timeout file with text editor in root explorer and reset the time from 1 to 10
did a hard reboot with the power button and home button holding for 15secs and it booted into moboot!!
woohoooooo!!!!
On boot/reboot, my TouchPad defaults to WebOS, and I have to catch it within 5 seconds to get to Android.
How can I change this default?
You can adjust the time out and the default boot quite easily.
First boot into webos and use the file manager "internalz" turn on master mode in the app settimgs, this allows you to delete and modify files. Then go to the folder called "boot" there should be a file called "moboot.default" open it as text and change webos to Cyanogenmod, or whatever you want as default. It must be spelt the same as it appears in the moboot menu. To change the time out edit the "moboot.timeout" change the 5 to however may seconds you want, I use 15.
Alternatively, install the Cyboot app from PreWare which allows you to make the changes.
Thanks to both of you. Went with Cyboot as it was a quick fix.
Can anyone tell me whats inside moboot.default? mine is empty
EDIT: Nevermind, just put CyanogemMod or webOS inside the moboot.default
I recommand Cyboot toooooooo
Or you can do it within WebOS using a root-level explorer, like RootExplorer, or if you're adventurous, using Terminal.
I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups.
Unfortunately, Moboot still has ClassicNerd's skin and it looks utterly disgusting and I would like to change it back to the plain old black Moboot screen.
Any ideas on how I would accomplish this?
Thank you.
Edit: I was able to install this Moboot Theme successfully and everything seems to be working. The problem I have now is that "Classicnerd" still shows up in Moboot's options. The problem is that when you select it, it goes through the boot animation but doesn't do anything, because I assume there's nothing for it to boot to.
Any idea how to remove that option from showing up in Moboot?
Edit2: Alright. I've figured out how to remove the Classicnerd option from showing up in Moboot. There were a few files inside of ../boot/. One of which was "uImage.Classicnerd" and the other was something like "moboot.classicnerd". Anyway, I deleted those two files and Moboot no longer shows the Classicnerd option in its boot menu.
HOWEVER..I now have another problem: CyanogenMod is no longer #1 on the list, so Moboot defaults to WebOS. Is there any way to change that? I shall do more research and update if I find anything.
Edit3: Figured out how to set the default boot option in Moboot.
"Open the Terminal Emulator and type:
su
mount -o remount,rw /boot"
Then I went into /boot and opened "moboot.default" in ES Note Editor and I replaced "WebOS" with "CyanogenMod". Make sure you put an enter at the end, because for whatever reason it wouldn't save it without the enter at the end.
--[Solved]--
First of all glad your using my theme
If you want to remove the classicnerd option from the menu then do :
Open terminal and type : rm /boot/uImage.ClassicNerd
Or if you have root browser go to /boot/ mount as R/W and delete the uimage.ClassicNerd
I appreciate the help.
One last question I have yet to figure out: How do I actually change the ORDER in which the items on Moboot show up? I've figured out how to change which one is default, but how do I change the actual ORDER of how they show up on Moboot?
Thanks for the reply.
jowyboy said:
I appreciate the help.
One last question I have yet to figure out: How do I actually change the ORDER in which the items on Moboot show up? I've figured out how to change which one is default, but how do I change the actual ORDER of how they show up on Moboot?
Thanks for the reply.
Click to expand...
Click to collapse
I'm not sure this is possible as there's no file (that i know of) that has order preferences for Moboot... Although i didn't really figure out how Moboot does that yet
jowyboy said:
I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups.
Unfortunately, Moboot still has ClassicNerd's skin and it looks utterly disgusting and I would like to change it back to the plain old black Moboot screen.
Any ideas on how I would accomplish this?
Thank you.
Edit: I was able to install this Moboot Theme successfully and everything seems to be working. The problem I have now is that "Classicnerd" still shows up in Moboot's options. The problem is that when you select it, it goes through the boot animation but doesn't do anything, because I assume there's nothing for it to boot to.
Any idea how to remove that option from showing up in Moboot?
Edit2: Alright. I've figured out how to remove the Classicnerd option from showing up in Moboot. There were a few files inside of ../boot/. One of which was "uImage.Classicnerd" and the other was something like "moboot.classicnerd". Anyway, I deleted those two files and Moboot no longer shows the Classicnerd option in its boot menu.
HOWEVER..I now have another problem: CyanogenMod is no longer #1 on the list, so Moboot defaults to WebOS. Is there any way to change that? I shall do more research and update if I find anything.
Edit3: Figured out how to set the default boot option in Moboot.
"Open the Terminal Emulator and type:
su
mount -o remount,rw /boot"
Then I went into /boot and opened "moboot.default" in ES Note Editor and I replaced "WebOS" with "CyanogenMod". Make sure you put an enter at the end, because for whatever reason it wouldn't save it without the enter at the end.
--[Solved]--
Click to expand...
Click to collapse
I like your post.
Just sayin.
Sent from my SPH-D700 using XDA
TedSamaha said:
I'm not sure this is possible as there's no file (that i know of) that has order preferences for Moboot... Although i didn't really figure out how Moboot does that yet
Click to expand...
Click to collapse
Meh. It's not a big deal; it would just be nice to order it however I please. My CyanogenMod Nightly installation is now set as default, so meh.
gregory15 said:
I like your post.
Just sayin.
Click to expand...
Click to collapse
Thanks, dude!
Ok, now the problem that I've been having is that for some reason neither root explorer nor ES explorer are letting me mount as R/W, when I try to check the Root option on ES Explorer it automatically says that it was denied superuser, I even changed superuser settings to automatically accept...
what to do here?
bassrebel said:
Ok, now the problem that I've been having is that for some reason neither root explorer nor ES explorer are letting me mount as R/W, when I try to check the Root option on ES Explorer it automatically says that it was denied superuser, I even changed superuser settings to automatically accept...
what to do here?
Click to expand...
Click to collapse
You tried updating binaries?
Sent from my cm_tenderloin using Tapatalk 2
if by updating binaries u mean updating SU then I tried but it didn't let me because it says I need root... WTF? I tried checking under options -> developers options and put it to root abd+apps and still nothing is happening... :/
Open the SuperUser app itself, and check your settings there. Something might be changed.
Me, I use the Prompt option, and every once in a while I have to remove an app from the accepted list and let it load itself up and prompt me again. Maybe that'll help you (I hope).
THANK YOU!
jowyboy said:
I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups...
--[Solved]--
Click to expand...
Click to collapse
Wow. Dude. Where do I start?! Thank you!!! This has plagued my kids tablet for months. Finally, this evening, I thought I would try and do something about it. This boot loader has been causing this tablet to force close after boot for months if it was left to boot up on the 'default' Classic Nerd ROM option (after I flashed another ROM).
Finally fixed.
I am looking for a way to flash complete stock rom witch is no where to be found? I deleted system apps thinking that will do the 8 boot fail thing and actually it didn't work like it did before? I need a flashable stock rom if it's possible? Any ideas?
Edit:
I also did a factory reset in cwm and that did not work either.
If you'd like to restore your device to factory default, you're need to do the "8-boot-loop-fail". This is not an automatic process, and you must do it manually.
Turn off your device.
Turn on your device.
Once you see the text "Nook" on your screen (before your Nook boots up), hold the power button down until the screen goes blank (turns off).
Repeat from step 2, seven more times (totalling to 8 failed boot attempts).
Do this eight (8) times, and your Nook will restore to factory defaults on the ninth boot. On the ninth boot, do not turn it off, let it do it's thing. It will take a while, and will restore the device back to stock; erasing all data on Internal Storage.
When performing the 8 boot-loop, I'd note down somewhere the amount of times you've turned your Nook off, as you can easily lose count.
HiddenG said:
If you'd like to restore your device to factory default, you're need to do the "8-boot-loop-fail". This is not an automatic process, and you must do it manually.
Turn off your device.
Turn on your device.
Once you see the text "Nook" on your screen (before your Nook boots up), hold the power button down until the screen goes blank (turns off).
Repeat from step 2, seven more times (totalling to 8 failed boot attempts).
Do this eight (8) times, and your Nook will restore to factory defaults on the ninth boot. On the ninth boot, do not turn it off, let it do it's thing. It will take a while, and will restore the device back to stock; erasing all data on Internal Storage.
When performing the 8 boot-loop, I'd note down somewhere the amount of times you've turned your Nook off, as you can easily lose count.
Click to expand...
Click to collapse
I haven't messed around with the nook.. but before I was able to delete a system app and it restored itself after a reboot?
Anyways.. Your guide did work. Thank you!
So my question now is are we able to edit stock files without it rebooting?
anthony062991 said:
I am looking for a way to flash complete stock rom witch is no where to be found? I deleted system apps thinking that will do the 8 boot fail thing and actually it didn't work like it did before? I need a flashable stock rom if it's possible? Any ideas?
Edit:
I also did a factory reset in cwm and that did not work either.
Click to expand...
Click to collapse
Look at my HD/HD+ CWM thread linked in my signature. I have a factory rom zip that can be flashed with my bootable CWM card. See item 9 and read the show content for the links and instructions.
The reason you are not back to where you were before you reset is because you were probably on a different version of stock ROM before it reset. The one stored on the device is usually older than what you had on it since it probably had updated itself a few times.
When you flash my plain stock (2.0.0) it will update itself to the latest version (currently 2.0.6) when you register.
Sent from my Nook HD+ running CM10 on Hybrid SD
anthony062991 said:
I haven't messed around with the nook.. but before I was able to delete a system app and it restored itself after a reboot?
Anyways.. Your guide did work. Thank you!
So my question now is are we able to edit stock files without it rebooting?
Click to expand...
Click to collapse
Glad to hear you've got it sorted.
I'm unsure which stock/system app would cause the reboot, as I haven't looked too deeply into it, sorry. Regarding editing stock files; yes, you can edit to your hearts content to what is visible. However once rooted, you can then edit additional files. You may get away with editing certain files, however, if you edit anything within the "/system/" directory, that will force a system reboot, and will erase all your content.
So in basic terms, you cannot edit within the "/system/" directory on the stock ROM. There maybe other files too which are outside this directory, but I haven't tested them either, sorry. But I can tell you that anything in system is a no-go.
All the best.
leapinlar said:
Look at my HD/HD+ CWM thread linked in my signature. I have a factory rom zip that can be flashed with my bootable CWM card. See item 9 and read the show content for the links and instructions.
The reason you are not back to where you were before you reset is because you were probably on a different version of stock ROM before it reset. The one stored on the device is usually older than what you had on it since it probably had updated itself a few times.
When you flash my plain stock (2.0.0) it will update itself to the latest version (currently 2.0.6) when you register.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Thank you! I will save the zip for backup. It will be much easier then rebooting 8 times.
HiddenG said:
Glad to hear you've got it sorted.
I'm unsure which stock/system app would cause the reboot, as I haven't looked too deeply into it, sorry. Regarding editing stock files; yes, you can edit to your hearts content to what is visible. However once rooted, you can then edit additional files. You may get away with editing certain files, however, if you edit anything within the "/system/" directory, that will force a system reboot, and will erase all your content.
So in basic terms, you cannot edit within the "/system/" directory on the stock ROM. There maybe other files too which are outside this directory, but I haven't tested them either, sorry. But I can tell you that anything in system is a no-go.
All the best.
Click to expand...
Click to collapse
That is what I was messing with. The "/system" files. I deleted some stock apps and it did not restored itself after a reboot? I am really shocked that it did not reboot itself back to its default. Last time i deleted an app from the /system it restored back to default. I used the latest Es File Explorer.
anthony062991 said:
Thank you! I will save the zip for backup. It will be much easier then rebooting 8 times.
That is what I was messing with. The "/system" files. I deleted some stock apps and it did not restored itself after a reboot? I am really shocked that it did not reboot itself back to its default. Last time i deleted an app from the /system it restored back to default. I used the latest Es File Explorer.
Click to expand...
Click to collapse
It could be that ES File Explorer did not really delete them. You have to set /system to r/w before deleting works.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
It could be that ES File Explorer did not really delete them. You have to set /system to r/w before deleting works.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I did R/W to the entire system. I deleted voice recording and then i forget the other apps, but it was all the system. I rebooted and it was completely out of the system. I am going to try to make google apps to work with stock rooted without it restoring itself after a reboot?
Edit:
I was on 2.0.6 Firmware if that means anything?
Edit:
You can edit /system/app but not anything else.
I install gapps and rebooted just fine and it kept all my stuff without it restoring itself..
Thanks
leapinlar said:
Look at my HD/HD+ CWM thread linked in my signature. I have a factory rom zip that can be flashed with my bootable CWM card. See item 9 and read the show content for the links and instructions.
The reason you are not back to where you were before you reset is because you were probably on a different version of stock ROM before it reset. The one stored on the device is usually older than what you had on it since it probably had updated itself a few times.
When you flash my plain stock (2.0.0) it will update itself to the latest version (currently 2.0.6) when you register.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Wow, it is useful for me !thanks