I know that you can change the moboot default option but I was curious if it was possible to skip the boot select screen completely and boot straight into Cyanogenmod? I have no reason to boot into WebOS and can boot into recovery via the power option inside Android. It just adds polish to just see the boot splash first when the device is switched on plus it saves a few seconds of waiting around.
Thanks!
I think you could set timeout to 0.
Unfortunately, that just turned off timeout all together.
Anyone have any other ideas?
You could try deleting moboot but I don't recommend it. Might work, might break things.
Sent from my SPH-L710 using Tapatalk 2
Please mind that if your ROM becomes unbootable and you can't boot straight to the recovery, it will be more problematic to fix.
However, I think it is possible. There's a possibility to set the next image to be booted by a text file on the boot partition. I don't remember the exact name and content, but this way android makes the moboot reboot straight to the recovery. Moboot reads the file, boots the desired image and deletes the file. So you would need to create such file for booting the android image and make that file somehow permanent. I don't think changing permissions would be enough, but you could recreate it every (re)boot by some script.
I was going to point out the same thing pojir said above me. Sure, you could boot into recovery from CM9 but if you cant boot into CM9 and are stuck in a boot loop or something, then what? Just set the timer to 1 second and have it boot to CM9 by default. It shouldn't be a big problem to wait 1 second before booting begins.
Related
Ok, so I have read through all of the posts I can and still cannot revert to stock.
I was playing with some different APKs and accidentally rewrote the AccountandSyncSetting apk with one from another device. At that point my NC rebooted and went into a boot loop. I eventually was able to get to recovery to restore factory settings, but after that completed it continued to boot loop. I have installed Nookie Froyo on an SD card which boots, however I get an SD card error, you may have to reformat. (nookie froyo is still usable, just no SDCard to mount) I have the stock files that I need to fix the device, however I cannot figure out how to do it from Nookie Froyo. Will someone please walk me through this.
thank you
I did this and I am still in a boot loop... please help
http://forum.xda-developers.com/showthread.php?p=10599116#post10599116
There are two different resets. Power+n (hold around 30 secs to boot) (data) and 8 failed boots (system). Do those two and your set.
Sent from my HTC Desire using XDA App
samuelhalff said:
There are two different resets. Power+n (hold around 30 secs to boot) (data) and 8 failed boots (system). Do those two and your set.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
How do I get it to 8 failed boots... just turn it off each time it starts looping?
Yes. Once the Nook tries to boot up unsuccessfully 8 times, It reinstalls the factory settings during the 9th time.
Solution:
All that you need to do is create a bootable clockwork mod sd card:
http://forum.xda-developers.com/showthread.php?t=922870
Then download the system and boot images from here:
http://forum.xda-developers.com/showthread.php?t=919353
Install ADB:
http://forum.xda-developers.com/showthread.php?t=910008
- ADB is a command line interface to your Nook.
Mount your Partitions (except sd) using ClockWork Mod (easy to find in the Nook ClockWork menu)
Get that system.img/boot.img file to your internal partitions:
Open your comand prompt. Browse to the folder with adb.exe using the cd command. (If you're on Vista or Higher you can shift+right click on the adb folder's background to get the option "open command window here".)
Type adb push "path to system.img file" / (eg.adb push "C:\Users\Name\Desktop\system.img" /). The last slash tells adb where to push your system img to. Also, this takes a few minutes 5-10.
Type adb shell, or adb.exe shell if the first doesn't work.
You'll just get a # symbol after that.
Type dd if=system.img of=/dev/block/mmcblk0p5 (dd - writes image to a location, if=input file, of=output file.
You can do the same with the boot.img just make the of=/dev/mmcblk0p1 for your dd command.
Also go ahead and format all of the partitions (except for sd anything) using clockwork mod before you use dd to write your img files to your partitons.
I think that should work to restore your system partiton.
If you have trouble getting it to boot, what works for me is holding all of the buttons for 10 seconds...3 times. And that usually makes it boot off of the microSD. That's probably the same as n+power, but idk.
dfellars77 said:
How do I get it to 8 failed boots... just turn it off each time it starts looping?
Click to expand...
Click to collapse
Actually, if you wait for the looping logo to start, you've waited too long. you want to hit the power button, then hold it down to start the restart as soon as you see the "n" logo to power it off. it will only trigger the auto reset after eight consecutive reboots that dont make it past that first "n" logo.
You could also do the reflash methods mentioned in this thread or in the dev threads, if you're up for something more intense. just be sure to take out the SD card when you're done flashing, or else you will boot back into whatever recovery you are using.
Thanks everyone. CWM is up and running and once I have a solid charge I will take another go at it. I have been having a heck of a time getting ADB to work properly on my machine (although it works fine on my Galaxy S). I think I just need to uninstall the Mass Storage Driver each time I connect and manually install the NOOK ADB driver. I will try some of the Dev tools recommended above and report back.
Thank you for the help (and at the very least nookie froyo works and has a better linpack score than my rooted stock!)
SUCCESS!!!! I can finally close all of the tabs I have open. In the end I had to run the dd commands through ADB while Nookie Froyo was running, but it all seems to have worked!
Thank you for all of the help.
Hi guys, here's my little contribution to the scene.
I was upset with the Flashback's Boot animation (no offense to the dev, but for the life of me... it's ugly!) so i decided to "port" the one i use on my HTC Desire.
So here it is, just copy the bootanimation.zip to your /data/local folder and reboot to enjoy it.
You can either use a file manager (root manager, file manager hd, es file explorer...), i personnally go for the QtADB option (easier way to handle files).
Here's what it will look like:
[media]http://www.youtube.com/watch?v=cUYhNWQc1_g[/media]
Edit - 18/Sept/2011:
Just a little video to show the work in progress.
I've managed to change the boot logo, working on a little app to ease the process for everyone atm.
Edit - 19/Sept/2011:
Until i come with a nice solution to reboot in APX mode, please use the following archive to flash a custom splash screen.
Little dirty tut, wait for a better one.
0. Always make a backup / Download and unpack the main archive / Read the whole tut twice before proceeding.
1. If you have already installed the APX drivers and made a backup of your partitions, please go to step 5.
2. Otherwise just power your tab off, then press Volume - and Power On till the screen turns black.
Windows will ask for specific drivers, locate them in the previous unpacked archive. When it's done proceed to the next step.
3. Run 'backup_hannspad.bat' to backup your partitions.
Please save those part?.img somewhere safe. Open the partition.txt and look for the following line: Name=BLO.
Just above, you'll find 'PartitionId=x'.
This number is important, as it tells us which partition holds the Boot LOgo. For me it's partition 7:
PartitionId=7
Name=BLO
DeviceId=19
StartSector=3712
NumSectors=2048
BytesPerSector=2048
Click to expand...
Click to collapse
4. Once it's done, power off. Then boot once again in APX mode (vol - and power), you might need to do this since sometime the apx command line isn't
really recognized.
5. If your partitionID is not 7, edit the "nvflash_hannspad_splash.bat" from the archive to the relevant number.
Otherwise run it and wait till it's finished. You'll see some progress in the window..
6. When everything is over, just reboot. Yoou should see your new splash screen.
7. If it doesn't work:
- Check the logo.bmp. Your picture must be 1024x655x24bits, check the following section ffor more info.
- Power the tab off, and restart the flash, sometimes apx is peeky.
Hope it helps till we find a better solution.
Quick sum up, for lazy users:
Double check your BLO partition (often 7 on our Hannspad, but could be 6 or Gtablet).
Make a specific bmp, width = 1024, height = 655, and 24bits, save it as logo.bmp
You could also open the one in the archive and edit it to your needs, make sure to keep the settings (1024x655x24).
Reboot the Hannspad in apx with Volume - and Power for a while, till it starts to boot but the screen turns black.
Then run the "nvflash_hannspad_splash.bat" from the archive, it will works just fine.
If your PartitionId is not '7', then you must edit the previous .bat file with the relevant number (for ex, 6).
Reboot and enjoy.
If it doesn't work, post your log or errors here.
Thx bro
Yeah the Standard one is ugly >_>
Good too see that there is some work for Hannspad
this is very cool thanks!! do you also have a different splash screen you use?
Will this also work for the Droid Incredible 2? Or does it have to be formatted?
I think that it should, there's no reason it wouldn't
If ever, just say it here and will sort it out.
However, i'm still stuck with the current Hannspad boot logo, i want to come with a clean/simple solution to flash the boot logo.
Hi everyone, just updated the 1st post with a little video.
I've managed to change the boot logo/splash screen so expect a little tool to perform this
Hopefully everyone will mod his/her tablet and we can then show xda that we truely deserve our own section!
Added a little and dirty tutorial so you guys can start messing with the custom splash screens (until i come with a nice reboot into apx mode solution).
Hi everybody I had a question, I tried installing TWRP from goomanager for the touchpad the other day. When it installed I went in to moboot and tried opening it it gave me the error invalid size. Also, after installing TWRP to option for clockwork mod disappeared on my moboot. So through intrernalz pro on web os I was able to remove the uimage of twrp from the boot folder, but that left me with only the option to boot into cyanogenmod and no type of recovery option available. I tried using acmeinstaller2, to just install CWM but after restarting there was nothing added to my moboot. I am sort of at a stand still since with out a recovery i cant update, nor can i recover from a back up. Any help would be appreciated. Thanks guys.
- Zero
zeroman9121 said:
Hi everybody I had a question, I tried installing TWRP from goomanager for the touchpad the other day. When it installed I went in to moboot and tried opening it it gave me the error invalid size. Also, after installing TWRP to option for clockwork mod disappeared on my moboot. So through intrernalz pro on web os I was able to remove the uimage of twrp from the boot folder, but that left me with only the option to boot into cyanogenmod and no type of recovery option available. I tried using acmeinstaller2, to just install CWM but after restarting there was nothing added to my moboot. I am sort of at a stand still since with out a recovery i cant update, nor can i recover from a back up. Any help would be appreciated. Thanks guys.
- Zero
Click to expand...
Click to collapse
Do you still have "ulmage.ClockworkMod" in the boot folder, it sounds like it must be gone or it should show up as an option in moboot? With mine when I installed TWRP it didn't change the options in moboot, moboot still says ClockworkMod but when that is selected it goes into TWRP and there is no "ulmage.TWRP" in my boot folder. I thought that was how TWRP was meant to install on the TP. I'm not sure if there is another way to install CWM other than with the ACME2installer, might be worth a search.
Did you make sure "update-cwm_tenderloin-1012" was in the "cminstall" folder when you ran ACME2?
You could move your backup to comp, run ACMEuninstaller and webos doctor and start from scratch and install CM9. Then just restore from your backup. I've done that a few times for other reasons.
Good Luck
Thanks for the help man, the CWM i was using was called recovery_cwm and i just had to change the name to update_cwm and let acmeinstaller do the rest. Saved me alot of time by avoiding uninstalling everything and restoring.
- Zero
CWM gone while installing TWRP through gooMan
Hi Zero,
Sorry but I am totally new to android and on how to install it in my TP. But, I was successfully running Cyanogenmod for sometime now until I thought of installing TWRP in my TP instead of CWM as installing nightly updates was becoming difficult for me.
I tried to install twrp through gooManager so that I would have both the option of Clockworkmod and twrp. SInce twrp is a better ui, I thought of using it instead of ClockworkMod.
So, I went to their site: teamw.in/project/twrp2/75
and followed the following:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
By doing so, it did not reboot but while I tried to reboot myself, I saw that the ClockWorkMod menu is gone from moboot and I have no recovery option left. The menu has 'Boot TWRP' but when selecting that, it says corrupt data and my TP hangs.
Please guide me in getting CWM back or get the TWRP.
Please help!!! Thanks in anticipation.
avisekhg said:
Hi Zero,
Sorry but I am totally new to android and on how to install it in my TP. But, I was successfully running Cyanogenmod for sometime now until I thought of installing TWRP in my TP instead of CWM as installing nightly updates was becoming difficult for me.
I tried to install twrp through gooManager so that I would have both the option of Clockworkmod and twrp. SInce twrp is a better ui, I thought of using it instead of ClockworkMod.
So, I went to their site: teamw.in/project/twrp2/75
and followed the following:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
By doing so, it did not reboot but while I tried to reboot myself, I saw that the ClockWorkMod menu is gone from moboot and I have no recovery option left. The menu has 'Boot TWRP' but when selecting that, it says corrupt data and my TP hangs.
Please guide me in getting CWM back or get the TWRP.
Please help!!! Thanks in anticipation.
Click to expand...
Click to collapse
If you have the install zip from sd card option, then flash jcsullins' recovery. Use the 12/15 version.
You can also install the same recovery using acmeinstaller 3.
There's a moboot cleaning utility, on the classic nerds' site (use it if you need to get rid of 'ghost' uimages).
Edit : here's the link to jcsullins' recovery : http://goo.im/devs/jcsullins/cmtouchpad/recovery
Edit 2 : here's another link that would be useful : http://forum.xda-developers.com/showthread.php?t=2030675&page=4
Hi,
I'm using Jellaxy ROM and I think there's something wrong that makes my phone stuck on bootscreen.
I noticed my ROM is having an issue with some services called 'netd', which using too many CPU usage, so I have to kill the process using Terminal Emulator everytime my phone feels laggy. It works but I have to do that multiple times on single day.
So I think if I just move the 'netd' files from /system/bin to another folder (in this case, /system), my phone won't be able to run it. And yes it works, but here's comes the next problem, when I try to reboot it, my phone stuck on CW bootscreen. I have solved it for the first time, I boot into CWM recovery, and run ADB through my computer to move the file back to its original folder. My phone had successfully reboot, problem solved and I move the file back again.
And today, I decided to reboot my phone after copy the file back to /system/bin folder, but it stuck on bootscreen again. I've tried to re-copy again, but now it seems my phone won't let me access its /system folder via ADB. I've tried to using Aroma File Manager but the result is the same.
Please help, and sorry for the long post.
EDIT : I've solved it by choosing "Fix Permissions" in CWM.
Greetings!
If this question was early on this forum please forgive for double it, because my search gives no result.
Today wanted update my old CM7 for a new CM9, because last update was about 2 years ago. So I went to thematic forums and remind myself how to do this, i guided this and some of this
So I download palm drivers, then moboot 0.3.5, then ACMEInstaller3 and ACMEUninstaller and last CM9 (cm-9-20130714-NIGHTLY-tenderloin.zip )
Then,I uninstall old android with ACMEUninstaller (operation was succes) after I login In webOS and use Full erase.
After Install moboot and CM9, BUT I forget to add a Clockworckmod.zip in cminstall folder. So I use an ACMEUninstaller, but nothing happened, all uninstall process was very fast (about 2-5 sec, and table goes to reboot)
So I load in CM9, add clockworcmode.zip in cminstall directory, reboot in Recovery mode to use ACMEInstaller3 with Clockworckmode.
But again - nothing only 4menu was available . So I load webOS and use Secure Erase.
After reboot in moboot menu I was not able to load webOS.And I decide to use webOSDoctor (3.0.5) then check tablet and start to instal some files and stuck at 4% then touchpad reboot.
When table powered on moboot loaded again... I was surprised... when I use load webOS option - table goes in reboot and doctor don't answered, then I choose Recovery, doctor progress bar down to 1% and all starts over and over.
I decided to close doctor with task manager.
CM9 loads every 1 of 3 try's (when I choose load CyanogenMod)so I used it to update/renew files incminstall I was confuseed...
Then I uninstall from my PC palm/webdoctor/acme and install older or this same programs again, but it reinstalling wasn't helps.Older versions of moboot3.4/acme2/CM was useless.
I try to folow this instruction (Factory condition restoration / Downgrade to webOS 3.0.0), after step 5) In that command prompt, run ( novacom boot mem:// < nova-installer-image-topaz.uImage )
When table start a reboot process it was failed, because of moboot that load after table powered.
So at this moment I have a working moboot without clockwockmod, and recover mode.
I don't know what to do, please help some advice. Iam in desper
Even without moboot's "boot webOS recovery" option working [which I have never had the misfortune of experiencing], you can still enter that mode by powering on the TP with the Volume Up button held down.
If that doesn't work, try using tpdebrick... but follow the instructions exactly, and if you have ANY questions - do not proceed. Ask on this forum post.
castrwilliam said:
Even without moboot's "boot webOS recovery" option working [which I have never had the misfortune of experiencing], you can still enter that mode by powering on the TP with the Volume Up button held down.
If that doesn't work, try using tpdebrick... but follow the instructions exactly, and if you have ANY questions - do not proceed. Ask on this forum post.
Click to expand...
Click to collapse
Yeah, i still can load webos recovery mode, but all what i use in that mode is not helping, webosdoctor and other commands like ACME. Just when touchap restart, he still load that same bugged moboot menu
FreeDooMF1 said:
Greetings!
If this question was early on this forum please forgive for double it, because my search gives no result.
Today wanted update my old CM7 for a new CM9, because last update was about 2 years ago. So I went to thematic forums and remind myself how to do this, i guided this and some of this
So I download palm drivers, then moboot 0.3.5, then ACMEInstaller3 and ACMEUninstaller and last CM9 (cm-9-20130714-NIGHTLY-tenderloin.zip )
Then,I uninstall old android with ACMEUninstaller (operation was succes) after I login In webOS and use Full erase.
After Install moboot and CM9, BUT I forget to add a Clockworckmod.zip in cminstall folder. So I use an ACMEUninstaller, but nothing happened, all uninstall process was very fast (about 2-5 sec, and table goes to reboot)
So I load in CM9, add clockworcmode.zip in cminstall directory, reboot in Recovery mode to use ACMEInstaller3 with Clockworckmode.
But again - nothing only 4menu was available . So I load webOS and use Secure Erase.
After reboot in moboot menu I was not able to load webOS.And I decide to use webOSDoctor (3.0.5) then check tablet and start to instal some files and stuck at 4% then touchpad reboot.
When table powered on moboot loaded again... I was surprised... when I use load webOS option - table goes in reboot and doctor don't answered, then I choose Recovery, doctor progress bar down to 1% and all starts over and over.
I decided to close doctor with task manager.
CM9 loads every 1 of 3 try's (when I choose load CyanogenMod)so I used it to update/renew files incminstall I was confuseed...
Then I uninstall from my PC palm/webdoctor/acme and install older or this same programs again, but it reinstalling wasn't helps.Older versions of moboot3.4/acme2/CM was useless.
I try to folow this instruction (Factory condition restoration / Downgrade to webOS 3.0.0), after step 5) In that command prompt, run ( novacom boot mem:// < nova-installer-image-topaz.uImage )
When table start a reboot process it was failed, because of moboot that load after table powered.
So at this moment I have a working moboot without clockwockmod, and recover mode.
I don't know what to do, please help some advice. Iam in desper
Click to expand...
Click to collapse
You should probably stick with the most recent and updated Install guide. Did you happen to read this note?
3)Note: When using the acmeinstaller2/3, the Rom and Gapps files must begin with update-xxxx. If update- is not present the Rom and gapps may not install. You can add update- to the Rom & Gapps file names if it is missing.
I noticed you didn't use gapps, are you sure you read my guide?
RolandDeschain79 said:
You should probably stick with the most recent and updated Install guide. Did you happen to read this note?
3)Note: When using the acmeinstaller2/3, the Rom and Gapps files must begin with update-xxxx. If update- is not present the Rom and gapps may not install. You can add update- to the Rom & Gapps file names if it is missing.
I noticed you didn't use gapps, are you sure you read my guide?
Click to expand...
Click to collapse
yes i forget about gapps at all. I didnt add it in cminstall folder on my tablet when i use acminstaller...
so what to do now? how erase all data and load webos again?
Problem solved
FreeDooMF1 said:
ok, topic can be close.
it's all about that i inattentive fool.
I dont reneme install files in cminstall folder that i added on table, and because of it ACME dont work right.
now all ok, i have full functional moboot and newest CM9 with play market.
Click to expand...
Click to collapse
Glad to hear you got it all working (@ RootzWiki), you just needed the right info to get started Time to enjoy all that Android goodness on your TouchPad! Don't forget to make a Nandroid backup and transfer it to your computer. If anything goes wrong in the future, you will be fully prepared