Related
Hi, just got a NC today. Am a total noob to Android (no smartphone) and am hoping someone can help me out. I have read and searched a bit of the posts in these NC forums, but there is just A LOT and I'm kinda lost. To start out..
After playing around with the stock 1.2 ROM for a bit, I installed the latest nightly (177) CM7 with this guide,
http://forum.xda-developers.com/showthread.php?t=1030227
Before this, I also switched to the older 1/5GB app/data partition with DeanGibson's zips via CWM. The installs are fine, although CM7's UI is thoroughly confusing. My questions are:
By installing CM7, am I also rooted as part of the process? If not, is there any additional benefit to get root?
Is ManualNooter needed if I have CM7, or is it redundant? Can I install it on top of CM7?
I can't get most apps from the Market ("your device is not compatible"). I also went to Amazon.com to try and get its AppStore app, but it gives the same error. Is this a noob issue, or is there a real problem, and is there a workaround if the latter?
What's a simple way to access network shares on my Windows network?
Is there a way to dismount & remove the microSD w/o turning the NC off?
Links would be fine. TIA for any help.
You are rooted! You might want to install clock work mod from the market... I'm not sure about the computability issue as I have never had it myself.
Sent from my NookColor using XDA Premium App
If I'm understanding this correctly, you were able to go from completely stock to CM7 without rooting with manualnooter first? I'm buying a NC next week and i was unsure root was needed to go to CM7.
You are already rooted.
Market fixes: http://forum.xda-developers.com/showthread.php?t=1255689
Sent from my LG Optimus V using Tapatalk
@sevs753
Yes, apparently the CM7 install does the root thing for you. Still not quite sure if it's needed for anything else other than allowing custom ROMs.
I'm a little flustered with Android at the moment. Trying to edit the build.prop as some others have mentioned to temp fix the market problem, only to find that I can't download ES Explorer (what others are reportedly using) to edit the file. Was going to edit it in terminal emulator & nano, but found that the soft keyboard has no cursor keys. So I found an ES Explorer apk, and now am trying to figure out how to sideload the app--I believe that's the correct lingo for Android.
I also found that many embedded flash videos don't play (Youtube does). I thought this was a done deal with 2.3 and CM7, but apparently not. Tried to download Flash 10.3 from market, but again am blocked.
Am also trying to find the parameters of what is allowable for video playback for 2.3. For HC, you can play up to 720p and high profile H264 with "reasonable" params. I've been encoding various test clips, and it looks like the max is 854x480 at baseline profile, same as with the stock ROM.
Change your LCD density to 240 and your market will start working. It makes the icons really large but you get used to it. The best way to change the density is by editing the build.prop line that is default: qemu.sf.lcd_density=161
Change that 161 to 240 and then save your build.prop and reboot. Problem should then be solved.
I edit the build.prop with root explorer (Paid version) - you have to change from r/o to r/w first, then change back to r/o after you are done editing.
Shandon84321 said:
Change your LCD density to 240 and your market will start working. It makes the icons really large but you get used to it. The best way to change the density is by editing the build.prop line that is default: qemu.sf.lcd_density=161
Change that 161 to 240 and then save your build.prop and reboot. Problem should then be solved.
I edit the build.prop with root explorer (Paid version) - you have to change from r/o to r/w first, then change back to r/o after you are done editing.
Click to expand...
Click to collapse
That's quite a jump. Most people are changing to 160 which is also a standard density.
Until you really get familiar with the CM7 and the NC, I suggest you try CM7 off uSD card.
patruns said:
That's quite a jump. Most people are changing to 160 which is also a standard density.
Click to expand...
Click to collapse
With 160 you will be clearing Market app data daily for it to keep working. 240 seems to keep working... I guess because almost all phones are set to 240.
DizzyDen said:
With 160 you will be clearing Market app data daily for it to keep working. 240 seems to keep working... I guess because almost all phones are set to 240.
Click to expand...
Click to collapse
+1 on this. I was going forever on 240 without a hiccup.
Note that ICS has also been demonstrated to change the UI depending on the density, with 160 for a tablet UI (honeycomb-ish) and 240 for phone UI (gingerbread-ish). Came across a couple references showing that density was the only thing that needed to be changed to make this happen.
I kind of suspect this may be part of why density is becoming such a big issue. It also fits with the fact that tablet-related apps show up in the market at 160 but not at 240. Perhaps Google is setting market up ahead of ICS release to handle this?
skwalas said:
+1 on this. I was going forever on 240 without a hiccup.
Note that ICS has also been demonstrated to change the UI depending on the density, with 160 for a tablet UI (honeycomb-ish) and 240 for phone UI (gingerbread-ish). Came across a couple references showing that density was the only thing that needed to be changed to make this happen.
I kind of suspect this may be part of why density is becoming such a big issue. It also fits with the fact that tablet-related apps show up in the market at 160 but not at 240. Perhaps Google is setting market up ahead of ICS release to handle this?
Click to expand...
Click to collapse
If i remember correctly this also happens on Honeycomb.
Sent from my LG Optimus V using Tapatalk
You're at the same spot I was at earlier last week. I just got my NC, and read about and made the cm7 sd card. To get market working correctly this is what I did:
- installed cm7 and gapps using this guide - http://forum.xda-developers.com/showthread.php?t=1000957
- once that was working I went to the market and got titanium backup installed
- once that's installed, I went to applications/manage/market and force closed market, cleared the cache, and uninstalled updates
- then I went to titanium and found marketupdater.apk and uninstalled it
- after that I opened market again, if force closed once but opened fine the second time. I now have the old style market and everything seems to work well.
I haven't used manualrooter, I only followed the above guide. As for unmounting the card, I have no idea. I'm probably going to keep things as they are, I really like being able to turn the NC off, take the card out, and have it back as stock.
koopakid08 said:
If i remember correctly this also happens on Honeycomb.
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
I believe honeycomb had the capability built in but was not supposed to be enabled. Would have to dig around for links n such.
I just want to say thanks for all those who replied. I'm taking some time trying different stuff on the NC, now that I've gotten a basic handle on CM7. I'll be sure to try some of the tips & info proffered.
Re: Market issue - I tried w/ File Expert to change file.prop's attribs so I can edit them, but the changes don't take. Since the entire /system partition is RO, I'm assuming I need to remount it to RW before I can do anything to the files, per NookDev's instruction. Am further assuming I'll need to install the SDK so I can get ADB running.
@Kingston73: I'm sure there are apps that do it more efficiently, but mount/unmount SD is in Settings | Storage.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Thanks again for all your help. Am learning both Android and CM7 as I go along.
Noob^2 said:
I just want to say thanks for all those who replied. I'm taking some time trying different stuff on the NC, now that I've gotten a basic handle on CM7. I'll be sure to try some of the tips & info proffered.
Re: Market issue - I tried w/ File Expert to change file.prop's attribs so I can edit them, but the changes don't take. Since the entire /system partition is RO, I'm assuming I need to remount it to RW before I can do anything to the files, per NookDev's instruction. Am further assuming I'll need to install the SDK so I can get ADB running.
@Kingston73: I'm sure there are apps that do it more efficiently, but mount/unmount SD is in Settings | Storage.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Thanks again for all your help. Am learning both Android and CM7 as I go along.
Click to expand...
Click to collapse
Flash will install fine from the market if you are in the old market. It doesn't care about the density.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
Click to expand...
Click to collapse
You can set or remove wallpaper upon your will.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Click to expand...
Click to collapse
Flash 10.3 installed and worked w/o any issue with CM7.
If you can't download it directly from Market, try to sideload it.
Oh, and, recommend trying Opera browser
patruns said:
Flash will install fine from the market if you are in the old market. It doesn't care about the density.
Click to expand...
Click to collapse
Flash should install fine with the new market too, if density is at 160 (or 240) and market data is freshly cleared. It is possible that in some cases the market will update itself too quickly for the 160 fix to stick long enough to install, and this has happened to me on occasion. If installing the basic "problematic" apps (flash, facebook, repligo, maps, etc.) for the first time, would suggest working with 240 dpi to get all the apps on your nook, then revert to 160 if that is your preferred screen sizing going forward.
Thanks for the continuing tips. I did get Flash 10.3 to install via sideloading. I still can't get Market to lift its "partial-ban", since the only version I have is 3.1.3 and there is no rollback. I did manage to edit build.prop to 160, then 240, (and cleared cache) but the ban is still present. I think us Johnny-come-latelies are just a bit screwed until some shining knight comes through with a fix.
To relate my further misadventures with CM7 and Market, I'm recounting some of my steps, in hope that they'll help someone else.
Networking to Windows boxes: I used CIFS Manager, which worked straightaway. Before that, I tried the networking function of ES File Explorer and Astro (w/ SMB plugin), but they both crashed or hung.
Finding a good file manager: I tried File Expert, ES File Explorer, and Astro File Manager. They have more functions than CM7's built-in file mgr, but the built-in mgr is the fastest at reading off large directories from the network (which still isn't that fast). This is critical for me, since most of my media will be accessed via wifi.
Finding a better terminal emulator: The built-in one is kinda barebone. Looks like Better Terminal Emulator Pro is the only game in town?
Finding a better keyboard: Since I'm a commandline guy, Hacker's Keyboard fits the bill. Well, at least until my BT keyboard arrives.
Getting USB HDD/key to work: Ordered a Tekkeon TekCharge MP1550 4xAA batt pack and a Y-cable, along with a 90-degree micro-USB cable.
Install font for Viet or any language not already on CyanogenMod 7:
I have a collection of Viet songs/movies, and most of them have UTF-8 filenames. I used this below to change the font so CM7 can see the files (it's also what I used to edit build.prop). There are easier ways to do this, but here you don't need to install anything else.
1. Get DejaVu Fonts from dejavu-fonts.org (personally, I used Arial.ttf from my Windows box since I know it covers Viet)
2. Get DejaVuSans.ttf and rename to DroidSansFallback.ttf
3. Copy DroidSansFallback.ttf to root dir of SD card
4. Insert SD card into NC and mount it (Settings | Storage)
5. Run Terminal Emulator
6. Enter su (confirm when asked) (all commands case-sensitive)
7. Enter mount. Note device node & FS for /system. For CM7, it's /dev/block/mmcblk0p5 /system ext4 (ro[...])
8. Enter mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system (node & FS must match)
9. Enter mount again to check, it should read /dev/block/mmcblk0p5 /system ext4 (rw[...])
10. Enter chmod 4755 /system/fonts/DroidSansFallback.ttf
11. Enter dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
12. Reboot. File and partition permissions should return to default.
I found that local UTF8 filenames are recognized, but not files over the network. After some hair pulling and a bunch more Googling, I stumbled on the extra needed step.
13. Unmount the CIFS share in CIFS Manager. Long-press to edit the share, enter iocharset=utf8 in the Options box. Save and remount.
Other apps chosen: EzPDF for PDFs, Aldiko for ePubs, FBReader for Mobis, PerfectViewers for CBRs, OverDrive for library checkouts, MoboPlayer for SD MKVs (doesn't work for AVI/XviD).
To-Do's:
. Try Opera like another had suggested. The default browser is pretty limited.
. Check out some of the compilers & editors for Android.
. Find a decent office suite.
Question:
. I'm having trouble with file associations with the built-in file mgr (am assuming it is part of ADW). The association is lost after a few files, and apparently it associates all file types in the share with the single app, regardless of extension. Is this an ADW issue, or did I just miss a setting somewhere?
Noob^2 said:
Thanks for the continuing tips. I did get Flash 10.3 to install via sideloading. I still can't get Market to lift its "partial-ban", since the only version I have is 3.1.3 and there is no rollback. I did manage to edit build.prop to 160, then 240, (and cleared cache) but the ban is still present. I think us Johnny-come-latelies are just a bit screwed until some shining knight comes through with a fix.
Click to expand...
Click to collapse
Are you actually clearing the market data specifically? if you're just clearing cache (such as through rom manager), that's a completely different thing and won't fix the problem. You need to clear the application data for the market specifically.
Would be seriously odd that you couldn't get the apps. Note that if you've flashed gapps through rom manager, it should install the old market. selecting "uninstall updates" in the application manager screen for the market should take you back to that old market, but it will update very quickly unless the market updater apk is already disabled.
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!!!!
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 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
Hi All,
I seek your help please, and yes I have searched and read as many, if not all the related posts.... I am fairly Tech savvy (I work in IT) and know my way around Android absolutely fine.... However I cannot for the life of me get Ubuntu to install on the Tablet, and dont know why??
Current setup...
1) HP Touchpad running, WebOS 3.0.5, and Android 4.2.2 (PAC 23:00) and have created a volume for Ubuntu
2) I've managed to install various Loaders, Recoveries, such as SmackMe2, NSBoot, MoBoot, Kexec, CWM.
I downloaded some image file for Ubuntu 12.10 v2, cant remember where or even find the thread again, but it was for HP Touchpad and was around 600Mb's.....
Took me a while to get my head around NSBoot, however I did manage to create a volume (after I released you cant have any spaces in it) and formatted it for Ext3. I then went to install the TAR.GZ file, which appeared to work...
However, when I try to boot it from either NSBoot or Kexec, it doesnt do anything... just looks like its loading, and then reboots the tablet to the NSBoot menu...
Is there something Im doing wrong, or an easy way to get it on... I'm going away on holiday soon, and would be ace to have Ubuntu on here too...
Thanks, Lister
Hi All,
Does anyone have any ideas how to get Ubuntu 12.10 on here?? Because at the moment, i am starting to think it is NOT POSSIBLE!!!
As no one has left any feed back, or clear instructions on how it done. And with a Boot partition of only 31Mb, it is clearly not enough to have all the scripts in there... I removed a few files, and ending up BRICKING my Touchpad. Through a few hacks, and tweaks, managed to get it back online... But now have to start again...
So any clues as to Linux on Touchpad please?
Thanks, Lister
ok what youre going to be doing is installing a chroot linux environment. you dont actually create a separate partition and bootloader for the linux install. you will actually be running it from within webos or from within android. i havent used webos forever so i cant remember how that goes but from within android its entirely too easy to do. you would likely benefit from an app called complete linux installer. it provides a complete walkthrough and links for the .img downloads. you shouldnt be deleting files all willy nilly from important device partitions, everything inside the /boot partition is there for a reason. youre not supposed to delete any of it.
Hi Haxin,
I will certainly look at those methods, as i will like to try it. Ideally I would like to try it outside of WebOS or Android, and have it as a native boot... But current efforts have proved useless so far, even though people say its possible. With little instructions, I have broken my Touchpad twice now, with current one needing a whole re-write of the filesystem to repair it.
I know to delete files in important system partitions is extremely risky/dangerous.... However after asking for various help and getting none, I needed to trial and error and removed files I added myself (or what I thought I had) However as you saw, that didnt really work out too well... lol
I am still looking for an easy way to install it natively prefered, but I will look at the method you mentioned though, just to see how it runs...
Many thanks, Lister