Setting Up NDK on Window - G1 Q&A, Help & Troubleshooting

Looking for some assistance getting the NDK working properly on Windows 7 (64).
I followed all of the instructions to set up the NDK in windows but am running into an issue.
Per the instructions you need to install CYGWIN which i did and then go to the root NDK folder and run build/host-setup.sh.
Once I run this i get the following error;
ERROR: Could not find a valid GNU make executable.
Please ensure GNU Make 3.81 or later is installed.
Click to expand...
Click to collapse
I do have GNU make 3.81 installed for windows.
If i try to use cygwin to run a make APP=hello-jni as a test as it states i get the error;
bash: make: command not found
Click to expand...
Click to collapse
if i use windows command prompt i can run the make.exe fine.
I'm thinking the issue is because its trying to use a Linux based make since i would assume Cygwin cannot rune EXE files.
Could anyone assist me with this that has it set up and working properly in windows?

Any takers please?

Check 'Make' package in Cygwin setup.

Do yourself a favor and use a real operating system. Ditch that MSJUNK.
On top of that, I *strongly* suggest that NOBODY EVER use windoze for compiling ANYTHING. When you are building software for other people to use, you most *definitely* do NOT want to build software that has been compromised. Windoze is the world's number ONE compromised platform. It about as save as having your way with a 50 year old street corner hooker without protection.

Related

spxploit help !

Could someone please spend a few minutes and write down the steps to get splxploit working !!! Like myself I think there are a number of people struggling with this.
I am not at all familiar with Linux but I HAVE tried and unfortunately failed.
I used a Live CD of Knoppix, which seems to run fine on my system but I can't get gcc to compile the file. I have tried other Live CD's but couldn't get any others to run properly.
What I have done is unzip the splxploit.c file to the desktop. I then right clicked on the file, went to properties and changed the permissions to read/write. The file appears to be in the directory ramdisk/home/knoppix/desktop .
So I then go to the start menu, and choose run command. I get a popup box where I enter the gcc command line (I also ticked the box to show the process in a terminal window)
I have tried various combinations of the gcc command line,but it aways says unable to find directory/file.
e.g.
gcc splxploit.c -o splxploit
gcc /ramdisk/home/knoppix/desktop splxploit.c -o splxploit
and every other combination I can think of !!
A quick tutorial for those who use windows would be VERY helpful
Thanks
let me get you a statically linked version later
ww2250 said:
let me get you a statically linked version later
Click to expand...
Click to collapse
here you're. unzip it and the binary should run in most linux x86 hosts.
See the splxploit thread:
http://forum.xda-developers.com/showthread.php?t=308691
I just posted a windows version
That is great news !!!! On my Hols, but will check out the windows version when I get back next week. Will let U guyz know how I get on

On-device C#compiler. Help me build it properly...

Hello xDevs
I'm trying these days to port the DotGNU .Net compiler toolchain for the pocket-pc. There was a port in the past (that even has an IDE! Pocket C#), but seems quite outdated and probably abandoned. I want to revive the effort.
Up to now, I have been successful in building (using CeGCC) and running the c# compiler on the Kaiser, but does not seem to be able to compile even the simplest program. So I'm calling out for help from this great community
The compiled toolchain can be downloaded from my site here: http://hypest.org/pnet_0.8.0_wince.zip
Limitations:
Problematic usage through the PocketC# IDE, so you have to use it directly from a command shell. (grab it from here). Even through the console, the usage is "unconfortable" as the compiler spawns a new process and its output is only shown momentarily.
See post #2 for a walkthrough of how to build the toolchain on an Ubuntu 7.10 linux machine (so to reach the point I am up to now).
Thank you,
hypest
walkthrough
This is a walkthrough executed in a console window on an Ubuntu 7.10 linux distro.
0.1 Make sure Flex, Bison and Alien are installed
sudo apt-get install flex bison alien
0.2 Make a directory to work in
mkdir /tmp/pnet_port
cd /tmp/pnet_port
1.1 Get and install CeGCC
wget http://downloads.sourceforge.net/cegcc/cegcc-cegcc-0.51.0-1.i586.rpm
sudo alien -i cegcc-cegcc-0.51.0-1.i586.rpm
2.1 Get and unpack treecc
wget http://download.savannah.gnu.org/releases/dotgnu-pnet/treecc-0.3.10.tar.gz
tar xzvf treecc-0.3.10.tar.gz
2.2 Build treecc
cd treecc-0.3.10
./configure
make
sudo make install
cd ..
3.1 Get and unpack DotGNU Portable.NET
wget http://download.savannah.gnu.org/releases/dotgnu-pnet/pnet-0.8.0.tar.gz
tar xzvf pnet-0.8.0.tar.gz
cd pnet-0.8.0
3.2 Setup proper path
export PATH=/opt/cegcc/arm-wince-cegcc/bin:$PATH
3.3 Get, unpack and apply my patch file
wget http://hypest.org/hypest_pnet.patch.zip
unzip hypest_pnet.zip
patch -p1 < hypest_pnet.patch
3.4 Build pnet
make
4.0 Finished
hypest
What benefits will this give a developer above what Pocket C# will do?
I actually did a repackage of Pocket C# a while back so that it would work on a WM5 device.
I've not used it for a while but someone may be interested in using it to compile on the newer devices.
Here is the link:
http://www.jaml.com/PocketCSharp/
Cheers
Mark
markvan said:
What benefits will this give a developer above what Pocket C# will do?
Click to expand...
Click to collapse
No extra features are to be expected for now I suppose. My goal is to make the toolchain "just work most of the time":
- Pocket C# includes an outdated version of the pnet compiler and perhaps that's the reason it doesn't compile some of my codes (rather simple ones, I should say). So I wanted to try to use the latest possible pnet version.
- the source code Mr Vitaliy Pronkin gave out, is not directly compilable as it seems to include only the files that he modified. I couldn't find the pnet version he used to be able to recompile Pocket C#, so I had to do it "from the beginning".
- I would also like to bugfix the IDE itself (make it landscape-friendly for starters).
A nice bonus of recompiling the pnet toolchain is that it makes other languages available too (java, c...)
markvan said:
I actually did a repackage of Pocket C# a while back so that it would work on a WM5 device.
I've not used it for a while but someone may be interested in using it to compile on the newer devices.
Here is the link:
http://www.jaml.com/PocketCSharp/
Cheers
Mark
Click to expand...
Click to collapse
Thanks for the link Mark.

