NOTE: This guide is for MBR disks and legacy bios. If you want install on UEFI, this method can not help you.
1- Preparing the installation
a. Download BlissOS Official Roms ISO image.
b. Extract .ISO files into the *\BlissOS\ folder and create a custom size data.img (4gb for fat32 disk - Recomended 16 GB or 32 GB for NTFS disk)
* = Must be disk part. (you can select C:\ , D:\ or another diskparts)
Tips: You can create data.img file with Android PC Toolbox . Create and copy data.img into the BlissOS folder.
2- Setup grup for dual boot
a. Download EasyBCD and install it.
b. Run EasyBCD.exe > Add new entry > NeoGrub > İnstall
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Click Configure and delete all text. (editing menu.lst)
-Copy and paste that text there..
default 0
timeout 1
title BlissOS
root (hd0,1)
find --set-root ls /BlissOS/kernel
kernel /BlissOS/kernel quiet root=/dev/ram0 androidboot.selinux=permissive SRC=/BlissOS vga=788
initrd /BlissOS/initrd.img
boot
Click to expand...
Click to collapse
Important Note for root settings: You will change these numbers according to where you installed it.
root (hd0,1)
hd0 is your hdd number..
1 is your hdd disk volume number..
-Download Bootice for see disk numbers..
-Run Bootice.exe > Physical disk > Parts Manage - You will see disk parts.. No = hdd disk Volume number
-Rename your boot entry
-Select Count down (you can change timing "10")
-For Windows 10 / windows 8.1 os, check the "use metro bootloader" option.
-Click Save settings.
3-Setup completed. Restart your pc and have fun.
Error 15 file not found
Edit : Changed menu.lst entries. Now,It is set to be the root kernel.
WoltreX said:
Edit : Changed menu.lst entries. Now,It is set to be the root kernel.
Click to expand...
Click to collapse
I hope this works fine, I used the easy installer provided by bliss but it shows error "not all requirement are met" and it opens but I cant click anything.
jhetrosky said:
I hope this works fine, I used the easy installer provided by bliss but it shows error "not all requirement are met" and it opens but I cant click anything.
Click to expand...
Click to collapse
the installer provided by bliss is only compatible with UEFI systems. Is not compatible with legacy. And it will tell you in the output window(top right corner of the installer) which conditions are not met. Just have to look:good:
ElfinJNoty said:
the installer provided by bliss is only compatible with UEFI systems. Is not compatible with legacy. And it will tell you in the output window(top right corner of the installer) which conditions are not met. Just have to look:good:
Click to expand...
Click to collapse
Does it creates a swap partition or use ramdisk. If ramdisk, then compatibility will also depend on the RAM.
TeamPrimeOS said:
Does it creates a swap partition or use ramdisk. If ramdisk, then compatibility will also depend on the RAM.
Click to expand...
Click to collapse
There is no swap created by Bliss
There is a ramdisk
ElfinJNoty said:
There is no swap created by Bliss
There is a ramdisk
Click to expand...
Click to collapse
Thanks for the info, what is the minimum ram required then?
TeamPrimeOS said:
Thanks for the info, what is the minimum ram required then?
Click to expand...
Click to collapse
We've not had an issue with a minimum requirement.
This is an OS booting directly. Compare it to an older phone that can run Android: 1gb? 2gb?safe to assume more ram the better...
Most modern systems have at least 2gb which should be sufficient for any Blisss OS build.
As usual, why not test and find out?
#StasyBlissful
ElfinJNoty said:
We've not had an issue with a minimum requirement.
This is an OS booting directly. Compare it to an older phone that can run Android: 1gb? 2gb?safe to assume more ram the better...
Most modern systems have at least 2gb which should be sufficient for any Blisss OS build.
As usual, why not test and find out?
#StasyBlissful
Click to expand...
Click to collapse
Thanks for the info.
---------- Post added at 07:25 AM ---------- Previous post was at 07:23 AM ----------
jhetrosky said:
I hope this works fine, I used the easy installer provided by bliss but it shows error "not all requirement are met" and it opens but I cant click anything.
Click to expand...
Click to collapse
Can you list the mentioned incompatibilities.
TeamPrimeOS said:
Thanks for the info.
---------- Post added at 07:25 AM ---------- Previous post was at 07:23 AM ----------
Can you list the mentioned incompatibilities.
Click to expand...
Click to collapse
His issue was not due to incompatibility
The installer has some basic minimum requirements which is explained in the OP and Post 2. It also produces a log which would have explained his exact problem. There is also a YouTube video demonstrating the process successfully from start to finish.
*I didn't want their to be any confusion of there being something incompatible or broken about the UEFI Windows installer.exe*
Why the link for BlissOS/Android PC Toolbox has been deleted? I need it for installing Bliss OS on my not uefi pc
EDIT: Anyway I created an USB Bliss image (BlissOS 7.2 stable) and installed successfully on my hd (on a new partition formatted as ext4), I created then the entry with EasyBCD as suggested, changing the hd number, but when I choose the Bliss entry in the boot menu i got the "Error 13, invalid or unsupported executable format” message. Can anybody help me?
nerub config file for a android 9 Pie Bliss
when you click on easy BCD and install a neogrub and open neogrub install file
you i have seen someone has made a code like this >
defaul 0
timeout 10
root (hd0,X)
title 1. Normal Mode - Start Android OS in normal mode.
find --set-root /Android/kernel
kernel /Android/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet SRC=Android/ DATA= CREATE_DATA_IMG=1
initrd /Android/initrd.img
boot
root (hd0,X)
title 2. Recovery Mode - Start Android OS in recovery mode.
find --set-root /Android/kernel
kernel /Android/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet SRC=Android/ DATA= CREATE_DATA_IMG=1 SAVE_LO
initrd /Android/initrd.img root=/dev/ram0 androidboot.selinux=permissive vmalloc=192M buildvariant=eng nomodeset RECOVERY=1 RAMDISK=recovery.img SRC
boot
--------------------------------------------------------------------------------------
then instead of X you find your partition and like everything but
my ask for help is a code is incomplete as you see a second part a recovery more
start android in recovery mode is incomplete ? does anyone knows the ending of a code ? thank you ....its for making a better boot android neogrub menu and dual boot with windows 10 .......
@WoltreX hey, i just followed your guide for my laptop but after booting it just keeps showing a yellow animation forever any idea what's wrong ?
works on windows 10 surface tablet? without touch or bluetooth bugs?
Any suggestions on what to use if EasyBCD doesn't work states cannot run on (U)EFI.
Detecting android x86 found at Dev/sda6
Stuck at this screen plz help plz.....
Stuck at (blinkin) _
After I press the BlissOS boot option
The last phrase on the text is Android-x86. . . found at /dev/sda4
then around 20 seconds
black screen appear with blinking _ at the top corner
wtf is up with the shady as hell link for the toolbox? Russian website says I have to install Multy App to download it.
This is some bull**** right here, not touching that with goddam 10 foot pole
Do you know if this is possible in Linux Ubuntu?
Related
I have working on a project in the form of an app, which guides you through the installation of Ubuntu within android via chroot. It includes a ubuntu 10.10 image I have been working on which includes lots of program to allow users to develop program/scripts etc within Ubuntu on there phone/tablet.
However I have I have yet to get much testing on this device and would like more feedback from users!
Please post your device/kernel/rom along with what did and didn't work, so I can draw up what I need to change in the next release of the app/ubuntu build.
Website
http://linuxonandroid.blogspot.com/
Video
http://www.youtube.com/watch?v=UCqzs8yQTM8
App Download
Free App
Paid App
Boot Script
ubuntu.sh(V5)
Full Image
This image is 1.5GB to download, once extracted 3.5GB, and include alot of programs like openoffice, thunderbird, firefox and over programs for 'developing' - Also allows you to switch between the LXDE and Gnome desktops, and you can define screen size on boot!
ubuntuV5-image.zip
Lightweight Image - This is yet to be included in an app, will be included in the next release (aka 2.0 ), so get it now before anyone else!
This image is just under 500MB to download, once extracted 2.5GB, and include only programs needed (LXDE desktop, web browser, + other basic programs) also allows you to define screen size on boot
ubuntuV5-sm-image.zip
12.04 images
I have now started work on building new 12.04 images these come in core (just the bear-bones ubuntu) and full (ubuntu with GUI and other programs) and will be updated as 12.04 moves through its milestones (and when I make new updates to the mods I make from the main stream arm port).
These are for testing ONLY until 12.04 reaches stable release.
You can view the images here:
http://sourceforge.net/projects/linuxonandroid/files/Ubuntu/12.04/
I also want to build up a small group of testers who I can email with new images and scripts, these will include all future distros that I do. If you are interested in joining this test group please PM me or send a email to [email protected]
The only requirement is that your willing to test and send feedback along with screen shoots etc where required, it would also be good if your willing to try different roms and kernels for your device!
Sig Banner
Show your love of ubuntu on android with my sig banner:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
image url is "http://dl.dropbox.com/u/11206993/ubuntuuser.png"
Other Guides
Like this guide? want to try something different? then check out my other guides for different distro's
Backtrack - This is a distro that is based around security testing, it also includes the Gnome desktop environment and a range of other programs.
Updates
18/02/12
*New 12.04 images started building, for now not included in the app but once a bit more stable will be included
29/01/12
*New V5 small image, featuring fixed Java, even more lightweight (now around 1.2GB free) and user can set screen size on boot
*PAID New Build guide which shows you how to build your own Ubuntu images
*Brand new UI To make the whole thing more useable
*PAID new 'one click boot' feature to allow quick booting from either the widget or inside the app
*PAID new widget to activate the one click boot
*PAID app install guide changed in light of 'one click boot'
*Fixed keyboard mapping of random letters in Gnome
18/01/12
*Large ubuntu image now allows user to set screen size on boot!
*Large Ubuntu image now lets you select between LXDE and Gnome desktops
*Large Ubuntu image has been recompiled to fix the likes of Java (note some of the above changes will be included in the small image in the future)
*FAQ section updated with more answers to questions I have been getting
*Install guide updated in light of the new large image
06/01/12
*PAID app file downloads now use new fast FTP server and support direct downloading (click the button to download a image and it starts to download right away)
*New boot script which has fixed problems with it not booting on alot of devices, and fixed problem which some people getting a grey screen when loading UI
*Boot script now downloaded in zip file to fix problems with downloading script
*Both apps fixed to support low resolutions
*Both apps cleaned up
28/12/11
*PAID app now supports 960x540 'qHD' resolution
*ALL Ubuntu lightweight images cleaned up even more saved another 300MB of space
*ALL Ubuntu images updated with all new updates
*ALL Ubuntu images now in .zip format to fix problems with some peoples devices failing to extract the .rar files
*Boot script updated, once booted now terminal acts like a command line interface for Ubuntu, and some boot problems now fixed
*Image and boot script now downloadable separately to allow easier updating
19/12/11
New 'lighter' ubuntu image options for all resolutions already supported
15/12/11
New ubuntu images with all updates up to 15/11/11
FREE app ubuntu image resized to fit 800x480 resolution
PAID app ubuntu images now includes 4 images for 800x480, 854x480, 1024x600 and 1280x800 resolutions
http://forum.xda-developers.com/showpost.php?p=20598548&postcount=83
Samsung Galaxy Note G7000
FM 1.5 Kernel
RocketRom V10 (14Toggle, smoothnessupdate, addperformance, stock theme)
Note freezes after executing ubuntu.sh, only restarting by holding powerbutton helps...
It's a pity, I thought booting ubuntu is only possible on a Rom with loop devices capabilities and now I read that only the stock rom is working
tried ubuntuv3.sh see picture:
http://imageshack.us/f/808/sc20111223042953.png/
Allamann said:
http://forum.xda-developers.com/showpost.php?p=20598548&postcount=83
Samsung Galaxy Note G7000
FM 1.5 Kernel
RocketRom V10 (14Toggle, smoothnessupdate, addperformance, stock theme)
Note freezes after executing ubuntu.sh, only restarting by holding powerbutton helps...
It's a pity, I thought booting ubuntu is only possible on a Rom with loop devices capabilities and now I read that only the stock rom is working
tried ubuntuv3.sh see picture:
http://imageshack.us/f/808/sc20111223042953.png/
Click to expand...
Click to collapse
Indeed its VERY odd that stock works but custom roms do not work...should really be the other way round, perhaps something to do with how the device file system in custom roms is different or something?
I don't know, this is the problem trying to support as many devices as possible, I don't have the device to test and work out what's wrong, just got to keep basically stabbing into the dark until I hit something
Change log for new release (release will be in the next few days for paid end of next week for free) - all new images etc will be added to the first post as they are finished and uploaded!
*PAID app now supports 960x540 'qHD' resolution
*ALL Ubuntu lightweight images cleaned up even more saved another 300MB of space
*ALL Ubuntu images updated with all new updates
*ALL Ubuntu images now in .zip format to fix problems with some peoples devices failing to extract the .rar files
*Boot script updated, once booted now terminal acts like a command line interface for Ubuntu, and some boot problems now fixed
*Image and boot script now downloadable separately to allow easy updating of the script
*+more likely before release
Allamann said:
http://forum.xda-developers.com/showpost.php?p=20598548&postcount=83
Samsung Galaxy Note G7000
FM 1.5 Kernel
RocketRom V10 (14Toggle, smoothnessupdate, addperformance, stock theme)
Note freezes after executing ubuntu.sh, only restarting by holding powerbutton helps...
It's a pity, I thought booting ubuntu is only possible on a Rom with loop devices capabilities and now I read that only the stock rom is working
tried ubuntuv3.sh see picture:
http://imageshack.us/f/808/sc20111223042953.png/
Click to expand...
Click to collapse
+1 I got it to boot with cf kernel but not with fm or abyss kernel.
Sent from my GT-N7000 using xda premium
timstanley1985 said:
+1 I got it to boot with cf kernel but not with fm or abyss kernel.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Odd so I'm guessing the two kernels that don't work don't have loop support...best talk with the kernel developer
Sent from my HTC Desire S using XDA App
timstanley1985 said:
+1 I got it to boot with cf kernel but not with fm or abyss kernel.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Yep, I was really enjoying - had PHP and mysql installed and working as a wee test environment, then flashed FM and no more Ubuntu.
Thanks for the work - appreciated
If I manually downloaded the script and the image, where do I put
the extracted content of the zip, and the script ? on the root of external SD or phone storage ?
lucid said:
If I manually downloaded the script and the image, where do I put
the extracted content of the zip, and the script ? on the root of external SD or phone storage ?
Click to expand...
Click to collapse
Place them in a folder called ubuntu on either your sdcard or internal memory as you have both either should work
Sent from my HTC Desire S using XDA App
Thanks, by pressing ahead without knowing I put the files there, however, in terminal emulator, after aquiring superuser persmissions, changing to the ubuntu folder wont work. I must be doing something wrong. I came as far as cd /sdcard but /sdcard/ubuntu fails. Asking ls -a says dir is empty ? Linux noob
lucid said:
Thanks, by pressing ahead without knowing I put the files there, however, in terminal emulator, after aquiring superuser persmissions, changing to the ubuntu folder wont work. I must be doing something wrong. I came as far as cd /sdcard but /sdcard/ubuntu fails. Asking ls -a says dir is empty ? Linux noob
Click to expand...
Click to collapse
check in a file explorer where the sdcard is mounted, sometimes the internal memory is mounted as the sdcard directory and then the sdcard itself is mounted in another directory within that.
Once you work out where its mounted then just cd to that location
Got it to work. Copied the ubuntu folder to /
Pretty responsive in 24bit colour. Working with cassies ultralight v4.
lucid said:
Got it to work. Copied the ubuntu folder to /
Pretty responsive in 24bit colour. Working with cassies ultralight v4.
Click to expand...
Click to collapse
which Kernel/Rom?
Hi
Before run ubuntu.sh check if loop inst bussy with other kind of programs who use it.
try losetup will show you how many loop you have used and edit ubuntu.sh to get 1 free
like last 1 user will be 10 then line with busybox mknod /dev/loop11 b 7 11
and wher you see loop0 change to loop11 or any free number.
Hope will works for you.
---------- Post added at 12:06 PM ---------- Previous post was at 12:03 PM ----------
Hi,
Nice work but you forgot something.
Your image wont work on many device since the /sdcard partition if VFAT who limit the file to 2G.
converting /sdcard to ext2 or ext4 is the way to work with files larger than 2G.
B.
dahas said:
Hi
Before run ubuntu.sh check if loop inst bussy with other kind of programs who use it.
try losetup will show you how many loop you have used and edit ubuntu.sh to get 1 free
like last 1 user will be 10 then line with busybox mknod /dev/loop11 b 7 11
and wher you see loop0 change to loop11 or any free number.
Hope will works for you.
---------- Post added at 12:06 PM ---------- Previous post was at 12:03 PM ----------
Hi,
Nice work but you forgot something.
Your image wont work on many device since the /sdcard partition if VFAT who limit the file to 2G.
converting /sdcard to ext2 or ext4 is the way to work with files larger than 2G.
B.
Click to expand...
Click to collapse
Thank you very much I will integrate these changes in the next version of the script
you can also change de fstab line where root partition is mount by uuid and replace by name
losetup returns nothing...
I also asked the dev of FM kernel and he told me that it has loop capabilities
if losetup show nothing then or you dont have loop set or you not root.
for see if you r root type id and the have to show your id. If is not root type su -
For the no loop set then the original ubuntu.sh have to work.
Runs perfectly on my Note
Had rooted it yesterday with CFRootFlasher
Kernel is "KK9" (Android 2.3.6)
Tested the V3 800 first, and now running with the V4 1280 image
Btw I´m an Android noob, came from Ios 2 weeks ago, so i dont really know what is important for you to know. But if you want to know something, just ask
kevinturbo said:
Runs perfectly on my Note
Had rooted it yesterday with CFRootFlasher
Kernel is "KK9" (Android 2.3.6)
Tested the V3 800 first, and now running with the V4 1280 image
Btw I´m an Android noob, came from Ios 2 weeks ago, so i dont really know what is important for you to know. But if you want to know something, just ask
Click to expand...
Click to collapse
Thank you very much, glad to hear you have it working!
And welcome to the dark side
hi guys here is BACKTRACK 5 on SGS-SL i9003
most of the work was done by anantshri, i have only modified it slightly so that it will works properly on SGS-SL i9003... dont forget to thank him!
i will try n keep it short and simple... this is running in chroot environment and doesnt boot as a separate OS... it can be accessed through shell or via a VNC client..
for more details u can read the original thread at X10 sub-forums...
[DEV] BACKTRACK 5 on Xperia X10 chroot
if u dont know what Backtrack is read this: http://bit.ly/z23em2
[ Screenshots ]
on startup (shell):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in GUI:
phone + BT5 GUI:
[ Requirements ]
rooted device
Some apps from Android Market:
Android Terminal Emulator
androidVNC
[optional] highly recomended keyboard: Hacker's Keyboard
7zip (for PC), for extracting the files
around 3.3 GB free on external sdcard (/sdcard/external_sd/)
[ How To : File Setup ]
u need to do this only once
download the files from the links provided in this thread
extract the files using 7zip to a temporary folder (needs 3.3GB free on that drive)
connect ur device to PC and mount USB storage
create a folder named 'bt' (without quotes) in the root of ur external sdcard and copy the bt.img in that folder
also place the file bt5_sgsl-i9003_shell_scripts_v1.zip in root of sdcard, this file has to be flashed via recovery
once u verify that the above is correct then un-mount usb storage
reboot into recovery and flash the file bt5_sgsl-i9003_shell_scripts_v1.zip stored in root of sdcard
once ur phone reboots into OS just check the /sdcard/external_sd/bt folder
final directory structure should look like this:
/sdcard/external_sd/bt/bt
/sdcard/external_sd/bt/bt.img
/sdcard/external_sd/bt/installbt.sh
/sdcard/external_sd/bt/startbt
/sdcard/external_sd/bt/stopbt
once u verify that the above is correct then u can proceed
[ How To : Launch BT ]
start Terminal Emulator app on ur device and enter the following commands step by step (accept/allow any SuperUser request/popup that u may receive)
su
cd /sdcard/external_sd/bt
sh installbt.sh
startbt
bt
now u are in BackTrack5 shell
to launch GUI (vncserver) enter the following command
ui
now note the number N shown localhost:N
e.g. as u can see from the above image that "New 'X' desktop is localhost:1", so N=1
the vncserver is running at (5900 + N, N=1 ; so server port is 5901)
now launch androidVNC app on phone and fill in the detials as follows
Nick : bt
Address : 127.0.0.1
Port : 5901
Password : 12345678
Username : <leave it blank>
Color Format : 24-bit color (4 bpp)
inside vnc window select input mode (i personally recommend the following)
TouchPad (here your screen works like a big touchpad use it to navigate mouse.)
and then press connect... now u are in BackTrack GUI!
if u want to exit/close BT5 then u need to follow these steps:
close the androidVNC app (Menu -> Disconnect)
go back into Terminal Emulator app and enter the following commands
u should be at this shell [email protected]:~#
killui
exit
now u will get back to this shell> #
now enter the following commands to stop bt and exit
stopbt
exit
exit
u can now exit the Terminal Emulator app
i would also recommend that u reboot ur phone
[ Important Info ]
root password is 12345678
[ Download Links ]
update.zip package containing shell scripts, busybox (which gets installed to temporary location) [to be flashed via recovery]
this will not disturb/conflict with busybox of ur ROM/CF-Root kernel
bt5_sgsl-i9003_shell_scripts_v1.zip (~800KB)
main bt.img
there are two sets of files... for those who dont have a very stable connection i have provided small 50MB (x 10) packages while for others who have a stable connection i have provided 250MB (x 2) packages... both contain the same file bt.img but for the convenience of users i have created these two sets... if u have already downloaded one set u do not need the other set...
KINDLY DO NOT MIRROR OUR FILES
SET 1
these links are 7zip archives split into 50mb files, u will need to download the following:
total size: 486MB
bt.7z.001 (50 MB)
bt.7z.002 (50 MB)
bt.7z.003 (50 MB)
bt.7z.004 (50 MB)
bt.7z.005 (50 MB)
bt.7z.006 (50 MB)
bt.7z.007 (50 MB)
bt.7z.008 (50 MB)
bt.7z.009 (50 MB)
bt.7z.010 (36 MB)
md5 hashes:
Code:
bt.7z.001 f19e769bf42b44867c8bb1d9bb9c5d44
bt.7z.002 a4dd26a98d2c6925d871fb108fb5fadb
bt.7z.003 ecca5a5d72c449117b1d3dbc23aeb1a2
bt.7z.004 8ad487a01e4d149f0247ad9288201f32
bt.7z.005 adab9cb3778cd8ac89ccc0e21997c3d7
bt.7z.006 ba6a28de70a1115dc316f45cea508215
bt.7z.007 f59757e891631607e1a35abadb231b3b
bt.7z.008 cdb8c28a1fbd03657bb42e8d69f0600b
bt.7z.009 426d892f872679e3d53d0ebb0376e138
bt.7z.010 c7d2957bc65340d967b9dd3646d7cb39
i am also uploading a different set where-in the files are split into 250MB parts... but that upload is taking time
OR
SET 2
these links are 7zip archives split into 250mb files, u will need to download the following:
total size: 486MB
part1
part2
md5 hashes:
Code:
bt.7z.001 fea6299bfa1677bd344d478108d458b2
bt.7z.002 b3897170d1f05dd0fb812fd092411203
ENJOY!
[ Tips n Tricks! ]
if u have ur device (SGS-SL i9003) connected over wifi u can connect to the BT5 vncserver running on ur phone!! u will just need to connect to
<ip_address_of_phone>:<portno>
most of the startup/launching commands can be executed even through adb shell
Lol it looks like you made a hard work with this Thanks to you and to the original dev
Good job man!
Wow...
Awsom work doomlord. Dont have words to say thanx.
For those people who dont understand what is Backtrack 5 so here is link for them to understand it in simple language
www.xda-developers.com/android/backtrack-5-for-android-smartphones/
can you kindly tell me what is backtrack 5 ? and what is its use ?
anna0811 said:
can you kindly tell me what is backtrack 5 ? and what is its use ?
Click to expand...
Click to collapse
http://bit.ly/z23em2
I think BT have advantage to track wifi rec.
this might be usefull ..
Sent from my GT-I9003 using xda
will this format the phone ? can i install it on any custom rom or only on stock rom?
after installing this will it convert the phone to linux os and android will be gone ?
anna0811 said:
will this format the phone ? can i install it on any custom rom or only on stock rom?
after installing this will it convert the phone to linux os and android will be gone ?
Click to expand...
Click to collapse
this boots of sd card,so ur eMMC will be safe
and doomlord,this contains i9003 kernel?so if i swap the kernel,will it work with other phones?(same screen size and res)
anna0811 said:
will this format the phone ? can i install it on any custom rom or only on stock rom?
after installing this will it convert the phone to linux os and android will be gone ?
Click to expand...
Click to collapse
If anybody who dont understand what is backtrack 5 then its better that they must search on net about it & then come here. Before just throwing question ask urself that do u really need this, do u really understood meaning of it. If yes then only go ahead
sakindia123 said:
this boots of sd card,so ur eMMC will be safe
and doomlord,this contains i9003 kernel?so if i swap the kernel,will it work with other phones?(same screen size and res)
Click to expand...
Click to collapse
no this is not related to any specific kernel...
which device u plan to "port" it to?
DooMLoRD said:
no this is not related to any specific kernel...
which device u plan to "port" it to?
Click to expand...
Click to collapse
i9001(msm7x30)
sakindia123 said:
i9001(msm7x30)
Click to expand...
Click to collapse
should work..
P.S.: ur kernel for that device looks a lot like my ARC kernel... ported some stuff from it?
not really.I didn't see much that cud me added w/o kernel not compiling.
Even adding SQLB allocator caused WiFi to become unstable(and it wasnt fixed with a new module)
Thanks a zillion!! WOW!!
I have my sd cards swapped.. Is there anyway to keep the files in the current int sdcard (16 gb) instead of the external (coz u have mentioned that it requires nearly 3gb in the external card)..
Anyway thanks a lot for getting it to our device.. Doom u rock..
Nice work doomlord i have used the backtrack and debian in my lg 2x
Doom thanks a lot.I always wanted to screw wpa passwords on my phone
Sent from my GT-I9003 using XDA App
yamchirobe said:
Doom thanks a lot.I always wanted to screw wpa passwords on my phone
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
Well without monitor mode support of the wifi chip in phone u wont be able to get that to work...
Sent from my LT15i using XDA App
(DISCLAIMER: Only for Windows 7 and Vista)
Things you will need
----------------------------
1- EasyBCD (to create boot configuration) - http://neosmart.net/Download/Register/1
2- Android x86 iso - http://android-x86.googlecode.com/files/android-x86-4.3-20130725.iso
3- My MBR files http://forum.xda-developers.com/attachment.php?attachmentid=2203408&stc=1&d=1377076042
4- iso extracting software (WinRAR or 7zip)
5- Paragon partition viewer (optional to view contents of ext3/2 partition) - http://www.paragon-software.com/home/pm-personal/
Steps
----------
1-Download all the files and install them.
2-Next you need to create a new partition for android installation if you don't already have one.
3-Go to device manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4-Then go to disk management
5-Create a new partition 2-5 GB recommended
6-Once you've finished creating the partition open EasyBCD > Add new entry > ISO > Choose the Android x86 iso path, and select load from memory.
7-Now you want to extract all the files in the Android x86 iso using 7zip or WinRAR to the hard drive C:/ or D:/ so it can boot.
8-When you're done you can now reboot your computer, the iso entry would show up in boot menu. boot up the Android x86 iso.
9-Choose 'installation - Install Android to hard disk'
10-Choose the new partition that you made it will always be the last one.
11-Now choose the filesystem, ext3 is recommended as it doesn't have maximum hard drive size like fat32 and it's the fastest.
12-Next question is whether to install boot loader Grub, (If you install this it would remove windows master boot record, but you can later install it if you want using EasyBCD)You need grub bootloader to boot android so Choose yes.
13-Now it will detect windows is already installed and add the boot entry to the grub bootloader so you can boot into windows. and it will start the installation.
14-When the installation is complete you will see a message to run android or reboot.
15-choose reboot and boot into windows.
16-Now open EasyBCD again > BCD Deployment > Install Windows vista/7 boot loader to the MBR > Write MBR (This will install windows master boot record again)
17-Then go to Edit Boot Menu, here you can change the boot entry name and count down time.
18-When you are done Click save settings and close EasyBCD
19-Then go to My MBR files(NST and ANG0) and extract them to C:/ (your system drive)
You have successfully dual booted Android x86 and Windows
Nice tutorial. But why would anyone install android on their computer? Installing it in a virtual machine would be safer and less troublesome.
lzk123 said:
Nice tutorial. But why would anyone install android on their computer? Installing it in a virtual machine would be safer and less troublesome.
Click to expand...
Click to collapse
Virtual machines run slower and have does not support some hardware . it would run extremely fast and smooth natively rather than an emulated one.
I booted it on my broken laptop(some keys didn't work on it) .. now I can use the android keyboard instead of my broken keyboard which is really useful.
it is as good as any other operating system for a computer you should definitely try it. It's can run all apps including ARM apps. the only problem I had with it was the portrait screen. I had to use a third party screen orientation changing app to lock it on landscape.
Will this method work for the latest 4.4 RC2?
karan128 said:
Will this method work for the latest 4.4 RC2?
Click to expand...
Click to collapse
Yes, this method should work with all the x86 iso.
Keyboard not detected during install
karan128 said:
Will this method work for the latest 4.4 RC2?
Click to expand...
Click to collapse
I'm trying to install 4.4RC2 on my PC but when I get to install to harddisk my wireless keyboard stops being detected. WHen I run the Live CD the keyboard runs just fine, alonge with the mouse, any ideas?
idk..use a wired keyboard
bethnesbitt said:
I'm trying to install 4.4RC2 on my PC but when I get to install to harddisk my wireless keyboard stops being detected. WHen I run the Live CD the keyboard runs just fine, alonge with the mouse, any ideas?
Click to expand...
Click to collapse
Did you try going to input methods and choosing the keyboard from the setting?
Fixed
Sippay said:
Did you try going to input methods and choosing the keyboard from the setting?
Click to expand...
Click to collapse
Fixed:
Had partitioned a section of my HD to install 4.4. Reading on android-x86.org found out that it wasn't even necessary to install if already using Linux, which I am. All I had to do was copy initrd.img, system.cfg kernel and ramdisk.img, created an empty directory called data to that partition that was manually formatted to an ext4. Edited my 40_custom menuentry to show 4.4 during bootup menu and it did the rest for me. Just for fun, also partitioned off another part of my drive called downloads so that I could have a emulated sdcard to share between linux and android-x86.
If anybody is interested in a more detailed explanation, they can check out my tut on my blog, not sure if I will get in trouble for posting the link, so.... I don't know, message me I guess, unless the moderator doesn't care.
Please help me!
after reaching the reboot/run android option , first i have chosen the run item and followed any other instructions you gave. but after restarting machine , i couldn't find the android to enter the OS again. the second time i have started every thing from zero and i have chosen the reboot option. but nothing changed. this time even my drive is still empty. how can i boot the previous installed android. please help me.:crying:
Backup?
okaye said:
after reaching the reboot/run android option , first i have chosen the run item and followed any other instructions you gave. but after restarting machine , i couldn't find the android to enter the OS again. the second time i have started every thing from zero and i have chosen the reboot option. but nothing changed. this time even my drive is still empty. how can i boot the previous installed android. please help me.:crying:
Click to expand...
Click to collapse
Not sure what you mean? Did the hack work? Is it booting but all your previous userdata/apps missing? Did you do a backup of your system/userdata/cache with MTK Droid Tools or andoid back up manager from the play store?
---------- Post added at 09:26 PM ---------- Previous post was at 09:21 PM ----------
okaye said:
after reaching the reboot/run android option , first i have chosen the run item and followed any other instructions you gave. but after restarting machine , i couldn't find the android to enter the OS again. the second time i have started every thing from zero and i have chosen the reboot option. but nothing changed. this time even my drive is still empty. how can i boot the previous installed android. please help me.:crying:
Click to expand...
Click to collapse
Not sure what you mean? Did the hack work? Is it booting but all your previous userdata/apps missing? Did you do a backup of your system/userdata/cache with MTK Droid Tools or andoid back up manager from the play store?
FOr future referance, I suggest anybody doing this hack to use this app:
https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore&hl=en
it is easy, you can backup to your sdcard and restore, make sure that your device is rooted and CWM is installed, this can be done with MTK Droid tools.
help
In point 7 what is the specifical hard drive; C:/ or D:/??
Thanks for nice guide, but it works only on systems which allow old way of booting (MBR).
Today I tried to do this on an ASUS UX31A, which only support UEFI and sadly even the newest beta of EasyBCD doesn't support grub booting on UEFI only system.
Issue is not only with EasyBCD, but also with Android-x86 itself. The installer doesn't support UEFI either. But I checked the iso and it contains EFI files, so I guess, there would be some manual way how to make it boot on EUFI only system.
Any idea how to do this? Manual install of Grub2 and copying of the ISO content to ext3 partition from some live Linux distro?
johny.mnemonic said:
Thanks for nice guide, but it works only on systems which allow old way of booting (MBR).
Today I tried to do this on an ASUS UX31A, which only support UEFI and sadly even the newest beta of EasyBCD doesn't support grub booting on UEFI only system.
Issue is not only with EasyBCD, but also with Android-x86 itself. The installer doesn't support UEFI either. But I checked the iso and it contains EFI files, so I guess, there would be some manual way how to make it boot on EUFI only system.
Any idea how to do this? Manual install of Grub2 and copying of the ISO content to ext3 partition from some live Linux distro?
Click to expand...
Click to collapse
This is what you looking for:
Sombody used rewrote an Linux EFI Bootloader to Boot Androidx86 with UEFI
groups.google.com/forum/#!msg/android-x86/D85Jq02cLrE/RhTWtOjH3H0J
what's the difference between installing and live CD?
thanks
I don't really know but u could install it on a completely wiped HDD then enter the portion manager and format it as primary and set as boot then wright and volia! U may have it if u don't don't blame me
Detecting Android x86...
I followed all the steps, but when I choose the installation option in step 9, I get stuck on "Detecting Android-x86 message.
Any idea how to fix this?
This tutorial is not working...
(W10 x64, Android x86 5.1)
It is not problem when using included GRUB, but I can't make it running with Windows boot menu.
Any suggestions?
I think the problem is with GRUB, we need to put it at the partition with Android itself, not to the Windows boot partition. I'm running Win 10 + KALI linux this way and it is working perfectly.
Just wanna throw this out here:
Followed this tutorial using Windows 10 and Android x86 9.0 rc1, worked like a charm.
Bios was set to legacy with safe mode off.
marinovanec said:
Detecting Android x86...
I followed all the steps, but when I choose the installation option in step 9, I get stuck on "Detecting Android-x86 message.
Any idea how to fix this?
Click to expand...
Click to collapse
Yes for me also!!!
What is the problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ATA Tool Only for Windows and Linux
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
*/
This tool include adb.exe and fastboot.exe and Scrcpy. This tool currently only supports Windows and Linux, in future updates I might add support for macOS.
Windows Versions:
Windows ATA Tool v0.9.3.10072020:
if the botton doesn't work click this link: https://github.com/MassimilianoSart...W/ATA-v0.9.3.10072020-for-Windows-By-Sway.zip
Linux Versions:
Linux ATA Tool v0.0.2.280920200:
if the botton doesn't work click this link: https://github.com/MassimilianoSart...20L/ATA-v0.0.2.28092020-for-Linux-By-Sway.zip
Windows Features:
UNLOCK BOOTLOADER
FORMAT DATA PARTITION (EXT4)
FORMAT DATA PARTITION (F2FS)
FLASH BOOT (only .img file)
FLASH BOOTLOADER (only .img file)
FLASH RADIO (only .img file)
FLASH RECOVERY (only .img file)
FLASH SYSTEM (only .img file)
FLASH VENDOR (only .img file)
FLASH CACHE (only .img file)
FLASH ROM (You must know what you are doing)
Check connected devices
Boot into ROM
Boot into recovery
REBOOT SMARTPHONE
REBOOT INTO THE RECOVERY
REBOOT INTO THE Fastboot/Bootloader
Check connected devices
Automate Apks installer
Check devices version connected
Install an app
Unistall an app (No System App)
Emulate device (Resize Screen)
Emulate device (Change Density)
Reset (Emulate device)
Screen Recording
Smarthphone Status
Change system info
Grant WRITE_SECURE_SETTINGS permission
Grant DUMP permission
Check for granted permissions
Create and run a program: keyevent Istruction https://developer.android.com/reference/android/view/KeyEvent.html
Scrcpy - Screen mirror
ADB over network working
Logcat and Display On Screen Only
Logcat and Record Text File Locally
"getevent" and Display On Screen Only
"getevent" and Record Text File Locally
View System Info (Data From build.prop, g.prop, and others)
Wireless debugging (only on Android 11)
adb backup and restore
input from keyboard to smartphone
Linux Features:
Check connected devices
REBOOT SMARTPHONE
REBOOT INTO THE RECOVERY
REBOOT INTO THE Fastboot/Bootloader
Check devices version
Enable/Disable Dark Mode in Q
Device serial number
Liked my work? Give me a beer
Requirements
1. To run Scrcpy the Android device requires at least API 21 (Android 5.0).
2. Make sure you enabled adb debugging on your device(s). On some devices, you also need to enable an additional option
Issues:
Strange outputs?
if you find strange outputs from commands, it's a know issue, you have to start again the command and it will work!
Licence:
ATA:
Copyright (C) 2019-2020 SwayWasTaken
Scrcpy:
Copyright (C) 2018 Genymobile
Copyright (C) 2018-2020 Romain Vimont
SDK Platform Tools:
Copyright (C) 2016-2019 Google LLC https://developer.android.com/license
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Links:
ATA Tool source Download link: https://github.com/MassimilianoSartore/Advance-Tool-for-Android/archive/master.zip
Scrcpy repository: https://github.com/Genymobile/scrcpy
SDK Platform Tools link: https://developer.android.com/studio/releases/platform-tools.html
Github page: https://github.com/MassimilianoSartore/Advance-Tool-for-Android-ADB-Tool-
Donate link: https://www.paypal.me/SWayGaming
Icon in the download botton: https://icons8.it
PS : I am not responsible for bricked devices use ATA at your own risks!
Android is a trademark of Google LLC.
This program was made with an Unlicensed compiler.
Please buy the PRO version to distribute your EXE.
Press any key to continue . . .
Click to expand...
Click to collapse
Always these lame bat2exe converters.
Why not people just distribute these as plain batch files I wonder...
CXZa said:
Always these lame bat2exe converters.
Why not people just distribute these as plain batch files I wonder...
Click to expand...
Click to collapse
O Sorry I will publish the source on GitHub.
I will try to resolve the problem
CXZa said:
Always these lame bat2exe converters.
Why not people just distribute these as plain batch files I wonder...
Click to expand...
Click to collapse
Now you can download the batch file from the link in the first post, sorry again
Sorry if I was a bit - well - a bit too me. I have just stumbled into these batexes maybe too many times. All sort of "kitchens" (what the heck, isn't there still a better word, really) use them, ASSAYYED, TOAD (open source? okay, maybe so***), Uppercut (several batexes inside each other, just plain weird..).
Maybe they have their use but I haven't figured it out yet really.
Great, now it's much smaller too... :good:
(*** the bat files can usually found from the temp folder when one runs these exes)
CXZa said:
Sorry if I was a bit - well - a bit too me. I have just stumbled into these batexes maybe too many times. All sort of "kitchens" (what the heck, isn't there still a better word, really) use them, ASSAYYED, TOAD (open source? okay, maybe so***), Uppercut (several batexes inside each other, just plain weird..).
Maybe they have their use but I haven't figured it out yet really.
Great, now it's much smaller too... :good:
(*** the bat files can usually found from the temp folder when one runs these exes)
Click to expand...
Click to collapse
Oh I didn't know that, hope you will appreciate that. If you will find something wrong, please report to me. I will make some changes in the batch this week.
V 0.3
Changelog:
- Added device info on the home
Download:
https://github.com/SwayWasTaken/Advance-Tool-for-Android/archive/master.zip
V 0.4
Changelog:
- some improvement under the hood
Download:
https://github.com/SwayWasTaken/Advance-Tool-for-Android/archive/master.zip
V 0.5
Changelog:
- some improvement under the hood, now the program will check if the device is connected
Download:
https://github.com/MassimilianoSartore/Advance-Tool-for-Android/archive/master.zip
V0.5.1
Changelog:
- Added more options to unlock and lock the bootloader
Download:
https://github.com/MassimilianoSartore/Advance-Tool-for-Android-ADB-Tool-/archive/master.zip
SwayWasTaken said:
Changelog:
- Added more options to unlock and lock the bootloader
Download:
https://github.com/MassimilianoSarto...ive/master.zip
Click to expand...
Click to collapse
The link doesn't work, but it's the same as before.
Nice batch project, helps those that don't want to type everything by themselves.
That :devicecheck you could make less strict. Just check that the value isn't empty...
CXZa said:
The link doesn't work, but it's the same as before.
Nice batch project, helps those that don't want to type everything by themselves.
That :devicecheck you could make less strict. Just check that the value isn't empty...
Click to expand...
Click to collapse
Thanks for the suggestion, change made!!
V0.5.2
Changelog:
-V 0.5.2: some improvement under the hood (Thanks to @CXZa for the suggestion)
Download:
https://github.com/MassimilianoSartore/Advance-Tool-for-Android-ADB-Tool-/archive/master.zip
V 0.5.7 Changelog:
-New information about your smathphone
-New loading screen
-New integration with more batch files
Now the main script must stay in the same folder as Scripts folder
Download:
https://github.com/MassimilianoSartore/Advance-Tool-for-Android-ADB-Tool-/archive/master.zip
V0.5.8
Changelog:
- Change system info
- New window size
V0.5.9
Changelog:
- Now you can uninstall system app without root access on your smartphone!!
Pay attention you can damage your phone!
Enjoy!
download:
https://github.com/MassimilianoSartore/Advance-Tool-for-Android-ADB-Tool-/archive/V0.5.9.zip
Hi. I tried to run this and it only gives me a yes or no option then shuts off. I'm not sure if I have my path set up at all as there really aren't any set up instructions. Could you give a quick set up tutorial?
0.6.0
Changelog:
- Grant WRITE_SECURE_SETTINGS permission
- Grant DUMP permission
- Check for granted permissions
- Changed window size
Download:
https://github.com/MassimilianoSartore/Advance-Tool-for-Android-ADB-Tool-/archive/0.6.0.zip
Supermatt01 said:
Hi. I tried to run this and it only gives me a yes or no option then shuts off. I'm not sure if I have my path set up at all as there really aren't any set up instructions. Could you give a quick set up tutorial?
Click to expand...
Click to collapse
the problem is that you dont have adb set as environment variable, follow this link to set it https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/.
SwayWasTaken said:
the problem is that you dont have adb set as environment variable, follow this link to set it https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/.
Click to expand...
Click to collapse
Okay. I'm giving it a look.
I have an Galaxy A6 which has the Exynos 7870 CPU. I downloaded the kernel source from the Samsung source page, and when I typed
Bash:
make menuconfig
it has the Virtualization option. So does that mean the CPU itself support KVM? Thanks!
I just compile the kernel, pack it to boot.img, put boot.img to the AP and flash it using Odin but not work. I want to try if KVM exist to run Windows ARM in QEMU kvm in Termux
I have the very same device and am currently working on a patch for KVM to work on it. Will post here if I get it working reliably. On the other hand this SoC has its own quirks, I'm not sure if it'll ever be possible to run unpatched guest OSes (some registers are only writable from EL3 (TrustZone), not initialized by that, guest VMs read them, and it can't be trapped).
I tried installing a root kernel with stock rom but then it said there is some illegal operation and force me to reset the phone. I have no important data on it so I reset it and then it still displays the error. So I guess if we need root to use
Code:
/dev/kvm
(or at least add user to kvm group)
WDYM by "root kernel"? Magisk?
Yeah the magisk patched kernel.
raspiduino said:
Yeah the magisk patched kernel.
Click to expand...
Click to collapse
Very weird. For me it once got into "KG state: Prenormal", but was fine otherwise. I first reverted it to full stock, then flashed TWRP from github, then flashed magisk apk via TWRP, then after reboot installed the apk normally. There is a notification about "unauthorized actions", but it does not force anything, I can just ignore it.
This seems to work for me. qemu-system-aarch64 in Linux Deploy works with -enable-kvm.
Attached a kernel with KVM enabled + latest Magisk: https://mega.nz/file/d8lGhY7b#NKQZEL3G6bT7SetrHLh4rNgmgg0L5EXJ0Lir_QjAebA
EDIT: uploaded the patch to Github: https://github.com/sleirsgoevy/exynos-kvm-patch
Oh thanks you so much! I will try this right now!
Just 3 questions:
- How do you build and pack the kernel? I tried both "make Image" and "make Image.gz" then unpack boot.img using android image kitchen but it did not boot when I flash with Odin.
- Do you get a factory reset prompt when first boot this kernel with stock firmware? I got it once when I tried patching stock kernel with magisk.
- If you get the factory reset prompt in question 2: after reset and setup Android, I cannot get the phone's pin lock and password work anymore. So how to fix this?
Thank you very much!
{Mod edit: Quoted post deleted}
Yeah you somehow can boot Windows ARM on it (natively)
raspiduino said:
Oh thanks you so much! I will try this right now!
Just 3 questions:
- How do you build and pack the kernel? I tried both "make Image" and "make Image.gz" then unpack boot.img using android image kitchen but it did not boot when I flash with Odin.
- Do you get a factory reset prompt when first boot this kernel with stock firmware? I got it once when I tried patching stock kernel with magisk.
- If you get the factory reset prompt in question 2: after reset and setup Android, I cannot get the phone's pin lock and password work anymore. So how to fix this?
Thank you very much!
Click to expand...
Click to collapse
I used magiskboot for repacking the kernel. Unpack boot.img with `magiskboot unpack boot.img`, replace `kernel` with `Image` (not `Image.gz`), then repack with `magiskboot repack boot.img`, and flash `new-boot.img`. The magiskboot binary can be found in the Magisk installation zip.
Edit: It does boot and run but the lock screen does not work . There is an issue thread in Magisk's github page and it only solve the problem temporarily . After reboot it asked again for password.
I will try to fix this.
A small status update: Windows on ARM currently halts due to missing support for performance counters in Linux 3.18's KVM. Linux handles its registers as "read all zeroes, write ignored", but Windows expects the counters to actually tick. Probably a proper implementation needs to be backported from newer Linux.
I tried your patch on my device, modified a little bit for calling your "preinit_hyp_mode()" function from "init/main.c". I can boot into stock rom, install termux on it and then install qemu-system-arm and qemu-system-aarch64. I also run "chmod 666 /dev/kvm". Then I tried qemu-system-aarch64 with --enable-kvm but it said kvm not found. I also tried qemu-system-arm but it said "kvm_init_vcpu failed: invalid argument". "/dev/kvm" is available. What am I doing wrong?
Also my hard keys (volume up/down and power key) don't work after booting with that kernel but it work with stock rom, although this is not the main problem.
Thanks!
Blame Samsung, not yourself. This phone has a 64-bit kernel but 32-bit Android system, thus (the 32-bit build of) qemu-aarch64 thinks that the architecture is incompatible, and qemu-arm cannot utilize the 64-bit interface the kernel is providing. What I did was to install an aarch64 chroot using Linux Deploy, and install qemu on it.
I tried installing Debian arm64, Ubuntu arm64, Fedora aarch64 and a Debian Bootstrap .tar.gz from debian.org but none of them work, always falls with "Bad system call" or "sh not found". So could you be more detailed, like which option do you use in Linux Deploy? Thanks!
This should not happen, unless for some reason you are trying to do it without using root. If you're using the proper root-enabled chroot, and not the proot hack, changing the architecture in settings should be enough.
I see the message "Linux deploy was granted superuser right", but the arm64 install failed, configure failed, deploy failed, ssh and vnc failed and if I use Linux deploy telnet then "su -" and "linuxdeploy shell" it said "/system/bin/sh not found" . I installed Magisk, busybox extension from magisk. Only the armhf work on my phone.
-------------------------------------------------------------------------------
NOT THAT FAST
I sloved it
Just install armhf chroot like normal in Linux Deploy, then VNC to that chroot. Type "dpkg --add-architecture arm64" then "apt update" then "apt install qemu-system-arm:arm64". Then "chmod 666 /dev/kvm" and "qemu-system-aarch64 -M virt -cpu host --enable-kvm" It just work I loved it !
I can confirm that file "qemu-system-aarch64" is aarch64 executable and it run on my phone
Thanks sleirsgoevy my friend )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How did you boot Linux on it? I tried Debian ARM64 netinst vmlinuz and initrd but it does not output anything, even with "-nographic" or "-vga std". I checked QEMU monitor and it show that the register does change.
I also tried Windows ARM but no luck. qemu_efi.fd does not bring up a EFI interface or anything and the registers value doesn't change.
For debugging, add proper earlycon options to kernel command line, 'coz it is probably panicking way before late serial is initialized.
Steps to boot Linux:
* dump DTB from your QEMU installation: `qemu -M virt,dumpdtb=dtb.bin`
* use dtc tool from the Linux kernel source to translate it to dts
* modify the dts file as follows:
```
timer {
interrupts = <0x1 0xd 0x304 0x1 0xe 0x304 0x1 0xb 0x304 0x1 0xa 0x304>;
always-on;
compatible = "arm,armv8-timer", "arm,armv7-timer";
clock-frequency = <0x18cba80>; <-- add this
};
```
* now recompile it to dtb and provide to qemu via the -dtb flag
Attached my own patched DTB for -M virt.
Linux now boot, thanks!