BootTools Native Compile - Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help &

I have been trying to get these BootTools from github cross compiled for android for around 2 weeks without success, they build but when I unpack and repack my boot.img and then cat it to the block, it hangs at the boot screen and then reboots into recovery, when I repeat the same process on my desktop with the perl scripts it works perfect so I come here to ask for help on getting these tools cross compiled to run natively on android in a manner that works, thanks Mark.
Sent from my GT-I9305 using xda premium

Related

[Q] Porting Meego to the Tab, some Android noob questions before I start

Hi chaps,
I've just bought a Galaxy tab with plans to port Meego to the device.
I'm new to all the Android stuff, and tbh the myriad methods for doing this/that/the other and the relative lack of explanation of what's actually being done in these various methods/tools is quite confusing (and worrying).
So, if you'll bear with me, I have a few questions which are probably quite basic.
I've rooted my Tab using SuperOneClick, no problems there, I also understand that there is a leaked flashing tool called (Multi)Odin and an open source flashing tool called Heimdall. I understand adb.
So onto the questions:
Before I start messing about, how should I backup my existing firmware image? I see people talking about taking image dumps using dd, or Odin or Heimdall. What is the preferred method? And how should one then restore the device from these backups?
Alternatively is it possible to simply download the firmware directly from Samsung (I see links to later firmware, but really I'd be happy with what I have currently - P1000XXJK5 and FROYO.XWJJ7)?
I'm assuming that the best installation method would be to replace recovery, then I can add my own kernel and have it boot a rootfs mounted on the external SD card for example. Any thoughts?
I've seen one thread about people compiling their own kernels, with panics and the like which are solved by giving the full path to the initramfs extracted from the existing image. Any clues as to why the built version doesn't work? This is not so important as I can have a look at this when I build the Samsung source.
Is anyone looking at the bootloaders? Is there any information anywhere about them (as changing the bootloader to allow selection of the kernel to be booted would make life easier)?
Thanks for your patience!
Ok, so to partly answer myself, I see www dot samfirmware dot com has links to downloads of firmware images.
I'd really prefer to generate my own image of what's currently on the device rather than trusting a download site, but I guess it's better than nothing. Does anyone know how these images were generated anyway?
lardman said:
Ok, so to partly answer myself, I see www dot samfirmware dot com has links to downloads of firmware images.
I'd really prefer to generate my own image of what's currently on the device rather than trusting a download site, but I guess it's better than nothing. Does anyone know how these images were generated anyway?
Click to expand...
Click to collapse
Samfirmware get their images direct from Samsung insiders. They are not dumps.
If you want to dump from your device search "rotobackup" here in the dev forum.
Sent from my GT-P1000 using Tapatalk
alias_neo said:
Samfirmware get their images direct from Saunaing insiders. They are not dumps.
Click to expand...
Click to collapse
Ok that's reassuring.
alias_neo said:
If you want to dump from your device search "rotobackup" here in the dev forum.
Click to expand...
Click to collapse
Great, just what I was looking for, many thanks
So some more questions:
Any limit to the size of the kernel? Presumably just the size of the partition (which after extracting the image for backup seems to be a pretty large 15.4MB)?
What do all the .rc files in the raminitfs do? They are as follows: fota.rc, init.goldfish.rc, init.rc, init.smdkc110.rc, lpm.rc, recovery.rc
The init.rc is the normal init.rc file, so that's fine. Presumably the recovery.rc file is run if the bootloader detects that recovery mode is wanted (holding down keys during boot). The init.goldfish.rc? I guess this is to do with the emulator, though why it would be in a release image I don't know.
I assume that init.smdkc110.rc is automatically run somewhere along the line, though I don't see where it's started.
Any thoughts on lpm.rc and fota.rc? Are multiple .rc files run for the normal and recovery boots?
Thanks
lpm.rc is for low power mode that displays battery charging animation
goldfish is for running the rom under qemu.
backup your rom using rotobackup. compile samsung's kernel from sources, mix up default initramfs with meego's init scripts. pack all Meego stuff into loop mounted disk image. then flash zImage to kernel and your disk image to factoryfs using heimdall. I assume you have experience hacking N8xx/N900 and Maemo or Meego?
factoryfs is around 300MB so I think it should fit Meego and it (and kernel) can be easily restored with heimdall.
Thanks for the comprehensive reply
Yes I do have experience hacking Maemo/Meego, though have never really had to fiddle with init scripts before and this is as good a reason as any to learn.
I'd actually like to dual boot, so am modifying recovery.rc to bring up the Meego system on the external SD card.
Am just fiddling about building extra kernel modules now (needs btrfs for my image for example) and modifying the recovery.rc file.
Hmm, well I was all set to go and flash my new zImage and was looking for the heimdall command line, when I saw this at the top of one of the threads in this part of the forum (http://forum.xda-developers.com/showthread.php?t=870690):
Restoring to factory after using this process (you need using stock images):
heimdall flash --kernel stockzImage --recovery stockzImage --factoryfs factoryfs.rfs
Click to expand...
Click to collapse
Which has made me worry a bit that I've missed a recovery partition with its own kernel and wrongly assumed that the same kernel is used for both recovery and normal running, just with a different .rc file to be interpreted by init.
Any thoughts?
Do we trust the partition sizes reported here: http://forum.xda-developers.com/showpost.php?p=9471190&postcount=14
They seem very small for the kernel partition. I used RotoHammer's dd method to grab the contents of the partitions as a backup, so am assuming the sizes shown above are not correct (or represent something else?)
Going back to RECOVERY and ZIMAGE partitions - the ZIMAGE partition contains a recovery.rc, the question is really whether, even if they use the same zImage in both the ZIMAGE and RECOVERY partitions, the version in the RECOVERY partition is actually booted if recovery mode is selected (by holding the up volume key, etc.)? OTOH it may be that the RECOVERY partition is either empty or unused, has anyone tested specifically to see whether recovery.rc is run from the ZIMAGE partition?
Well I think I can answer my own question there, I flashed my modified kernel (modified recovery.rc) only to the KERNEL partition, and it boots normally if I don't touch anything, and just gets stuck on the first Samsung screen if I boot in recovery mode.
So it's doing something, I just can't tell what. Not sure if any kernel messages are getting lost behind that image, or perhaps they aren't even output to the framebuffer at all. I seem to remember seeing something about disabling the splashscreen so I'll go and have a look for that. Anyone got any other suggestions?
P.S. I also note there's a flash of screen corruption as the device starts up with my new kernel, I don't remember seeing that before. Is this a usual occurance?
I see from the Nexus S port that including adbd in the image seems to be the way to go for early messages, I'll need to generate a new Meego image and have another go later on.
Interesting, I can't see that I've done anything wrong, and my extra init shell script is not started. I am trying to use the "exec" keyword in recovery.rc to start a shell script which will pass control to the Meego rootfs. At the start of my shell script I start adbd (i.e. still within the initramfs), so I should be able to tell if it has started, and it doesn't appear to do so.
Therefore I did some Googling, and I've seen that in some cases the initramfs init does not implement the "exec" keyword (http://forum.samdroid.net/f9/new-init-exec-import-implemented-3280/). This is troublesome for me as it's what I'm trying to use, but at least would explain why I don't seem to leave the init process
I couldn't see the Samsung specific source for init anywhere, has anyone found any? I'm not happy to replace it using the standard Android source as I'm guessing there's code missing which allows the bootloader to tell init how the device was started so that it knows which of the .rc files to run. Has anyone looked into this?
Thanks
Looking at the code in that link it looks pretty straightforward, just a case of parsing the kernel command line (though I might just reverse engineer the existing init first to make sure I'm not missing anything).
Would still be easier to get the actual source code from Samsung, so I've emailed their Open Source group.
lardman said:
P.S. I also note there's a flash of screen corruption as the device starts up with my new kernel, I don't remember seeing that before. Is this a usual occurance?
Click to expand...
Click to collapse
I get it with CM
Does CM use a compressed initramfs? I'm using one of those and wondering if it's something to do with the (admittedly small) extra time required to move to init.
I don't have my Tab with me here, could someone post the output of /proc/cmdline please? You'll need to be root. Thanks.
Well it's booting you'll all be glad to hear.
More details to follow, but from memory the following were required:
Custom kernel to add btrfs support (as the image I'm booting is a btrfs partition on the external SD); kernel patch to allow compile-time cmdline to be added to the end of the bootloader cmdline (to enable console=tty0); replace Android init with init script to perform some basic setup then pivot_root to the Meego partition.
Next steps are to get the Meego system running usefully (which includes getting a terminal as currently I just have a login prompt but no way of inputting anything!) and also seeing whether I can get dual booting working with an Android system standard boot and Meego replacing the recovery boot.
Poor pic, but still: http://people.bath.ac.uk/enpsgp/Tab/PICT0040.JPG
Good stuff. Thanks for keeping us informed.
After you've got the groundwork for this done, how easy would it be to get Ubuntu running?
Try google http://lmgtfy.com/?q=ubuntu+on+galaxy+tab
Sent from my GT-P1000 using XDA App
brilldoctor said:
Try google http://lmgtfy.com/?q=ubuntu+on+galaxy+tab
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
That's using chroot, which I don't want. I want it running natively.
Sent from my Galaxy Tab

Help in Linux

What software do I need so I can use fastboot cmds? or is it ADB?
I'm wanting to load a ROM =)
MazinDLX said:
What software do I need so I can use fastboot cmds? or is it ADB?
I'm wanting to load a ROM =)
Click to expand...
Click to collapse
did you follow the directions to unlock your bootloader? if so, you already have all the tools you need
I was on a wind0ze box..
I am running gentoo only now.
You also need eclipse to flash hboots and at least 3 ubuntus to compile and flash baksmalis.
Sent from my HTC PH39100 using xda premium
I just want to flash a ROM.. do I really need 3 ubuntus to do that??
At least 3. Do you alreadiy have a flash-resistant USB cable?
Sent from my HTC PH39100 using xda premium
I just want to install the ROM... I dont understand where it got so complicated??
lol, KX
OP, just set up ADB SDK for linux...
no u need 2 ubuntu distros first to use compiler and compile 16 bit kernel then ubuntu 64 bit to make 32 arm kernel then u need again 32 bit linux, altho ubuntu is bit buggy for diff byte calc. but you can try so you need do diff on both kernels and diff apply to 16 bit kernel to get 18 bit kernel.
or
or you could use fastboot flash tool to flash new kernel or rom to your device...
aZuZu said:
no u need 2 ubuntu distros first to use compiler and compile 16 bit kernel then ubuntu 64 bit to make 32 arm kernel then u need again 32 bit linux, altho ubuntu is bit buggy for diff byte calc. but you can try so you need do diff on both kernels and diff apply to 16 bit kernel to get 18 bit kernel.
or
or you could use fastboot flash tool to flash new kernel or rom to your device...
Click to expand...
Click to collapse
Chumby, this is a dual core phone, so you have to diff twice for 36 bit.
Sent from my HTC PH39100 using xda premium
Ok, I'm on Gentoo Linux
I was following the guide here.
But I'm unsure how to make the program "android" actually start.
If anyone could help me I'd appreciate it.
http://developer.android.com/sdk/installing.html
Sent from my HTC PH39100 using xda premium
Ok, I have Android SDK installed, Platform Tools added.
Now when I try to get ADB or Fastboot going, It says permission denied.
But if I try to start Fastboot or ADB in SU/Root it says command not found.
WTF?
Once again, I'm on the newest Gentoo && 3.1.6 Custom Kernel.
Thanks for your time.
sudo ./adb devices
you either have to be in the same directory as the adb binary or you need to have platform tools in your PATH. if you added your PATH, you need to log out and log back in or reboot it
or restart bash....i prefer the log out
I don't know what the PATH is so i'm assuming I didn't add it.
Care to explain ?
Do I need to add my root/su account to a certain profile?
Like I said it works under my regular account, just not as root.. which is like sudo in ubuntu.
Sent from my HTC PH39100 using xda premium
http://developer.android.com/sdk/installing.html
How to update your PATH
Adding both tools/ and platform-tools/ to your PATH lets you run command line tools without needing to supply the full path to the tool directories. Depending on your operating system, you can include these directories in your PATH in the following way:
On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ and platform-tools/ directories to the path.
On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ and platform-tools/ directories to it. If you don't see a line setting the path, you can add one:
export PATH=${PATH}:<sdk>/tools:<sdk>/platform-tools
On a Mac OS X, look in your home directory for .bash_profile and proceed as for Linux. You can create the .bash_profile if you don't already have one
Click to expand...
Click to collapse
MazinDLX said:
Do I need to add my root/su account to a certain profile?
Like I said it works under my regular account, just not as root.. which is like sudo in ubuntu.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
well that doesnt make sense. why are you trying to run as root? thats completely not necessary
You're enabling, PG.
kxhawkins said:
You're enabling, PG.
Click to expand...
Click to collapse
i love you
#nohomo

Ubuntu 13.04 Final Release

This thread is to announce the release of, and provide information for,
Ubuntu 13.04 FINAL VERSION for the HP TouchPad.
Brought to you in LESS THAN 24 HOURS AFTER RELEASE by WillCast.
Screenshots of "new" E17 attached to this post!
FEATURES
Automatic login to Enlightenment 17 (E17)
All E17 packages (including Terminology) rebuilt from source from the enlightenment-svn PPA.
e17-gtk-theme installed and activated.
< 2 GB extracted size. For best results, use a 4GB or larger ubuntu-root. (Most are.)
GUI Config Programs (see next section)
Wi-Fi working
RNDIS over USB working (2.6 and 3.0)
Bluetooth working except for BTAudio
Normal Ubuntu boot sequence (no strange initramfs hacks, and working fstab)
(new and updated) KEXEC IS REQUIRED
2.2GHz max Overclock - Not even stable on my TP! (Max 1.78GHz on 3.0.8)
Working Audio (manual switch between Internal and External)
AUTOMATIC, TOGGLABLEScreen Rotation
Software Compositing Enabled
Desktop Style Interface with Seperate Windows
Settable Brightness
Settable Charger Current Limit
Settable LED Triggers
VLC Media Player, GStreamer (Rhythmbox/Pithos) pre-configured to work
PULSEAUDIO (Enslaved to alsa dmix to prevent issues) (yay)
GRAPHICAL TOUCHPAD CONFIG UTILITIES
All are available from the desktop.
setbrightness (fixed) - Set LCD brightness with a slider.
setImax (new) - Set the charger current limit from a list.
setfreq (new) - Configure CPU speed from a list, optionally, set to persist over reboot.
tsrotate (fixed) - Turn auto-rotation on or off.
audiocfg - Select the audio output - internal, external or both.
setLEDtrigger (New) - Select the LED triggers for the left and right sides of the home/center button. Examples provided in dialog.
PRE-INSTALLED SOFTWARE
Available from the EVERYTHING Starter in the Bottom-Left Corner
Mozilla Firefox
Gnash (Flash 7-8) plugin, Lightspark (Flash 9+) plugin, IcedTea 7 (Java) plugin
Pithos (Pandora radio client)
Rhythmbox (music player)
VLC media player
LibreOffice
GIMP 2.8
GNOME system monitor, Baobab disk usage tool, GCalcTool calculator, gedit text editor
RELEVANT INFORMATION
Root password: root
Normal Username: ubuntu, Password: ubuntu
Auto-login Enabled
To configure Bluetooth and date/time, go into System Settings (aka gnome-control-center).
Use the NetworkManger Applet in the panel to configure Wi-Fi.
TO PERFORM A NEW INSTALL (ONLY), AUTOMATICALLY WITH SMACKME2
SmackMe2 thread: http://forum.xda-developers.com/showthread.php?t=2132703
Copy the two provided files (uImage.kexec and TouchPadBuntuRootfs1304b2.tar.gz) to the sminstall folder under the root of your /media/internal. If "sminstall" does not exist, first create it.
Follow the instructions on how to install "native Linux' in the SmackMe2 thread.
TO PREPARE FOR MANUAL UPGRADE (NOVATERM)
Install NovaCom and NovaTerm on your "real" computer - please consult one of the many references on how to install it.
Boot the TouchPad into WebOS.
Connect the TouchPad to the PC with a microUSB cable.
Enter USB mode and copy the uImage.kexec and TouchPadBuntuRootfs1304b2.tar.gz files to the root of your TouchPad's internal storage.
PROPERLY "eject" the TP from your PC.
Enter Developer Mode. (In the Just Type box, type "upupdowndownleftrightleftrightbastart", and select Developer Mode.)
On your PC, open "novaterm".
You are now ready to type in the "Manual Installation" commands.
MANUAL UPGRADE (Commands to type into Novaterm)
This will erase any data and settings stored under Ubuntu. Stuff in the media storage (/media/internal or /mnt/sdcard) will be unaffected.
Code:
mkfs.ext3 /dev/store/ubuntu-root
mkdir /tmp/u
mount /dev/store/ubuntu-root /tmp/u
cd /tmp/u
tar -xzpvf /media/internal/TouchPadBuntuRootfs1304f.tar.gz
umount /tmp/u
cd /media/internal
mount -o remount,rw /boot
cp uImage.kexec /boot
sync
TO BOOT AFTER INSTALLATION
Reboot your TouchPad.
Select "kexec" in the MoBoot menu, and press Center to boot kexec.
Wait for the white screen.
Select "Ubuntu 13.04" in the kexecboot screen, and select (press POWER/SLEEP button on top, not CENTER button).
Wait for Enlightenment to start.
TROUBLESHOOTING / FAQ:
If you don't see Ubuntu in the moboot menu, that is normal - you have to boot Kexec and then boot Ubuntu 13.04 from kexec.
If your TouchPad doesn't have a "kexec" menu option after rebooting, make sure you copied uImage.kexec to the proper location, and retry.
If your kexec uImage doesn't boot or freezes before the white screen, check your free space on the boot partition (/dev/mmcblk0p13). Delete kexec, free up at least 3MB (by deleting extra uImages and/or themes) and recopy it manually.
If you can't select Ubuntu from the kexec menu, make sure you're pressing Power and not Center to select it.
If your kexec freezes instead of booting Ubuntu, make sure you have the latest kexec from this post. The old one doesn't support large initramfs files which are present in 13.04 beta2 (and the final version.)
If you experience problems with Kernel 3.0.8, remember that it is alpha quality!
To reboot your TouchPad if it stops responding, hold down Center and Power until you see "Please release key(s)."
DOWNLOAD LINKS - Google Drive hosted
NEW AND UPDATED KEXEC: (required to boot): https://docs.google.com/file/d/0B4WUjKii92l2RHJoNE93c2dVRlU/edit?usp=sharing
13.04 FINAL ROOTFS: https://docs.google.com/file/d/0B4WUjKii92l2bDRlQ0NTbTZBemM/edit?usp=sharing
KERNEL 3.0.8 ALPHA: https://docs.google.com/file/d/0B4WUjKii92l2TXd5RTJfQnJtS3c/edit?usp=sharing
PREVIOUS VERSIONS - UNSUPPORTED
13.04beta2: https://docs.google.com/file/d/0B4WUjKii92l2N0V2Q3ljTHI0WEU/edit?usp=sharing
12.10final: https://docs.google.com/file/d/0B4WUjKii92l2eDduajFwUGhVYlU/edit?usp=sharing
12.10beta1:https://docs.google.com/file/d/0B4WUjKii92l2OExhVDdXX3dGcjQ/edit?usp=sharing
nicee. was thinking to sell my touchpad. but now. thanks to u.
Sent from my LG-P769 using Tapatalk 2
How's battery life with this?
Battery life is something I haven't tested. It's okay, I think, about 3-4 hours. Remember, Ubuntu doesn't sleep on these, never has AFAIK.
i cant format the ubuntu-root to ext4. everytime i run mkfs.ext4 i get this error while mounting:
mount: mounting /dev/store/ubuntu-root /tmp/u failed:Invalid Argument
if i format to ext3 mounting works. Can i use ext3 instead of ext4??
I'm using Ubuntu 12.10, I don't mind to start from scratch.
But..... Would upgrading from 12.10 to this version via novaterm screw anything up?
Sent from my Nexus 7 using xda app-developers app
That (ext3) should work - I enabled the config option where you can mount ext2/ext3 as ext4 on my kernel. I forgot that webos uses slightly old filesystems
I'll update the instructions.
In the battery life quest, I just noticed that the dnsmasq process often eats up 100% CPU, so I just disabled it. I'll upload a revised image to the same link (love GDrive), but if any of you have already DLed one then I can tell you what to do to fix it:
in Terminal:
Code:
sudo gedit /etc/NetworkManager/NetworkManager.conf
delete or comment out ("#") the line reading "dns=dnsmasq" and save, quit, reboot (or sudo killall dnsmasq)
castrwilliam said:
That should work. If you were to encounter any trouble installing then there is an error with the commands I posted.
On the battery life quest, I just noticed that the dnsmasq process often eats up 100% CPU, so I just disabled it. I'll upload a revised image to the same link (love GDrive), but if any of you have already DLed one then I can tell you what to do to fix it:
in Terminal:
Code:
sudo gedit /etc/NetworkManager/NetworkManager.conf
delete or comment out ("#") the line reading "dns=dnsmasq" and save, quit, reboot (or sudo killall dnsmasq)
Click to expand...
Click to collapse
I remember there being sleep issues on old builds. On this, can I sleep the device, or does it have to be shut down when not in use?
- Thanks, always wanted an Ubuntu build
Sent from my ADR6425LVW using xda app-developers app
---------- Post added at 09:42 AM ---------- Previous post was at 09:39 AM ----------
Also, right clicking was really annoying before. Is it usable on your build?
Sent from my ADR6425LVW using xda app-developers app
eriscentro said:
I remember there being sleep issues on old builds. On this, can I sleep the device, or does it have to be shut down when not in use?
- Thanks, always wanted an Ubuntu build
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You need to turn off the whole tablet, yes. I don't think it was ever made to work on ubuntu. It wasn't really a priority when we were missing stuff like headphone audio. I guess I can look into dmesg and try to diagnose.
To right click you need to click on the mouse cursor button on onboard, and then the flipped looking pointer button on the 2nd row down of the button group that appears - after tou do that, the very next click wll be seen as a right click.
I'll take a look once I do the install later today, waiting for my TP to finish charging up. Thanks!
Sent from my ADR6425LVW using xda app-developers app
there are a lot of dependencie errors and broken packages when u try to install software(i.e. eclipse). is there a way to fix it
??
imapjonny said:
there are a lot of dependencie errors and broken packages when u try to install software(i.e. eclipse). is there a way to fix it
??
Click to expand...
Click to collapse
I haven't tried this release yet, eclipse worked fine under 12.10.
May not be compiled properly or hasn't been updated to the 13.04 armhf port repositories.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------
blmvxer said:
I haven't tried this release yet, eclipse worked fine under 12.10.
May not be compiled properly or hasn't been updated to the 13.04 armhf port repositories.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
One thing I'd like to see in the armhf repository is spotify. That's honestly all I need on an Ubuntu tablet.
Sent from my Nexus 7 using xda app-developers app
Im struggling to get sound working, any ideas?
Sent from my GT-N7100 using xda app-developers app
imapjonny said:
there are a lot of dependencie errors and broken packages when u try to install software(i.e. eclipse). is there a way to fix it
??
Click to expand...
Click to collapse
Depends on what you're installing. Remember this is an ARM powered device and not your normal x86/x64 processor you'll find in a normal laptop or desktop.
castrwilliam said:
Ubuntu 13.04 beta 2 [FINAL BETA]
Click to expand...
Click to collapse
Thanks for this.
When you say final beta I assume you mean final build?
Or do you have plans for something that can be considered past the beta stage of development?
Thanks for this. Things seem to be running alot better than the previous 13.04 build.
A couple things i noticed -
The onscreen keyboard didn't easily come up. I have a bluetooth one so maybe i gave up too soon on trying to get it.
I also have a bluetooth mouse. After a minute or 2 of using it the cursor disappears from the screen. You can tell its still connected because as I move it, various things get hovered on.
Flash player is no longer available for firefox or chromium. I tried linking to the webos flashplayerlib but it still doesn't work. i installed the gnash stuff but that doesn'
t work everywhere.
Thanks again for this though. is working great post from it now.
Isn't there an Open-Source flash player somewhere?
Sent from my Nexus 7 using xda app-developers app
Im not a massive linux user so apologies if this sounds pretty basic, but can tou theme the bar with rhe wifi and clock? I really want the 'classic' ubuntu look...
Sent from my GT-N7100 using xda app-developers app
fach1708 said:
Im not a massive linux user so apologies if this sounds pretty basic, but can tou theme the bar with rhe wifi and clock? I really want the 'classic' ubuntu look...
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Sudo apt-get gnome-shell
Sent from my Nexus 7 using xda app-developers app
Thanks Castrwailliams Great work dude
:good:
Rock On Castrwilliams keep up the good work man
installed it using smackme2

[Touch Interface kexec Bootloader/Installer] nsboot aka NinjaSwag Bootloader beta

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

Need Help Recompiling Kernel

Howdy Folks,
I've been working on porting some ROMS to our device from the Sensation forum and I'm getting closer. I am currently using cygwin in Windows 7 64-bit so that I am able to use dxdia's kitchen. I have been able to successfully decompile both boot.img from the Base (U.S. Stock Vivid) and Port (Elegancia Pegasus) but when I need to recompile, I get the error "Compiling mkbootfs ... Error: mkbootfs not successfully compiled!"
I don't know how to proceed at this point in time. After I get the boot.img working, I'll need to start working on the AROMA script so you might not hear from me for a few weeks (due to work and school). I've been following the guide from http://forum.xda-developers.com/showthread.php?t=2245786. If anyone has experience with using dxdia's kitchen or has a different tool that I can use in Windows, that would be great. I want to keep the development for this phone going until a pick up the Nexus 5 (whenever that may be).
-Apatche

Categories

Resources