Related
Okay, well the title should be pretty self explanatory I hope, but here's what I'm looking for:
A way to install TWRP and FireFireFire 1.4 on a Kindle Fire using a Mac (OS X 10.7.4 Lion if anyone wants to know).
I know that you should install TWRP only through fastboot then use TWRP to flash FFF and your custom ROM.
I also know there's something about modifying Android SDK drivers to make ADB and fastboot work properly with the Kindle Fire.
I am not looking for any sort of one-click solution. I once jailbroke my iPhone using a simple one-click, it didn't turn out well. Fortunately iPhones are almost always fixed by an iTunes restore. Did it using redsn0w after that, it was better. I manually installed homebrew on my Wii as well, which is more complex than redsn0w and more of an actual manual install. Wii homebrew works beautifully.
Anyways, I'm against one-clicks/simple rooters/jailbreakers because it seems like if even one thing is out of place, they mess things up.
I want to manually do this, and I know there's a way to. I just need to install Android SDK, I can do that. Modify the drivers, this is the thing I need the most assistance with, because I don't know how to do it and I know tools like KFU do it automatically. And of course, I want to manually use pokey9000's fbmode to get into fastboot, then flash TWRP, then get into TWRP, flash FFF and my custom ROM.
Anyone who could help me with this, I'd greatly appreciate it!
Well I see you don't want the easy solution but maybe part of this will help you with the drivers easily http://forum.xda-developers.com/showthread.php?t=1790139 then its just a matter of fastboot flashing twrp.img and fff.bin to your kindle. From that point you enter recovery make a backup. I suggest reboot after this. transfer a ROM zip and gapps zip of your choice to the root of your sdcard. Boot back to recovery- factory reset, -wipe cache, -wipe dalvik,-wipe system,-flash ROM,-flash gapps- select reboot then select system if prompted enjoy
---------- Post added at 03:49 AM ---------- Previous post was at 03:32 AM ----------
Take some time read these to threads since the hard way makes you happy familiarize yourself with what needs to be done and how to do it so you are always in the safe zone http://forum.xda-developers.com/showthread.php?t=1552547 and this http://forum.xda-developers.com/showthread.php?t=1638452 kinfauns took a lot of time to compile these threads to build awareness I believe he as well is on Mac just a guess. Some of this is a little gauged to windows but the concept is relatively the same so I have been told. I'm on windows myself and I understand that on Mac and Linux drivers aren't a problem as they are on windows. Good luck don't be afraid to ask more questions before you leap others out there have more experience with Mac than I
Edit: And note that I said fff.bin is the file you fastboot flash not a zip a zip file will break your bootloader severely unless you flash in recovery then a zip is the desired file type. Research is good prevents mishaps
Thepooch said:
Well I see you don't want the easy solution but maybe part of this will help you with the drivers easily http://forum.xda-developers.com/showthread.php?t=1790139 then its just a matter of fastboot flashing twrp.img and fff.bin to your kindle. From that point you enter recovery make a backup. I suggest reboot after this. transfer a ROM zip and gapps zip of your choice to the root of your sdcard. Boot back to recovery- factory reset, -wipe cache, -wipe dalvik,-wipe system,-flash ROM,-flash gapps- select reboot then select system if prompted enjoy
---------- Post added at 03:49 AM ---------- Previous post was at 03:32 AM ----------
Take some time read these to threads since the hard way makes you happy familiarize yourself with what needs to be done and how to do it so you are always in the safe zone http://forum.xda-developers.com/showthread.php?t=1552547 and this http://forum.xda-developers.com/showthread.php?t=1638452 kinfauns took a lot of time to compile these threads to build awareness I believe he as well is on Mac just a guess. Some of this is a little gauged to windows but the concept is relatively the same so I have been told. I'm on windows myself and I understand that on Mac and Linux drivers aren't a problem as they are on windows. Good luck don't be afraid to ask more questions before you leap others out there have more experience with Mac than I
Edit: And note that I said fff.bin is the file you fastboot flash not a zip a zip file will break your bootloader severely unless you flash in recovery then a zip is the desired file type. Research is good prevents mishaps
Click to expand...
Click to collapse
BreakDroid is one of those "one click" solutions I'm really trying to keep away from. I know that installing a custom bootloader + recovery is just a matter of having your computer properly recognize the Kindle Fire as an ADB interface, which I need to modify drivers for. I need to know how to modify drivers.
After that, it's just that I need to get into fastboot and I've got it from there.
Well, since you want a complex approach, may as well go with Firekit: http://forum.xda-developers.com/showthread.php?t=1430038&highlight=firekit (install_fff_twrp_from_stock)
I simply just said to use breakdroid for the driver install I didn't suggest you use it for anything else but with drivers I'm sure there are plenty of driver setup tutorials for Mac and the kindle fire so Google is your friend. Read the very first sentence of my first post seems you overlooked that
Breakdroid works great though is simple and installs exactly what you need. From there you have twrp and can flash away.
Sent from my MB860 using xda app-developers app
Thepooch said:
I simply just said to use breakdroid for the driver install I didn't suggest you use it for anything else but with drivers I'm sure there are plenty of driver setup tutorials for Mac and the kindle fire so Google is your friend. Read the very first sentence of my first post seems you overlooked that
Click to expand...
Click to collapse
Actually from what I've seen on various tutorials, ones about rooting, they always have instructions for Windows to install drivers but most of them instruct Mac / Linux to skip that step, then Mac / Linux picks back up where you're already issuing ADB and fastboot commands. I feel totally stupid if I've overlooked this, but if it's actually possible to skip this step that'd be so much easier.
Also I did read your first post. But when looking at BreakDroid I saw nothing specific about installing drivers, just that it was supposed to be a simple tool where you go through each step.
blue71 said:
Breakdroid works great though is simple and installs exactly what you need. From there you have twrp and can flash away.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
All simple tools are meant to work great. Unfortunately, they just don't sometimes.
Is there anyone who has actually rooted a Kindle Fire on Mac or Linux here that can verify you don't need to do anything with drivers? And that just installing the Android SDK is sufficient to proceed?
superriku11 said:
All simple tools are meant to work great. Unfortunately, they just don't sometimes.
Click to expand...
Click to collapse
Very true. The unfortunate part is when users of these tools have no idea how to get themselves out of trouble, but I digress...
superriku11 said:
Is there anyone who has actually rooted a Kindle Fire on Mac or Linux here that can verify you don't need to do anything with drivers? And that just installing the Android SDK is sufficient to proceed?
Click to expand...
Click to collapse
Here's a guide for setting up a Linux environment...
http://forum.xda-developers.com/showthread.php?t=1475740
All you really need for Linux are the binaries (adb/fastboot) and /root/.android/adb_usb.ini with 0x1949 in it. Once you have those, you just need to run the binaries as root. The other things in that guide sets things up so a user without root privileges can access the USB ports and set paths to those binaries. There are no "drivers" in the Windows sense to be installed and you don't need to install the SDK if you can find those binaries elsewhere.
I'm confident the setup will be similar to Mac OS X, but udev is linux specific. I don't know what the Mac OS X equivalents are because I've always used virtual machines with Linux or Windows to interact with the KF. Regardless, you should still be able to use them as root and issue commands to the KF.
Thepooch gave you links to my guides... whichever OS you decide to use, all of the fastboot and adb commands will be the same. You just need to swap out the directory path conventions from Windows to Linux/Mac OS X.
kinfauns said:
Very true. The unfortunate part is when users of these tools have no idea how to get themselves out of trouble, but I digress...
Here's a guide for setting up a Linux environment...
http://forum.xda-developers.com/showthread.php?t=1475740
All you really need for Linux are the binaries (adb/fastboot) and /root/.android/adb_usb.ini with 0x1949 in it. Once you have those, you just need to run the binaries as root. The other things in that guide sets things up so a user without root privileges can access the USB ports and set paths to those binaries. There are no "drivers" in the Windows sense to be installed and you don't need to install the SDK if you can find those binaries elsewhere.
I'm confident the setup will be similar to Mac OS X, but udev is linux specific. I don't know what the Mac OS X equivalents are because I've always used virtual machines with Linux or Windows to interact with the KF. Regardless, you should still be able to use them as root and issue commands to the KF.
Thepooch gave you links to my guides... whichever OS you decide to use, all of the fastboot and adb commands will be the same. You just need to swap out the directory path conventions from Windows to Linux/Mac OS X.
Click to expand...
Click to collapse
Thanks for your help! Thanks for everyone's help actually! You all contributed somehow, and thanks to you I successfully installed FFF 1.4a, TWRP 2.2.0, and Jandycane 7-29 on my Kindle Fire! Awesome so far, thanks guys!
:highfive::good:
Okay, semi-newb here. I've been able to replace the ROM on an Arnova tablet a year ago, and sideloaded Google play on a Polaroid tablet. I've been researching the simplest way to turn my Mom's Kindle Fire V1 into a simple android tablet with access to Google Play. If I can accomplish this, then I'm hoping to repeat the process on my son's Kindle Fire HD. I'd like to load one of the Nexus 7 Roms. Unfortunately, there's a /lot/ of different Nexus ROMs and methods, each with links to other software that I'm trying to understand. Please forgive my questions...
I've downloaded these apps:
-gapps-jb-20130813-signed.zip
-GooManager_2.1.3.apk
-Kindle Fire Utility v0.9.9.zip
-SmoothROM-1.7_otter.zip
-Smirkit.apk
I started at this thread: http://forum.xda-developers.com/showthread.php?t=2265999
Which led me to this thread: http://forum.xda-developers.com/showthread.php?t=2103278
"Installation
-Make sure you have the latest TWRP"
Is this in the goomanager file? I downloaded from this link, http://forum.xda-developers.com/showthread.php?t=1592681, but I don't see the screen that shows up in the OP, and I'm not entirely sure what to do with this program.
"-I suggest you make a backup"
Is this what TWRP is for? I've copied all the KF files onto my computer already, but I don't have an .img file. And if I want to reflash with the original files, do I need to create an .img of my existing files, or do I download one from the list of files that I see in the goomanager?
"-Wipe data, cache, system, and dalvik cache"
Do I use one of these files to do this, or do I go into the KF settings to do this?
-Install ROM
Do I just copy the boot.img over to the root directory of the KF. I recall doing this for the Arnova.
-Install the latest gapps for CM10.1.x
Again, do I use one of these programs to do so, or copy files over (side-load)? I don't see .apk files in this package
-Reboot
I think I can do this one.
Again, sorry for being a newb...I just want to make sure I'm doing everything right. Haven't bricked a tablet yet, but I've probably just been lucky so far.
Thanks in advance. (Oh, do I need the fastboot cable for any of this? Is it recommended to get one just in case?)
Ok lemme get to things straight, this is the kfhd forum, if you have a kindle fire 1 then this is technically the wrong forum but i will point you in the right direction becasue theres some things you need to understand. First off the kindle fire 1 is very very easy to do what you want to do to it. Basically you download kindle fire utility and it will root and install whatever recovery you want onto it and from there you grab rom's from the kindle fire 1's development section and you can flash them with the corresponding gapps.
Here's where the important thing is, if you want to do this to a hd model it isnt the same process, if you attempt to use kindle fire utility on a hd model you are likely to hard brick it because the hd has a locked bootloader. The hd has a simple enough method to flash it though, as long its not the 2013 model you can install roms on it, theres a tutorial for installing with fireflash that i think is the easiest method as long as you make sure to downgrade the bootloader, somehow people tend to miss the checkbox for it.
If you mention which hd you have i cna link you to the tutorial for it but i don't wanna send you the wrong one even though there really isnt much of a difference since its the same program and inlcudes the files in teh apk.
Now to answer some questions:
First off the backup in twrp is useful yes, but only if you have twrp installed, lets say something happens and you no longer can access recovery and are forced to use fastboot, in that case you would need the image files that you mentioned, those images can be downloaded off the internet or you can jsut backup up your kindle and use those images.
Second: The wipe options are in twrp once you have it working
Third: You don't copy the boot.img over, you hit install in twrp and select the zip file that is the rom and tell it to flash.
Fourth: do as said in previous step, just do it after you flash teh rom though.
and finally yes its kinda recommended to have a fastboot cable, though i am one to talk since i don't have one but i have the means to make one at any time. Hope this helps!
Also thought i'd mention if it turned out to be a kindle fire 2 that its process is similar to the hd's so dont use kindle fire utility on it either. You can always check software version that it has installed an i can tell you for sure what model it is.
Just a thought... the kernel command line just runs /init. If I removed Android from /system, put the files for Arch Linux and symlinked /usr/lib/systemd/systemd to init, wouldn't Arch just happily boot atop the Android kernel? (I know, I'd need to make a custom kernel with systemd support). I'd probably also run into driver trouble, doubt X would work but I should at least be able to get to a tty, correct?
If that works... maybe I could reengineer some programs to use the Android drivers and use Gentoo to compile a Linux distro for the phone? Is this possible? Thanks!
I guess @ycavan is the guy to ask about this kind of thing?
You've pretty much described the sailfish os. I think there's a forum dedicated to that on xda.
Sent from my ASUS_Z00AD using XDA Free mobile app
I present to you instructions on how to get Arch Linux working natively on your shield TV dual booted with your Android rom. This is all thanks to the amazing people in this thread for getting Ubuntu on the shield and would not be possible without them.
http://forum.xda-developers.com/shield-tv/general/ubuntu-utopic-nvidia-shield-tv-t3150352
This install will put arch Linux on a micro SD card, and does not modify your shield at all if you so choose. First download these 2 files.
Archlinux Stage 3 install
http://archlinuxarm.org/os/ArchLinuxARM-aarch64-generic-latest.tar.gz
Kernel (Credits to jagger11 from his thread) You only need nvidia_boot.img
https://drive.google.com/folderview...ZSS1VxUVBJZmFqSXNFYUhpN2lHcklhVzZtX0Z5OENxdU0
To intstall
1. Unlock your shield TV
2. Format your SD card to EXT4
3. Mount the SD card
4. As the root user on your linux distro (not sudo) run this command (From the same directory that you downloaded that file to, and replacing mountpoint to where you mounted the SD to)
bsdtar -xpf ArchLinuxARM-aarch64-generic-latest.tar.gz -C mountpoint
5. Unmount the drive, then run the command "sync". When that finishes, pull the SD card from the computer.
6. Put the SD in the shield
7. Reboot to bootloader (adb reboot fastboot) with your preferred method
8. Boot Linux
To boot it once run this
a) fastboot boot nvidia_boot.img
To save to recovery run this (Reboot android to recovery to boot arch after)
b) fastboot flash recovery nvidia_boot.img
Default users and passwords are
root:root
alarm:alarm
For more information, check this page.
http://archlinuxarm.org/platforms/armv8/generic
Tested Working
*Ethernet
*USB
*TTY Terminals
*Framebuffer (Install X11 as usual and xf86-video-fbdev)
Untested
*WIFI (Should work)
*Bluetooth (Probably doesn't work)
Broken
*3D acceleration (Will work on this in the future)
*You tell me
*Sometimes does not boot after a few working boots (I think it's a problem with my SD, or my android install messing with it. Working that out now, but please report if you have this issue only after it boots fine at least once)
My request to you. I am not a kernel dev any more. I once was, but things have unfortunately changed, and I don't have the time or resources to learn it all again. If anyone wants to develop a kernel for this, please do and I'll add it in the OP. Unless something changes, and Ubuntu kernel from the Utopic thread will work fine here)
I'll format this a bit better later, but hopefully this is a good start. I have some good tips and tricks to add if people are interested in this, and was able to watch quite a lot of my videos in vlc even on framebuffer. Please give me some feedback on what you want to see, and ask any questions. I'll be glad to help!
kdb424 said:
I present to you instructions on how to get Arch Linux working natively on your shield TV dual booted with your Android rom. This is all thanks to the amazing people in this thread for getting Ubuntu on the shield and would not be possible without them.
http://forum.xda-developers.com/shield-tv/general/ubuntu-utopic-nvidia-shield-tv-t3150352
This install will put arch Linux on a micro SD card, and does not modify your shield at all if you so choose. First download these 2 files.
Archlinux Stage 3 install
http://archlinuxarm.org/os/ArchLinuxARM-aarch64-generic-latest.tar.gz
Kernel (Credits to jagger11 from his thread) You only need nvidia_boot.img
https://drive.google.com/folderview...ZSS1VxUVBJZmFqSXNFYUhpN2lHcklhVzZtX0Z5OENxdU0
To intstall
1. Unlock your shield TV
2. Format your SD card to EXT4
3. Mount the SD card
4. As the root user on your linux distro (not sudo) run this command (From the same directory that you downloaded that file to, and replacing mountpoint to where you mounted the SD to)
bsdtar -xpf ArchLinuxARM-aarch64-generic-latest.tar.gz -C mountpoint
5. Unmount the drive, then run the command "sync". When that finishes, pull the SD card from the computer.
6. Put the SD in the shield
7. Reboot to bootloader (adb reboot fastboot) with your preferred method
8. Boot Linux
To boot it once run this
a) fastboot boot nvidia_boot.img
To save to recovery run this (Reboot android to recovery to boot arch after)
b) fastboot flash recovery nvidia_boot.img
Default users and passwords are
root:root
alarm:alarm
For more information, check this page.
http://archlinuxarm.org/platforms/armv8/generic
Tested Working
*Ethernet
*USB
*TTY Terminals
*Framebuffer (Install X11 as usual and xf86-video-fbdev)
Untested
*WIFI (Should work)
*Bluetooth (Probably doesn't work)
Broken
*3D acceleration (Will work on this in the future)
*You tell me
*Sometimes does not boot after a few working boots (I think it's a problem with my SD, or my android install messing with it. Working that out now, but please report if you have this issue only after it boots fine at least once)
My request to you. I am not a kernel dev any more. I once was, but things have unfortunately changed, and I don't have the time or resources to learn it all again. If anyone wants to develop a kernel for this, please do and I'll add it in the OP. Unless something changes, and Ubuntu kernel from the Utopic thread will work fine here)
I'll format this a bit better later, but hopefully this is a good start. I have some good tips and tricks to add if people are interested in this, and was able to watch quite a lot of my videos in vlc even on framebuffer. Please give me some feedback on what you want to see, and ask any questions. I'll be glad to help!
Click to expand...
Click to collapse
Thanks for the new thread. You are correct that the "nvidia_boot.img" from jagger11 can boot to archLinux but the kernel I built can't.
I have always been using Ubuntu with desktop enabled by default. How did you install X11 under archLinux?
yahoo2016 said:
Thanks for the new thread. You are correct that the "nvidia_boot.img" from jagger11 can boot to archLinux but the kernel I built can't.
I have always been using Ubuntu with desktop enabled by default. How did you install X11 under archLinux?
Click to expand...
Click to collapse
Following the standard guide on their wiki.
I installed
xorg-server
xorg-server-utils
xorg-init
xf86-video-fb
And then just the standard startx after setting my xinitrc to the usual. In my case I used awesome WM, though you can use any, and exec that in your .xinitrc file
kdb424 said:
Following the standard guide on their wiki.
I installed
xorg-server
xorg-server-utils
xorg-init
xf86-video-fb
And then just the standard startx after setting my xinitrc to the usual. In my case I used awesome WM, though you can use any, and exec that in your .xinitrc file
Click to expand...
Click to collapse
I have to admit I was spoiled by Ubuntu which installs everything by default. I have to read archLinux wiki and try them tomorrow morning.
yahoo2016 said:
I have to admit I was spoiled by Ubuntu which installs everything by default. I have to read archLinux wiki and try them tomorrow morning.
Click to expand...
Click to collapse
Those packages will do you other than desktop manager, but I have to say, I'm pretty minimalist, and arch is by default, so don' feel too bad. I've just been using arch for the last few years, and was using Gentoo before that, which is all even more manual and source built.
https://wiki.archlinux.org/index.php/Xorg
That page will go through it all. Once you know what desktop manager you want (I recommend XFCE if you don't know what, or LXDE which is even lighter), check the pages out on there for them. It covers haw to do absolutely everything. I honestly use arch linux for the wiki. It's by far the best source of linux information on the net I'd be willing to bet.
kdb424 said:
Those packages will do you other than desktop manager, but I have to say, I'm pretty minimalist, and arch is by default, so don' feel too bad. I've just been using arch for the last few years, and was using Gentoo before that, which is all even more manual and source built.
https://wiki.archlinux.org/index.php/Xorg
That page will go through it all. Once you know what desktop manager you want (I recommend XFCE if you don't know what, or LXDE which is even lighter), check the pages out on there for them. It covers haw to do absolutely everything. I honestly use arch linux for the wiki. It's by far the best source of linux information on the net I'd be willing to bet.
Click to expand...
Click to collapse
What display driver should I install?
The wiki starts with
lspci | grep -e VGA -e 3D
But lspci does not work for shield TV.
yahoo2016 said:
What display driver should I install?
The wiki starts with
lspci | grep -e VGA -e 3D
But lspci does not work for shield TV.
Click to expand...
Click to collapse
xf86-video-fbdev works for me. Since we don't have access to the GPU directly, we are using the framebuffer at the moment.
kdb424 said:
xf86-video-fbdev works for me. Since we don't have access to the GPU directly, we are using the framebuffer at the moment.
Click to expand...
Click to collapse
That confused me since I thought xf86 meant x86 but Shield has Arm CPUs.
yahoo2016 said:
That confused me since I thought xf86 meant x86 but Shield has Arm CPUs.
Click to expand...
Click to collapse
Yeah, it's actually got nothing to do with architecture. Not quite sure why they are named as such. Also, xf86-video-fbdev isn't listed there as it's a last resort kinda thing, but it works well on the shield for the moment. Once I figure out why my system stops booting linux from time to time, I'll work on GPU drivers. Hard to know what broke it if I don't fix that first.
kdb424 said:
Yeah, it's actually got nothing to do with architecture. Not quite sure why they are named as such. Also, xf86-video-fbdev isn't listed there as it's a last resort kinda thing, but it works well on the shield for the moment. Once I figure out why my system stops booting linux from time to time, I'll work on GPU drivers. Hard to know what broke it if I don't fix that first.
Click to expand...
Click to collapse
You may want to have a look at this: https://github.com/NVIDIA/tegra-nouveau-rootfs
Arch Linux is the target rootfs and the Jetson TX1 is supported. Now the questions is how to get a mainline kernel running on shield tv. I guess one issue is the device tree which will not be provided by uboot like on normal arm systems. In the kernel configuration you can define that the device tree is appended to the kernel image (e.g. by "cat Image foster.dtb > newImage"). Maybe this is a solution.
Thanks_Meter said:
You may want to have a look at this: https://github.com/NVIDIA/tegra-nouveau-rootfs
Arch Linux is the target rootfs and the Jetson TX1 is supported. Now the questions is how to get a mainline kernel running on shield tv. I guess one issue is the device tree which will not be provided by uboot like on normal arm systems. In the kernel configuration you can define that the device tree is appended to the kernel image (e.g. by "cat Image foster.dtb > newImage"). Maybe this is a solution.
Click to expand...
Click to collapse
Thanks for the info. I'm going to have the next 2 days off work, so I'll definately get to work. I'm going to need assistance in getting a working kernel as I don't have an x86 machine around currently. Crazy, I know, but I don't. I'll see if I can get the drivers installed if someone works on a kernel. If not, I'll contact some of my linux friends and see what they come up with.
kdb424 said:
Thanks for the info. I'm going to have the next 2 days off work, so I'll definately get to work. I'm going to need assistance in getting a working kernel as I don't have an x86 machine around currently. Crazy, I know, but I don't. I'll see if I can get the drivers installed if someone works on a kernel. If not, I'll contact some of my linux friends and see what they come up with.
Click to expand...
Click to collapse
That link mentioned:
"The first prerequisite is that you must use an up-to-date U-Boot as bootloader"
Jetson TK1 and TX1 uses U-boot, Shield TV however uses fastboot not U-boot and the kernel is not Linux but Android.
I'd really like someone can have u-boot ported to Shield TV as 2nd or 3rd stage boot loader.
Damn! I just found out that this CONFIG_ARM_APPENDED_DTB trick only works with zImage but not with Image as needed for abootimg. Currently I don't have an idea how to get a mainline kernel running on the shield tv. I guess uboot makes no sense since we don't have an uart.
Thanks_Meter said:
Damn! I just found out that this CONFIG_ARM_APPENDED_DTB trick only works with zImage but not with Image as needed for abootimg. Currently I don't have an idea how to get a mainline kernel running on the shield tv. I guess uboot makes no sense since we don't have an uart.
Click to expand...
Click to collapse
u-boot could use netconsole:
http://forum.doozan.com/read.php?3,14,14
---------- Post added at 10:33 PM ---------- Previous post was at 10:28 PM ----------
My kernel can boot to command line archLinux now, I updated the procedure:
http://forum.xda-developers.com/showpost.php?p=64330336&postcount=147
I'll try that kernel when get home with the gui running on framebuffer. Should work.
kdb424 said:
I'll try that kernel when get home with the gui running on framebuffer. Should work.
Click to expand...
Click to collapse
I uploaded my latest kernel tested with command line archLinux:
https://drive.google.com/file/d/0Bz5kaPQJx_AgUklNekxGeWFuNW8/view
yahoo2016 said:
I uploaded my latest kernel tested with command line archLinux:
https://drive.google.com/file/d/0Bz5kaPQJx_AgUklNekxGeWFuNW8/view
Click to expand...
Click to collapse
Any chance you can maybe try to patch in the Nouveau kernel driver from here?
With a kernel running that I can get 3D acceleration work started. Till I get that sorted out I can only guess if my changes are working or not.
I'll also be trying to get the closed source binaries running on this. I have decided to pay a decent sum of money for a VPS to get a compile machine. Hopefully we can get this project rolling.
kdb424 said:
Any chance you can maybe try to patch in the Nouveau kernel driver from here?
With a kernel running that I can get 3D acceleration work started. Till I get that sorted out I can only guess if my changes are working or not.
I'll also be trying to get the closed source binaries running on this. I have decided to pay a decent sum of money for a VPS to get a compile machine. Hopefully we can get this project rolling.
Click to expand...
Click to collapse
I did not expect it'd take me so long just to have gui running for archLinux. As I mentioned before this thread started, I'd like to try Cuda 7.0 on ArchLinux. I main goal is to have Cuda working so I can use Gpgpu of Tegra for image processing and other applications.
A script or procedure for post installation to quickly install gui is what I was interested. To install archlinux rootfs without gui was very simple and I did it the first day when I received my Shield TV to troubleshoot Utopic rootfs. I could read the wiki to have gui working for archLinux, but I have to spend my time on other things, e.g., without hope to have u-boot or multirom working for Shield TV, I have to learn Android kernel (I'm in the process of clone Android kernel source tree).
I'll write a script for you once I get home. Thanks for the input. Any requests for a desktop environment or window manager? If not I'll just pick a light one like lxde.
kdb424 said:
I'll write a script for you once I get home. Thanks for the input. Any requests for a desktop environment or window manager? If not I'll just pick a light one like lxde.
Click to expand...
Click to collapse
Any desktop is fine. I'd like to push Cuda 7.0 from my build PC to archLinux like I did for L4T. Network connection and any desktop are what I need. If it works, we can see performance differences between 32 bits and 64 bits
Thanks.
On page https://wiki.lineageos.org/adb_fastboot_guide.html whatever is written under Linux is beyond my understanding. I am using Ubuntu 14.04 and want to root my A7 (2017) with that OS. I have extracted the .zip file namely platform-tools_r30.0.1-linux.zip which doesn't match with the article's 2nd point under Linux, that is Extract it somewhere - for example, ~/adb-fastboot. I do not extracted any folder with name 'adb-fastboot' however I got a folder namely 'platform-tools'.
Now coming to the 3rd point what they mean by Add the following to ~/.profile: which is followed by some commands. Do I need to open some text file namely ".profile" or something and add those commands to it??
And 5th point says You may also need to set up udev rules: see this repository for more info.. So how do I know if I need to set up udev rules? And what are udeve rules in the first place?
I am supposing to root my phone step by step. But it seems very hard. I can't get hold of a Windows PC which seems easy compared to Linux. Also I am not following any guide on XDA Developers because my phone is supported by official Lineage OS website and I am following their instructions.
Hi,
Adb fastboot guide isn't necessary for root on LineageOS. You can find the root addon here https://download.lineageos.org/extras. You'll want to download 16.0 arm64 one.
Just enter your recovery (TWRP) and flash the root addon. Later you can enable it in developer options.
Some users flash magisk (search xda for it) so you can try that too.
livelife01 said:
On page https://wiki.lineageos.org/adb_fastboot_guide.html whatever is written under Linux is beyond my understanding. I am using Ubuntu 14.04 and want to root my A7 (2017) with that OS. I have extracted the .zip file namely platform-tools_r30.0.1-linux.zip which doesn't match with the article's 2nd point under Linux, that is Extract it somewhere - for example, ~/adb-fastboot. I do not extracted any folder with name 'adb-fastboot' however I got a folder namely 'platform-tools'.
Now coming to the 3rd point what they mean by Add the following to ~/.profile: which is followed by some commands. Do I need to open some text file namely ".profile" or something and add those commands to it??
And 5th point says You may also need to set up udev rules: see this repository for more info.. So how do I know if I need to set up udev rules? And what are udeve rules in the first place?
I am supposing to root my phone step by step. But it seems very hard. I can't get hold of a Windows PC which seems easy compared to Linux. Also I am not following any guide on XDA Developers because my phone is supported by official Lineage OS website and I am following their instructions.
Click to expand...
Click to collapse
Using ADB isnt the "normal" way to root a samsung device.
The preferred method is installing a custom recovery (like TWRP, SHRP or Orangefox) and then simply install magisk in the recovery.
I dont know if its even possible to root through ADB to be honest.
Also, even if your phone is supported by Lineage, that doesnt mean every guide on their website fits perfectly to your device.
Simon1511 said:
The preferred method is installing a custom recovery (like TWRP, SHRP or Orangefox) and then simply install magisk in the recovery.
Click to expand...
Click to collapse
Then can you please please tell me how can I root my A7 (2017) with baseband version A720FXXU9CTA2? I also prefer TWRP over any other method because I have used it before but it was near a decade ago and now I have forgotten so much things. It's best if I am given a way to root on Linux (my work computer) otherwise I have to wait or purchase a Windows PC.
(PS: Every forum made for a specific phone on XDA should have an official thread with step by step rooting instructions.)
livelife01 said:
Then can you please please tell me how can I root my A7 (2017) with baseband version A720FXXU9CTA2? I also prefer TWRP over any other method because I have used it before but it was near a decade ago and now I have forgotten so much things. It's best if I am given a way to root on Linux (my work computer) otherwise I have to wait or purchase a Windows PC.
(PS: Every forum made for a specific phone on XDA should have an official thread with step by step rooting instructions.)
Click to expand...
Click to collapse
See here:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
If you want to install lineage anyway, you dont need to care about the RMM and no-verity things.
For rooting, you can simply search for a guide on how to install magisk on google, there are more than enough.