Related
I have already removed webOS ulimage so webos does not appear in the moboot menu. However now i want to know how to remove the webOS recovery option in the moboot menu as well.
I wouldn't completely advise removing it - maybe rename it so it's still there, but just hidden, in case you have to return to it with WebOS Doctor or anything. Especially since it's the only way to go about using ACMEUninstaller / ACMEInstaller2 / WebOS Doctor / Recovery images and the like.
Then again, I just did some looking in the /boot, and can't see anything about that recovery, unless it's tied into the WebOS one.
UnderZone7 said:
I have already removed webOS ulimage so webos does not appear in the moboot menu. However now i want to know how to remove the webOS recovery option in the moboot menu as well.
Click to expand...
Click to collapse
I wouldn't remove webOS, not only for the reasons ve6ay stated above, but because I find webOS very useful. It is a useful and elegant os, battery life is much better, and that's the beauty of the TP, the ability to dual boot.
The nice thing is, if you remove the Moboot entry for WebOS, you don't actually remove WebOS - you just remove the option to boot from it. BUT you also can bring it back with just a quick terminal command (I noticed this during my poke-around of /boot as I stated earlier).
Besides, if you want to skip it entirely, you can create two file in your /boot directory directly from your CM install.
I used Terminal Emulator, but you can from Root Explorer, too. Browse to /boot, mount it (hit the mount r/w button up top), hit Menu => Create New File. Call it "moboot.timeout" (without quotes). Long-press it, click Open With, choose Text Editor. In there, as the only line there, type in your timeout - (if you want it to be always super-fast, chose 1), then hit enter, back, then save.
Second file to create is one called moboot.next - which basically says "On next reboot, always choose <selection>" To use this, again, Menu => Create New File => Long-press it => Open With => Text Editor. In here, type in CyanogenMod, hit enter, back, save, and then reboot. On reboot, you should automatically go straight into Android, no options to go anywhere else.
Or, if you can stomach booting into WebOS long enough, install Cyboot from Preware, and use it to make your changes to the timeout and default boot options. I just did this, and can tell you, if you do set Next to Android, and timeout to something abysmally small, you automatically will boot into Android, no choice of anything else.
Hope that helps you, mate.
You REALLY don't want to do this, as stated above if something goes terribly wrong it's the only way to use ACMEInstaller and stuff. Even WebOS takes not much space and pretty cool, so i choose to leave it, but recovery is a must..
I'm sure I have done something stupid and if I can't get this fixed it's not the end of the world. My moboot defaulted to CM7 until I used recovery to flash CM9 nightly. Since then it has defaulted to WebOS. CyanogenMod shows up as the second option in moboot. I have tried the following directions to change the default to CM9 with no luck;
Cyboot to change to "android" - Still defaults to WebOS
Internalz pro on webOS to change moboot.default to "CyanogenMod" (with no quotes, case sensitive, which matches the Ulmage.CyanogenMod). I did this in developer mode on WebOS and saved it- Still defaults to WebOS. I confirmed in root explorer that the moboot.default is changed to "CyanogenMod" no quotes.
Used Terminal in android (can't find the link but followed directions exactly, same idea, changing moboot.default)- Nothing
Wiped everything and flashed CalssicNerd, changed the moboot.default accordingly - No luck.
Wiped everything again, flashed CM9 nightly, again tried cyboot, internalz pro, terminal, root explorer, still no luck. The moboot.default file is definitely changed to "CyanogenMod" no quotes.
Any ideas???????
Wipe clean with webOS doctor and then clean install of CM9
Sent from my cm_tenderloin using Tapatalk 2
That is not the answer I wanted but I thought it was probably going to be necessary
One more noob question, once I have wiped and reinstalled CM9, using Titanium to "restore all apps and system data" shouldn't cause the problem again should it? I'm assuming titanium doesn't mess with the boot folder? Are there things in "system data" that could be causing the problem? I guess either way I will find out shortly!
Thanks
Hey Use adb shell then:
mount -o rw,remount /
mkdir /boot
mount /dev/block/mmcblk0p13 /boot
echo Cyanogenmod > /boot/moboot.default
Should work if it doesn't you'r going to have to clean install i think its mainly because you flashed CM9 over CM7 without Wiping the TouchPad.
No luck with ADB. when I run the mkdir /boot I get "mkdir failed for /boot, File exists"
After running the rest of the commands it makes the new moboot.default file but puts it on the SD card main directory, not in the boot folder overriding the current moboot.default. (which is already CyanogenMod anyway)
Anyway, I'm just going to wipe and do a clean install. Thanks for the suggestions.
Edit: Wiped everything, started from scratch with eyeballers unofficial nightly cm9. It was still going to WebOS so I checked and there was no moboot.default. Created one with root explorer and I'm good to go. Plus I love this rom!!
Thanks again to all the people that help noobs like myself.
Glad that you resolved your problem if u need any help just ask
I wish I'd caught this before you wiped everything. Try adding a blank enter at the end of the moboot.default file - it's what I found fixed the error for me.
The other thing you could've done was booted into WebOS, installed PreWare from your PC, and then installed CyBoot and modified all your boot settings that way - you could set it to default to android, set the timeout to less or more than the default 5 seconds, etc.
ve6ay said:
I wish I'd caught this before you wiped everything. Try adding a blank enter at the end of the moboot.default file - it's what I found fixed the error for me.
The other thing you could've done was booted into WebOS, installed PreWare from your PC, and then installed CyBoot and modified all your boot settings that way - you could set it to default to android, set the timeout to less or more than the default 5 seconds, etc.
Click to expand...
Click to collapse
I think he clearly states that he tried that on his first post
Whoops. Now I see where he said he tried the Cyboot method. My bad. But the blank enter at the end, I'm not sure he said he did or not. And for some reason, it needs that blank CR/LF at the end of the line, else it sometimes (for some people) doesn't work.
It's all good, It was a good excuse to play around with new ROMs and learn some new stuff. Truth is when everything on the touchpad is running just how I want it, I get bored. I like tweaking it more than I like using it
If I ever run into the same problem, or find someone that does, I will pass on your advice of the blank enter. Thanks
i have all the files needed for android but when i restart the touchpad it doesnt go into bootloader. What am i doing wrong??? Please help
sflecha35 said:
i have all the files needed for android but when i restart the touchpad it doesnt go into bootloader. What am i doing wrong??? Please help
Click to expand...
Click to collapse
What do you mean by boot loader?
What exactly have you done so far ?
sstar said:
what do you mean by boot loader?
What exactly have you done so far ?
Click to expand...
Click to collapse
i want to go into moboot and every time i restart it goes straight to the home screen on webos. I put all the files needed for cwm and android on the touchpad i followed the instructions from a you tube video and its still not working.
What were the instructions? Or rather, step by step, what have you done so far?
bananagranola said:
What were the instructions? Or rather, step by step, what have you done so far?
Click to expand...
Click to collapse
Yes exactly what bananagranola and I have asked .
Have a look at this guide http://rootzwiki.com/topic/31548-ho...era-microphone-updated-1302013/page__st__1820 is that more helpful ?
sstar said:
Yes exactly what bananagranola and I have asked .
Have a look at this guide http://rootzwiki.com/topic/31548-ho...era-microphone-updated-1302013/page__st__1820 is that more helpful ?
Click to expand...
Click to collapse
ok what im trying to accomplish is putting android on my hp touchpad. i have watched videos on youtube on how to "root" your hp touchpad i have followed the instructions in the video but when i reboot the touchpad it suppose to go into moboot so i can select either cyanogen mod or something else but its not doing that. its going straight into webOs home screen.
sflecha35 said:
ok what im trying to accomplish is putting android on my hp touchpad. i have watched videos on youtube on how to "root" your hp touchpad i have followed the instructions in the video but when i reboot the touchpad it suppose to go into moboot so i can select either cyanogen mod or something else but its not doing that. its going straight into webOs home screen.
Click to expand...
Click to collapse
We know what you are trying to do, and have asked you to explain/list exactly what steps you have taken as we have no idea of what YouTube video you watched or actions you took.
Did you read and or follow the very good guide I gave you a link to ?
Sent from my cm_tenderloin using Tapatalk 2
sstar said:
We know what you are trying to do, and have asked you to explain/list exactly what steps you have taken as we have no idea of what YouTube video you watched or actions you took.
Did you read and or follow the very good guide I gave you a link to ?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I agree, and would add: if you were considering it, please don't just link to the video (I personally at least have no intention of watching it to figure out what you did). Please just list your steps.
sstar said:
We know what you are trying to do, and have asked you to explain/list exactly what steps you have taken as we have no idea of what YouTube video you watched or actions you took.
Did you read and or follow the very good guide I gave you a link to ?
Sent from my cm_tenderloin using Tapatalk 2[/QUOTE
Ok i have followed the guide to the link you gave me and after it reboots its suppose to go into moboot and its not.....its going into webos home screen.
Click to expand...
Click to collapse
sflecha35 said:
sstar said:
We know what you are trying to do, and have asked you to explain/list exactly what steps you have taken as we have no idea of what YouTube video you watched or actions you took.
Did you read and or follow the very good guide I gave you a link to ?
Sent from my cm_tenderloin using Tapatalk 2[/QUOTE
Ok i have followed the guide to the link you gave me and after it reboots its suppose to go into moboot and its not.....its going into webos home screen.
Click to expand...
Click to collapse
OK for the last time can you list the exact steps YOU took one by one this is the third time you have been asked for this info which is needed in order to help you .
If I not I certainly can't help and I doubt any one else can either .
Click to expand...
Click to collapse
sflecha35 said:
Ok i have followed the guide to the link you gave me and after it reboots its suppose to go into moboot and its not.....its going into webos home screen.
Click to expand...
Click to collapse
That's not supposed to happen with that guide (I've used it and it works perfectly), so you are not doing something on it or you are doing something incorrectly. So. One more time. Exactly. Step by step. What have you done?
Quite honestly, if you still don't answer this question, I give up.
sstar said:
sflecha35 said:
OK for the last time can you list the exact steps YOU took one by one this is the third time you have been asked for this info which is needed in order to help you .
If I not I certainly can't help and I doubt any one else can either .
Click to expand...
Click to collapse
ok these are the steps i have done.
1) Start by downloading Java from the link below or in the description:
http://java.com/en/download/
2) Next open the Novacom files you downloaded in videos description. Run the UniversalNovacomInstaller-1.3 installer.
-Once the installation has completed navigate to the install directory on your PC. The Default path will be C:/Program Files/ Palm, Inc. Once there Paste the files located in the “Add to Palm, Inc folder” here.
3) Choose One of the following versions of CyanogenMod. Download your chosen package and extract it to your PC.
Next attach your HP TouchPad to your PC with the USB cable and place it into USB mode.
Transfer the extracted cminstall folder onto the Root Directory of your HP TouchPad; the location that opens when you attach the USB to the PC/Mac.
Once complete disconnect the TouchPad from the USB cable.
1) CyanogenMod 10 Jelly Bean (CM10) Preview cminstall package:
http://d-h.st/er3 Note! This one folder now contains all 4 needed files!
2) CyanogenMod 9 Ice Cream Sandwich (CM9) cminstall package:
http://d-h.st/rda
3) CyanogenMod 7 Gingerbread (CM7) cminstall package:
http://www.2shared.com/file/raSLI1my/CM7_cminstall.html
4) Installation:
-Once the cminstall files are on The TouchPad and you have disconnected the USB cable, it’s time to reboot into USB mode.
-Reboot the device by going into Settings/Device Info/ and select “Reset options” choose restart. As soon as the screen goes dark hold down the volume up button until you enter USB mode. Note* the large USB symbol that should be on the screen. If you miss it just reboot again and hold down Volume up button right away.
On your PC
Open a command prompt by going to the start button and typing CMD into the search window (enter)
-Next either type or copy and paste the following in to the command prompt (without the part in brackets)
cd\ (enter)
cd program files (enter)
cd palm, inc (enter)
(only type One of the Following lines below based on the Version of CyanogenMod you are installing.)
Note*The ACMEInstaller3 should be used to install all versions of CyanogenMod.
novacom.exe boot mem:// < ACMEInstaller2 (installCM9 or CM7)
novacom.exe boot mem:// < ACMEInstaller3 (installCM10)
novacom.exe boot mem:// < ACMEUninstaller (uninstall CyanogenMod)
Click to expand...
Click to collapse
You just copied and pasted that, and you didn't even bother to crop out the CM versions or ACMEInstaller directions that you didn't use...
I give up. Good luck.
EDIT: unless you used all 3 ACME commands?! In which case you installed whichever ROM you downloaded twice (once with ACMEInstaller2, then once with ACMEInstaller3) and then uninstalled it (with ACMEUninstaller).
nsboot - NinjaSwag Bootloader/Installer
WILL REPLACE smackme2 and kexecboot!
Source: https://github.com/willcast/nsboot
Kernel source: https://github.com/willcast/ubuntu-kernel-tenderloin/tree/kexec (kexec branch, not Ubuntu)
Binary: https://docs.google.com/file/d/0B4WUjKii92l2Ukl4TE1EM1pjTDg/edit?usp=sharing
I have been working on this for about 2 weeks...
Features
Touch screen based interface
Able to boot kexec kernels
Able to install Android and Native Linux OSes, kexec tar files, and uImage kernels
Able to back up entire volumes as .tar.gz (with permissions & ownership)
Directly compatible with smackme and kexecboot config files
Can replace moboot entirely with the touch of a button.
Integrated file browser
Software touch keyboard available
Haptic feedback
uImage is < 4 MiB
Loads 3x faster than kexecboot
Has integrated ADB server so you can push and pull files from any mounted FS, or run a local shell.
Known issues so at this time
Colors are messed up in included TWRP recoveries
Things still to be tested
nothing as of now
kexec images for reference
webOS 3.0.5: https://docs.google.com/file/d/0B4WUjKii92l2WU9fdkNZa0V5NUk/edit?usp=sharing
Arch Linux ARM: https://docs.google.com/file/d/0B4WUjKii92l2YWRFUWJoMkpXRzg/edit?usp=sharing
Ubuntu: https://docs.google.com/file/d/0B4WUjKii92l2MXlEVmxQUHoyUzg/edit?usp=sharing
Slackware: https://docs.google.com/file/d/0B4WUjKii92l2MnRwMGRyTmRQcW8/edit?usp=sharing
Fedora untested: https://docs.google.com/file/d/0B4WUjKii92l2S3pVUkZNNzNSQUU/edit?usp=sharing
Android 2.2 Froyo: https://docs.google.com/file/d/0B4WUjKii92l2d2cwQlBtVVd4aGM/edit?usp=sharing
Android 2.3 Gingerbread: https://docs.google.com/file/d/0B4WUjKii92l2UGtETzBwNnNvckU/edit?usp=sharing
Android 4.0 Ice Cream Sandwich: https://docs.google.com/file/d/0B4WUjKii92l2UDc2cVZ2TjBWM2s/edit?usp=sharing
Android 4.1 Jelly Bean: https://docs.google.com/file/d/0B4WUjKii92l2d3g0U3p6c0l4NFk/edit?usp=sharing
Android 4.2 Jelly Bean: https://docs.google.com/file/d/0B4WUjKii92l2dlFzcFBacThSVXc/edit?usp=sharing
How to test
Code:
novacom boot mem:// < uImage.nsboot
To install, copy it to /boot (/dev/mmcblk0p13). It can also install itself if you put a copy of it on the SD card, and go Installer menu -> install uImage and navigate to it.
Screenshots are attached.
YouTube demo of a earlier version with only the boot working and a simpler menu: http://www.youtube.com/watch?v=0oQhSa4sqPU
Updates:
All OSes now boot (At least on my TP.)
Those which have had their kexec archives revised on GDrive since the first post are in italic.
Android 4.2
Android 4.1
Android 4.0
Android 2.3
Android 2.2
Android Recovery (included with all Android kexec archives)*
webOS
Ubuntu
Slackware
Arch Linux
Fedora
* The colors are still out of whack in recovery. It's mostly unneeded at this point with Built-In ADB support and zip installation, but I included it for those who want its more obscure or advanced features, or are more comfortable with its UI. Testing it specifically is appreciated because I don't have any plans to develop a test suite for it.
Compatibility list
Android ROMs
4.2
There is currently an issue with installing later Android 4.2 ROMs. The following 4.2 ROMs will install and boot:
Evervolv nightly 05-15-2013
The following 4.2 ROMs get stuck in a fairly serious bootloop (logcat shows at least surfaceflinger, mediaserver, and zygote segfaulting). I have tried different kernels.
CM 10.1 unofficial nightly 06-02-2013
Schzoid 2.0 nightly 04-23-2013
Other 4.2 ROMs are untested.
4.1
The following Android 4.1 ROMs have been tested and work:
JCSullins' CM 10 preview, 12-16-2012
Schzoid 1.2, 03-06-2013
4.0
The following Android 4.0 ROMs have been tested and work: CM 9 nightly, 01-06-2013
2.3
The following Android 2.3 ROMs have been tested: CM 7 Alpha 3.5
Issue: When the screen is woken up in CM7, nothing shows up on the display. The backlight does turn on.
2.2
The following Android 2.2 ROMs have been tested and work: my Froyo kang, version 0.4 and 0.3 (0.4 is on google drive on top of 0.3)
Native Linux
Ubuntu
The following Ubuntu releases have been tested and work: Ubuntu 13.04 final, Ubuntu 12.10 final.
Others are welcome to be tested, but I will probably not take issue with anything before 12.10 beta not working.
Arch Linux
Arch Linux boots, and seems to work. Wi-Fi has not been tested.
Slackware
Slackware boots and seems to work. Wi-Fi and Bluetooth have not been tested.
Debian/Bodhi
I am unable to locate any tar.gz archives to test for this distribution, nor a kernel of any sort. If anyone wishes to step up and send one to me or even host it, I would be grateful and also I'd probably get it booting within a day.
Fedora
These haven't yet been tested. They are theorerically installable with the new "tar.gz to custom LV" feature, but I would need to find a way to free more space on my TP to install them (my media partition is currently about 10 GB, 6 GB used for music, and 2.5 GB used for testing files.
Thank you
Good Job! I will test it tomorrow.I have been looking forward to ArchLinuxArm for a long time.Thank you.
Looks really good, I'll give it a spin.
Nice thing. But how Do I add my existing cm Installation to it? And how to add the cwm recovery in bootlist?
I repaced moboot with this and now i Can only Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
superboy123 said:
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Same here! But i Can Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
superboy123 said:
Sir, I downloaded this, installed it, installed kexec-webos.
I rebooted
in boot menu section, i selected HP WebOS 3.0.5
Waited for 10 secs in Starting new kernel.
nothing only reboots
thinking to use webOSDoctor
But it is not going to webOS recovery mode.:crying:
What to do?:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
After I made the webOS image, I noticed that it's a bit... finicky. Just reboot from nsboot main menu. Then try loading webOS again.
If you need to get to recovery mode, the way to do it is to reboot like that, holding down VOLUME UP.
imapjonny said:
Nice thing. But how Do I add my existing cm Installation to it? And how to add the cwm recovery in bootlist?
I repaced moboot with this and now i Can only Access Ubuntu
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you installed CM to the logical volumes named /dev/store/cm-*, you need to back up and reinstall it from nsboot. As for booting CM recovery from nsboot, if you haven't done that yet, a feature I put in already lets you make .tar.gz archives from volumes (including Android ones.) I just enabled the extraction of them to Android volumes (used to only allow others), so you could use that to "move" your Android.
Minimum System Sizes to use for android partitions:
2.2 (froyo): 256MB
2.3 (gingerbread): 320MB
4.0 (ics): 320MB
4.1 (jellybean): 450MB
4.2 (jb mr1): 480MB
Step by step instructions:
Upgrade nsboot. Just released a new one. Either scp/adb it from a running OS or redo the install procedure except for the replace moboot part, after downloading it again.
Get the kexec tarchive for your android version onto the SD card. You could scp or adb push it. If needs be, find your old Android recovery image, and boot it via novacom:
Code:
novacom boot mem:// < uImage.ClockworkMod
Boot nsboot.
Go to Utilities - create volume tarchive.
Select "cm-system". Name the backup "System".
Repeat last two steps for "cm-data" if you want to keep your data partition. I don't recommend backing up "cache".
Go to Utilities - create volume set.
Name the new Volume Set depending on your Android/CM release: Use the names "android22", "android23", "android40", "android41", or "android42".
Format the new volume set: go to Utilites->format volume set, and select it. Click Confirm/OK.
After the set is created, go to Installer menu -> install .tar.gz to existing volume. Navigte to /mnt/media/nsboot/backups. You will find your two backups. Select "System" to restore to "androidXX-system", depending on the version you just created. Make sure you use a big enough size - see above table.
Repeat the last step for data, if you made such a backup.
You now need to find the kexec archive you copied to your SD card (it's mounted in /mnt/media.) Install it. If you chose the right volume set name, it will work.
Reboot or rescan boot items and you should see the Android version in your boot menu. Tell me if it doesn't work.
If it does work, go to utility menu -> delete volume set and select "cm" as your set. This will remove the old cm set, and leave the new androidXX one.
After that, if it did work, go to utility menu -> reclaim media space to get back any lost space for your media/sdcard partition.
Thank s it worked well. But i didnt get webos to run. I installed the webos kexec tar via install kexec tar to existing volume and of i wann Boot it, it hangs up and reboots nsbootloader
Sent from my GT-I9300 using xda app-developers app
imapjonny said:
Thank s it worked well. But i didnt get webos to run. I installed the webos kexec tar via install kexec tar to existing volume and of i wann Boot it, it hangs up and reboots nsbootloader
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
So when you guys who are having trouble with webOS try launching it, do you get to the screen that says 'please wait, booting...' or the HP logo that pulsates? Where does it reboot? I'm thinking I might have uploaded an old, non-workable tar file for that OS.
FYI: After testing every boot option, I discovered a problem with Android 4.1 (only 4.1). I'm looking into it.
EDIT: just uploaded a new kexec-webos.tar. I have things set up so the link remains the same. Redownload the new tarfile, and see if it works, it works on my end. Still working on fixing 4.1 - it's the only thing left, but most of you are probably using it (trying to.)
Sir,
Thanks for your reply.
But, I cannot get into recovery mode
I rebooted pressed POWER+VOLUME UP, nothing just going into nsboot.
I also tried pressing POWER+HOME+VOLUME UP, that is also the same.
please help.:crying::crying::crying:
I also replaced moboot with nsboot.
superboy123 said:
Sir,
Thanks for your reply.
But, I cannot get into recovery mode
I rebooted pressed POWER+VOLUME UP, nothing just going into nsboot.
I also tried pressing POWER+HOME+VOLUME UP, that is also the same.
please help.:crying::crying::crying:
I also replaced moboot with nsboot.
Click to expand...
Click to collapse
I have never seen this happen for real, and there is no way my code can just disable that combination. That said, I'm not leaving anyone out in the cold with a practically unusable TP.
If you have any ROMs installed, now is the time to use them to transfer needed files over to your sdcard.
Recovery mode works perfectly when I do it, I use that when I want to test a new version without installing it. I'll look in the moboot source and add a button to reboot directly into recovery. I'm also adding ADB support (if I can get kexec to tolerate the usage of the USB bus before the call, which I'm not sure.)
bootie (the TP first stage loader, comes before nsboot or moboot) transfers control over very, very quickly, so if you're pressing these buttons after you touch "Reboot", then don't. Though I don't seem to have issues if I do so, don't hold down Power unless you're force rebooting the TP or powering it on from the cold. Hold down Volume Up as you click reboot, keep it held down as you click "yes", and don't release it.
Also try powering off, then powering back on after 10 secs. Again, hold down Volume Up, then Power, don't switch over.
If you are really frantic, purposefully deleting the nsboot uImage (/mnt/boot/uImage.nsboot) will make your TouchPad boot to the "www.palm.com/ROM" screen, which is a more mandatory form of recovery mode. You could also "rename" or "move" moboot into nsboot, and you'll get moboot back.
castrwilliam said:
EDIT: just uploaded a new kexec-webos.tar. I have things set up so the link remains the same. Redownload the new tarfile, and see if it works, it works on my end. Still working on fixing 4.1 - it's the only thing left, but most of you are probably using it (trying to.)
Click to expand...
Click to collapse
Okay everything is working well with this new tar.
Sent from my GT-I9300 using xda app-developers app
Make sure your pad is fully charged. I have had problems before during partially charged tp
John 3:16
castrwilliam said:
I have never seen this happen for real, and there is no way my code can just disable that combination. That said, I'm not leaving anyone out in the cold with a practically unusable TP.
If you have any ROMs installed, now is the time to use them to transfer needed files over to your sdcard.
Recovery mode works perfectly when I do it, I use that when I want to test a new version without installing it. I'll look in the moboot source and add a button to reboot directly into recovery. I'm also adding ADB support (if I can get kexec to tolerate the usage of the USB bus before the call, which I'm not sure.)
bootie (the TP first stage loader, comes before nsboot or moboot) transfers control over very, very quickly, so if you're pressing these buttons after you touch "Reboot", then don't. Though I don't seem to have issues if I do so, don't hold down Power unless you're force rebooting the TP or powering it on from the cold. Hold down Volume Up as you click reboot, keep it held down as you click "yes", and don't release it.
Also try powering off, then powering back on after 10 secs. Again, hold down Volume Up, then Power, don't switch over.
If you are really frantic, purposefully deleting the nsboot uImage (/mnt/boot/uImage.nsboot) will make your TouchPad boot to the "www.palm.com/ROM" screen, which is a more mandatory form of recovery mode. You could also "rename" or "move" moboot into nsboot, and you'll get moboot back.
Click to expand...
Click to collapse
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
superboy123 said:
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
Click to expand...
Click to collapse
Okay, try the volume up button. If that doesn't work, try holding power + volume up + home (rebooting it), ignoring the boot loop. I only said to delete one uImage... wait, uImages are the only files you deleted, not anything else in /boot, right?
Do you ever see the HP logo?
If you touched "boot.bin" (among certain other possible files in /boot) you'll probably need the debrick program. This isn't nsboot's fault... link to program is here: http://forum.xda-developers.com/showthread.php?t=2010270
If you use that program, follow its instructions TO THE LETTER, if there is anything you need clarification on, ask here - I've never had to use it, but I've heard of it fixing TPs that don't even show anything on the LCD. That said, if something goes wrong with it, it has the opportunity to make the problem far, far worse.
castrwilliam thank you for your work
Rock on dude
loving your work man keep it up dude:good:
superboy123 said:
Sir,
I deleted nsboot, moboot and all uImages.
But now i am getting a blank screen after 5 secs it reboots.
this has been occured unlimited times.
Please Help
Click to expand...
Click to collapse
Is the pad fully charged? I would strongly suggest letting it charge for twenty four hours.
P.S. don't panic
Sent from my Galaxy Nexus using Tapatalk 2
Is it possible to install Ubuntu 13.04 and 12.10 at the same time?
Sent from my GT-I9300 using xda app-developers app
I am a little confused on the install process, would you mind elaborating.
Sent from my Galaxy Nexus using Tapatalk 2
I did a search and did not find anything so here it goes. I am running KitKat on my HP Touchpad with no issues. However, I was going to try and load the new MM build. When I try to go into the usb mode by either rebooting and selecting webos recovery or by pressing the vol key and power button while it is rebooting, I do not get the usb symbol, but instead I get 4 designs that appear identical except for shades of color. It freezes in that state (or at least a couple of minutes). To get out of it I do the pwr and press menu 15 times to reset. I am used to using the toolbox, but can't get to it this way. Is there a way to get back to the usb from here? PS. Detailed steps are preferred if possible.
You could load TPToolbox onto the /boot partition so you don't need to use pc and webos recovery?
Peace.
chris5s said:
You could load TPToolbox onto the /boot partition so you don't need to use pc and webos recovery?
Peace.
Click to expand...
Click to collapse
Thanks, but I'm not sure which files to place where. I can still get pc access via twrp 2.8.3, but I have wiped the tp of an OS so I'm really messed up.
golfnut22 said:
Thanks, but I'm not sure which files to place where. I can still get pc access via twrp 2.8.3, but I have wiped the tp of an OS so I'm really messed up.
Click to expand...
Click to collapse
So you still have moboot and can boot in recovery?
And can you access the TP using adb?
If you can mount the sdcard thru twrp, can you not copy the files over from the pc to install an os , prob kitkat at this stage?
Otherwise use adb to push the files over, eg using these commands:
adb push /sdcard/name.of.kitkat.rom
adb push /sdcard/name.of.gapps.file
All done whilst in recovery, then use twrp to flash the rom.
Once kitkat reinstalled, use a rooted file manager, eg ES File Explorer to get TPToolbox into the boot folder.
If you manage to get kitkat up and running I'll detail the next steps.
You could circumvent all this by deleting webos from /boot and pushing TPToolbox all using adb but i dont feel confident telling you how to do that, so the 'longwinded' way may be better!
Peace
chris5s said:
So you still have moboot and can boot in recovery?
And can you access the TP using adb?
If you can mount the sdcard thru twrp, can you not copy the files over from the pc to install an os , prob kitkat at this stage?
Otherwise use adb to push the files over, eg using these commands:
adb push /sdcard/name.of.kitkat.rom
adb push /sdcard/name.of.gapps.file
All done whilst in recovery, then use twrp to flash the rom.
Once kitkat reinstalled, use a rooted file manager, eg ES File Explorer to get TPToolbox into the boot folder.
If you manage to get kitkat up and running I'll detail the next steps.
You could circumvent all this by deleting webos from /boot and pushing TPToolbox all using adb but i dont feel confident telling you how to do that, so the 'longwinded' way may be better!
Peace
Click to expand...
Click to collapse
Thanks Chris. I am able to get into moboot. I just now mounted the TP, created a folder called ttinstall (which is what the tptoolbox always used), copied my kitkat rom and gapps into that folder, unmounted the tp, then from twrp ran install for the rom first then the gapp and it all worked. I still may try your way to get to the toolbox, but at least now it is working again. I have had several of these over the years and this is the only one that gives me a weird pattern on the tp when I want to go into recovery. Thanks for the response.
golfnut22 said:
Thanks Chris. I am able to get into moboot. I just now mounted the TP, created a folder called ttinstall (which is what the tptoolbox always used), copied my kitkat rom and gapps into that folder, unmounted the tp, then from twrp ran install for the rom first then the gapp and it all worked. I still may try your way to get to the toolbox, but at least now it is working again. I have had several of these over the years and this is the only one that gives me a weird pattern on the tp when I want to go into recovery. Thanks for the response.
Click to expand...
Click to collapse
The four block weird design or pattern apparently was just substitue picture of the usb symbol as far as I can tell. I was thinking because I did not see the usb symbol, it was not going into recovery, however, the tptoolbox loaded anyways and I was able to perform the changes to ttinstall folder as ususal. I'm not sure why I get that weird pattern instead of the usb symbol, but nervertheless, it worked. I may try MM now.
golfnut22 said:
The four block weird design or pattern apparently was just substitue picture of the usb symbol as far as I can tell. I was thinking because I did not see the usb symbol, it was not going into recovery, however, the tptoolbox loaded anyways and I was able to perform the changes to ttinstall folder as ususal. I'm not sure why I get that weird pattern instead of the usb symbol, but nervertheless, it worked. I may try MM now.
Click to expand...
Click to collapse
Cool! Running flintman's MM build right now, well worth a punt!
Peace.