Related
Hello I was just wondering if it's even possible to port over MIUI to the D2 as stated in the below thread:
http://forum.xda-developers.com/showthread.php?t=994081
I was reading up on it and I thought the Moto D2 had a locked bootloader and something called eFuse would make the D2 unusable if you changed the bootloader software/kernel and MIUI uses a custom kernel, so yeah I was just wondering if this is even possible
Not to be rude, but shouldn't you be posting the above in the exact thread that you referenced?
-Gilgamesh- said:
Not to be rude, but shouldn't you be posting the above in the exact thread that you referenced?
Click to expand...
Click to collapse
Causeeee I can't post in android development cause I'm new to these forums, You need have like 10 posts or something
We don't know whether it's possible to get MIUI working on Droid 2. From what I can tell, no one has actually gotten the ROM to boot. Someone just sort of put together a ROM that might hypothetically boot (since the hardware is relatively similar to the OG Droid, which runs MIUI). However, as the developer doesn't have a D2 (or any similar phone), it's going to be kind of hard to get it working.
I asked about the kernel issues in that thread, but I don't think the person who posted the ROM has any experience with bypassing eFuse (meaning that the ROM won't work unless it can be run on the stock kernel). There is some exploit called 2nd-init that was used to hijack the Milestone, but I haven't heard of anyone getting it to work on the Droid 2.
Overall, seems like a longshot. But maybe someone can pull it off...
You should've read a bit more in the thread
Both me and the developer are working together on the 2nd_init hack lol.
ljbaumer said:
You should've read a bit more in the thread
Both me and the developer are working together on the 2nd_init hack lol.
Click to expand...
Click to collapse
Super hyped about this MIUI.
.hopefully all goes well
Count me in with a donation when u guys get it up n working!
Sent from my DROID2 using XDA Premium App
ljbaumer said:
You should've read a bit more in the thread
Both me and the developer are working together on the 2nd_init hack lol.
Click to expand...
Click to collapse
I read the entire thread. It appears that all you have accomplished through this effort is bricking your phone.
With Fission, Angdroid didn't report anything until he had a proof of concept working (a ROM that booted).
From what I can tell, these guys don't really seem to know much about how to get this to work. Hopefully they will figure it out, but it's definitely going to take a working D2 and some significant knowledge about ROM development on the D2 (which neither of these guys appear to have). I would recommend staying away from it until they at least can report that it's booting on the D2...
I have the new 2.6.35 kernel that gnarlyc was working on working on my eris, I am going to post the link to download after I test it on a few of the other roms. I will release the new kernel in a couple days just wanted to let you all know
Thanks gnarlyc http://forum.xda-developers.com/showthread.php?t=992323
for starting this greate WORK!
mjgdroid said:
I have the new 2.6.35 kernel that gnarlyc was working on working on my eris, I am going to post the link to download after I test it on a few of the other roms. I will release the new kernel in a couple days just wanted to let you all know
Thanks gnarlyc http://forum.xda-developers.com/showthread.php?t=992323
for starting this greate WORK!
Click to expand...
Click to collapse
Well, no real need to thank me. I just start projects and hopefully someone else comes along and finishes them! Great job. Thank you. I look forward to flashing this on my kid's Eris.
Oh sure, now you tell me
What are the differences between the old kernel and this one. Also will this be okay to flash on GSB?
Sent from my ERIS using XDA App
mjgdroid said:
I have the new 2.6.35 kernel that gnarlyc was working on working on my eris, I am going to post the link to download after I test it on a few of the other roms. I will release the new kernel in a couple days just wanted to let you all know
Thanks gnarlyc http://forum.xda-developers.com/showthread.php?t=992323
for starting this greate WORK!
Click to expand...
Click to collapse
Congrats!
Is this based on the recent HeroC/DesireC sources, or the older s0be based sources?
Are the updates on github or some other repository site?
jaybob413 said:
Congrats!
Is this based on the recent HeroC/DesireC sources, or the older s0be based sources?
Are the updates on github or some other repository site?
Click to expand...
Click to collapse
Yeah, me too I had been working on the breber github source and finally got a bootable ERIS that I could adb into and captured a dmesg as well. Only thing lacking (small issue), is that none of the buttons worked I had an idea on a fix but lost my dev box and am waiting on a replacement MB to continue.
Question is, how different is the source tree for this kernel from the breber github source? When I used the breber source, I did change many kernel options to build many items as modules (ipv6 etc...) I've used the stock CM7 as the base w/ many mods for our older phones, and was able to reduce the size of the kernel image fairly significantly. Bootup was a bit quicker, but main idea was to remove some options that are rarely used, but still make them available as modules.
I've not tested this kernel yet, but I had to make a lot of mods to the defconfig etc... to get breber to work. 2.6.35 gives us some nice features, such as auto memory compaction / defragmentation etc... In the short time I was able to use it, it appeared to run better than the .29 we've all been using.
has it been a few days yet?
theboo7 said:
has it been a few days yet?
Click to expand...
Click to collapse
Yes, finally I just got it up and running end of last week and have been playing catch-up. I use this box as a mailserver for my domain, so it spent the first 10 hours processing over 49000 messages.
Funny timing though, just compiled .35 and was getting ready to flash it. At this point, I have no idea where I left off Maybe I'll smoke the Eris next....
as long as we get a download link soon
I was hoping we might hear some updates for the people working on this...
It would be a big help if those who have gotten it to boot would post their source so others can help get this to a stable point without having to repeat work. I'd like to see Eris development stay alive even as many, including myself, have moved on to more powerful phones.
MongooseHelix said:
I was hoping we might hear some updates for the people working on this...
It would be a big help if those who have gotten it to boot would post their source so others can help get this to a stable point without having to repeat work. I'd like to see Eris development stay alive even as many, including myself, have moved on to more powerful phones.
Click to expand...
Click to collapse
sounds good to me. I do have my box up and running, just haven't had much time to mess with it. somewhere along the the line, I screwed up my Conf, but I'll get it. It boots, but I've messed up the mtd enumeration, so no init gets started.
Just as an fyi, I'm using breber's github source with the arm 4.4.3 eabi.
Well, the good news is, I'm running 2.6.35 now. But.... the bad news is that it's on a new Moto Razr. However, I'll still be tinkering with the Eris in my spare time.
I've rooted the Razr, but I'll tell you. Getting recovery on it's a booger. Also, the battery is sealed in (I'm sure the 2 small screws at the top allow a lift out and disconnect). But, kinda got nervous for a sec when I tried to boot into recovery and got nowhere with no easy way to pull the batt. Overall, liking the phone a lot.
Now.... If only I can dig up my working config. I have a cloud based backup system that versions stuff. Need to go through and see if I've got something there.
sracer9 said:
Well, the good news is, I'm running 2.6.35 now. But.... the bad news is that it's on a new Moto Razr. However, I'll still be tinkering with the Eris in my spare time.
I've rooted the Razr, but I'll tell you. Getting recovery on it's a booger. Also, the battery is sealed in (I'm sure the 2 small screws at the top allow a lift out and disconnect). But, kinda got nervous for a sec when I tried to boot into recovery and got nowhere with no easy way to pull the batt. Overall, liking the phone a lot.
Now.... If only I can dig up my working config. I have a cloud based backup system that versions stuff. Need to go through and see if I've got something there.
Click to expand...
Click to collapse
Having a current generation phone is quite a change. I am enjoying my gnex a lot and since it doesn't need much modification, I still get to spend a good bit of my dev time with the eris .
Maybe we can talk workshed into messing with this .35 kernel again when you find that config...or he might be burnt out for awhile on the frustrations that are the kernel porting and the tbolt as a whole.
Hi everyone,
as the LG G2 is produced by the same manufacturer (LG) as the Nexus 5 and has the same chipset (despite some minor differences e.g. Battery, Display,...), I have been wondering if there is a way to port the Kali-Linux Android ROM (Nethunter) to work with the LG G2.
LINK: http://http://www.kali.org/kali-linux-nethunter/
LINK:http://http://www.offensive-security.com/kali-linux-nethunter-download/
The mere existence of a MAHDI ROM port from N5 to G2 makes me think, that it should be possible.
I would also be quite keen on getting involved in such an effort but I am not very fluent in porting Android ROMS.
I have basic coding skills and am not afraid of learning new stuff so I'd really appreciate if one of the Android-Gurus would kind of orchestrate the whole thing.
Thanks for your attention and good bye.
mick
That would be really awesome!
Yeah, but it seems it will remain a dream, as the members to whom this is addressed to, obviously do not read the Q&A Forums. Why should they anyway?
The problem is, if I open a development-thread it's not unlikely, that someone will be playing the wrong-forum-double-post-card.
mickmattes said:
Yeah, but it seems it will remain a dream, as the members to whom this is addressed to, obviously do not read the Q&A Forums. Why should they anyway?
The problem is, if I open a development-thread it's not unlikely, that someone will be playing the wrong-forum-double-post-card.
Click to expand...
Click to collapse
To be honest, I'd say look at Dr87's github. He ported Mahdi over... Though really I don't think that the rom itself is "ported" so much as the drivers/kernel/ramdisk need to be modified to work with the code on this device.
I would suggest starting by getting the rom source you want. Then setting up the device in the source using the devices/kernel/vendor files he made. You'll likely get errors during the build, but it would give you a starting point.
There are many, many guides out there on porting roms to new devices. Read through some of those if you haven't and it might help to steer you in the right direction.
Yoinx said:
To be honest, I'd say look at Dr87's github. He ported Mahdi over... Though really I don't think that the rom itself is "ported" so much as the drivers/kernel/ramdisk need to be modified to work with the code on this device.
Click to expand...
Click to collapse
Do you mean, that it is not "ported" due to the fact that the chipsets of both devices are the same?
I would suggest starting by getting the rom source you want. Then setting up the device in the source using the devices/kernel/vendor files he made. You'll likely get errors during the build, but it would give you a starting point.
Click to expand...
Click to collapse
Yeah, I'm going to try that. Sounds promising.
There are many, many guides out there on porting roms to new devices. Read through some of those if you haven't and it might help to steer you in the right direction.
Click to expand...
Click to collapse
I don't want to look lazy, but as you pointed out, there are many guides out there. Some are old, most are really old. Can you name one or two particularly good ones?
Anyway, thanks for your suggestions...it's going to be a long night.
No, I mean the rom source doesn't seem to need heavy changing typically. Usually the changes to the rom code at large is pretty minimal. Most of the time you need to tweak the device files to work with the rom (caf changes and such).
To be honest, I'd point you toward the Cyanogenmod guides... they have some custom commands but their guide would probably be the most up to date of any.
That should be correct. They have a FAQ at the Nethunter site where they say, that one could use the rom by building a rootfs. This would imply, however, that one could not use the features that come with a dedicated kernel.
So, yes, the rom part should not be the problem. The kernel part will be problematic. I think I'll send a message to dr87, perhaps he has some advice,too.
Just to make it clear, I bought this device some days ago and I want to be quite sure that my messing around with it will not brick or damage it somehow.
Ok. So I'll have a look at the CM-Guides.
I just read about this for the nexus 5 and googled for the lg g2 and came across this thread. I would love to get this working on my g2, gonna do some more googling and see if I can find anything else going on.
twist said:
I just read about this for the nexus 5 and googled for the lg g2 and came across this thread. I would love to get this working on my g2, gonna do some more googling and see if I can find anything else going on.
Click to expand...
Click to collapse
Hello
Is it possible to install NetHunter a device is jailbroken.
My phone Is LG G2 ....
.........0x0........
Would be freaking awesome!!
I am learning how to port Ubuntu, at the moment. Once I learn that, I can attempt to do it with Kali. Sound good? It may a take a bit, but better than no one trying at all.
SamsungIsBetterThanApple said:
I am learning how to port Ubuntu, at the moment. Once I learn that, I can attempt to do it with Kali. Sound good? It may a take a bit, but better than no one trying at all.
Click to expand...
Click to collapse
so, its been 6 years... Did u do it?
Hey everyone,
I'm actually genuinely curious about this, I'm looking to potentially start developing for this phone but in order to do this I need to know the state of affairs and what exactly we have at the moment and don't. I see we can unlock bootloader and root....but the techniques used to do so seem very......primitive.... to say the least, and quite compressed for a newbie.
What exactly is the issue for lack of ROM development, what are we missing? Is it possible to make a tool to help with bootloader unlock and root, and if it is why hasn't it happened yet? I see we have TWRP but what else do we need?
Like I said I'm genuinely curious and not trying to start a flame war, this is for productive conversation and discussion. I come from a Nexus 6 so the lack of development is something I'm aware of before I bought this phone, but I would really like it to thrive as it's a great phone. As a disclaimer I haven't rooted or unlocked my phone yet, I just got it, and as much as I am very experienced in this field, I'm not yet ready to go through the process if it's not worth it.
Thank you.
A full image from ZTE is what we are waiting on (last I heard)
tele_jas said:
A full image from ZTE is what we are waiting on (last I heard)
Click to expand...
Click to collapse
The full image is not a problem. All binary files can be extracted from partition backups.
If you check https://github.com/hax-on you will see progress. As an developer you will especially see what's missing. The main issue is audio vendor blobs getting to work without help of ZTE devs.
It requires reverse engineering. (IDA Pro, radar2).
Not everyone knows how to RE. That is why the community is pushing ZTE for help or release the sources for the required blobs.
Additionally, I am running into a back order issue so maybe more development will occur when next batch hits the shelves in a few weeks? But op brings up a good question.
Sent from my Pixel using XDA-Developers mobile app
canezila said:
Additionally, I am running into a back order issue so maybe more development will occur when next batch hits the shelves in a few weeks? But op brings up a good question.
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Jet.com has it shipping Monday with 30$ off, free shipping, and no tax
Have faith - once they get CM13 going the flood gates will open.
Anything that can be done by us that don't have the experience but want to contribute?
S8ntsHaz3 said:
Anything that can be done by us that don't have the experience but want to contribute?
Click to expand...
Click to collapse
For now only patients. And once CM becomes available testing and reporting bugs using logs and pastebin.
Anyone know what the chances of AOSPA making an appearance on the V20?
AOSPA came and went. No longer under development. Unless somebody else takes over the project, not likely it will resurface.
hawkeye29 said:
AOSPA came and went. No longer under development. Unless somebody else takes over the project, not likely it will resurface.
Click to expand...
Click to collapse
Darn. i wonder how hard it would be to attempt a build of this ROM for a first timer
truf28 said:
Darn. i wonder how hard it would be to attempt a build of this ROM for a first timer
Click to expand...
Click to collapse
Pretty hard for a beginner. It was pretty hard for me to build it too and I'm not a beginner.
This device is simply phenomenal but LG simply become like Samsung but LG not see their north yet lack of updates, bootlops, failure hardware etc same applies for others but LG no learn can`t imagine this device LG v20 GPE simply a beast plus stock camera on AOSP ROM!!!!!
Yes I know only was a dream
hawkeye29 said:
AOSPA came and went. No longer under development. Unless somebody else takes over the project, not likely it will resurface.
Click to expand...
Click to collapse
Do you have a link to that ROM? Also why did they stop development?
Sent from my LG V20 using XDA Labs
I wish it was. It's my favorite rom.
BROKEN1981 said:
Do you have a link to that ROM? Also why did they stop development?
Click to expand...
Click to collapse
Ill see if I still have it. Dude moved onto the note 8.
Damn, thought I was getting a christmas gift. I wanted this for our phone too but it seems any other rom other than stock has some issues with the kernel.
https://github.com/PA-CAF
This is similar to AOSPA legacy as stated by the maintainer of the source I've built on it for the oneplus2 which which dident get offical N support its easier to build than regular AOSPA but the way lineage separated trees has complicated things... I'm going to try to get it going but I haven't really dealt with this conversion stuff before
Update while I've gotten it to build, a while back actually, it fails to boot something in the dalvik machine setting up boot it fails to register a method in an other file the full log found here:
https://hastebin.com/upeceyuhel.pl
I'm more of a kernel guy (pretty newish at it too ) so I have no idea how to fix this, so please chime in if you know something but ill ask for help in the building thread see if they can help. Just wanted to let you guys know some progress is being done on it. Im in classes so not much free time left over and with Oreo on the horizon for lineage, so this PA-CAF Nougat build feels a bit out of place especially since i stripped out a lot for it to build, I don't think that may affect the dalvik machine mostly ambient, double tap to wake, and a few customization features......
With all that said can I a show of hands (or thanks so the thread is kept clean) who is interested in this I have us996 so that will come first if I get it done (don't think it will be that hard as opposed to fixing the gestures and ambient displays stuffs) still no promises I'm used to building for myself with most the work is already done and me only adding a few things, but I wouldn't mind a challenge.
Dr_DjEnder said:
Update while I've gotten it to build, a while back actually, it fails to boot something in the dalvik machine setting up boot it fails to register a method in an other file the full log found here:
https://hastebin.com/upeceyuhel.pl
I'm more of a kernel guy (pretty newish at it too ) so I have no idea how to fix this, so please chime in if you know something but ill ask for help in the building thread see if they can help. Just wanted to let you guys know some progress is being done on it. Im in classes so not much free time left over and with Oreo on the horizon for lineage, so this PA-CAF Nougat build feels a bit out of place especially since i stripped out a lot for it to build, I don't think that may affect the dalvik machine mostly ambient, double tap to wake, and a few customization features......
With all that said can I a show of hands (or thanks so the thread is kept clean) who is interested in this I have us996 so that will come first if I get it done (don't think it will be that hard as opposed to fixing the gestures and ambient displays stuffs) still no promises I'm used to building for myself with most the work is already done and me only adding a few things, but I wouldn't mind a challenge.
Click to expand...
Click to collapse
Is this still being worked on? I'd love to see AOSPA on my V20!
Grillac said:
Is this still being worked on? I'd love to see AOSPA on my V20!
Click to expand...
Click to collapse
Since the last post was Jan 2018 doubt it
Sent from my LG-H910 using XDA Labs
Grillac said:
Is this still being worked on? I'd love to see AOSPA on my V20!
Click to expand...
Click to collapse
no I would work on it again but I've stepped back from compiling for a bit and it was also during the time oreo was on the horizon for the v20 so getting nougat AOSPA working felt like a waste of time
now pie is on the horizon and would like to see how it's going with PA-CAF on pie but lineage pie tree would need to become available for our device as idk how bring up to a new android version works