Database Info

Android gingerbread 2.3.1 on Nokia N900 step by step installation guide

A step-by-step Android installation guide for Nokia N900 Users
Things you will Need:
1: Your nokia n900
2: Any Micro SD card (i used a 2GB)
---------------------
For this installation you need to Enable all repositories from App Manager (you need to input those information manually and be precise):
The configuration below is for N900 up to firmware PR 1.1.1:
Application manager --> Application catalogs --> New
Catalog name: maemo.org
Web address: http://repository.maemo.org/extras/
Distribution: fremantle
Components: free non-free
----------------------
The configuration below is for N900 for firmware PR 1.2:
Application manager --> Application catalogs --> New
Catalog name: maemo.org
Web address: http://repository.maemo.org/extras/
Distribution: fremantle-1.2
Components: free non-free
-----------------------
The configuration below is for N900 for firmware PR 1.3:
Application manager --> Application catalogs --> New
Catalog name: maemo.org
Web address: http://repository.maemo.org/extras/
Distribution: fremantle-1.3
Components: free non-free
------------------------
Second step :Install rootsh from app manager or from this site : http://maemo.org/downloads/product/Maemo5/rootsh/
-------------------------
Third step we will use X-terminal (here get your fingers ready )
basic commands used : root( to give root access) ls (list files in a folder or directory) mkdir (create directory) rmdir (removes directory this command is specially used if you Used any NITDroid before and created AND directory in the root of the phone) Ok lets get started Type in X-terminal :
root
apt-get update (to download packages needed make sure you are connected to internet )
apt-get install nitdroid-installer
y
y (if its asks again)
-------------------------------------
After this you have to download two files on your PC:
1st file : http://downloads.nitdroid.com/e-yes/gingerbread.tar.bz2
2nd file: http://downloads.nitdroid.com/nitinstaller/Packages/nitdroid-kernel-2.6.28-06_final1_armel.deb
-------------------------------------
Once you downloaded those files make sure you copy them to the root phone memory ( once you connect it to the pc tap the mass storage mode and just copy them to the phone memory for example lets say its H: just open H: and copy it there)or for other users they can copy it anywhere as long as they put the path correctly
--------------------------------------
After you have successfully copied the files open the x-terminal and typeNOTE:be precise and take care for space)
root
cd /home/user/MyDocs (cd(space)/home/user/MyDocs)
bzip2 -d gingerbread.tar.bz2 (bzip2(space)-d(space)gingerbread.tar.bz2) WAIT
cd /home (cd(space)/home)
mkdir /and (mkdir(space)/and)
cd / (cd(space)/)
mount /home /and (mount(space)/home(space)/and)
cd /and (cd(space/and)
tar xvf /home/user/MyDocs/gingerbread.tar (tar(space)xvf(space)/home.......or the path you put the file in
dpkg -i /home/user/MyDocs/nitdroid-kernel-2.6.28-06_final1_armel.deb (write this one like this as it here with all spaces / _ . -
-----------------------------------------------------------
Now You have to install two more updates to Patch some Bugs in the OS.
First Is Codec Update:http://downloads.nitdroid.com/e-yes/gingerbread_update1.tar.bz2
second VOIP update :http://downloads.nitdroid.com/e-yes/gingerbread_update2.tar.bz2
copy both files in directory like the before 2 files
------------------------------------------------------------
After downloading both the files Again open X-terminal and type
root
mount /home /and
cd /home/user/MyDocs
bzip2 -d gingerbread_update1.tar.bz2
cd /and
tar xvf /home/user/MyDocs/gingerbread_update2.tar
Make sure you install the updates correctly.
-------------------------------------------------
After the updates are installed you are done Installing Android Gingerbread On your Nokia n900 . just slide open your keyboard and reboot your phone. you will get a Dual Boot Option screen Select Nitdroid And Unleash the Gingerbread Power.
For more visit Nitdroids official wiki

Wow, i've been waiting for a step by step post. And some of the posts i read said it needs a minimum 4GB SD card. Will all the features work, i mean calls and internet with 3G with other basic phone features ? This is for my wife and all she does is to go to FB, calls and text Is the Market working ?
Thanks again for the lovely tip

zeus09 Thanks for reply .....for me calls sometimes work sometimes not i need to fix it, camera also is not working, otherwise everything is working fine but you can try it and see it wont brick your device i will work on 2.3.3 to fix those minor bugs here....try it and tell me whats wrong so i can develop it more

Oh yeah, I'm gonna have the phone charged fully now. Gonna give it a shot tomorrow morning. Wish me good luck man . Hope I will not brick it ha ha

hey man go for it dont worry ! and if you need anything tell me here ill help you

Hi
I just want to know if someone could help me..
I found a problem on my n900 at ''apt-get update'' it said 99%(working) but then it said fail after a while it said some packages would be ignored, or the old ones would be used instead
apt-get install nitdroid-installer
It then said nitdroid couldnt be found
If someone could help it would be great..tnx

I found the problem tnx but the airplane mode is always on..

Just a? . Would this work for any nokia. Um say e7? Irs the same nokianess?
Sent from my Defy. Using XDA App.

I can't install the updates....

I can't install the updates. I receive the message: "Can't open input file gingerbread_update1.tar.bz2: No such file or directory."
I tried several times and always the same error. I put the 2 files in the root as i did with the first 2 files.
Please help!!!!

deviljf it worked for you ? just fine? is there any kind of deley ? but in both ways its nice to have android on n900 the concept is awesome even with some minor bugs ,,thanks for trying it man

metal_n ...you must specify the directory and the path well other wise it wont work ....but now if you reboot your phone and open the keyboard and choose nitroid you can boot it ... if you face the same problem... tell me ill try to help you but its matter of pathing only man and thanks for trying it

gplock ... no it wont work mate... sorry cuz nokia e7 is based on Symbian^3

^ damn nokia. Fingers crossed they go android n not windows. Good job man thanks for sharing
Sent from my Defy. Using XDA App.

First of all thanks a lot for the easy steps you have provided,
On the other hand we have two issues:
1. This version as many as other versions does not support the Mic, or the cam plus other features on the droid system
2. For the users that are trying to follow the steps you will face one issue, make sure to add the following:
root
mount /home /and
cd /home/user/MyDocs
bzip2 -d gingerbread_update1.tar.bz2
----------------->bzip2 -d gingerbread_update2.tar.bz2
cd /and
tar xvf /home/user/MyDocs/gingerbread_update2.tar
Hope to hear from u when you get the full version
Regards,

Hey, jut installed it on my n900 and it's pretty good... A few things don't work right, but it's pretty impressive - I think it's faster than my old g1 already!
Points of interest:
Wifi seems to work but very slowly...
No 3G but I can't seem to add an APN in the network settings...
I made a call but I don't think the speaker was working...
Marketplace is acting weird but probably because of slow connection
Anyway it's awesome that it's working at all - great job mate!
Rick

Rick glad you like it thanks mate for trying it

silver386.....ill try my best thanks for replay

i cant install the nitdroid-installer
error
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package multiboot
Click to expand...
Click to collapse
also when i type apt-get update its says.
failed to fetch repisitory devil
failed to fetch moff mozilla
some index files failed to download.. they have been ignore or use the old ones used insteal
Click to expand...
Click to collapse
i solve the previous problem
now the last one when i install the nitdroid-kernel-2.6.28-06_final1_armel.deb
error
files list file for package 'com.ea.app.sim; contains empty filename
Click to expand...
Click to collapse
how to solve?

I managed to get an APN added - it was me being dense but no 3G. Been doing a bit of reading and it appears that the 3G radio is not fully working with android at the moment...
Do you think that is going to be possible to have android able to make calls properly or is this just going to be a fun hacking experiment.
Either way is fine - it's the journey I enjoy with these things not necessarily the destination...
Thanks again for your efforts
Rick

Guide [Linux][Android]Android on Linux for complete Android dummies

As a new Android user, it take me hours, if not days, to understand some very basic Android concepts. So here we are:
Welcome to the Android on GNU/Linux for complete Android dummies
Introduction
The first concept to understand is that Android, even if it is based on a Linux kernel, is not GNU/Linux, it is Android. That imply some huge differences, the first ones being the file hierarchy and what you can do or not do with that file hierarchy. :cyclops: :crying: :cyclops:
To illustrate that difference, on GNU/Linux, you can copy, move, modify or delete any file, the only condition for that is to have the corresponding access rights. As root, you can do whatever you want on the whole file hierarchy.. On Android, you cannot do that, because the device comes with built-in protections that can save your device if you make a wrong manipulation, but get in your way when you want to make a backup or restore it..
To make things worst on GNU/Linux, even if Android is reasonably well supported, the actual Android support of your installation will depend on your distribution, your WM/Desktop and what software is actually installed.
My distribution is Gentoo, my desktop FVWM-Crystal. That imply I will use generic solutions that should work in any combination of distribution/desktop. The way to install the software will differ, the main difference being that Gentoo use 'emerge' to install the software, when Debian use 'apt' and the rpm based distributions use 'rpm' (or Yast in Suse, etc.).
Note: The command that must be issued as root will be prefixed by '$ ', the command that must be issued as your normal user will be prefixed with '# '.
Android
The most important thing to understand is:
To make a full backup of an Android device, it must be rooted or have a Recovery mode with backup
That imply you must first unlock your phone and install a Recovery.
To make a full backup of an Android device, it must be rooted or have a Recovery mode with backup
That imply you must first unlock your phone and install a Recovery.
To make a full backup of an Android device, it must be rooted or have a Recovery mode with backup
That imply you must first unlock your phone and install a Recovery.
To make a full backup of an Android device, it must be rooted or have a Recovery mode with backup
That imply you must first unlock your phone and install a Recovery.
To make a full backup of an Android device, it must be rooted or have a Recovery mode with backup
That imply you must first unlock your phone and install a Recovery.
To be able to root your device, you must have a Recovery, which imply the device must be first unlocked.
As long your device is not unlocked and don't have a Recovery, what you will be able to backup is device dependent. It can vary from nothing to not much.
When you understand that, you can begun to work in an efficient manner.
MTP
Most recent Android devices use MTP to communicate via the USB bus. MTP mean Media Transport Protocol. What a given device will provide via MTP is device dependent. It will also vary if it is locked or not, and if it is rooted or not.
Android on GNU/Linux
It is 3 ways to communicate via MTP. The first one is using mtpfs, the second one via rsync, the third one via adb.
mtpfs
We will not use plain mtpfs, because it give unreliable results. Instead, it is several other tools that have a much better MTP support, and we will use them.
On Gentoo, it is a global USE flag 'mtp' that will enable MTP support in all programs that have optional MTP support. It is a good thing to add it in /etc/portage/make.conf and update your system as usual before continuing.
Also, for mtpfs to work, as with other pluggable devices, we need to be into the plugdev group:
To check it:
Code:
# groups
wheel audio cdrom video games usb users portage android vboxusers roccat plugdev dom
If you are not into the plugdev group:
Code:
$ gpasswd -a YOUR_USER plugdev
You can now logout and login.
KDE
kio-mtp is a slave for KDE's KIO framework. After installing it, your MTP devices appear e.g. in Dolphin. You may have to logout and login.
Gnome
I don't use Gnome at all (no systemd, *kit, udisks and the like here, which imply a Gnome free system ). See XFCE as Gnome use gvfs, it should work with Nautilus too.
XFCE
PcManFM support MTP via gvfs. If it doesn't work, check your distribution documentation. On Gentoo, to have mtp as global USE flag will add MTP support in gvfs. Alternatively, you can add it for gnome-base/gvfs in /etc/portage/package.use. This should work for Thunar too.
On Debian, it is a package called gvfs-mtp.
gMTP
gMTP is a simple MTP client for Solaris and Linux based on GTK+.
After its installation, launch it, click on connect. A few seconds later, you will get the file hierarchy of your device. You can start to manipulate the files. It support features like Album, Artwork and play lists. The actual support of a given feature can depend on your device and on the libmtp version.
Media players
Many media players have built-in or optional MTP support. Those players include Amarok, Audacious, Rhythmbox and others. MTP support on these players can vary, as example with Audacious it depend on plain mtpfs and is completely buggy at that time of writing (April 2014). On the other hand, if you use another MTP file system implementation like gphotofs, simple-mtpfs or go-mtpfs, you can use any GNU/Linux software with your MTP devices.
gphotofs
gphotofs is a FUSE file system for interfacing with digital cameras using gphoto2. Most modern mobile phones are cameras at the same time, and gphotofs can be a good alternative to simple-mtpfs or go-mtpfs. gphotofs is used among other by professional cameras and is therefore very well tested and reliable.
You can also install software like gtkam, and your MTP device will appear automatically into them. That can be very useful if you take a lot of pictures with your phone.
After installation, to mount the device:
Code:
# mkdir ~/AndroidDevice
# gphotofs ~/AndroidDevice -o allow_other
To unmount the device:
Code:
# fusermount -u ~/AndroidDevice
I really prefer to manually mount the device. When done, you can use any file manager to browse its files, and any graphic or media software as well. Please be aware that, due to limitation with the MTP protocol (it can only deal with complete files), it is better to copy your files locally and to work on these copies.
simple-mtpfs
It work the same than gphotofs.
After installation, to mount the device:
Code:
# mkdir ~/AndroidDevice
# simple-mtpfs ~/AndroidDevice
To unmount the device:
Code:
# fusermount -u ~/AndroidDevice
go-mtpfs
Another MTP FUSE implementation.
On Gentoo, we need to unmask 2 packages in /etc/portage/package.keywords:
Code:
dev-libs/go-fuse **
sys-fs/go-mtpfs **
That will install these 2 packages directly from their source code repositories:
Code:
$ emerge --ask go-mtpfs
As usual, to mount the device:
Code:
# mkdir ~/AndroidDevice
# go-mtpfs ~/AndroidDevice &
To unmount the device:
Code:
# fusermount -u ~/AndroidDevice
rsync
rsync is a software mainly used to make professional backups and restores, or to synchronize websites. The main advantage of rsync is that it is possible with it to automatize the process of backup and restoration.
To use it, you need to install rsync.
Code:
$ emerge --ask rsync
In /etc/rsyncd.conf:
Code:
# /etc/rsyncd.conf
# Minimal configuration file for rsync daemon
# See rsync(1) and rsyncd.conf(5) man pages for help
# This line is required by the /etc/init.d/rsyncd script
pid file = /var/run/rsyncd.pid
use chroot = yes
read only = yes
# Simple example for enabling your own local rsync server
#[gentoo-portage]
# path = /usr/portage
# comment = Gentoo Portage tree
# exclude = /distfiles /packages
[backup]
path = /home/dom/rsync
list = yes
comment = personnal backup
hosts allow = 192.168.178.*
The exact content of that file may be dependent on your distribution. You also have to adapt the variables 'path' and 'host allow' to your actual configuration. rsync will not use the USB but your WAN network (typically the wi-fi). In that example, the backup will be find in /home/dom/rsync and all the devices on your local home network will be allowed to access it via rsync. For testing purpose, you can comment the hosts allow line, this will allow any host.
When done:
Code:
$ /etc/init.d/sshd start
We also need to install rsync backup for Android by Michal Kowalczuk in the phone.
TODO: continue the rsync setup to the end and put some examples.
adb.
ADB mean mean Android Debug Bridge, and it is a part of the Android Software Development Kit (SDK). We will need it anyway to flash the Android devices.
To install it on Gentoo:
Code:
$ emerge --ask android-sdk-update-manager
This will install just an infrastructure. To actually install, manage and update the Android SDK, just run:
Code:
$ android
.
As emerge modify the PATH environmental variable, that for the Android SDK to work well, the best thing to do at that point is to reboot your computer. It doesn't append often on GNU/Linux, but that time it is best to do so.
On other distribution, if it doesn't provide a package to install it, you have to download the SDK from Get the Android SDK. It is several threads on the forum that deal with that:
[GUIDE/Linux] Install Android SDK the "Linux way"
[APP] Linux-on-Android project (Complete Linux Installer) (more for developers this one)
Now, we are ready to play with our phone.:good:
Operations on files
To be able to play with the files in your phone, you don't need to install all the above packages. The one that is really needed is adb. After that, all depend of what you want to do and what kind of integration you want into your GNU/Linux system.
Anyway, it is cool to be able to play with the phone with any file manager. This is why I would recommend to also install one of gphotofs, simple-mtpfs or go-mtpfs. If you also have a MTP camera, go for gphotofs, you will need it anyway. From my short experience, simple console based solution like gphotofs are more reliable than GUI solution (with the notable exception of gMTP and gphoto2 GUI like gtkam), and after mounting they allow the use of any file manager, player, etc.
Where we are now, what files you will be able to see and to operate on will depend on your device. We are not even unlocked.
If you still not believe me, read that: Solution Available for 4.x Devices: This solution will not back up and restore contact, SMS or calendar information
With my HTC One, I can copy the content of the whole sdcard. Most interesting are the Download, Movies, Music and DCIM folders.
It is just to plug the phone on the USB, mount it as explained above, and use any file manager to copy the files. We can also copy new files into the phone.
This must be enough to get you started. From here, you may want to continue with something like [Tutorial] Root, Unlock, Recovery and flashing a Custom ROM . Choose the one that correspond to your device.
If you want to start developing for Android, you may be interested by [GUIDE][WIN/LINUX] A COMPLETE ANDROID DEVELOPMENT GUIDE FOR NEWBIES-SArnab©®.

[Q&A] Running Ubuntu natively on the Shield Tablet

Q&A for Running Ubuntu natively on the Shield Tablet
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Running Ubuntu natively on the Shield Tablet. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

It's amazing
Wow, it is really great that we will be able to run Ubuntu on the Shield!!
As of now, how would you describe the performance of it? Is it laggy or running smoothly? Also, do I understand correctly from your fist post that wifi is not working? Is there other functions not working?

dual boot
Also, as someone managed to get an android /ubuntu dual boot?

Teve1982 said:
Wow, it is really great that we will be able to run Ubuntu on the Shield!!
As of now, how would you describe the performance of it? Is it laggy or running smoothly? Also, do I understand correctly from your fist post that wifi is not working? Is there other functions not working?
Click to expand...
Click to collapse
it works well enough, I don't have anything to compare it to but it's not slow or anything
WiFi and Bluetooth work now. Touchscreen doesn't work, and I don't know yet if it ever will on Linux. Touchscreen works too!
Teve1982 said:
Also, as someone managed to get an android /ubuntu dual boot?
Click to expand...
Click to collapse
it's already dual boot, Linux stays in its own directory on the userdata partition

miscellaneous info
Hi guys, I'm totally noob with linux and ubuntu so my question may be stupid:
How Can I dualboot lollipop and ubuntu on the shield tablet?
If I use the img linked here what is the command that I must use to flash on tablet? I need only that file or I need something else?
I saw that the image kernel file is updated frequently to implement new feature, how can I upgrade to a new version?
Thanks a lot and be patient with me
Polve72

Interest is peaked.
Sent from Bad Azz VZW LG G3 Cyan Tapatalk

Unable to complete boot
Hey guys,
so i followed the instructions to the letter, or at least i think so.
1. downloaded the latest boot image. new_boot(94)
2. downloaded , unpacked and repacked the files from nvidia as explained
3. transferred repacked bz2 file to device, unpacked in /data/linux/
4. booted using fastboot command with command extra command line arguement.
given that i add the extra command line argument, then ubuntu seems to boot fine, but it stops after a while with the last report being :
"enable autosuspend for nvidia bruce"
nothing seems to be happening after that...
i have tried the two previous boot images also, but the same thing happens... any ideas?

Ubuntu issues
Hey,
I tried following the directions on the post. I got the device rooted and unlocked the bootloader, cwm is installed, busybox is installed, and root checker says I am rooted. I also followed the directions and have the root file system moved across into /data. When I use fastboot to load the image, I get a kernel panic. Things are scrolling pretty quickly but it looks like the busybox operations that are trying to mount certain areas keep failing saying no such file or directory. It almost seems like from the bootloader, it can't see /data, however I am able to mount it via cwm and see the files are there via adb. One of the error messages I got on the boot was that "mount /dev/mmcblk0p24 on /data failed invalid argument". Would you have any idea what I might be missing here. One thing I did notice while following the directions was that sudo ./apply_binaries.sh did not seem to do anything, it just displays the usage info like it was expecting different arguments.
Any suggestions you have for me would be much appreciated.
Thanks.

polve72 said:
Hi guys, I'm totally noob with linux and ubuntu so my question may be stupid:
How Can I dualboot lollipop and ubuntu on the shield tablet?
If I use the img linked here what is the command that I must use to flash on tablet? I need only that file or I need something else?
I saw that the image kernel file is updated frequently to implement new feature, how can I upgrade to a new version?
Thanks a lot and be patient with me
Polve72
Click to expand...
Click to collapse
At the moment, I honestly can't recommend trying this if you have no Linux experience, it's still WIP (for example, the touchscreen and Bluetooth won't work without additional configuration), and this is still ARM so most closed-source software (such as most games) still won't work (at least not at acceptable performance levels). But, if you still want to try, you need to follow the instructions from the post that contains the boot.img downloads (mainly the rootfs part). At the moment there's no real solution for dual-booting, but it's possible to flash the boot.img to the recovery partition (after which, booting the recovery will go to Linux instead). Good luck!
dud3rin0 said:
Hey guys,
so i followed the instructions to the letter, or at least i think so.
1. downloaded the latest boot image. new_boot(94)
2. downloaded , unpacked and repacked the files from nvidia as explained
3. transferred repacked bz2 file to device, unpacked in /data/linux/
4. booted using fastboot command with command extra command line arguement.
given that i add the extra command line argument, then ubuntu seems to boot fine, but it stops after a while with the last report being :
"enable autosuspend for nvidia bruce"
nothing seems to be happening after that...
i have tried the two previous boot images also, but the same thing happens... any ideas?
Click to expand...
Click to collapse
Can you please post a picture of the screen when it gets stuck? (the bruce message usually appears after the rootfs is mounted, so since it doesn't continue, that probably failed). apply-binaries.sh should work fine, if it didn't run I think it would still boot, but there will be no GPU acceleration for sure (and maybe no X11 at all).
jfsir said:
Hey,
I tried following the directions on the post. I got the device rooted and unlocked the bootloader, cwm is installed, busybox is installed, and root checker says I am rooted. I also followed the directions and have the root file system moved across into /data. When I use fastboot to load the image, I get a kernel panic. Things are scrolling pretty quickly but it looks like the busybox operations that are trying to mount certain areas keep failing saying no such file or directory. It almost seems like from the bootloader, it can't see /data, however I am able to mount it via cwm and see the files are there via adb. One of the error messages I got on the boot was that "mount /dev/mmcblk0p24 on /data failed invalid argument". Would you have any idea what I might be missing here. One thing I did notice while following the directions was that sudo ./apply_binaries.sh did not seem to do anything, it just displays the usage info like it was expecting different arguments.
Any suggestions you have for me would be much appreciated.
Thanks.
Click to expand...
Click to collapse
It's possible that your internal memory isn't recognized by the kernel. I'll send you a PM later today with a custom kernel so that we can start debugging this, I've had this issue before but I'm pretty sure I fixed it early on.

@Bogdacutu
I think you'll right. I'll wait a better and more user friendly approach.
Polve72

Thanks. Any help is much appreciated.

Thank you
@Bogdacutu Thank you very much for this!!!! buntu runs fairly smooth on my Tablet. But how will you get x86 software run on ARM? I thought there is no way.
Best Regards

aarr_ee said:
@Bogdacutu Thank you very much for this!!!! buntu runs fairly smooth on my Tablet. But how will you get x86 software run on ARM? I thought there is no way.
Best Regards
Click to expand...
Click to collapse
qemu can run in userspace (so it can run x86 software relatively seamlessly without a full VM), but x86 apps can't load ARM libraries, so x86 apps don't have direct rendering (which slows them down even more than they are already)

Portable
Is there any way to make this possible for the Shield Portable?

Great project,
Are you able to play any linux games with decent fps? I ask because ive found following video:
https://www.youtube.com/watch?v=hRBPeNzE558

thewolf16 said:
Great project,
Are you able to play any linux games with decent fps? I ask because ive found following video:
https://www.youtube.com/watch?v=hRBPeNzE558
Click to expand...
Click to collapse
Pretty much any game compiled for ARM will work, so Steam games won't work without QEMU (and so far I haven't been able to get Steam to actually start properly), which would mean some performance loss.

Thank you for your answer
Will this work with your build?:
https://www.youtube.com/watch?v=uVknjU7eGbI
https://www.youtube.com/watch?v=4GUP27TJ5w4
This would be much faster than qemu.
EDIT: And can you run the 2D adventure game "Edna & Harvey: The breakout". Its an windows game but because its made in java you can run it natively on linux with the java-installer:
java -jar ednaunpack.jar
Click to expand...
Click to collapse

thewolf16 said:
Thank you for your answer
Will this work with your build?:
https://www.youtube.com/watch?v=uVknjU7eGbI
https://www.youtube.com/watch?v=4GUP27TJ5w4
This would be much faster than qemu.
Click to expand...
Click to collapse
Probably. I'm not planning to pay for that anytime soon as I really dislike their licensing scheme, so I can't know for sure if it works or not.
EDIT: decided to buy it, apparently they don't give you the license automatically, so I might have to wait a day or so until I get it

Not Enabled Bluetooth...
Hi,
I have the SHIELD TABLET 16GB Wi-Fi model and succeeded to run Ubuntu with new_boot(123).img!
Recently, I try to the bluetooth configuration to use bluetooth keyboard. However I cannot enable bluetooth.
To enable bluetooth, I do the following commands on terminal.
Code:
sudo aptitude install bluetooth bluez-hcidump bluewho bluez-tools blueman
git clone https://code.google.com/p/broadcom-bluetooth/
cd broadcom-bluetooth
make brcm_patchram_plus
sudo cp brcm_patchram_plus /usr/local/bin
sudo brcm_patchram_plus -d --patchram /system/etc/firmware/bcm43241.hcd --baudrate 3000000 --enable_lpm --enable_hci --use_baudrate_for_download --no2bytes --tosleep 1000 /dev/ttyTHS2
After brcm_patchram_plus, these message is shown.
Code:
option patchram with arg /system/etc/firmware/bcm43241.hcd
option baudrate with arg 3000000
option enable_lpm
option enable_hci
option use_baudrate_for_download
option no2bytes
option tosleep with arg 1000
/dev/ttyTHS2
writing
01 03 0c 00
writing
01 03 0c 00
(...looping)
The last 2 lines are looping until do Ctrl-C on terminal.
So I try to change the bluetooth setting from "OFF" to "ON" on the Unity's System Setting Panel.
After that, I retry the brcm_patchram_plus command and its output message is changed as bellow.
Code:
...
writing
01 18 fc 06 00 00 c0 c6 2d 00
received 7
04 0e 04 01 18 fc 00
Done setting baudrate
writing
01 27 fc 0c 01 01 01 01 01 01 01 00 00 00 00 00
received 7
04 0e 04 01 27 fc 00
Done setting line discpline
the brcm_patchram_plus doesn't finish until Ctrl-C. In this state, I can open the "Bluetooth New Device Setup" Panel.
However, I cannot find any bluetooth devices...(attatched picture) So I open the other terminal and type some commands.
Code:
$ hciconfig -a
hci0: Type: BR/EDR Bus: UART
BD Address: 43:24:1B:00:00:00 ACL MTU: 1021:8 SCO MTU: 64:1
DOWN
RX bytes:642 acl:0 sco:0 events:36 errors:0
TX bytes:983 acl:0 sco:0 commands:38 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: Dm1 DM3 Dm5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
$ hcitool dev
Devices:
$ rfkill list
0: bluedroid_pm: Bluetooth
Soft blocked: yes
Hard blocked: no
1: phy0 Wreless LAN
Soft blocked: no
Hard blocked: no
2: brcmfmac-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
$ rfkill unblock all
$ rfkill list
0: bluedroid_pm: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0 Wreless LAN
Soft blocked: no
Hard blocked: no
2: brcmfmac-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
$ hcitool scan
Device si no available: No such device
Please give me any advices!
Thanks,

How to make a keyboard and mouse work on it?
Thanks

[ROOT] Universal (temporal) root tool for dirtycow-capable Android M devices

Hi,
I've developed an universal & stable temporal root tool for "dirtycow-capable" Android M (and N?), i.e., without the 2016-11-06 patch.
It bypasses selinux via a vdso backdoor inside the init process which is injected by a memory-only dirtycow exploit.
This approach has the following advantages:
Memory-only: does not modify the filesystem
Scalable: easy to add new kernel and/or new devices
Stable: does not affect stability of your device
Reversible: the backdoor is cleared immediately after the root shell ends, which means no reboot is required after usage
Please use version v0.1.1 instead of v0.1 which has a severe bug!
Attention:
By "SELinux bypass" I mean the payload will run in init domian even if SELinux is in enforcing mode, however, a patch to sepolicy is still needed for making init domain unconfined. Usually this means a modified boot image is required.
Details, releases, usage and the source code is available at Github.
Maybe I'll turn it into a SuperSU installer in the future. Donations are welcome.
XDA:DevDB Information
VIKIROOT, Tool/Utility for all devices (see above for details)
Contributors
hyln9
Source Code: https://github.com/hyln9/VIKIROOT
Version Information
Status: Testing
Created 2017-01-20
Last Updated 2017-01-21

Hi, I am working on the LG Tribute HD model LGLS676 and we are looking for an exploit for MM 6.0.1 build MXB48T. is it possible to create a 32-bit version of this exploit? It's exactly what we need right now for a method to gain root as not even temp is not even close to possible, lg has this one airtight. I'm running Ubuntu 16.04.01 64 bit and can help test if needed on my device. Thanks in advance for any help you can or cannot provide ?

Sands207 said:
Hi, I am working on the LG Tribute HD model LGLS676 and we are looking for an exploit for MM 6.0.1 build MXB48T. is it possible to create a 32-bit version of this exploit? It's exactly what we need right now for a method to gain root as not even temp is not even close to possible, lg has this one airtight. I'm running Ubuntu 16.04.01 64 bit and can help test if needed on my device. Thanks in advance for any help you can or cannot provide
Click to expand...
Click to collapse
Thanks for your reply.
Unfortunately, 32-bit vDSO support is not available for Android currently.

hyln9 said:
Thanks for your reply.
Unfortunately, 32-bit vDSO support is not available for Android currently.
Click to expand...
Click to collapse
Could we use a different backdoor/exploit for x86 devices?

AptLogic said:
Could we use a different backdoor/exploit for x86 devices?
Click to expand...
Click to collapse
Great idea, I'll have a try in the emulator.

Hello and thank you for this!
I am stuck and need your help here please... I'm on an LG V10 (H960A) mm, and I think I followed the instructions on GitHub correctly:
1. Extracted the "exploit" binary
2. adb push /data/local/tmp
3. adb shell (cd to /data/local/tmp and made "exploit" executable)
4. Executed the "exploit"
and now I am stuck in "waiting for reverse connect shell". Turning device on/off, toggling Bluetooth etc does nothing... How should I proceed? Thanks in advance!

ftaios said:
Hello and thank you for this!
I am stuck and need your help here please... I'm on an LG V10 (H960A) mm, and I think I followed the instructions on GitHub correctly:
1. Extracted the "exploit" binary
2. adb push /data/local/tmp
3. adb shell (cd to /data/local/tmp and made "exploit" executable)
4. Executed the "exploit"
and now I am stuck in "waiting for reverse connect shell". Turning device on/off, toggling Bluetooth etc does nothing... How should I proceed? Thanks in advance!
Click to expand...
Click to collapse
A debug version was added to the download page.
Would you please run it as before and send me the two generated debug info file "vdso_orig.so" and "vdso_patched.so" to me? They are just dump of some part of kernel and don't contain any personal information.
My e-mail address is: hyln9$live.cn (replace $ with @)
Thanks!

@hyln9 how goes the looking for a 32bit exploit? I'm available to test any developments that have been made, using an AT&T Galaxy S5 running Android 5.0 ((I can upgrade to 5.1.1 or 6.0 if needed)
(Try exploiting wpa_supplicant )

hyln9 said:
A debug version was added to the download page.
Would you please run it as before and send me the two generated debug info file "vdso_orig.so" and "vdso_patched.so" to me? They are just dump of some part of kernel and don't contain any personal information.
My e-mail address is: hyln9$live.cn (replace $ with @)
Thanks!
Click to expand...
Click to collapse
Just sent them to you...

hyln9 said:
A debug version was added to the download page.
Would you please run it as before and send me the two generated debug info file "vdso_orig.so" and "vdso_patched.so" to me? They are just dump of some part of kernel and don't contain any personal information.
My e-mail address is: hyln9$live.cn (replace $ with @)
Thanks!
Click to expand...
Click to collapse
I also sent!!

Is there any way this can with for the at&t lg g5 h820 I believe. I hope so that is the only thing I hate with this phone. No root. So boring.

What port should we be using? When I use the non-debug version it hangs waiting for the reverse connection... using the debug version it dies before even creating a log file it says: "Internal error: unknown kernel." I'm running an AT&T G5 (H820) without the latest patches...

rvyhmeister said:
What port should we be using? When I use the non-debug version it hangs waiting for the reverse connection... using the debug version it dies before even creating a log file it says: "Internal error: unknown kernel." I'm running an AT&T G5 (H820) without the latest patches...
Click to expand...
Click to collapse
did you reboot phone?
and maybe you don't get error.

Not executable 64 bit elf file?

jcpowell said:
Not executable 64 bit elf file?
Click to expand...
Click to collapse
That means you're trying to run this 64 bit exploit on a 32 bit android system. The exploit doesn't work on 32 bit because 32bit systems don't have vdso. I'm working on a different exploit and I think this dev is too but I don't expect much out of my tests since it's mostly device specific.

iptr9 said:
did you reboot phone?
and maybe you don't get error.
Click to expand...
Click to collapse
Rebooted... running the debug
Now I get this
Syscall error: bind at line 392 with code 13.
No files are created... what port should I tell it? Thanks!

rvyhmeister said:
Rebooted... running the debug
Now I get this
Syscall error: bind at line 392 with code 13.
No files are created... what port should I tell it? Thanks!
Click to expand...
Click to collapse
maybe you have to cd into /data/local/tmp
and then ./exploit

iptr9 said:
maybe you have to cd into /data/local/tmp
and then ./exploit
Click to expand...
Click to collapse
I've done that... the interesting thing is that if I run simply
./exploit
it replies
CVE-2016-5195 POC FOR ANDROID 6.0.1 MARSHMALLOW
Usage:
./exploit port: use local terminal.
./exploit ip port: use remote terminal.
If I enter any number, it then fails...

rvyhmeister said:
I've done that... the interesting thing is that if I run simply
./exploit
it replies
CVE-2016-5195 POC FOR ANDROID 6.0.1 MARSHMALLOW
Usage:
./exploit port: use local terminal.
./exploit ip port: use remote terminal.
If I enter any number, it then fails...
Click to expand...
Click to collapse
try a port above 1024

saspipi said:
try a port above 1024
Click to expand...
Click to collapse
thanks.... it starts fine.... but then hangs waiting for the reverse shell to connect.... I've got the zip with the two debug files that I'm attaching

General 32-bit ARM Application Checker

With the news that the Pixel 7 is now restricting applications to 64-bit only, I have created a shell script that can be ran on your old phone to check for any armeabi-v7a only applications that will not run on the Pixel 7.
Obviously this script does not make much sense to run on a Pixel 7, but this will help anyone prepare for switching over and give you a heads up if you won't be able to bring over any apps.
As far as I know almost all applications from the Play Store should already be arm64-v8a as Google has been enforcing this requirement on the Play Store for over 3 years now, but any ancient apps that have not been updated for years might still be 32-bit.
There's two methods to run the script, and two different scripts that can be ran.
Both methods will take some time so be patient if you have a lot of user installed applications.
ADB from computer (root not required)​
Make sure you have ADB debugging enabled, platform-tools installed, and your old phone plugged in
Run adb shell
You should now be dropped into a shell on the device
If you aren't then you should try making sure ADB debugging is enabled on the phone, that your phone has authorized your computer, and that the adb server is running on your computer
Paste and run the following command:
for PACKAGE in $(pm list packages -3 | sed "s/^package://"); do if ! pm dump "$PACKAGE" | grep -E "^Dexopt state:" -A4 | grep -q "arm64:"; then echo "$PACKAGE is 32-bit ARM and will not function as of now on the Pixel 7 or later."; fi; done
Any applications that only have 32-bit binaries will be output.
Example:
Code:
raven:/ $ for PACKAGE in $(pm list packages -3 | sed "s/^package://"); do if ! pm dump "$PACKAGE" >
com.dotgears.flappybird is 32-bit ARM and will not function as of now on the Pixel 7 or Android 14.
raven:/ $
If nothing is output then you are fine and have no applications that are only 32-bit.
On Device​The following script will be ran, it will also be attached to this post if you want to download it. This is a bit more verbose.
Code:
#!/bin/sh
echo "Script will check for user installed packages that are 32-bit ARM."
echo "This may take a while."
for PACKAGE in $(pm list packages -3 | sed "s/^package://"); do
if ! pm dump "$PACKAGE" | grep -E "^Dexopt state:" -A4 | grep -q "arm64:"; then
echo "$PACKAGE is 32-bit ARM and will not function as of now on the Pixel 7 or later."
FOUND="1"
fi
done
if [ -z "$FOUND" ]; then
echo "No user installed 32-bit packages found."
fi
echo "Script done."
Either download the script or copy the above code and paste it into an empty file. Make sure you don't mangle it if you are pasting it and to name it arm32appchecker.sh.
Terminal Emulator (root required)​
Use your favorite terminal emulator (I prefer TermOne Plus)
Make sure you have functional root, and that you navigate to where the script is or supply the path to it
Make sure the above script is on your phone somewhere accessible
Navigate to the directory where it is (most likely /sdcard/Download)
Run the following command
su -c sh arm32appchecker.sh
Over ADB (no root)​
Make sure you have ADB debugging enabled, platform-tools installed, and your old phone plugged in
Make sure you get the script on to your device, either via adb push arm32appchecker.sh /sdcard/Download or download it.
Run the following command on your computer
adb shell sh /sdcard/Download/arm32appchecker.sh
Any applications that only have 32-bit binaries will show up. This script will also let you know if there aren't.
Example:
Code:
raven:/sdcard/Download $ su -c sh arm32appchecker.sh
Script will check for user installed packages that are 32-bit ARM.
This may take a while.
No user installed 32-bit packages found.
Script done.
raven:/sdcard/Download $
What Can I Do If I Have 32-bit Apps?​If you have old APKs then I suggest trying to find some new ones. Check on APKMirror for the application to see if there are any newer ones or variants that are built for arm64-v8a. If the application is from a developer directly then try reaching out to them.
Beyond that, there is nothing else that can be done at the moment. It's theorized that the change is only in the Android zygote process, and that the phone still has a full compliment of 32-bit libraries. It is entirely possible for a custom ROM or Magisk module could patch zygote and you can then launch 32-bit apps.
What we do know is that the chipset (Tensor G2 - GS201) is still using ARMv8-A processors that support AArch32, so it's not a hardware limitation.

It is my intention to at some point also create a script that will use aapt to check any downloaded APKs you have. This script will be Linux only, but I will give the commands used so you could cobble together one for Windows. I used to actually have a script to do this several years ago, but have lost it since.
A couple more things to note.
Any applications that are wildly out of date, like built for Android 1-2 might not run at all on Android 13 if they are trying to get permissions that are blocked now. You're not going to get around that if the application isn't functioning because of permission changes.
There is evidence that Google might be forcing this change with phones launching with Android 14. This certainly sets a deadline for new devices going forward. They may also force this change with upgrades to Android 14, but it is currently speculation.

Oh I'm loving this, thank you!
But seems like I'm the only one who voted "yes" haha! (haven't used your script yet but I think I have older apps that are not updated anymore that are probably 32 bits)

Ghisy said:
Oh I'm loving this, thank you!
But seems like I'm the only one who voted "yes" haha! (haven't used your script yet but I think I have older apps that are not updated anymore that are probably 32 bits)
Click to expand...
Click to collapse
That's what I thought originally, I scrolled all the way to the bottom of my previously installed on the Play Store and found the oldest application that hasn't been updated. It was from 2014 so I was certain it was going to be 32-bit, however much to my surprise it was actually 64-bit.
I actually don't have a single application that is 32-bit only, I had to download Flappy Bird from APKMirror just to have a test case for the script.

Thank you, wise one! This confirms the problem I was having installing some of my favorite modded apps yesterday. It will be interesting to see if the apps get updated and/or there is a workaround at some point.

Alright, I have 12 apps that are 32-bit and not compatible with the P7P.
Most of these I can uninstall/replace but it seems like the Instagram mod I'm using is 32 bit-only. Surprisingly, the Amazon App Store is one of them too. Cr*p!

Ghisy said:
Alright, I have 12 apps that are 32-bit and not compatible with the P7P.
Most of these I can uninstall/replace but it seems like the Instagram mod I'm using is 32 bit-only. Surprisingly, the Amazon App Store is one of them too. Cr*p!
Click to expand...
Click to collapse
Same with the Instagram Moded apk. I guess we'll have to wait a bit.

Supermaxness said:
Same with the Instagram Moded apk. I guess we'll have to wait a bit.
Click to expand...
Click to collapse
I've emailed the dev of the one I'm using. I'll PM you if I get a reply (not too sure we're allowed to talk about this here).

For direct, quick and dirty checking an apk (either on your desktop or device) you can just do an unzip and a grep.
The details are dependent on how unzip and grep take flags and the listing format.
Code:
C:\>7zip l fennec-68.11.0.multi.android-arm.apk|grep lib
247300 169274 lib\armeabi-v7a\libfreebl3.so
26376 12943 lib\armeabi-v7a\liblgpllibs.so
132744 60551 lib\armeabi-v7a\libmozavcodec.so
144924 70955 lib\armeabi-v7a\libmozavutil.so
1213340 485264 lib\armeabi-v7a\libmozglue.so
1164536 764454 lib\armeabi-v7a\libnss3.so
352812 176726 lib\armeabi-v7a\libnssckbi.so
14196 7407 lib\armeabi-v7a\libplugin-container.so
141344 85415 lib\armeabi-v7a\libsoftokn3.so
58525688 31002207 lib\armeabi-v7a\libxul.so

Thanks for the script! Looks like I only have about 3 apps that won't work on my P7P when it arrives.
I ran it over wireless ADB.

The script isn't working on my phone, it's listing a bunch of apps that I know have 64-bit (or might be pure java/kotlin) such as Swift Backup.
When I break it down, the pm dump has output, but piping that to the grep -E does not

Is this how the script should work? If yes, does it mean that I have none 32-bit apps on my phone? Thank you

davidgro said:
The script isn't working on my phone, it's listing a bunch of apps that I know have 64-bit (or might be pure java/kotlin) such as Swift Backup.
When I break it down, the pm dump has output, but piping that to the grep -E does not
Click to expand...
Click to collapse
I have Swift Backup on my phone and it doesn't show up. Which method did you use? What phone do you have? What version of Android are you running?
flashbac76 said:
Is this how the script should work? If yes, does it mean that I have none 32-bit apps on my phone? Thank you
Click to expand...
Click to collapse
You're not doing it right, you're just pasting the script into the terminal emulator or letting it try to read and paste the file for you, download the script from the attachment in the post and follow the directions for a terminal emulator with root. If you still can't get it to function or don't have root then try the ADB method that is listed right after the terminal emulator method.

Ghisy said:
Alright, I have 12 apps that are 32-bit and not compatible with the P7P.
Most of these I can uninstall/replace but it seems like the Instagram mod I'm using is 32 bit-only. Surprisingly, the Amazon App Store is one of them too. Cr*p!
Click to expand...
Click to collapse
I just checked and it's absolutely hilarious that the Amazon App Store can't be installed, nearly 2023 and they still don't know how to make universal APKs.

Thank you very much! The script found 2 apps on my phone. One I should be able to easily replace with another, and the other is a game that I won't miss.
I have a game on my phone that hasn't been on the play store or updated for many many years, I'm surprised that didn't show up.

davidgro said:
The script isn't working on my phone, it's listing a bunch of apps that I know have 64-bit (or might be pure java/kotlin) such as Swift Backup.
When I break it down, the pm dump has output, but piping that to the grep -E does not
Click to expand...
Click to collapse
So I checked and it appears you're using a V20? It's possible that your device has old enough utilities that they don't support grep with extended regular expressions. The script might work without that one grep, but with how much junk pm dump includes about the system state I wanted to be able to anchor it to a point where I know the data I am looking for will be so I don't end up with false positives or negatives.
You can try this updated script to see if it works. I tested it on my phone and it still works, so if it works for you I guess it can be pushed to everyone else.

One App com.amazon.venezia = Amaton Appstor, wtf Amazon 32bit in 2022?

Ghisy said:
I've emailed the dev of the one I'm using. I'll PM you if I get a reply (not too sure we're allowed to talk about this here).
Click to expand...
Click to collapse
If you get any answer, please send me a PM too if you can. I was using Instander. I tried Aeroinsta, InstaPro and InstaXtreme, but all of them are 32 bits only...

narcisrm said:
If you get any answer, please send me a PM too if you can. I was using Instander. I tried Aeroinsta, InstaPro and InstaXtreme, but all of them are 32 bits only...
Click to expand...
Click to collapse
Yeah, they all seem to be 32 bits only. I believe the official Instagram app is 64 bits so why?
No reply yet but I'll PM everyone who is interested. Don't wanna flood this thread too much.

Namelesswonder said:
I just checked and it's absolutely hilarious that the Amazon App Store can't be installed, nearly 2023 and they still don't know how to make universal APKs.
Click to expand...
Click to collapse
You know what? I emailed the Amazon App Store support through the app for 64-bit support. No idea if I'll ever get a reply (it's mostly for sh*ts and giggles haha) but eh, worth a try.