[GUIDE] How to get Ubuntu on the TouchPad

First off this is completely from Rennat over at PreCentral
-------------------------------------------------------------------------------------
TUTORIAL: How to get the UbuntuChroot up and running for your HP TouchPad
Intro:
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card.
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.
Warnings:
I nor WebOS Internals take no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do endup messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.
Step Zero:
- I have provided 2 different ways to set your device up to install the UbuntuChroot onto your device; use the meta-doctor and create your own doctor (Step 1-A) or do as Step 1-B says and contact my army of monkeys for an easier alternitive that won't take forever.
##You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so! And done hesitate to ask questions.
Step 1-A: Creating a WebOS Doctor
- We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.
- Use the WebOS Internals Guide to installing and running the Meta Doctor. In Step 2 you will have to rename you downloaded webOS doctor to the name of the Bell Mobility doctor they have under Step 2'3 (webosdoctorp100ewwbellmo.jar) go ahead and add the webOS version after it like it advises.
- In Step 2'6, if you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.
- Once the Meta Doctor is done, run the Web's Doctor it created under the 'builds' folder. And setup your device.
Step 1-B: Contacting My Army of Monkeys
- If you are having trouble with or are intimidated by Step 1-A go ahead and contact my army of monkeys at [email protected]. Simple.
Step 2: Mounting the new ext3fc partition on bootup
- Now before we continue we have to make sure we have the partition fully setup and mounted on bootup. To do this follow the below WebOS Internals instructions.
All of this is done on device either via novaterm or an SSH login. (simpler terms mean use WebOS Quick install by connecting you device, opening WebOSQuickInstall, and click Tools-Command Line.) If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:
Code:
mount -o remount,rw /
mkdir -p /media/ext3fs
it is important that you use /media/ext3fs as the location, otherwise some homebrew applications (such as Optware and the Ubuntu 11.04 Chroot) will not be able to find it and use it properly.
After you have created the mountpoint, we are going to edit the fstab file to set it up to mount at bootup.
Code:
mount -o remount,rw /
echo "/dev/mapper/store-ext3fs /media/ext3fs ext3 noatime,data=writeback 0 0" >> /etc/fstab
Now to get it mounted you have several options, the best one is the first command as it will use the data in /etc/fstab. If that works, then you have done this correctly and your ext3fs will mount at bootup.
Code:
mount -a
If you do not want it mounted at bootup, but you do need it mounted, you can use this command.
Code:
mount /dev/mapper/store-ext3fs /media/ext3fs
Click to expand...
Click to collapse
Step 3: Adding Testing Feeds
- Follow these WebOS Internals Instructions to add the Testing Feeds.
NOTE: These are edited slightly and will only work on a Wifi only TouchPad.
- Open Preware and wait for it to finish loading.
- Open the App Menu (tap "Preware" in the top left corner of the screen) and tap Manage feeds.
- Scroll to the bottom until you see the New Feed box.
- Type or paste a name (webos-testing-armv7) and URL (Right Click - Copy Address) sure the URL does *not* have a slash at the end.
- Make sure the IS COMPRESSED option is set to YES.
- Tap Add Feed and then tap Yes when the alert pops up.
- Gesture swipe back. Preware will alert you that you have added feeds and ask if you want to update them now. Choose YES.
Click to expand...
Click to collapse
Step 4: Installing UbuntuChroot, Xecutah, and XServer
- Open up Preware and tap List Of Everything.
- Search for and install the following: UbuntuChroot, Xecutah, and XServer
- Now opened Xecutah and tap XServer and a new card will come up.
- Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.
- Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:
Step 5: Installing Programs
- Now to have some fun after all that work you put in!
- Type the below and it will update the program lists.
Code:
apt-get update
- Now type the following to install what ever you wish!
Code:
/***type the below for AbiWord
apt-get install abiword
/***type the below for the Chromium Browser
apt-get install chromium-browser
/***type the below for GIMP
apt-get install gimp
/***type the below for Eclipse
apt-get install eclipse
/**type the below for LibreOffice
apt-get install LibreOffice
/***type the below for LXDE (a windows graphical interface) and then launch it by typing lxsession.
apt-get install lxde
---------------------------------------------------------------------------------------
agian from precentral enjoy guys
Mods please move to there thread i was in a rush (dead battery) and put it in the wrong forum
Does anything else besides chromium, abiword, eclipse, libreoffice, lxde and gimp work?
linkinpark4175 said:
Does anything else besides chromium, abiword, eclipse, libreoffice, lxde and gimp work?
Click to expand...
Click to collapse
anything you can compile for ARM or want to compile for ARM. there is a apt repository.
You could also find a complete guide to install Ubuntu Linux on HP TouchPad here
same thing
XDAnoobr said:
You could also find a complete guide to install Ubuntu Linux on HP TouchPad here
Click to expand...
Click to collapse
agian that is only for Chroot which is the exact same thing
Works great, now I have lxde on my touchpad.
able to get ubuntu chroot working properly, with libreoffice
now, hunting for a Bluetooth Keyboard
any one going to test if BT Mouses work? (yeah, i know theres a touchscreen)
Is multi-touch supported on this?
what version of libreoffice does it install the latest one? And if anyone has installed it the ubuntu laggy or is it normal.
harsh3090416 said:
what version of libreoffice does it install the latest one? And if anyone has installed it the ubuntu laggy or is it normal.
Click to expand...
Click to collapse
a little laggy sometimes, but still usable most of the time without any problems
libreoffice 3.3.2... you should probably check the ubuntu ARM 11.04 repository to see what is there
top says 1gb ram, 0.90gb used.... not sure why......
EDIT: Tried pairing a BT Mouse... able to find the device via "BT->Search other", but unable to pair properly. Mouse said paired successful, but touchpad couldnt continue, kept searching for devices
Tried "BT->Search Keyboard", but couldnt find the mouse this way
Now they have Debian chroot. Works great as well. Both can coexist at once. All it is is a folder at /media/extfs
Btw, has anyone gotten gnome working? I keep getting segmentation faults.
Is there a way to make that partition without meta doctor?
DJGonzo said:
Is there a way to make that partition without meta doctor?
Click to expand...
Click to collapse
metadoctor makes a partition
you could loop a filesystem ontop of the existing partition to avoid this issue, but the page below recommends against it
http://www.webos-internals.org/wiki/Chrooting
mount: mounting /dev/mapper/store-ext3fs on /media/ext3fs failed: No such file o
r directory
Why am i getting this error when trying to mount? It's really ticking me off as I haven't done anything different from the instructions.
I just spent an hour redoing the whole thing and guess what... i'm pissed off
same ****
samvillian said:
mount: mounting /dev/mapper/store-ext3fs on /media/ext3fs failed: No such file o
r directory
Why am i getting this error when trying to mount? It's really ticking me off as I haven't done anything different from the instructions.
I just spent an hour redoing the whole thing and guess what... i'm pissed off
same ****
Click to expand...
Click to collapse
looks like you didn't do metadoctor properly,
or you didn't make the /media/ext3fs directory,
or "mount -o remount,rw" didn't execute properly
1st problem: your touchpad should have around 10GB free(out of 16GB, or do the math if you have a 32/64gb)
2nd problem: go back to cmd prompt and check that /media/ext3fs exists
3rd problem: reinstall via webos doctor and do it again
kevina90 said:
Now they have Debian chroot. Works great as well. Both can coexist at once. All it is is a folder at /media/extfs
Btw, has anyone gotten gnome working? I keep getting segmentation faults.
Click to expand...
Click to collapse
Sorry, this is off topic. I'm sure Android will get here, but I really want to use my Touchpad (I haven't done much because I figured everything would get wiped anyway this weekend), so I think I'm going to give Linux a go. My understanding of Linux is rather crap. I thought Linux was the OS, and Ubuntu and other things were just GUIs to make it easier for people unfamiliar with command line. How could Debian simultaneously coexist?
I know I could go to wikipedia and look around and try to understand it, but by chance does anyone know any website that kinda describes Linux to beginners? I don't just want to follow the directions step by step on the guide (although its brilliant, looks very easy)without having the slightest effin idea what everything is, you know? Its weird, Linux confuses me, I don't know why. I've used ubuntu a number of times but it's just browsing firefox, not exactly rocket science!
Thanks if you can easily give link and press send then thanks but don't go out of your way, I can find something eventually, but I don't want someone else mucking around for my sake. Its no emergency.
Komodo Rogue said:
Sorry, this is off topic. I'm sure Android will get here, but I really want to use my Touchpad (I haven't done much because I figured everything would get wiped anyway this weekend), so I think I'm going to give Linux a go. My understanding of Linux is rather crap. I thought Linux was the OS, and Ubuntu and other things were just GUIs to make it easier for people unfamiliar with command line. How could Debian simultaneously coexist?
I know I could go to wikipedia and look around and try to understand it, but by chance does anyone know any website that kinda describes Linux to beginners? I don't just want to follow the directions step by step on the guide (although its brilliant, looks very easy)without having the slightest effin idea what everything is, you know? Its weird, Linux confuses me, I don't know why. I've used ubuntu a number of times but it's just browsing firefox, not exactly rocket science!
Thanks if you can easily give link and press send then thanks but don't go out of your way, I can find something eventually, but I don't want someone else mucking around for my sake. Its no emergency.
Click to expand...
Click to collapse
I would just find a book on amazon about linux with good reviews made in the past 1-2 years. I would look for one that is distribution neutral.
The reason you can have webos on there and another version of linux is because it's basically installed in another partition (not really, but that's the easiest way I can describe it to you). The actual details of how chroot works are different, but that should relate enough to you to get what it it is.
Linux is the Kernel. Debian, Ubuntu, Fedora and the rest are distributions of that kernel along with a GUI, and programs to make it a fully functional OS like Windows or OS X.
The Debian and Ubuntu on WebOS is minimal pared down distribution with no gui.
I just went thru all the steps , contacting the army of monkeys, and installed all the preware stuff.
I get Service Error Unable to run command : /sbin/initctl start org.webinternals.debian-squeeze etc etc
Unknown job org.webosinternals.debian-squeeze-chroot.
I got this with the Ubuntu chroot too. any ideas?
paperWastage said:
looks like you didn't do metadoctor properly,
or you didn't make the /media/ext3fs directory,
or "mount -o remount,rw" didn't execute properly
1st problem: your touchpad should have around 10GB free(out of 16GB, or do the math if you have a 32/64gb)
2nd problem: go back to cmd prompt and check that /media/ext3fs exists
3rd problem: reinstall via webos doctor and do it again
Click to expand...
Click to collapse
I've redone webos doctor like 4 times already.
How do I check if the directory exists? Plus i'm on a fresh 32gb, so its not that.
thanks
edit: i tested to see if the directories existed and i found a possible error.
i just cd to the folder to see if it exists, and media/ext3fs existed.
but the /dev/mapper/store-ext3fs doesn't exist apparently...
would that be the issue?

Linux ON droid not IN android question????

Ok, this goes out to any and all DEVs out there. We all know by now that we (some people not me) can run linux within android using the loop mounts, vnc viewer, etc... Now how about REPLACING android with a linux distro like debian or maybe even what these guys use http://openpandora.org/ ..... its linux based and has an arm CPU.. Any way I'm talking about flashing over android wiping the internal sorage and installing linux on it or even using the boot loader to flash over android???, of course this is getting rid of any 3g connection and phone usage. I understand that, I am talking about giving our RETIRED droid 1s a use. I wanna see my D1 run a linux distro in full hardware mode NO MORE ANDROID. now dont get me wrong I love android as much as the next guy, but why now flash something else to it???
Another link I found, this is for windows mobile but hey, similar idea.
http://wing-linux.sourceforge.net/trac/wiki/FAQ
P.S. I AM NOT A DEV JUST AN IDIOT WITH AN IDEA!! my ignorance is NOT bliss and I would love to know if this is even possible. I'm willing to help ANY WAY I CAN. lol
THANKS!!!
I don't think it's possible. Because of the locked bootloader we're forced to use Motorola's bug-ridden Kernel and as Android's Kernel is a heavily modified Linux Kernel it most likely won't run an ordinary Linux distro.
But I'm no expert either
Milestone is locked, Droid is not ...
Maybe this will help (if you don't know german, you can use Google Translate):
http://www.android-hilfe.de/anleitu...debian-chroot-mit-lxde-auf-dem-milestone.html
Thanks for the replies. Again the USA Droid 1 is nit locked or at least has been completely unlokcked. I've read a million "run debian on android" posts... I don't need to know German to see that the post above is the same thing. Like I said before I have NO INTEREST IN RUNNING LINUX ON ANDROID. I want TO REPLACE android completely with Linux to make a device like the openpandora handheld from my first link.
Any one up to the challenge????
Thanks again!
Really, no one??
I've been running Debian on my Droid booting from the SD card for a while, more recently trying Arch Linux after realizing that anything optimized for ARMv7, VFPv3, NEON, or Thumb-2 (I'm not sure which unfortunately) won't boot because of a page fault or something. Ubuntu, MeeGo, and Angstrom just kernel panic and don't give any useful information even at the highest debugging level. I'm back to using an ARMv5te Arch Linux build (http://archlinuxarm.org) although I could just as well use Debian. I really wish Ubuntu worked for multitouch.
Well, I got the touchscreen calibrated! I forgot that my screen rotation hack only rotated the framebuffer It's stuck in portrait for now. I decided to use mtev (MeeGo's multitouch X11 input driver) after being fed up with evdev's aversion to being rotated, but now that I'm back to the stock portrait rotation evdev should work fine.
If you want instructions, either PM me or wait until I post a full guide and/or my patched kernel tree. It's not super difficult, but it's a lot of command line use and compiling.
What works:
*CPU and SD card (obviously )
*Touchscreen (single touch/portrait only for now)
What needs work:
*Keyboard mapping is wrong, the number keys and symbols don't work. I need to figure out how Android handles Alt. I had to patch the GPIO keyboard driver because the keyboard worked in the console but not in X11, which expects EV_SYN.
*Sound is OSS only, but there is no mixer device, so aumix is useless and there's no volume control or sound output.
*I haven't tried the SGX driver, so I can't comment on hardware acceleration yet.
*Battery charging relies on battd, which is a proprietary Android binary from Motorola. It might run on Debian with "ls -s / /system" and the creation of the socket it expects (init.sholes.rc I believe), but I'm not getting my hopes up.
Untested:
*WiFi (needs firmware, but should work)
*Bluetooth
*Calls/data
*Sensors (although the accelerometer and compass seem to be recognized by evdev)
I'll upload my kernel, either as patches or on GitHub (or binaries if there's enough demand) once I get around to fixing the keyboard issue. Fingers crossed that I don't get carried away cleaning up the kernel, or worse yet, give up...
This is incredible news! I'm so glad to hear it. Of course you are running in hardware mode? Not through android? If so I'm super exited about this! I love arch Linux, I run it on all my computers and I understand it more than any other distro I've tried. I would love to give it a shot, though I'm not that great at compiling I think it will be worth it.
As I said before I am in no way a dev or even a Linux pro, but I can get by and if theres any way I can help this project become "complete" I'm willing to learn what ever is necessary to do so.
Also were u able to get an x server running? Possibly a DE? That would be crazy awesome.
Thanks a million, looking foreword to work with you and make this happen!
For anyone who's interested, I put together a quick package containing my kernel patches, configuration notes, and an automated kernel build script.
It's pretty self-explanatory aside from the installation of the root filesystem, which I leave up to your imagination
As I've probably repeated several times now, I've run Debian and Arch Linux natively on my Droid with my patched kernel (no chroot or VNC "hack"). With enough determination, it's possible to run practically anything on it - personally, I'm determined to get Ubuntu on it.
WOOT... insta-fail for me LOL you have it set up to work in specific directories? I thought i placed everything right but I guess not.. I got an error on the first line of output lol
Welcome to gTan64\'s lazy Droid kernel compiler\!
build.sh: line 5: [: missing `]'
build.sh: line 5: -z: command not found
build.sh: line 5: -z: command not found
Entering $WORK
Applying patches
build.sh: line 16: /*.patch: No such file or directory
mv: cannot stat `/arch/arm/boot/compressed': No such file or directory
cp: cannot stat `/compressed': No such file or directory
Setting up build
cp: cannot stat `/GNUmakefile': No such file or directory
cp: cannot stat `/sholes_config': No such file or directory
FIXME! No numeral or symbol input until someone finds a third-level
modifier key to use instead of AltGr for the keyboard.
cp $MISC/defkeymap.map $K_SRC/drivers/char
Building kernel!
make: *** No targets specified and no makefile found. Stop.
Kernel build done!
You have done something amazing, I'm just to stupid to figure it out my self. XD
I can understand why you would want ubuntu with all its pre-setup glory and support for nearly all hardware but dont you think its a little heavy for this hardware? lol I doubt you would try to use the Unity UI but I doubt that alone would even fit in ram LOL you could just use the ubuntu packages and drivers with debian maybe?
THANKS AGAIN!!!!
That's what happens when I don't test my own scripts
I was thinking too much about making it easy. Just try applying my patches to your tree manually.
Code:
cd kernel_src
patch -p1 <../patches/first.diff
patch -p1 <../patches/next.diff #and so on...
#Obviously, substitute the paths of the actual patches ;)
#Finally, copy sholes_config to .config and invoke 'make'.
It's actually much simpler than my script makes it, and you don't need my convoluted folder setup.
UM lol I cant find any patch files? are they in the ZIP? or do I have to obtain them elsewhere?
I can tell this is gonna be a hell of a project LOL
THANKS!!!
"Duh" moment - I used the .diff file extension instead of .patch
I'm such a scatterbrain... Remind me not to release anything before testing
EDIT: Strike that, reverse it. They're .patch files.
I AM BLIND lol I found them... BUT.. when I try to patch. terminal just seems to lock up... I press enter, the curser moves to the next line but it doesnt do anything. lol how long should 1 patch take?? its been about 10 minutes and I leave it be for now
EDIT:
LOL i forgot the "<" in the command OOPS but I'm not seeing any .config file or folder in the source to copy the sholes_config too. yes I have show hidden files on.. PS unfortatly usinf Fedora 15 gnome 2...... (on server so I can work on this anywhere through vnc )
THANKS
When I said "copy sholes_config to .config", that's literally what I meant. .config is the Linux kernel build configuration file, not a folder.
'cp /path/to/sholes_config .config' from your kernel tree should do it.
Oh, I forgot to mention that you need an ARM cross-compiler/toolchain. I use the gcc-arm-linux-gnueabi package in Ubuntu, but I don't know what the Arch equivalent is off the top of my head.
The "GNUmakefile" is just a convenience, it exports "ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-" before calling the actual makefile. If you don't have an ARM cross compiler in your path, it won't build at all. If you do, modify CROSS_COMPILE to point to it - on some systems it's called arm-unknown-linux-gnueabi, etc. etc.
Let me know if you get anywhere before it errors out.
OK I put the config file in the kernel_src but unfortainatly I'm using Fedora 15 XP I installed arm-gp2x-linux-gcc which is the fedora arm gcc I guess... lol so wha would I edit in the .config to make it point to arm-gp2x-linux-gcc. Its not my first attempt to compile an android kernel but I've never been succesfull LOLOL
thanks
I'm pretty sure that toolchain won't work - the GP2X was ARMv5 IIRC, so unless it's a newer build of GCC (4.3 or higher) and you're absolutely sure it supports the ARM EABI and the ability to generate ARMv7 instructions (which is unlikely if it's pre-4.1), I would recommend a newer toolchain.
CodeSourcery makes a pretty solid one: https://sourcery.mentor.com/sgpp/lite/arm/portal/release1803
If you end up using it, you can change the second line in GNUmakefile to "CROSS_COMPILE=arm-none-linux-gnueabi-". Don't worry about changing .config.
Well I DLed the linux/GNU installer and it gave me "arm-2011.03-41-arm-none-linux-gnueabi.bin" LOL
so I was thinking would it just be easier to just use my lappy with crunchbang (debian based) so I can follow ur instructions with deb / apt-get LOL fedora is a ***** and it dont have what I need... I cant find an arm v7 cross compiler for it
thanks
.bin files are the Linux equivalent of Windows EXE installers. Run it like this:
Code:
#cd /path/to/installer.bin
./installer.bin
#substitute the actual name, of course.
It needs root permissions if you want to install it to /usr/local (sudo ./installer.bin or su -c 'sh installer.bin'). You can also install it to /usr, but that will make it more tedious to uninstall later. If you decide to install it in your home folder - say ~/toolchain - you don't need root permissions, but you will need to add ~/toolchain/bin to your path:
Code:
export PATH=$PATH:$HOME/toolchain/bin
To be honest, I prefer Ubuntu to Fedora/OpenSUSE/$RPM_distro, so if you have access to a Debian or Ubuntu system, using that would make my life easier
Omg duh... the "non_Linux" part of the name true me off lol i'll start doing this on my laptop it's deb based crunchbang. I prefer anything over rpm distros too but it was a quick painless install on my server XP thanks ill try this when I get home
Sent from my DROIDX using XDA App

[TOOLS] Create unlock.img, fix boot.img, repack update.bin (for aboot

The attached archive includes 3 tools for those of you with .3.2.3.2 (or earlier) bootloaders.
Since other tools (and earlier version of these very tools) are available and working well,
this is mostly meant as an entry to an imaginary beauty contest. (JOKING!!!)
cuber.py
a generic gmpy2-free reimplementation of @vortox's signature.py
use this to generate your unlock.img
cuboot.py (uses cuber.py)
a Python-only reimplementation of @vortox's cuber
includes fixes to the kernel command-line and the device-tree
use this to convert a standard Amazon boot.img (>=.4.x.x)
upHDX (uses cuboot.py)
bash script to repack Amazon updates for TWRP
could be DANGEROUS, use with care
tested on Apollo for both 14.4.5.2 and 14.4.5.3
my unit is fully 14.4.5.3 now, except for aboot (which is 3.2.3.2)
should work on Thor as well
Those with bootloader .3.2.6 and lower can downgrade to .3.1.0
and upgrade the bootloader to the latest vulnerable version .3.2.3.2.
Those with .3.2.7 and higher appear to be out of luck with forged signatures, but I hear there's progress on rooting .4.5.2.
The python scripts have been tested on the following OS / Python combinations:
Windows: 2.7.9 and 3.4.3
Linux: 2.7.9 and 3.3.4
OSX: 2.6.? (cannot quite remember)
In addition to the tools themselves, I also included "educational" examples
(examples.sh for Linux/OSX, examples.bat for Windows).
These make use of the split.py script, which is otherwise unnecessary.
(The Windows example also shows that simply echoing your manfid/serial
combo to cuber.py -the way one does in Linux/OSX- won't work due to
the carriage-return character introduced by the echo command.
You'll need to handcraft a file matching the '0x%02x%08xn' format...)
Another batch file py..bat is meant as an extra aid for Windows users
to avoid trouble with setting paths and such. You should be able to simply
download and install your preferred Python version.
Open a command shell (cmd.exe), navigate to wherever you extracted the
archives, and type 'py PYTHON-SCRIPT ARGS' to run the Python scripts.
(This handholding intentionally does NOT work for the upHDX script.)
Hopefully, someone will find these simple tools useful.
EDIT: To unlock your bootloader (<=.3.2.3.2), you'll need adb and fastboot.
On Linux, most distributions package these separately. Look for android-tools-{adb,fastboot} or some such.
For Windows, you can get these from the official Android SDK (which is a **large** download,
with a lot more tools you won't need, if you don't already use them, but it's safe).
Alternatively, there's a very legit-looking project here an XDA, with a much smaller
download, fast install, and exactly the tools you need. I haven't used either... (-;
The actual unlock procedure is described here and here.
EDIT#2: I added another script 'cublock.py' to make unlock.img generation super easy both on Windows and Linux.
MD5( tools.zip) = c17fc91344bd3b4b040129a79a39741f
EDIT#3: Fixed issues with older versions of certain tools on Debian 7.
MD5( tools.zip) = 4f93ab667fd61db26c83675ce0bd6d9f
EDIT#4: Fixed a bug when 'cuber.py' is used directly from the command line.
MD5(tools.zip) = 67b4a6d65aa2b0aa3500b122c8a25290View attachment 3210856
XDA:DevDB Information
HDXtools, Tool/Utility for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
draxie
Version Information
Status: Alpha
Created 2015-03-13
Last Updated 2015-03-13
Thank for your works.
Can I use upHDX to remove bootloader, recovery from 4.5.3 and flash via TWRP?
Thanks
tuanda82 said:
Thank for your works.
Can I use upHDX to remove bootloader, recovery from 4.5.3 and flash via TWRP?
Thanks
Click to expand...
Click to collapse
Let's hope so. That's what I did, in any case.
I'm an adventurer; so, I ran './upHDX fw update-kindle-14.4.5.3_user_453011120.bin',
pushed the resulting update-kindle-14.4.5.3_user_453011120-upHDXfw.zip to my HDX 8.9
and installed it with TWRP.
Worked for me, but I cannot provide any guarantees, unfortunately.
It may be wise to omit 'fw', and doublecheck that you're happy with the contents of the
updater-script in the newly generated archive.
AND, -of course- make sure your bootloader version is at most .3.2.3.2!!!
draxie said:
Let's hope so. That's what I did, in any case.
I'm an adventurer; so, I ran './upHDX fw update-kindle-14.4.5.3_user_453011120.bin',
pushed the resulting update-kindle-14.4.5.3_user_453011120-upHDXfw.zip to my HDX 8.9
and installed it with TWRP.
Worked for me, but I cannot provide any guarantees, unfortunately.
It may be wise to omit 'fw', and doublecheck that you're happy with the contents of the
updater-script in the newly generated archive.
AND, -of course- make sure your bootloader version is at most .3.2.3.2!!!
Click to expand...
Click to collapse
Thanks. But your upHDX scripts is for linux user only. I am on Windows .
If you have time could you upload your xxxx_14.4.5.3_xxxx.zip? Thanks
draxie said:
The attached archive includes 3 tools for those of you with .3.2.3.2 (or earlier) bootloaders.
Since other tools (and earlier version of these very tools) are available and working well,
this is mostly meant as an entry to an imaginary beauty contest. (JOKING!!!)
cuber.py
a generic gmpy2-free reimplementation of @vortox's signature.py
use this to generate your unlock.img
cuboot.py (uses cuber.py)
a Python-only reimplementation of @vortox's cuber
includes fixes to the kernel command-line and the device-tree
use this to convert a standard Amazon boot.img (>=.4.x.x)
upHDX (uses cuboot.py)
bash script to repack Amazon updates for TWRP
could be DANGEROUS, use with care
tested on Apollo for both 14.4.5.2 and 14.4.5.3
my unit is fully 14.4.5.3 now, except for aboot (which is 3.2.3.2)
should work on Thor as well
Those with bootloader .3.2.6 and lower can downgrade to .3.1.0
and upgrade the bootloader to the latest vulnerable version .3.2.3.2.
Those with .3.2.7 and higher appear to be out of luck with forged signatures, but I hear there's progress on rooting .4.5.2.
The python scripts have been tested on the following OS / Python combinations:
Windows: 2.7.9 and 3.4.3
Linux: 2.7.9 and 3.3.4
OSX: 2.6.? (cannot quite remember)
In addition to the tools themselves, I also included "educational" examples
(examples.sh for Linux/OSX, examples.bat for Windows).
These make use of the split.py script, which is otherwise unnecessary.
(The Windows example also shows that simply echoing your manfid/serial
combo to cuber.py -the way one does in Linux/OSX- won't work due to
the carriage-return character introduced by the echo command.
You'll need to handcraft a file matching the '0x%02x%08x\n' format...)
Another batch file py..bat is meant as an extra aid for Windows users
to avoid trouble with setting paths and such. You should be able to simply
download and install your preferred Python version.
Open a command shell (cmd.exe), navigate to wherever you extracted the
archives, and type 'py PYTHON-SCRIPT ARGS' to run the Python scripts.
(This handholding intentionally does NOT work for the upHDX script.)
Hopefully, someone will find these simple tools useful.
EDIT: To unlock your bootloader (<=.3.2.3.2), you'll need adb and fastboot.
On Linux, most distributions package these separately. Look for android-tools-{adb,fastboot} or some such.
For Windows, you can get these from the official Android SDK (which is a **large** download,
with a lot more tools you won't need, if you don't already use them, but it's safe).
Alternatively, there's a very legit-looking project here an XDA, with a much smaller
download, fast install, and exactly the tools you need. I haven't used either... (-;
The actual unlock procedure is described here and here.
EDIT#2: I added another script 'cublock.py' to make unlock.img generation super easy both on Windows and Linux.
MD5( tools.zip) = c17fc91344bd3b4b040129a79a39741f
Click to expand...
Click to collapse
Thanks a lot for the good work but id like to let tell you that it will be great if you can explain all the entire work in layman's terms because there would be many people having hundreds of questions and concerns.
Just an advice if you feel worthy... No disrespect intended...
I would like it in layman terms...
And how to do it on Windows. This seems like confusion for me. I have no idea where to start.
I did it all in windows 8.1 64 bit edition.
With help from this post:
http://forum.xda-developers.com/showpost.php?p=58897784&postcount=67
get Python 2.7 for windows and install it >>https://www.python.org/download/releases/2.7/
btw I installed the 64 bit edition for both
get GMPY2 for Python 2.7 https://code.google.com/p/gmpy/downloads/list
Follow the post for step by step. I encountered some trouble with fast boot driver, I had to remove the driver and install a generic one I selected from windows then I manually installed it. Ran the fast boot command to unlock and I was unlocked. a lot easier than it looks.
Reckerr said:
I would like it in layman terms...
And how to do it on Windows. This seems like confusion for me. I have no idea where to start.
Click to expand...
Click to collapse
Appreciate it. Will attempt Saturday after a read through.
Works on Windows...
tuanda82 said:
Thanks. But your upHDX scripts is for linux user only. I am on Windows .
If you have time could you upload your xxxx_14.4.5.3_xxxx.zip? Thanks
Click to expand...
Click to collapse
Actually, I tested upHDX in Windows using Cygwin.
I had to select zip and unzip in the Archive group and python in the Python group
in the installer to get all the dependencies in place, and the only issue I faced was a few filename collisions
in the /system/media/audio/ringtones folder (case-sensitivity problem).
Code:
[COLOR="Lime"]>[/COLOR] diff -ru cygwin/ linux/
Only in linux/system/media/audio/ringtones: ANDROMEDA.ogg
Only in linux/system/media/audio/ringtones: CANISMAJOR.ogg
Only in linux/system/media/audio/ringtones: Hydra.ogg
Only in linux/system/media/audio/ringtones: PERSEUS.ogg
Only in linux/system/media/audio/ringtones: URSAMINOR.ogg
These could just be copied from the original update-*.bin after installation.
Reckerr said:
I would like it in layman terms...
And how to do it on Windows. This seems like confusion for me. I have no idea where to start.
Click to expand...
Click to collapse
If you could spell out what you mean by 'it', I might be able to help.
yujikaido79 said:
I did it all in windows 8.1 64 bit edition.
With help from this post:
http://forum.xda-developers.com/showpost.php?p=58897784&postcount=67
get Python 2.7 for windows and install it >>https://www.python.org/download/releases/2.7/
btw I installed the 64 bit edition for both
get GMPY2 for Python 2.7 https://code.google.com/p/gmpy/downloads/list
Follow the post for step by step. I encountered some trouble with fast boot driver, I had to remove the driver and install a generic one I selected from windows then I manually installed it. Ran the fast boot command to unlock and I was unlocked. a lot easier than it looks.
Click to expand...
Click to collapse
Of course, if you want to make it more difficult for yourself,
you can use the older version of my tool as well.
The new one is not limited to Python 2.7, but works on both current Python versions;
and does NOT require GMPY2.
Also, if you are looking to unlock your bootloader, the 'cublock.py' script is your friend.
You just pass in the manfid and serial (separately; no need to fuse them).
Whether you choose to install Python standalone or as part of Cygwin is up to you.
The latter also includes 'bash' and lets you convert the Amazon update to a TWRP-friendly ZIP.
draxie said:
Of course, if you want to make it more difficult for yourself, you can use the older version of ny tool as well.
The new one is not limited to Python 2.7, but works on both current Python versions; and does NOT require GMPY2.
Also, if you are looking to unlock your bootloader, the 'unlock.py' script is your friend.
You just pass in the manfid and serial (separately; no need to fuse them).
Whether you choose to install Python standalone or as part of Cygwin is up to you.
The latter also includes 'bash' and lets you convert the Amazon update to a TWRP-friendly ZIP.
Click to expand...
Click to collapse
I have Windows 7 and Nexus 2.0.5 with bootloader from http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504 installed Python 2.7 and the adb and fastboot and driver package from post 1
Using
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
And unlock.py and then
adb reboot-bootloader
And
Fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock <unlock file>
fastboot -i 0x1949 reboot
IT was very easy, I only had some driver problems in fastboot mode
Uphdx don't work on debian 7
Bruder Torgen said:
I have Windows 7 and Nexus 2.0.5 with bootloader from http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504 installed Python 2.7 and the adb and fastboot and driver package from post 1
Using
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
And unlock.py and then
adb reboot-bootloader
And
Fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock <unlock file>
fastboot -i 0x1949 reboot
IT was very easy, I only had some driver problems in fastboot mode
Click to expand...
Click to collapse
FYI - followed this process on an identical environment with identical results. Struggled a bit more with Windows drivers; if you're having trouble this might help (posts 8-10).
im running this version 13.3.0.2 and im a newbe with kindle what should I do
benyo8990 said:
im running this version 13.3.0.2 and im a newbe with kindle what should I do
Click to expand...
Click to collapse
Welcome to the HDX forums. How to proceed depends on what you want to accomplish. Read through the various threads to see what is available and the effort required. If your goal is to root and/or install custom roms you MUST disconnect from WiFi as Amazon will attempt to upgrade your tablet to the lastest Fire OS. Should that happen your options will be severely limited.
Two words of caution:
1) Kindles are not like other devices. Tough to tame and easy to brick. If you approach modding with a casual attitude you'll probably end up with a non-recoverable brick. READ, READ, READ before doing anything. Ask questions when you are ready.
2) There are no tidy fail-safe tutorials for the HDX. There is work and risk involved. You have to do your homework first. No one is going to hold your hand (sorry for the lecture - just trying to set expectations early).
More info please!
dpeddi said:
Uphdx don't work on debian 7
Click to expand...
Click to collapse
Given that it worked for me even in Cygwin on Windows 7, this sounds odd.
Nevertheless, I'd appreciate more info on how it fails (and which flavor of Debian 7
you are using; so, that I have a chance to reproduce your issue).
UPDATE: Nevermind. I fired up a VM with Debian 7.8.0-amd64-standard,
and found out for myself. Apparently, 'df' in 'coreutils 8.13' used here
doesn't support the '--output' option; AND, python 2.7.3 is more strict
about the input types to 'unpack'. I fixed these and the script worked.
I'll post the new version in a second.
DF --optional not supported, $m seems to not be set
Thank you for posting this awesome tool. I am running 13.4.5.2 with a twrp recovery and the most recent available (without breaking twrp) kernel.
My question is, if worst case scenario happens and I try to use cygwin to upHDX, it does not work, but I think it did, and I install a partially working update, am I bricked? Or, will it just write over my kernel and recovery with no hope of going back. As I type this, I am thinking the answer is, both are possible, but thought I would ask before breaking things.
Sent from my KFTHWI using Tapatalk
[Edit] If you know what you are doing, this script is very helpful. I especially enjoy how it explains everything it does as it does it. So, you can see the files it changes. I used cygwin and it worked perfectly. If you understand the Unix command tools, it is a piece of cake. I do not mean to belittle the risk involved, it is significant, however, if you read what is happening, and know this worked, and can be assured there is no issue with your recovery, you can still roll back if something goes wrong. Do not take this comment as minimal risk, the risk is substantial, and you need to wipe to go back. One of my devices did not take the update well (My fault), and, I had to go back. These devices do not handle wipes well. So, the moral of the story.
-This is an excellent and versatile tool,
-There is significant risk
-If you do your research, follow directions, and meet the requirements, you can get success. Have your cake and eat it too on your terms!!
-With this tool, I have the most recent update, root, and twrp (Amazon apps work too).
Thanks again for the tools.
[/Edit]
lekofraggle said:
My question is, if worst case scenario happens and I try to use cygwin to upHDX, it does not work, but I think it did, and I install a partially working update, am I bricked? Or, will it just write over my kernel and recovery with no hope of going back. As I type this, I am thinking the answer is, both are possible, but thought I would ask before breaking things.
Click to expand...
Click to collapse
I saw you managed fine, but just in case anybody else wonders,
the script will bail at the first sign of error and you'll know it.
Of course, this won't guarantee that things cannot go wrong,
but minimizes the chances that they go unnoticed.
NOTE, HOWEVER that:
This has only been tested on 4.5.2 and 4.5.3; and, I would strongly recommend against blindly running it on newer releases (as the pattern matching that's being relied upon for what to throw away --including the anti-rollback fuse stuff-- might easily get broken with relatively minor changes.
A good sanity check is to unzip both the original update and the newly created "sanitized" version, and compare them (e.g. via a recursive diff) to doublecheck if the changes are sensible.

Categories

Resources