Okay so there are two multi-boot modifications flowing around XDA for a ton of various devices.. Has anyone ever considered porting one to the robin? lately with all these rock solid Roms it doesn't seem like too bad of an idea and I truly wish I had the experience to do it myself.
https://github.com/chenxiaolong/DualBootPatcher/
and
https://github.com/Tasssadar/multirom
and
https://github.com/efidroid/
Oh hell yes! I'd like to see this!
Desperately waiting for it!
Sounds cool, I can have Omni and XOSP at the same time ;P
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Alexandroid99 said:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Click to expand...
Click to collapse
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
AnierinB said:
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
Click to expand...
Click to collapse
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
AnierinB said:
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
Click to expand...
Click to collapse
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Alexandroid99 said:
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Click to expand...
Click to collapse
Let me know how it goes man :highfive:
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
No dice. Tried to compile lk using msm8994 (SD810- same workaround as 5x) and was able to fastboot boot a nouefi lk.img but but once booted there was no device showing up in fastboot devices which unfortunately is key to the next step
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
I got lk to boot using the same lk_base as the 5x so there are a few thing in common because the aboot dump showed the same value. anyways I made some progress: Display to show, finalize_device to execute and was able to build uefi.img and boot it. upon booting uefi the kernel panics and reboots so I have to to figure that out before proceeding to the checklist.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
I've got it to boot and run for the most part but I'm not the most experienced at porting and there are a few things left to do like configuring the fstab.multiboot correctly which is key to multi booting roms and installing the ota through efidroid app via github sever
AnierinB said:
So I've got efi-droid ported and working for the most part. I'm not the most experienced at porting and there are a few things left to do like testing multiboot roms and configuring a local ota sever to do so..
I'm making this post so that I can hand off my findings, config.ini, and my lk_inc.make to someone who has more experience/ someone who can get this done and wants to test multiboot and see if it's a go. Think you can do so and become the maintainer for this project?
Click to expand...
Click to collapse
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
valhallen.282 said:
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
Click to expand...
Click to collapse
As soon as I get these local ota server problems figured out and are able to actually test dual booting a rom I'll pm you with some goodies:good:
It's pretty easy to build yourself after you figure out what variables the lk.mk and config.ini need. Although I have been doing this for 3 days now with many trial and error. Pretty shocked it's even working as good as it is right now because there's been a lot of known issues with 64bit socs
delete
I'm gonna have to put this project behind me... I lack some knowledge on a few areas of the porting process and to configure it correctly is possible but I, myself can not do it. If a developer has the device, and wants to try porting/configuring it then go for it. The main thing is that we are able to get lk, uefi to boot and display screen (properly) so fixing the other issues like fstab.multiboot table should be easy for someone more experienced. At least theres hope with this modification. Sorry folks, I'll stick to my boot logos for now haha.
AnierinB said:
@ValHallen can you download the efi manager application off the play store and tell me what device it gives you an error for? then after doing so can you edit your build prop and add this line: efidroid.server_url=https://raw.githubusercontent.com/anierinbliss/efidroid_ota/master
then delete the app, reboot your phone and reinstall it.. Does it still fail?
Click to expand...
Click to collapse
I think you tagged the wrong person. But I'll try. In a short while.
It's probably best to put all thaz work out in the open including github repos and a separate thread so someone who's capable might stumble upon it and pick up qhere you left off.
Related
Hey Guys,
I've noticed many other phones have guides explaining how to download and compile Android for their phones including proprietary drivers and misc files. I know CM6/CM7 and MIUI all are very clearly doing this but I was wondering if we could get any kind of documentation like that for the Epic? It doesn't have to include any super detailed coding information other then how to download AOSP, Samsungs required drivers, and build them into a "working" rom of some kind..
The drivers and kernels you guys have been using so far must be available via some kind of git command..
I'd love to be able to compile a ROM just to learn about it lol.
Think a quick and dirty write up for compiling a rom could happen? I think it would really help incoming developers and newbies alike.
+1 on this.
+1 as I would like a good starting point...
Samsung Epic using Team Viper's latest ROM and kernel
I'm glad to see some support for this. I sincerely hope a developer takes this seriously enough to help us out!
I'm answering my own question here
Check it out... it's how to build CM for the epic. Anyone interested in learning the process could probably follow this guide and accomplish it. Took it from the CM post in General.
http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Epic
Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic
mxcoldhit said:
Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic
Click to expand...
Click to collapse
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.
TheDub said:
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.
Click to expand...
Click to collapse
way to go, man. keep us posted...
yogi2010 said:
way to go, man. keep us posted...
Click to expand...
Click to collapse
Steps seem to be broken.. the ./get-rommanager and ./getgooglefiles -v HDPI or whatever both don't work because of broken web links.
Seems this hasn't been updated in a while..
I tried to go on without them following the directions but it doesn't work, says something about the vibrant? idk.. I think the directions would need updating to work properly.. at least the code was fun to look at.
Still hoping a developer can teach us how to compile lets say just 100% AOSP for our phones using our progress so far with the drivers.. i think the drivers need to be their own branch of code so all devs can use them for their own roms.. maybe it's already like this? Idk pretty new to rom compiling.
I have, for the most part, returned from my leave of absence and hopefully this time around I will be able to provide you folks with something a bit more useful.
Admittedly, this was a fairly halfhearted attempt but, hey, it's something to start with. I branched the CM7 for Nook Color source. Part of the compilation process involves running a script (system/device/bn/encore/extract-files.sh) that extracts proprietary libraries (or something?) from stock Nook Color, so I plugged in a rooted N2E instead for this step and ripped the files off of it. Some files were missing from the N2E, so I copied those over from a Nook Color. Here's a list of those files:
Code:
/system/lib/libOMX.TI.720P.Decoder.so
/system/lib/libomap_mm_library_jni.so
/system/etc/powervr.ini
/system/lib/libpvrPVR2D_FLIPWSEGL.so
/system/lib/libusc.so
/system/lib/libpvrPVR2D_FRONTWSEGL.so
/system/lib/libOpenVG.so
/system/lib/libOpenVGU.so
/system/lib/liba2dp.so
/system/lib/hw/alsa.omap3.so
/system/usr/share/alsa/init/hda
/system/usr/share/alsa/init/00main
/system/usr/share/alsa/init/help
/system/usr/share/alsa/init/default
/system/usr/share/alsa/init/info
/system/usr/share/alsa/init/test
Compilation of the franken-nook-color source went without problems.
Unfortunately although unsurprisingly, the produced userland doesn't boot. I'll keep y'all updated with my progress; this is only the very tip of the iceberk.
I have two NST so I can use one for testing your rom if you promise no to brick it very often ;-)
I have a NST that, while the 3/4's of the screen is broken, it still functions fine and I can see anything in the top right quadrant of the screen. It doesn't do anything else for me, so you're welcome to brick it in the name of experimentation.
Thanks for the offering! I am not really in need of anything just yet but should anything come up I will PM y'all.
Anyhow, I tried again but this time excluded all the missing prop files from the build by editing them out of device-vendor-blobs.mk. It still didn't work so that means we're probably going to have to find a way to actually debug it instead of using trial and error like we have been.
Maybe there is like, a serial port or something on this thing.
klausef said:
Maybe there is like, a serial port or something on this thing.
Click to expand...
Click to collapse
Yes there is a UART on the OMAP3621.
Still, it's hard to get any info out of TI since it's an OEM part.
Does anybody have a real pinout?
Actually, unless somebody has a dead Nook that you can pull the processor off it would be hard to trace.
I guess the best bet would be to look for suspicious unused pc lands.
Can you toggle the charge light gpio as a progress indicator?
You don't need anything special.
As long as you can boot a kernel, which you can, you can do all your debugging over adb. Just enable adbd in the ramdisk.
The use for a serial console is for debugging KERNEL failures.
The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.
GabrialDestruir said:
The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.
Click to expand...
Click to collapse
Thanks for the direction, I kind of have been seeing that getting this working isn't as trivial as swapping a few files. I've been asking on some Freenode channels about what exactly makes a kernel 'CyanogenMod compatible.' There are clearly people out there who know exactly what facilities and stuff need to be backported, but such people are hard to find. Do you have any idea where this kind of stuff is documented? The CyanogenMod wiki seems a bit sparse, although maybe I haven't been looking in the right places...
If it is of any interest to anyone:
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html
I've recompiled U-Boot to call our current N2E kernel with a new `console=[...]` parameter, and recompiled the kernel with USB serial support. I figure I should be able to plug this thing into a linux box and just use `minicom` to look at the kernel's output in this manner. I know this probably won't give too much information about userspace issues but at least hopefully it will give some info on why/if/when/where init fails.
It would be nice if a spare UART could be found directly on the board.
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html said:
The USB subsystem is started rather late in the boot process, console messages printed during boot before the USB subsystem is loaded will be lost.
Click to expand...
Click to collapse
I should be more specific, it's not so much you need to make the current kernel CM7 compatible, as it is you need to make it Android Froyo Compatible, which usually involves porting features from the eclair, if you want to get specifics, try talking with people in #nookcolor or #nook-tablet on Freenode. They may be able to help point you in the right directions for porting the kernel.
Waiting for my NST to come from new continent.
Personally, I would start building original kernel source from b&n. When it works and device boots, then I would clone google repository for kernel 2.6.x and would compare its files with the files from original kernel. And then adding needed source files for booting, and needed device drivers.
I doubt I'll have free time and enough knowledge for that.
Sent from my GT-I9000 using XDA
seeing as we now have the uart http://forum.xda-developers.com/showthread.php?t=1702734 i feel its time to make a cm7 port. it would unlimit the device, and bring it into more compatible apps.
How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?
imachine said:
How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?
Click to expand...
Click to collapse
Sorry if you weren't asking me.
I don't write a single line of C code since almost twelve years. I'm a programmer in a very different environment, fact which makes me know that such a port needs a lot of dedication.
In the next weeks I'm gonna be father for the first time and this makes me set completely different goals in my life.
As far as I've understood of cyanogenmod, is that this world is made of brilliant volunteers, some accepting donations, some not. Maybe in the whole cm community, there is somebody with time and experience.
Sent from my GT-I9000 using XDA
I've been considering picking this up as a project, because I'm tired of 2.1, i would like some GB at least I doubt we will see cm9, but cm7 seems doable. I'll have to learn some to do it, but I don't see why it's not outside of reach; now that we have a serial port, and such.
tdcfpp said:
Sorry if you weren't asking me.
Click to expand...
Click to collapse
No problemas, I wasn't. I directed my message at klausef who started this thread, though anyone willing to help out would probably be beneficient from fundraising, were it to start funding a project, instead of a single developer.
If money's a problem, perhaphs starting a kickstarter (or similar) project might help out?
Donating via paypal works as well, but I don't think it's possible to allow public access to account levels in order to motivate the experience of funding, by letting people see how much the project has risen.
i can't wait to get CyanogenMod on my nook! Have you guys discovered anything new?
Cheers!
Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along
imachine said:
Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along
Click to expand...
Click to collapse
Bump. I've got a great use for a NST / N2E application, and the app is currently compiled for Android 2.2 only. I may not be able to get to the source (and may not be able to make it work in 2.1 even if I did!), so a NST with 2.2 would be ideal!
This ROM is in no way suitable for daily use and is only shared so that other fellow developers can take a look and maybe provide fixes to one or multiple things on the "not working" list.
Take it as a very early proof of concept.
ROM DOWNLOAD: http://www.androidfilehost.com/?fid=23501681358554238
What I did to get this far...
1. I took the MI3W miui-germany ROM
2. I unpacked the MI3W's ROM
3. I unpacked the boot.img of the MI3W ROM (zImage, dt.img, ramdisk)
4. I patched the fstab.qcom and init*.rc files to match the Find 7a
5. I unpacked the latest OmniROM for Find7a
6. I unpacked the boot.img of OmniROM (zImage, dt.img, ramdisk)
7. I copied zImage and dt.img from OmniROM's extracted boot.img into MI3W's extracted boot.img
8. I repacked the MI3W boot.img
9. I bundled the MI3W system partition with the modified MI3W boot.img and uploaded it onto the internet for someone else to iron out the remaining bugs
What seems to work...
*) Basic Operation (MIUI apps, status bar, well what you would expect really)
*) Bluetooth
*) Wired Headset / Bluetooth Audio
*) RIL / Mobile Data
*) GPS
What doesn't work... yet...
*) WiFi (there seems to be some issues with wcnss / pronto / prima, this one is bad...)
*) Random Reboots / Blackscreen Glitches (from what kmsg tells me it seems to be related to wcnss, aka. WiFi drivers causing a critical error in kernel every once in a while, fix WiFi and this error will fix itself)
*) Speaker Audio
*) Rotation Sensor (and probably others)
*) Vibration
*) Skyline Notification Light
*) NFC
For pictures check the thread at the oppoforums: http://www.oppoforums.com/threads/rom-miui-port-for-find-7a.17409
Good things always have the obstacles.
You've done your part. And let other(s) help you.
I don't have knowledge about cooking a ROM.
But I think someone can help. @Entropy512, can you look at this one?
If you want mae some cool port, i thikn sense rom is good candidate...
Great work
hey there mrcoldbird,
great work so far...keep it up..will definately help support you on this when it is up and running..i am not a dev but if you need someone to just bug report i am there for you,will keep my eyes n ears peeled on the thread and as soon as it's near ready i will flash and help you anyway i can...thank you for all your hard work so far
Right now we need developers involved in this. We know the countless obvious bugs.
Just have to fix them.
Awesome work. Thanks bird. Any chance you want to try lewa os while you're at it. I personally think it is better. I imagine just how busy you are but just wanted to throw it out there
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
MrColdbird said:
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
Click to expand...
Click to collapse
I updated my post. You should really check out lewa. It has find 5 official support
uppon2 said:
I updated my post. You should really check out lewa. It has find 5 official support
Click to expand...
Click to collapse
no news about this rom
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
ok thanks for answer. i love miui rom. i think it can be the best rom for find 7a
good luck
---------- Post added at 12:23 PM ---------- Previous post was at 12:21 PM ----------
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
if you need help for test rom tell me. i have a lot of time for this.
when i try to install your rom twrp failed. do you know why ?
jazzypit said:
no news about this rom
Click to expand...
Click to collapse
Lewa OS website
YouTube video
uppon2 said:
Lewa OS website
YouTube video
Click to expand...
Click to collapse
no rom for oppo find 7a
do you have a link for test ?
jazzypit said:
no rom for oppo find 7a
do you have a link for test ?
Click to expand...
Click to collapse
No. That is what I'm asking for; a build for lewa for the find 7.
uppon2 said:
No. That is what I'm asking for; a build for lewa for the find 7.
Click to expand...
Click to collapse
Which doesn't belong in this thread. Take it elsewhere.
justin654 said:
Which doesn't belong in this thread. Take it elsewhere.
Click to expand...
Click to collapse
Lewa OS is extremely similar to MIUI and that is why I even bothered to mention it. I know the developer is having some trouble with MIUI so I thought it would be useful and helpful to mention Lewa as it might be a project that will help the development of either or rom.
Please don't take a blunt tone with me (if that's what it was) as it only makes you look arrogant. Taking in to account our post and thanks scores it is quite clear who has contributed in a more positive way towards XDA. On that note; you might also want to thank MrColdbird in the OP for his contribution, which you have not done as of yet but you seem to be poking your nose in to the thread
That is all
Edit* I apologise MrColdbird if my suggestion was unwarranted.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
I am setting up a build environment and will be looking in to it; starting with wifi. I think I might check out lewa as well.
good luck
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
FareedYusoff said:
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
Click to expand...
Click to collapse
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
MrColdbird said:
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
Click to expand...
Click to collapse
Quite fast actually. By the way, I just can wait and see your nice work.
I'm trying to help, but that's all I can do right now. All the best on your effort.
I appriciate your hardwork. :highfive:
In light of the newly-minted LuneOS alpha release, I was wondering if anyone had experience dualbooting webOS on their Galaxy Nexus? I know it's possible to do so with Android-based ROMs, but I want to keep my CM nightlies as a fall-back, especially since the LuneOS is in such an early stage and technically does not officially support the device (they're looking for community support *hinthint devs*). If you do, please drop a note with your experience in this area! Thanks in advance. :good:
drfandroid said:
In light of the newly-minted LuneOS alpha release, I was wondering if anyone had experience dualbooting webOS on their Galaxy Nexus? I know it's possible to do so with Android-based ROMs, but I want to keep my CM nightlies as a fall-back, especially since the LuneOS is in such an early stage and technically does not officially support the device (they're looking for community support *hinthint devs*). If you do, please drop a note with your experience in this area! Thanks in advance. :good:
Click to expand...
Click to collapse
Well,it would be cool,even with sailfish os,that i really love
Anyway for everybody who wants to try webos (LunaOs) http://webos-ports.org/wiki/Maguro_Info
I just saw the news on Engadget and came here to see if anyone was talking about this. I'm going to try this out since my GNex is mainly just sitting in a box now. I miss webOS.
The only thing I wonder about is that I have a Verizon GNex. If I don't use it for calls or anything, does it matter if I flash the Maguro version? I remember I was in the same boat with the Ubuntu phone port but I think I waited for the Toro port. I can't remember.
jsgraphicart said:
I just saw the news on Engadget and came here to see if anyone was talking about this. I'm going to try this out since my GNex is mainly just sitting in a box now. I miss webOS.
The only thing I wonder about is that I have a Verizon GNex. If I don't use it for calls or anything, does it matter if I flash the Maguro version? I remember I was in the same boat with the Ubuntu phone port but I think I waited for the Toro port. I can't remember.
Click to expand...
Click to collapse
Wondering this as well.
they had, and still have the best multitasking on a mobile device i've ever used. it was just so fluid and intuitive. some of their features they incorporated are still ahead of their time today
x000x said:
they had, and still have the best multitasking on a mobile device i've ever used. it was just so fluid and intuitive. some of their features they incorporated are still ahead of their time today
Click to expand...
Click to collapse
Agreed. Has there been any other phone that uses a gesture area like they did? I loved that.
jsgraphicart said:
Agreed. Has there been any other phone that uses a gesture area like they did? I loved that.
Click to expand...
Click to collapse
I looked for a long time, but nothing recent. there was one thing kind of similar, a few years back called 'itching thumb' http://www.xda-developers.com/android/use-itching-thumb-to-multitask-in-android/ but was discontinued long ago.
Yeah, well I just checked the comments on their official release post, and after some helpful replies I can (sadly) announce that there is no dual-boot support. Also, the latest build they have is a couple weeks old, since they no longer have a maintainer for the device The post is here, if any of you want to skim it . So at this point it's either flash a build that's dated, without a fall-back that would come with dual-booting, or wait and see
drfandroid said:
Yeah, well I just checked the comments on their official release post, and after some helpful replies I can (sadly) announce that there is no dual-boot support. Also, the latest build they have is a couple weeks old, since they no longer have a maintainer for the device The post is here, if any of you want to skim it . So at this point it's either flash a build that's dated, without a fall-back that would come with dual-booting, or wait and see
Click to expand...
Click to collapse
There's a Sept. 1st build there. More towards the Center.
http://build.webos-ports.org/luneos-testing/images/maguro/
There's a Sept. 1st build there. More towards the Center.
Click to expand...
Click to collapse
Yes, I just noticed haha my bad. I was just paraphrasing a comment off of the post I linked to. Shame there's only dual-booting available on the Touchpad (for now at least). I'll probably wait until the next stable release or so before diving in.
jsgraphicart said:
I just saw the news on Engadget and came here to see if anyone was talking about this. I'm going to try this out since my GNex is mainly just sitting in a box now. I miss webOS.
The only thing I wonder about is that I have a Verizon GNex. If I don't use it for calls or anything, does it matter if I flash the Maguro version? I remember I was in the same boat with the Ubuntu phone port but I think I waited for the Toro port. I can't remember.
Click to expand...
Click to collapse
im flashing it on a toroplus right now, gonna let you guys know how it goes when it finishes. on a related note, make sure to wipe /system before you flash, because the updater script doesnt do that. i had cm11 installed on there before and forgot to do it, so im reflashing clean now.
also, it looks like at least some of the android file system is retained, so that means we may be able to get data working by pulling libs from a 4.2.2 rom. dont quote me on that, ill try it and see what happens when i get this thing to boot. I pulled apart the boot.img and nothing seems to be stopping us there either from what I can tell.
edit: as much as i wish this worked, dont waste time flashing it if your not a maguro device. doesnt boot on toroplus, prolly wont boot on toro either.
whoshotjr2006 said:
im flashing it on a toroplus right now, gonna let you guys know how it goes when it finishes. on a related note, make sure to wipe /system before you flash, because the updater script doesnt do that. i had cm11 installed on there before and forgot to do it, so im reflashing clean now.
also, it looks like at least some of the android file system is retained, so that means we may be able to get data working by pulling libs from a 4.2.2 rom. dont quote me on that, ill try it and see what happens when i get this thing to boot. I pulled apart the boot.img and nothing seems to be stopping us there either from what I can tell.
edit: as much as i wish this worked, dont waste time flashing it if your not a maguro device. doesnt boot on toroplus, prolly wont boot on toro either.
Click to expand...
Click to collapse
That's too bad. What are you getting when it tries to boot? Have you let it sit for a while before coming to that conclusion? Maybe it doesn't have any sort of booting indication.
Update: I ended up going for it, and flashed the stable build onto my maguro. Worked, but none of the apps would open again after I had closed them for some reason (If I wanted to open Preware 2 again, I had to reboot the device...). The dev build wouldn't boot at all after flashing, so I'm running on the August 10th stable build.
jsgraphicart said:
That's too bad. What are you getting when it tries to boot? Have you let it sit for a while before coming to that conclusion? Maybe it doesn't have any sort of booting indication.
Click to expand...
Click to collapse
sorry it took so long to reply, but yep i waited 10 minutes for adb or any indication that it was going to boot. after reading drfandroid's post about getting august 10ths build to boot and not being able to get the newest nightly to boot, im thinking thats my problem too. ill try to use the one mentioned and see if i get different results.
whoshotjr2006 said:
sorry it took so long to reply, but yep i waited 10 minutes for adb or any indication that it was going to boot. after reading drfandroid's post about getting august 10ths build to boot and not being able to get the newest nightly to boot, im thinking thats my problem too. ill try to use the one mentioned and see if i get different results.
Click to expand...
Click to collapse
Well that sucks. Hopefully someone picks up development for this device. I'd like to try it out eventually. I have an HP Touchpad but it has Android on it as well. I havent looked into it yet but installing this might need a full wipe. I don't want to go through the hassel of starting all over again. lol
jsgraphicart said:
Well that sucks. Hopefully someone picks up development for this device. I'd like to try it out eventually. I have an HP Touchpad but it has Android on it as well. I havent looked into it yet but installing this might need a full wipe. I don't want to go through the hassel of starting all over again. lol
Click to expand...
Click to collapse
You're right, flashing it on your nexus pretty much requires a full wipe lol. The Gnex doesn't have dual-boot capability for LuneOS (yet!! ). I asked in the comments of the announcement post. Fingers crossed for that, though! Really hoping a dev steps out and continues the project, even if it's just on the side.
whoshotjr2006 said:
sorry it took so long to reply, but yep i waited 10 minutes for adb or any indication that it was going to boot. after reading drfandroid's post about getting august 10ths build to boot and not being able to get the newest nightly to boot, im thinking thats my problem too. ill try to use the one mentioned and see if i get different results.
Click to expand...
Click to collapse
Any luck with the August 10th build? My build can't activate developer options (Settings--> Developer Options, flicked the switch, still says "Developer mode is disabled"-->entered Konami Code into search, tapped on the dev mode result, nothing happened), so I can't activate USB Debugging or anything like that. On top of that, the phone takes forever to even boot into the Google screen, and I can't get into Recovery or Fastboot mode. In essence, even if I wanted to re-attempt to flash the nightly or go back to Android, I can't. I was hoping to go try the PA 4.6 Beta on my Gnex, so I was a bit gutted. Any ideas??
drfandroid said:
Any luck with the August 10th build? My build can't activate developer options (Settings--> Developer Options, flicked the switch, still says "Developer mode is disabled"-->entered Konami Code into search, tapped on the dev mode result, nothing happened), so I can't activate USB Debugging or anything like that. On top of that, the phone takes forever to even boot into the Google screen, and I can't get into Recovery or Fastboot mode. In essence, even if I wanted to re-attempt to flash the nightly or go back to Android, I can't. I was hoping to go try the PA 4.6 Beta on my Gnex, so I was a bit gutted. Any ideas??
Click to expand...
Click to collapse
yep no luck for me here, mine just wont boot into it at all. I can still access fastboot though, holding both volume buttons from and power from completely off doesnt get you into fastboot? if your volume button hardware has gone bad, i know you can buy new on ebay for cheap, might have to do that. sorry to hear about your problem, and I hope you get it fixed somehow.
Mod edit: TG link removed as per XDA's TG Chat Rules.
(TG link and home page was removed I can only see in their rules the TG link all good so adding back the home page to the home page)
I started project rooted to provide pre rooted roms to people. I'm looking for someone to help with pixel 6 pro. If anyone is interested please let me know. All it really is is patching operating systems, recompiling then, and sharing them.
I think that there is no value at all in this project. All anyone needs to do is run the original boot.img through magisk before they write it to the boot partition and the job is done.
In addition, if anyone was inclined to use 3rd party hosted pre-rooted (or not) boot images, I would VERY STRONGLY recommend that they DO NOT. This is simply because it opens them up to whatever other undisclosed changes happen to have been added to it.
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Jacobh1245 said:
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Click to expand...
Click to collapse
And I can absolutely assure you that I am a Nigerian Prince, and if you direct deposit $500 into my bank acount, I will turn it into $5,000,000.
Gytole said:
And I can absolutely assure you that I am a Nigerian Prince, and if you direct deposit $500 into my bank acount, I will turn it into $5,000,000.
Click to expand...
Click to collapse
Lol, I get it. I'm not well known or trusted yet as this is not my first project but first I've tried to get out there as much as I am. Again I'll reiterate that you don't have to use it if you don't trust it all my work is posted even the as basic as it is website is open source on GitHub. If you have any genuine feedback for me I'd love to hear it. Constructive feedback on how to get started and trusted wouldn't be so bad. Thanks for your opinion though, it's good to hear what a community thinks of new projects/ideas
Jacobh1245 said:
Lol, I get it. I'm not well known or trusted yet as this is not my first project but first I've tried to get out there as much as I am. Again I'll reiterate that you don't have to use it if you don't trust it all my work is posted even the as basic as it is website is open source on GitHub. If you have any genuine feedback for me I'd love to hear it. Constructive feedback on how to get started and trusted wouldn't be so bad. Thanks for your opinion though, it's good to hear what a community thinks of new projects/ideas
Click to expand...
Click to collapse
Thanks for being a great sport
Is there benefit in having it pre rooted? Perhaps easier to pass the safety checks for banking apps?
TrustAugustus said:
Is there benefit in having it pre rooted? Perhaps easier to pass the safety checks for banking apps?
Click to expand...
Click to collapse
Yes I have had better success with safetynet since doing this they don't always work out like that but for the most part it's been better. As far as pre-rooted with pixel devices it's not too hard to do, just time consuming. I'm going to build a set of instructions tonight for my website as to how to do so yourself for those who would rather do it manually
That sounds great. I'm looking forward to the project.
Back... like 10 years ago roms came pre rooted as well
TrustAugustus said:
That sounds great. I'm looking forward to the project.
Back... like 10 years ago roms came pre rooted as well
Click to expand...
Click to collapse
I remember that was one of the best things ever. That's just one of my reasons I wanted to do this. THANKS for the support!!!
Jacobh1245 said:
I remember that was one of the best things ever. That's just one of my reasons I wanted to do this. THANKS for the support!!!
Click to expand...
Click to collapse
We understand, just with the new safeties built into to hardware anymore it can comicate things for some people. I am not saying prerooted is WRONG, it can just cause problems. It's not you. Lol
Yeah, some devices can, some won't. I am alware of these but also understand the risk is minimal and unlikely to be president. Reality with anything like this even down to the roms themselves have so many variables that could cause problems. Which I why I have taken the extra steps to test that I have a solidly rooted Rom
Jacobh1245 said:
I started project rooted to provide pre rooted roms to people. I'm looking for someone to help with pixel 6 pro. If anyone is interested please let me know. All it really is is patching operating systems, recompiling then, and sharing them.
Click to expand...
Click to collapse
For anyone who might want to know this. I have a very poor excuse for a guide on making pre rooted roms on my page now if you have a pixel device it does work. It was quickly put together and I WILL update it SOON and will add screenshots to help as well as fine tuning the wording.
What would be nice is to have the installation routinely root the boot.img if the system is pre-rooted, like Lineage 18 does on my 1+7pro.
Jacobh1245 said:
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Click to expand...
Click to collapse
Its not a question of you having malicious intent. Its a question of best practices for security. Other people who may be more or less trustworthy than you may have similar projects (and in fact, I remember another thread with this exact purpose), and trusting those may be quite dangerous.
But more to the point, and WITHOUT putting your trustworthiness or honor in question, how can anybody know whether you are *actually* trustworthy or just someone claiming (falsely) to be?
And since the process of running it through Magisk is so absurdly trivial, what advantage does this provide to users to compensate them for the risk?
Advantages: nil
Risks: elevated
Rational choice: avoid.
96carboard said:
Its not a question of you having malicious intent. Its a question of best practices for security. Other people who may be more or less trustworthy than you may have similar projects (and in fact, I remember another thread with this exact purpose), and trusting those may be quite dangerous.
But more to the point, and WITHOUT putting your trustworthiness or honor in question, how can anybody know whether you are *actually* trustworthy or just someone claiming (falsely) to be?
And since the process of running it through Magisk is so absurdly trivial, what advantage does this provide to users to compensate them for the risk?
Advantages: nil
Risks: elevated
Rational choice: avoid.
Click to expand...
Click to collapse
It does a few things, it in many cases seems to help with safetynet being easier to pass( not always some roms are more stubborn). It provides a convinent place where everything is at. All my stuff is open source and downloadable so you may check whatever you want. Though I don't have the source code to the roms since I'm not building them. And I put links to the roms group chat and instructions as to how(for pixel devices) to make a pre-rooted rom yourself. So if you don't trust it but want it I give how to and where to get the files to do so some also fear that things may not work as mentioned above can happen but is very minimal especially since I test before releasing.
Jacobh1245 said:
It does a few things, it in many cases seems to help with safetynet being easier to pass( not always some roms are more stubborn). It provides a convinent place where everything is at. All my stuff is open source and downloadable so you may check whatever you want. Though I don't have the source code to the roms since I'm not building them. And I put links to the roms group chat and instructions as to how(for pixel devices) to make a pre-rooted rom yourself. So if you don't trust it but want it I give how to and where to get the files to do so some also fear that things may not work as mentioned above can happen but is very minimal especially since I test before releasing.
Click to expand...
Click to collapse
What version of Magisk do you intend to use? Because on at least 2 or 3 occasions due to Google changing things, Canary has been needed. On the other hand, there have also been occasions where Canary broke some things and Stable was needed.
Because the Pixel 6 series seems to be "often" affected by changes made by Google in their monthly updates, as well as Magisk itself, it seems that pre-rooting a rom on the Pixel 6 series "may" cause some unintended problems.
It's been quite the cat and mouse game when it comes to the Pixel 6 series and rooting in terms of these changes, and not in terms of just rooting itself, but other things like custom kernels, etc..
Lughnasadh said:
What version of Magisk do you intend to use? Because on at least 2 or 3 occasions due to Google changing things, Canary has been needed. On the other hand, there have also been occasions where Canary broke some things and Stable was needed.
Because the Pixel 6 series seems to be "often" affected by changes made by Google in their monthly updates, as well as Magisk itself, it seems that pre-rooting a rom on the Pixel 6 series "may" cause some unintended problems.
It's been quite the cat and mouse game when it comes to the Pixel 6 series and rooting in terms of these changes, and not in terms of just rooting itself, but other things like custom kernels, etc..
Click to expand...
Click to collapse
Currently I've been using v25.0 that is one thing I test too and check with others about. So far 25.0 is working great with the minor detail of having to download the magisk apk and install rather then the greyed out icon to "update" but it still works exactly the same and I have not experienced anything broken so far
Jacobh1245 said:
Currently I've been using v25.0 that is one thing I test too and check with others about. So far 25.0 is working great with the minor detail of having to download the magisk apk and install rather then the greyed out icon to "update" but it still works exactly the same and I have not experienced anything broken so far
Click to expand...
Click to collapse
Yes, but there have been occasions where after a monthly update a Canary version was needed (e.g. December update when Google moved its fstab to /system/etc.) and John had to update Magisk and push a Canary version before people could actually boot a rooted boot image.
And I'm curious if you closely follow the issues, PRs and commits in the Magisk Github? For example, Beta 25.0 has changed (actually changed with Canary 24303 I believe) so that custom kernels will no longer boot unless verity and verification are disabled or if the kernel uses the latest AK3 which patches vendor_dlkm.img and vbmeta.img, or if the kernel patches them itself.
My point is there could be some unintended consequences for people who may not be aware of any current issues unless they are made aware of them before flashing a pre-rooted rom.
Anyway, if people find this useful then good for them and good for you.
Lughnasadh said:
Yes, but there have been occasions where after a monthly update a Canary version was needed (e.g. December update when Google moved its fstab to /system/etc.) and John had to update Magisk and push a Canary version before people could actually boot a rooted boot image.
And I'm curious if you closely follow the issues, PRs and commits in the Magisk Github? For example, Beta 25.0 has changed (actually changed with Canary 24303 I believe) so that custom kernels will no longer boot unless verity and verification are disabled or if the kernel uses the latest AK3 which patches vendor_dlkm.img and vbmeta.img, or if the kernel patches them itself.
My point is there could be some unintended consequences for people who may not be aware of any current issues unless they are made aware of them before flashing a pre-rooted rom.
Anyway, if people find this useful then good for them and good for you.
Click to expand...
Click to collapse
I which case testing would show that plus I'm usually pretty good at keeping up with that kind of thing. It is a valid concern but since the versions I release are going to have the correct version for them I will do the same for each rom indevidually as need to make sure they will work properly. Whenever a new version is released. That too means if you are on the same rom and dirty flash to the next one magisk will prompt you to update the app(has been tested too)