Related
This is now obsolete, Erasmux has ported the hardware (some of it) which i am havign trouble doing.I dont intend to steal his work so please use his!
http://forum.xda-developers.com/showthread.php?t=1026699
To revert MTD and flash back please see HERE
Issues and Changelog
Changelog..
First version..
Issues..
WIFI
MICROPHONE
CAMERA
NETWORK DATA - A little fishy
ROTATE - Think ive fixed in next version
MARKET - Loops Crashing?
BROWSER - Loops Crashing?
Well no bug or something, but I've added the rom on my mirror . here
Good luck with this. It's great to see that there are still some people who believe in a 2.2 sense rom for the hero
when the rom is tested a bit i will add it to my rom database
dude, you built a rom! congrats on being so bleeding edge bonesy!
I'm impressed with your guts
um, don't take this the wrong way, but I'm not about to try it just yet... ;-) It's just because I need my phone and it's camera etc for daily use. I have faith in you - you've been messing with this stuff longer than I have probably dude and your flashing instructions are VERY clear which is comforting.
I'm really impressed that you persevered like this though man!
cheers
Don
Like I said gonna give it a try when at work. Great work man. And ill report back in here all my findings.
Like don said. Great to see this still happening to the hero.
Sent from my HTC Hero using Tapatalk
What is working? What not?
krygo said:
What is working? What not?
Click to expand...
Click to collapse
see 2nd post,Lots working but lots not,was up untill 4am trying to fix some,as soon as i get mic and / or wifi going ill release 0.2
hi there!
I'm a bit puzzled how to revert to pre-MTD changes state.
I am willing to test this rom, but I would like to have an option to nandroid back without much of a problem. I read through the topic bonesy linked, but haven't found a simple answer/solution.
I hope I could help some more, at least confirm bugs or something.
Cheers!
brat.haneq
EDIT:
Is it as simple, as flashing "remove" zip?
Nearly, you will need to re-flash recovery too, Through fastboot..
Im struggling at the moment as i have 2 different builds on 2 different computers.As soon as i can get to my work computer i can carry on with it all
Call me stupid but is CustomMTD really necessary ? This rom can't work as all roms do? I've flashed it without MTD method and I am stuck on first splash-screen (mine says HERO on black background).
BTW ty for working on a Froyo Sense port for Hero GSM
omg Ninpo is involved, <3 him (nogay)
I will try when it's a little bit better ^^ and can be used for 1 day at school
good work man!
Wupper said:
Well no bug or something, but I've added the rom on my mirror . here
Click to expand...
Click to collapse
offtopic:
omg you again XD hahahaha
I will not flash this yet but still I want to say thanks to all devs for working on froyo sense
@bonesy. how are you hoping the development of this ROM will be community driven? Would you like us to simply try it and report bugs (no different to most other ROMS I think) or would you like us to get down and dirty with code wherever possible?
Im just a regular user but i'd like to help with the development of this rom. if i was pointed in the right direction I would even be willing to learn about how to develop this rom!
anyway good effort for starting on this (I expect, long) journey
f_padia said:
@bonesy. how are you hoping the development of this ROM will be community driven? Would you like us to simply try it and report bugs (no different to most other ROMS I think) or would you like us to get down and dirty with code wherever possible?
Im just a regular user but i'd like to help with the development of this rom. if i was pointed in the right direction I would even be willing to learn about how to develop this rom!
anyway good effort for starting on this (I expect, long) journey
Click to expand...
Click to collapse
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
Is custom MTD really necessary?
Click to expand...
Click to collapse
In a word..Yes (its over 200mb in size just on /system partition) hopeing eventually it wont need it
bonesy said:
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
Click to expand...
Click to collapse
I couldnt agree more! well if you do find anything useful I will help anyway I can
bonesy said:
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
In a word..Yes (its over 200mb in size just on /system partition) hopeing eventually it wont need it
Click to expand...
Click to collapse
Well took a quick look at this. Will try to devout some more time over the next few days and see if it'll get me anywhere.
What I got for now is:
a) There is quite a lot of "junk" on the system partition here, after a short cleanup it fits very nicely without the MTD patch .
b) libwebcore.so fixes the browser crashes and most likely the markets too.
If I have time tomorrow I'll try to give the microphone a shot, cause this is the most critical problem at this point - whats the point of having a telephone you even talk to...
Hopefully I'll also release something for testing tomorrow...
Thanks Erasmux, i would have gtalked you today but been at work and the boss was in...so no devvin on the work pc lol.Got market and browser fixed as you say and also rotate and i think light sensor.I removed nabservice.apk as it only FC'd.Would be great if we can arrange a time over the W/end to talk
Opened a new thread for "my" version of this port:
http://forum.xda-developers.com/showthread.php?t=1026699
Please note, that the amount of effort I will be able on such a (closed source) ROM is limited. I mainly what to see how far I can get this, especially in terms of hardware support, with my past experience.
So its up to you if you want to continue to keep your version going in parallel. If you do (or anyone else), please feel free to reuse anything from "my" ROM....
I assume this is the correct forum otherwise please move this.
What is the best article(s) to read if you want to start learning how to port roms from other android phones to the Evo? I've been searching on here and on google and it seems most articles are either outdated or only talk about editing existing cooked roms so I finally broke down and posted this. Yes I do use Linux and I do program in Java and .NET and do have a bachelors in software development but I have just never looked into doing this type of work until now.
Thank you, any direction I'm pointed in is appreciated.
I'll direct to you the Q&A forum.
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
sirmx said:
I'll direct to you the Q&A forum.
Click to expand...
Click to collapse
Thanks sirmx, I did do a search there but again came up short.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Sounds good, what I'll do is go ahead and start one, nothing special maybe even ones that already been done just to get the experience under my best.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is if friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
What about something A LOT simpler like adding the CRT animations to a ROM? any pointers? Any TUT you can point me to?
ThatSmartB0y said:
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
Click to expand...
Click to collapse
Oh I hear ya. Just throwing in my 2 cents. Found that having a clean updater-script is half the battle.
Sent from my PC36100 using Tapatalk
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
evomattnc said:
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well said. People love to flame anyways and XDA is famous among other Android forums for being so harsh. This thread helped me out big time, and it's especially nice to see Leoisright and myn in here giving up a few pointers, because I too was curious about porting. I never worked up the confidence to ask, just too worried about it being passed over or getting flamed because I'm young and curious.
Sent from my PC36100 using XDA App
Yah, Q&A never got me anywhere, i learned off of trial and error, still learning now.
EDIT:OP:IF you want you can ombine mine and leo's tuts together, to make this thread permanent.
Subscribed!!!!!!!!
Good stuff!
Sent from my PC36100 using Tapatalk
Yeah I want to thank the devs that have stopped by so far and gave tips, already using them . Hopefully most of them drop In at least once and leave one tid bit that would make this thread awesome!
Sent from my PC36100 using XDA App
Ha, you taking applications for an apprentice myn?
myn said:
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Yes I was afraid to post this at first which isn't good, you shouldn't be afraid to ask questions but I get that sometimes the same questions have been answered 100 times prior so I understand the quick to judge portion of it. But I want to thank everyone who has contributed tips, advise and places to start. Thank you.
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
So I've been looking at beyond compare, did you use this from everything and just edit all the non evo files to match existing evo ones from within windows?
MOD EDIT/NOTICE: You all accept the risks of flashing this - anyone caught complaining, flaming or idiot posting will receive a 24 hr ban. Off topic will also be subject to the same.
Here is the system dump & custom TAR of the ICS XXKP8 ROM that was leaked for the international version. This version will boot on our phones but without a CDMA kernel, there will no data, wifi, CWM, etc, so this is meant for DEVS\POWER USERS ONLY to play with.
DO NOT TRY FLASHING THESE FILES UNLESS YOU KNOW WHAT YOU ARE DOING, DON'T COMPLAIN IF YOU DON'T KNOW HOW TO REVERT TO A WORKING ROM AS YOU HAVE BEEN WARNED
GT-I9100XXKP8_4.0.3_IML74K.7z - System dump plus zImage
GT-I9100XXKP8_4.0.3_IML74K.tar - Flashable through ODIN
interesting, thanks for this. how far do you suppose we are from a somewhat functional ICS build?
ninja edit: first!
Oh man, thing's are getting hot in the kitchen.
So just a quick question: Why wont this won't brick our phones? Why have their been so many people with bricked phones for flashing international ROMs?
Other then that, awesome work. Just saw your Stock EL29 repack. Youre on fire !
Sweet, great job calkulin... you the man.
I'll do a quick review video of these for sure
This is a good starting point. We need to someone who can hack the 2.3 kernel to run Android 4.0
rpnunez said:
Oh man, thing's are getting hot in the kitchen.
So just a quick question: Why wont this won't brick our phones? Why have their been so many people with bricked phones for flashing international ROMs?
Other then that, awesome work. Just saw your Stock EL29 repack. Youre on fire !
Click to expand...
Click to collapse
Because this is just the kernel & system files. If they flashed the complete tar(modem, bootloader, etc), then they definitely will cause a lot of issues
When you get that one bastardized kernel, it'll be good for all international ports to use for awhile til we get source
Has anyone been able to DL the .tar?
qbking77 said:
Sweet, great job calkulin... you the man.
I'll do a quick review video of these for sure
Click to expand...
Click to collapse
It has it's issues, front cam doesn't work(main cam works tho), rotation is inverted, no data, no wifi, etc but at least we get a feel for what the official ICS update will be like once it's released. If we get a working kernel, then fixing those issues wouldn't be that hard as I have fixed them before on the EVO ports but until we get a kernel, I'm not even going to start trying
KingOfThaJungle said:
Has anyone been able to DL the .tar?
Click to expand...
Click to collapse
He's uploading it lol
KingOfThaJungle said:
Has anyone been able to DL the .tar?
Click to expand...
Click to collapse
EDIT: Link is up now
Review video is done... just have to compile and upload
doesn't seem to work for me? just stutters and doesn't respond to any input.
Dioscorus said:
doesn't seem to work for me? just stutters and doesn't respond to any input.
Click to expand...
Click to collapse
Kernel is the problem. Need to try to compile a kernel that will align the hardware with ICS
http://forum.xda-developers.com/showthread.php?t=1348832
it appears that this group had a working kernel...
Dioscorus said:
doesn't seem to work for me? just stutters and doesn't respond to any input.
Click to expand...
Click to collapse
Yep, although if you wait for it to unfreeze, you can then move around momentarily, before it freezes again...so far I can see that it DOES NOT have the face unlock, and other than settings, popup\menus and the Gmail app, which you can notice a difference right away, even without emails in it, it looks pretty much the same being that its TWIZ and not AOSP!
Dioscorus said:
http://forum.xda-developers.com/showthread.php?t=1348832
it appears that this group had a working kernel...
Click to expand...
Click to collapse
I was watching that thread intently during November & all of December. Seems to be completely dead in the water tho
dbaybay said:
I was watching that thread intently during November & all of December. Seems to be completely dead in the water tho
Click to expand...
Click to collapse
For many many reasons, not least of which was no significant progress towards ICS (which at that point needed CM7 as a prerequisite). Hopefully with the system files maybe someone can drag up that kernel and see if they can be made to work together but I think it is a CM kernel and I'm not sure that could be made to play with this...
Review of this port is up...
http://www.youtube.com/watch?v=NXqOZ2DCKDE
Thanks calkulin, feel free to add to the OP
Dioscorus said:
http://forum.xda-developers.com/showthread.php?t=1348832
it appears that this group had a working kernel...
Click to expand...
Click to collapse
The kernel we compiled for that does not work with this. Were going to see if we can get it going though.
I'm curious to what the binaries mean for upcoming roms. My assuption was that the roms were from the source meaning they had everything. So what are they and what for and why would they matter now? No this is not a "i'm a noob question" I just don't know...:angel:
www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app
b1337 said:
www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking
digitallure said:
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking
Click to expand...
Click to collapse
They have provided th 4.2.2 binaries for building a 4.2.2 rom from aosp, that's all.
Currently, developers have been building 4.2.2 hybrid roms.
digitallure said:
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking
Click to expand...
Click to collapse
ROMs are made with Google binaries, for the most part. Think of them as drivers for your hardware. For this Nexus, we're still missing camera and GPS binary. There's other ways around this though.
Sent from my Nexus
bk201doesntexist said:
ROMs are made with Google binaries, for the most part. Think of them as drivers for your hardware. For this Nexus, we're still missing camera and GPS binary. There's other ways around this though.
Sent from my Nexus
Click to expand...
Click to collapse
ooohhhh. ok. I get it. So this should make ROMs perform and stablier? I've been bouncing around 3 ROMs I like and when one acts up then i'll go to another. Almost given up and went back to stock 4.1.1...lol.
digitallure said:
ooohhhh. ok. I get it. So this should make ROMs perform and stablier? I've been bouncing around 3 ROMs I like and when one acts up then i'll go to another. Almost given up and went back to stock 4.1.1...lol.
Click to expand...
Click to collapse
Well, they do allow custom ROMs to be made, but new binaries don't necessarily mean new ROMs will be stabler. If you don't build from source, don't worry about it.
Sent from my Nexus
b1337 said:
www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Get off the forum. Seriously, you're not contributing to anything, you know damn well that's not an easy google-able answer.
Anyway, to expand on bk201's answer:
Code needs to be compiled for it to be run. When you take code and compile it, you get a "binary" that you can run, but you can't see the original code that created it.
Manufacturers and chip designers don't always like their secrets exposed (and for good reason) so rather than put out all the code for their hardware, they compile it themselves, and give us their binary.
The result is a driver we can use, but not change. That makes it trickier to work with when making a rom, and they're the reason many old phones run newer versions of Android very unstable or not at all.
Electrodeath0 said:
Get off the forum. Seriously, you're not contributing to anything, you know damn well that's not an easy google-able answer.
Anyway, to expand on bk201's answer:
Code needs to be compiled for it to be run. When you take code and compile it, you get a "binary" that you can run, but you can't see the original code that created it.
Manufacturers and chip designers don't always like their secrets exposed (and for good reason) so rather than put out all the code for their hardware, they compile it themselves, and give us their binary.
The result is a driver we can use, but not change. That makes it trickier to work with when making a rom, and they're the reason many old phones run newer versions of Android very unstable or not at all.
Click to expand...
Click to collapse
Thanks for the answer
Does anyone have a zip file to flash the new binaries for Maguro?
ReggieS2 said:
Does anyone have a zip file to flash the new binaries for Maguro?
Click to expand...
Click to collapse
You don't flash them. As has been discussed in this thread, they are used by developers when compiling a rom from source. If you're not compiling, then they aren't of much use to you.
Sent from my Nexus 7 using Tapatalk HD
najaboy said:
You don't flash them. As has been discussed in this thread, they are used by developers when compiling a rom from source. If you're not compiling, then they aren't of much use to you.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I read this over at Paranoid Android's G+ page so it lead me to think that I needed something
Recently the AOSP has been fully completely, all the needed drivers are supplied. We have updated AOSPA immediately of course and a couple of hours later we've had it merged.
Now i want everyone to listen up. YOU ABSOLUTELY NEED TO BE UP TO DATE. Or else your device will be incompatible, unable to make calls perhaps or who knows what. Google supplied a new bootloader, and for phones, new radios. You can get them straight from Google and install via fastboot. Or, the easier way perhaps, you go to XDA and get them as flashable ZIP files.
Either way, this concerns all 4.2.2 roms out there that include Googles new 4.2.2 hardware drivers.
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.