Related
Is it possible to replace Android Ice-cream Sandwich with a linux/Ubuntu OS on an Asus Tablet?
Or is it best to wait a couple of years before trying this?
the lemming said:
Is it possible to replace Android Ice-cream Sandwich with a linux/Ubuntu OS on an Asus Tablet?
Or is it best to wait a couple of years before trying this?
Click to expand...
Click to collapse
See my sig for my linuxonandroid project which is a great way to get Ubuntu running without removing android
Sent from my GT-N7000 using xda premium
zacsthepack, I will also definitely give your linuxonandroid a shot if I ever manage to snag myself a tablet.. Would love to try Ubuntu on a tablet, I would try it on my phone but personally I think that would just be silly, since my phone isn't all that big
Sent from my SPH-D710
Anybody given the Ubuntu ARM version a try?
https://wiki.ubuntu.com/ARM/OmapDesktopInstall
Before attempting an install of Ubuntu, how would I back up my entire Android hard drive in case anything goes t1ts-up and I need to revert everything back to factory quality settings?
Cheers
observation
the lemming said:
Anybody given the Ubuntu ARM version a try?
https://wiki.ubuntu.com/ARM/OmapDesktopInstall
Before attempting an install of Ubuntu, how would I back up my entire Android hard drive in case anything goes t1ts-up and I need to revert everything back to factory quality settings?
Cheers
Click to expand...
Click to collapse
I could be mistaken here but it seems the point of the linuxonandroid project is so you can enjoy the functionality of the ubuntu OS without needing to do the steps you are talking about (backing up everything and nuking the OS).
Thebeast715 said:
I could be mistaken here but it seems the point of the linuxonandroid project is so you can enjoy the functionality of the ubuntu OS without needing to do the steps you are talking about (backing up everything and nuking the OS).
Click to expand...
Click to collapse
bingo, android is not effected in any way (ok well a loop device is created but thats it) theres no chance of damage to your device and to uninstall you just delete the image file
From what I've seen, Ubuntu is actually working on a port for Android. Other than that, I'm not absolutely sure, but going by a completely uneducated guess, I'd say it's entirely possible because of Android's Linux-based core.
Hi!
I'm surprised, nobody asked this already, at least I haven't found it:
Is there a way of flashing/upgrading my GT-S8500 phone a custom firmware/newer stock firmware using linux?
I know, s1 have to use multiloader for flashing, and it's windows only, but maybe some expert can tell me, if there's some alternative, even if it's harder/longer, way of reproducing what multiloader is doing, in linux. Thx in advance!
konrad.lorenz said:
Hi!
I'm surprised, nobody asked this already, at least I haven't found it:
Is there a way of flashing/upgrading my GT-S8500 phone a custom firmware/newer stock firmware using linux?
I know, s1 have to use multiloader for flashing, and it's windows only, but maybe some expert can tell me, if there's some alternative, even if it's harder/longer, way of reproducing what multiloader is doing, in linux. Thx in advance!
Click to expand...
Click to collapse
What exactly are you trying to do. I'm not familiar with the s1 and it's 'multiloader'. Are you referring to dual booting? Sorry if i'm missing your question completely. Some of us at ArcDatum do embedded systems research with ARM boards and have various multibooting devices booting anything from basic stock android stuff to gentoo/arch linux distros both separately and in dual booting environments. We use dev boards like the BeagleBoard and Pandaboards.
If you're trying to flash something weird onto ur phone though, chances are you can't or shouldn't. The only reason why it's safe for us to do it with the dev boards is because the System on a Chip is configured (by pulling specific pins high or low) to boot from the SD card and read the bootloader from there. In the case of most phones, you have locked bootloaders and no way to change that without risking destroying your boot process.
I'm trying to upgrade the factory system of my phone to a newer factory one, or to turkocfw (at first try, i'd be happy with the factory one).
Basically this is done through Kies -but thats windows only- or Multiloader -which is also windows only-, but my laptop has linux on it. I want to know, if there is a way, if I can manually do on linux, what kies and multiloader does on windows.
ArcDatum said:
What exactly are you trying to do. I'm not familiar with the s1 and it's 'multiloader'. Are you referring to dual booting? Sorry if i'm missing your question completely. Some of us at ArcDatum do embedded systems research with ARM boards and have various multibooting devices booting anything from basic stock android stuff to gentoo/arch linux distros both separately and in dual booting environments. We use dev boards like the BeagleBoard and Pandaboards.
If you're trying to flash something weird onto ur phone though, chances are you can't or shouldn't. The only reason why it's safe for us to do it with the dev boards is because the System on a Chip is configured (by pulling specific pins high or low) to boot from the SD card and read the bootloader from there. In the case of most phones, you have locked bootloaders and no way to change that without risking destroying your boot process.
Click to expand...
Click to collapse
Anyone?
That sounds a bit odd..I still dont quite understand how linux comes into play here. All the phones I've had deliver official Samsung updates over the air. Have you tried upgrading directly from ur phone?
Sent from my SGH-I747M using xda app-developers app
It should work under Wine or in a Virtual Machine. If you don't know what these are, you can easily Google them up. A basic concept
Also, for S8500 I would like to recommend http://darkforestgroup.com/forum/ a decent forum for all those older Samsung handsets.
Thats a good point. I havent used wine In a while. Although Id be careful of that, u kno, with the magic wine stuff that they pull off. Might cause some issues and risk ur phone
Edit: vm on the other hand id be more comfortable with
Sent from my SGH-I747M using xda app-developers app
ArcDatum said:
I still dont quite understand how linux comes into play here.
Click to expand...
Click to collapse
That's the operating system of my notebook. I want to use that computer for upgrading/flashing my phone.
ArcDatum said:
All the phones I've had deliver official Samsung updates over the air. Have you tried upgrading directly from ur phone?
Click to expand...
Click to collapse
Yes, but the function is 'defect by design', it is FUBAR, that function doesn't work (not only for me, it doesn't work for anyone using the same system on their phone (bada1.2)). I don't know, if it is working on bada 2.0, because I can't upgrade it.
Eddie^^ said:
It should work under Wine or in a Virtual Machine.
Click to expand...
Click to collapse
It should, but looks like it doesn't. Wherever I've looked (looks like I cannot post outside links to prove my point, sorry :S), I've found the same advice: "Don't use Kies in a VM!"
Eddie^^ said:
Also, for S8500 I would like to recommend darkforestgroup.com/forum/
Click to expand...
Click to collapse
Thanx, I had a look at there, but didn't see anything related
So, the question remains the same, if anyone knows, how (exactly) multiloader works, and that working can be reproduced on linux (without multiloader)...
Or can this be achieved using Heimdall?
Bump?
konrad.lorenz said:
Bump?
Click to expand...
Click to collapse
I would like to know if it is possible as well. Otherwise I might test it, but I'm afraid to break my phone
working on Virtualbox
autra said:
I would like to know if it is possible as well. Otherwise I might test it, but I'm afraid to break my phone
Click to expand...
Click to collapse
Ok, I can confirm it works using VirtualBox and Win7... No particular things to know, just follow the step as you would do on Windows !
Hello all. How are ya's today. I was wondering what I can do with my tablet. I bought it in haste really cause it was cheap. It is running android 4.0.4 The tablet itself is a HS-9DTB4 8gb hipstreet flare. It came rooted already so that is already done. What can I do with it. Can I upgrade the android or replace it with something. I would like to use it for business purposes but can't find the right apps for it I want. Any suggestions. ??
No one has ideas ??
1bigguy said:
Hello all. How are ya's today. I was wondering what I can do with my tablet. I bought it in haste really cause it was cheap. It is running android 4.0.4 The tablet itself is a HS-9DTB4 8gb hipstreet flare. It came rooted already so that is already done. What can I do with it. Can I upgrade the android or replace it with something. I would like to use it for business purposes but can't find the right apps for it I want. Any suggestions. ??
Click to expand...
Click to collapse
there could be lots of things you can do with a rooted device, problem is you need a custom recovery, (for restoration and backup purposes) generic tablets like your most of the time dont get one. you can go onto the play store and just type in root and there will be a huge number of apps you can use, read the desc to make sure you meet the requirements, lots of people screw up on that.
Where would I get a custom recovery...from the people that make the device or is there a place on the play store to get it for this device. "Read the Desc"...what is that. ?? As long as I don't brick the tablet I don't really care what I do to it. I called hipstreet and they say there are no more updates for this tablet at all so either I do something or I get to use what I have forever, lol. I don't wanna do that.
1bigguy said:
Where would I get a custom recovery...from the people that make the device or is there a place on the play store to get it for this device. "Read the Desc"...what is that. ?? As long as I don't brick the tablet I don't really care what I do to it. I called hipstreet and they say there are no more updates for this tablet at all so either I do something or I get to use what I have forever, lol. I don't wanna do that.
Click to expand...
Click to collapse
Custom recovery is cwm, clockworkmod, google and see if a version exists for your device. Rooting gives superuser permission which is extremely powerful, it removes all safeguards that prevent a user from destroying their system, downloading the wrong app or pushing a wrong option can instantly brick a device, which is why custom Recovery's exist, they back up the entire system not just /data but also /system and others. If you do not know what any of this means then i would suggest not messing with root access.
And read the desc means read the description, it is the mass of words under an app in the play store or app thread that outline use, require my a, what not to do and other good stuff
Please quote me in replies.
Sent from Dell Venue 8 3830
hunterk11 said:
Custom recovery is cwm, clockworkmod, google and see if a version exists for your device. Rooting gives superuser permission which is extremely powerful, it removes all safeguards that prevent a user from destroying their system, downloading the wrong app or pushing a wrong option can instantly brick a device, which is why custom Recovery's exist, they back up the entire system not just /data but also /system and others. If you do not know what any of this means then i would suggest not messing with root access.
And read the desc means read the description, it is the mass of words under an app in the play store or app thread that outline use, require my a, what not to do and other good stuff
Please quote me in replies.
Sent from Dell Venue 8 3830
Click to expand...
Click to collapse
A Custom Recovery is not CWM, CWM is one of the few Custom recovery we have, but pretty much what he said, the only way you would get a recovery is for someone to make one witch i doubt anyone has for your specific tablet.
Trozzul said:
Custom Recovery is not CWM, CWM is one of the few Custom recovery we have, but pretty much what he said, the only way you would get a recovery is for someone to make one witch i doubt anyone has for your specific tablet.
Click to expand...
Click to collapse
Cwm or twrp are the main ones, if someone says custom recovery most will say cwm, i was just trying to keep it relatively simple.
Please quote me in replies.
Sent from Dell Venue 8 3830
So basically there is nothing I can do with it unless someone has made an image specifically for this device, which I to doubt anyone will do. It's not a high end tablet so there is no reason for anyone to in the first place. Is there anyway to update the existing android o/s on it or no. ??
EDIT:
I actually just found this:
http://forum.xda-developers.com/showthread.php?t=2172412
1bigguy said:
So basically there is nothing I can do with it unless someone has made an image specifically for this device, which I to doubt anyone will do. It's not a high end tablet so there is no reason for anyone to in the first place. Is there anyway to update the existing android o/s on it or no. ??
EDIT:
I actually just found this:
http://forum.xda-developers.com/showthread.php?t=2172412
Click to expand...
Click to collapse
well from the thread it looks like it might be your device, you should ask the person if its for your model only, i searched and it seems like there is a few different ones. otherwise it looks like this is what you need if its for your tablet.
Now that's just for recovery right. ?? How do I find out what else I can load onto my tablet. ??
1bigguy said:
Now that's just for recovery right. ?? How do I find out what else I can load onto my tablet. ??
Click to expand...
Click to collapse
so if you get this recovery what your going to do is make a backup so you can always restore to when you do something wrong (for safe purposes) then apps that need root will let you use them, as for the update i doubt someone made a rom aswell, if theres no recovery theres no way people have made a rom for the tablet.
Ok, So I guess I will go on a bit of a search then to see what I can find. So not just ANY rom will do. It has to be made for this specific tablet. Like I couldn't say try and load windows on it or something silly like that. ??
Correct. Regardless of anything else you can only run code that's compiled for that.machine ... and I assume you Microsoft doesn't compile Windows for that thing.
You may want to look for a different tablet that's a clone of yours. A lot of the cheap tablets share hardware designs and are identical inside.
ljwobker said:
Correct. Regardless of anything else you can only run code that's compiled for that.machine ... and I assume you Microsoft doesn't compile Windows for that thing.
You may want to look for a different tablet that's a clone of yours. A lot of the cheap tablets share hardware designs and are identical inside.
Click to expand...
Click to collapse
So I should be looking more at what hardware it has in it to figure out a rom for it. ??
I'm kind of expert in the PC/laptop world, but a little rookie in Android and smartphones world. I don't get how a phone can get bricked.
As far as I know, an Android device has internal memory, and a portion of this internal memory is ROM (read-only memory), where the OS/firmware is installed. It's ROM because you don't want to mess around changing things of the OS, because you're not supposed to change things of the OS for the sake of a correct behavior of the phone.
The thing is that if you accidentally mess up something in the OS/firmware, you can, or should be always able to, re-install the OS again and start all over again. I mean, if I delete some Windows files in my PC and completely mess Windows up, I can always turn off the PC, turn it on, go to BIOS menu, boot from a Windows CD and re-install it. No problems at all.
1. So... where's the BIOS in Android? The recovery menu in Android is like the BIOS in Windows?
2. Bricking a phone is like damage the software of the hard disk drive (windows) or is it like mess up the BIOS?
3. Is there any difference between Operative System (android), firmware and ROM?
Well, ROM is memory, a physical drive/electronic device, completely different to a program/software/OS, but I'm referring to the conception you guys usually use (wrong I must say).
4. Why is it said that you flash a firmware, and not you install a firmware? Is it because it's done in a ROM, so it's called then flash?
Thanks!
rambomhtri said:
I'm kind of expert in the PC/laptop world, but a little rookie in Android and smartphones world. I don't get how a phone can get bricked.
As far as I know, an Android device has internal memory, and a portion of this internal memory is ROM (read-only memory), where the OS/firmware is installed. It's ROM because you don't want to mess around changing things of the OS, because you're not supposed to change things of the OS for the sake of a correct behavior of the phone.
The thing is that if you accidentally mess up something in the OS/firmware, you can, or should be always able to, re-install the OS again and start all over again. I mean, if I delete some Windows files in my PC and completely mess Windows up, I can always turn off the PC, turn it on, go to BIOS menu, boot from a Windows CD and re-install it. No problems at all.
Click to expand...
Click to collapse
I'm neither an expert in PCs or Android, so I might just be blowing hot air. I think the difference is that with a PC, it's designed to run Windows, thus Windows (obviously) will work on it (depending on version and processor compatibility). Linux runs because it's designed to run on that hardware. With Android however, everything is manufacturer-specific, and device-specific beyond that. If the firmware and kernel isn't written for that specific device, you'll brick your phone.
1. So... where's the BIOS in Android? The recovery menu in Android is like the BIOS in Windows?
Click to expand...
Click to collapse
Kinda? Maybe? I don't know.
2. Bricking a phone is like damage the software of the hard disk drive (windows) or is it like mess up the BIOS?
Click to expand...
Click to collapse
It could come from either. Flashing the wrong recovery (like TWRP for a Galaxy S3 Exynos instead of a Snapdragon model) would brick, and flashing the wrong ROM would brick as well.
3. Is there any difference between Operative System (android), firmware and ROM?
Well, ROM is memory, a physical drive/electronic device, completely different to a program/software/OS, but I'm referring to the conception you guys usually use (wrong I must say).
Click to expand...
Click to collapse
"ROM", in Android parlance, is indeed the OS. Sometimes also referred to as the firmware. Yes, both are misnomers. The use of "ROM" to refer to the OS I think comes from ROM image, when referring to gaming console emulation, but I could be mistake. "Firmware" typically refers to the programming in an electronic device that doesn't have a proper OS, per se. Like a basic mp3 player, VCR, cable modem, microwave oven, etc. It could be argued that Android is indeed a "firmware", by definition, even though "operating system" is more appropriate. Regardless, "ROM", and "firmware", in the Android world, both mean the OS.
4. Why is it said that you flash a firmware, and not you install a firmware? Is it because it's done in a ROM, so it's called then flash?
Click to expand...
Click to collapse
Flashing installs, but installing isn't necessarily flashing. "Flashing" is typically done at the recovery level (or through ADB), in the form of zips, tars, and other formats. It isn't incorrect to say that you installed a Gapps package through recovery, or you installed a newer version of TWRP, even though such actions are commonly known as "flashing". However, one wouldn't say that you flashed Clash of Clans through the Play Store, because that's not what you're doing. Flashing can refer to both firmware and software. For example, you can flash apps (like a Gapps package) TWRP batch back-ups, or even individual apps, and these are all software. You can flash nandroid backups or ROMs, and these are operating systems (and software/data). You can also flash proper firmware, such as radios/modems. You can flash kernels. Again, it's not wrong to say you "installed" it, but saying "flashed" is a more appropriate (in the Android community) and specific term.
rambomhtri said:
I'm kind of expert in the PC/laptop world, but a little rookie in Android and smartphones world. I don't get how a phone can get bricked.
As far as I know, an Android device has internal memory, and a portion of this internal memory is ROM (read-only memory), where the OS/firmware is installed. It's ROM because you don't want to mess around changing things of the OS, because you're not supposed to change things of the OS for the sake of a correct behavior of the phone.
The thing is that if you accidentally mess up something in the OS/firmware, you can, or should be always able to, re-install the OS again and start all over again. I mean, if I delete some Windows files in my PC and completely mess Windows up, I can always turn off the PC, turn it on, go to BIOS menu, boot from a Windows CD and re-install it. No problems at all.
1. So... where's the BIOS in Android? The recovery menu in Android is like the BIOS in Windows?
2. Bricking a phone is like damage the software of the hard disk drive (windows) or is it like mess up the BIOS?
3. Is there any difference between Operative System (android), firmware and ROM?
Well, ROM is memory, a physical drive/electronic device, completely different to a program/software/OS, but I'm referring to the conception you guys usually use (wrong I must say).
4. Why is it said that you flash a firmware, and not you install a firmware? Is it because it's done in a ROM, so it's called then flash?
Thanks!
Click to expand...
Click to collapse
A BRICKED phone is a phone that can't be fixed,no matter how hard you try.In other words,bricking your phone is altering the OS of your device in a way that causes it to become unusable/inoperable.
A BRICKED phone will not be able to Boot/Display any information/Boot into Recovery Mode.And thus your device turns into a very costly BRICK or Paperweight.
I have never seen any BRICKED device but heard about 2-3 cases here on XDA.I guess there are slight chances of getting your phone bricked until you do something HORRIBLY wrong or you do something,you don't have any idea about.
AFAIU,following factors can lead your device to BRICKING.
1.Overwriting the Firmware of the device or System softwares.
2.Interrupting Firmware update process (Half-written firmware ).E.g. Your device loses power during the process/data cable is pulled out during adb or rooting (That's the reason you get notifications or warnings as “Do not power the device off” when performing firmware updates and "Make sure your Battery is charged")
3.Flashing a ROM/MOD/Kernel that's not compatible to specific Device and Carrier.
Hope this helps!!
Regards
Do tell...
optimusodd said:
A BRICKED phone is a phone that can't be fixed,no matter how hard you try.In other words,bricking your phone is altering the OS of your device in a way that causes it to become unusable/inoperable.
A BRICKED phone will not be able to Boot/Display any information/Boot into Recovery Mode.And thus your device turns into a very costly BRICK or Paperweight.
I have never seen any BRICKED device but heard about 2-3 cases here on XDA.I guess there are slight chances of getting your phone bricked until you do something HORRIBLY wrong or you do something,you don't have any idea about.
AFAIU,following factors can lead your device to BRICKING.
1.Overwriting the Firmware of the device or System softwares.
2.Interrupting Firmware update process (Half-written firmware ).E.g. Your device loses power during the process/data cable is pulled out during adb or rooting (That's the reason you get notifications or warnings as “Do not power the device off” when performing firmware updates and "Make sure your Battery is charged")
3.Flashing a ROM/MOD/Kernel that's not compatible to specific Device and Carrier.
Hope this helps!!
Regards
Click to expand...
Click to collapse
That being said,
To my understanding so long as you flash your phones specific Kernel after flashing a carrier-incompatible ROM you will not BRICK. That is the only time I've bricked a device. It was an S3 and after 3 days of research I learned an SD card can be used to bring it back to life by basically flashing your .img onto it, albeit I could never boot the device without it again, though I could take it out afterward.
It was strange... but since using that device as a learning toy I believe that is something I learned from the experience, but correct me if I'm fatally wrong please before I get someone in trouble.
trinathaniel said:
That being said, To my understanding so long as you flash your phones specific Kernel after flashing a carrier-incompatible ROM you will not BRICK. That is the only time I've bricked a device. It was an S3 and after 3 days of research I learned an SD card can be used to bring it back to life by basically flashing your .img onto it, albeit I could never boot the device without it again, though I could take it out afterward. It was strange... but since using that device as a learning toy I believe that is something I learned from the experience, but correct me if I'm fatally wrong please before I get someone in trouble.
Click to expand...
Click to collapse
Short answer: If you can boot into Fastboot Or Recovery mode,you are not Hard bricked and there is still some hope
The scenerio you are talking about is Soft Brick.In this case your device don't boot but you can still get into Recovery.To fix it you boot into Recovery and restore the backup / flash the system image.You don't need to flash a kernel to make it working.
A hard bricked device won't show any sign of life,you won't be able to boot into Fastboot or Recovery to run Fastboot commands / ADB shell commands / Flash any image or zip.
Hope this helps!!
Plug out your Phone on flash Befor he finish boting
optimusodd said:
Short answer: If you can boot into Fastboot Or Recovery mode,you are not Hard bricked and there is still some hope
The scenerio you are talking about is Soft Brick.In this case your device don't boot but you can still get into Recovery.To fix it you boot into Recovery and restore the backup / flash the system image.You don't need to flash a kernel to make it working.
A hard bricked device won't show any sign of life,you won't be able to boot into Fastboot or Recovery to run Fastboot commands / ADB shell commands / Flash any image or zip.
Hope this helps!!
Click to expand...
Click to collapse
I totally understand what you're conveying and trust and believe when I say I've had my fair share of both types of Brick. What I mean is.... essentially the Kernel is going to be the defining difference between Hard Bricking vs Soft. For instance, I'm using a Note 5 Sprint (SM-N920P). If I were to flash BlahRom_N920T.zip then try and boot to system it'd definitely Hard Brick me, but if I were to flash an N920P Kernel immediately afterwards THEN boot to system out wouldn't. It might be kind of jacked up and buggy, but that's the determining factor as far as I understand.
Hello, I just got a new phone. It's probably my first actual phone in many years, as I'm mostly a PC kind of guy. I have been having trouble getting it booted for a while now. Someone informed me that it might be an Axia phone from AT&T, but I don't know the validity of that. It says Q-Innovations every time I use it on Google stuff. Does anyone here know of the phone or know how to boot one?
Thanks a lot in advance!
CamShirayuki said:
Hello, I just got a new phone. It's probably my first actual phone in many years, as I'm mostly a PC kind of guy. I have been having trouble getting it booted for a while now. Someone informed me that it might be an Axia phone from AT&T, but I don't know the validity of that. It says Q-Innovations every time I use it on Google stuff. Does anyone here know of the phone or know how to boot one?
Thanks a lot in advance!
Click to expand...
Click to collapse
The model number seems to be the AT&T version of that phone.
When you say that you can't get it booted, what do you mean exactly? What is the device doing when you try to boot it?
Have you tried holding volume up+power(let go when you see the splash screen) to boot into recovery, then factory reset and wipe cache partition?
Some devices have to hold volume down+power, then at the bootloader menu, choose the recovery option.
Sent from my LGL84VL using Tapatalk
What do you mean? I didn't think it was that easy to boot a phone? I wanted to put Linux on my phone instead of the current android version or even put them both on there.
CamShirayuki said:
What do you mean? I didn't think it was that easy to boot a phone? I wanted to put Linux on my phone instead of the current android version or even put them both on there.
Click to expand...
Click to collapse
I think you need to do some research to get familiar with how android devices actually work. Android devices are not like PC, you can't just install whatever OS you want, android devices are not "generic" like that. Operating systems for android devices have to be built specifically based on the hardware in the device, down to the kernel level, the kernel has to be specific to the device. You need to do some reading about how android stock recovery and custom recovery actually work , you also need to research how android stock firmware and custom operating systems are flashed on android devices.
It is "possible" to remove android and install Linux on an android device, but only certain devices can do it, depending on the security built-in to the bootloader that is installed on the device. There isn't a universal way to install Linux on android.
It is also possible to install Linux on top of android in a sort of emulator/VM then use a VNC to .
There are some apps to install linux on top of android, such as:
1) Linux Deploy
2) Complete Linux installer
3) UserLAnd
I installed and tested UserLAnd last night. Try this and see what you think.
https://github.com/CypherpunkArmory/UserLAnd
View the README.md for instuctions to set it up.
Sent from my LGL84VL using Tapatalk