Thinking of a new method of installing AoW, and I think I have found a way to install AoW without the Dev update on the latest release of W10M.
How many of you would want something like this done? It would require full interop/cap unlock with 1st/2nd/3rd party permissions unlocked as well using the Root Tool.
I am starting research on this now to see if it is worth while.
Let me know peeps!
If this would manage to skip the device hardware check and allow us to run project astoria on 512MB RAM devices then I am really interested and ready to test.
Thanks, I am still doing a lot of research to see if this is even possible, but I have the AoW files for P.A. I just need to figure out the registry entries, and where each file goes.
Might be awhile, but I will let you know when I have an alpha installer.
sandix said:
Thanks, I am still doing a lot of research to see if this is even possible, but I have the AoW files for P.A. I just need to figure out the registry entries, and where each file goes.
Might be awhile, but I will let you know when I have an alpha installer.
Click to expand...
Click to collapse
I already tried adding the files and registry entries myself, some of the registry entries can't be written, at least not by any registry editor released until now, also did the downgrade and update with an other device's entries trick to try to enable it so I now seem to have all the aow files in their place and the entries are also there (at least the entries I know about) yet it doesn't work so at least for users of devices with 512MB RAM this might not be possible (I think that somehow the android build/hyper-v implementation/something else check the hardware and don't allow it to boot on 512MB RAM).
I am still willing to test but I think that even if you manage to find and write all the registry entries you might need an other tester with a (hardware wise) better device to actually find out if it's working or not.
Ranomez said:
I already tried adding the files and registry entries myself, some of the registry entries can't be written, at least not by any registry editor released until now, also did the downgrade and update with an other device's entries trick to try to enable it so I now seem to have all the aow files in their place and the entries are also there (at least the entries I know about) yet it doesn't work so at least for users of devices with 512MB RAM this might not be possible (I think that somehow the android build/hyper-v implementation/something else check the hardware and don't allow it to boot on 512MB RAM).
I am still willing to test but I think that even if you manage to find and write all the registry entries you might need an other tester with a (hardware wise) better device to actually find out if it's working or not.
Click to expand...
Click to collapse
Well I have a Lumia 640 which is not supported yet, but will be in the future. 1GB RAM Quad-Core
i can test if you want i have a lumia 625....
UPDATE: I think I am getting close to a solution. if someone who has astoria on their device already could you rip all the files from "C:\Windows\System32\aow" from your phone, zip them up and send them to me in a private message? It would be of GREAT help to make sure I have the latest files.
Thank you.
Old post, but I'm interested.
I have the files, go pm.
I would venture to say anyone with a high spec windows 10 mobile device is extremely interested in this. I think heathcliff is researching this. if astoria could be ported to the latest build of windows 10 mobile..
barc0d3 said:
I would venture to say anyone with a high spec windows 10 mobile device is extremely interested in this. I think heathcliff is researching this. if astoria could be ported to the latest build of windows 10 mobile..
Click to expand...
Click to collapse
I made some tests but I was stuck on adding new values in registry.. But I had all the values to put and all the files and other modifications
valentinbreiz said:
I made some tests but I was stuck on adding new values in registry.. But I had all the values to put and all the files and other modifications
Click to expand...
Click to collapse
Realistically this would only work on Nokia, which requires a special DLL to be used in the project to set/create registry items.
sandix said:
UPDATE: I think I am getting close to a solution. if someone who has astoria on their device already could you rip all the files from "C:\Windows\System32\aow" from your phone, zip them up and send them to me in a private message? It would be of GREAT help to make sure I have the latest files.
Thank you.
Click to expand...
Click to collapse
You need a lot more than that, me and other people are working on this. I already pushed all the astoria files and dlls, and restored the service key and values to trigger the dlls. It needs more than that to work in newer builds, when i mean newer builds i refer to 10586.x or higher .
xxJMarian said:
You need a lot more than that, me and other people are working on this. I already pushed all the astoria files and dlls, and restored the service key and values to trigger the dlls. It needs more than that to work in newer builds, when i mean newer builds i refer to 10586.x or higher .
Click to expand...
Click to collapse
Hey thanks for the reply, I already know this, but thanks for the information! However, I have long since abandoned this project (see date of my OP and the post you quoted). Cheers!:good:
Be careful
sandix said:
Thinking of a new method of installing AoW, and I think I have found a way to install AoW without the Dev update on the latest release of W10M.
How many of you would want something like this done? It would require full interop/cap unlock with 1st/2nd/3rd party permissions unlocked as well using the Root Tool.
I am starting research on this now to see if it is worth while.
Let me know peeps!
Click to expand...
Click to collapse
Well... I have a Lumia 925 running latest Windows 10 Mobile build ever (Redstone 4) Build 15254
But be careful!
You may brick a lot of devices...
If you really want to work on this, i can give you all the files i've got on my research aswell as the registry keys that you can import with interop tools. Since i had to format my pc and such, didn't install anything related to windows phone, so i left the project in the trunk but, as i said, if you really want to work on this i can provide you with the files and keys.
Yep!
xxJMarian said:
If you really want to work on this, i can give you all the files i've got on my research aswell as the registry keys that you can import with interop tools. Since i had to format my pc and such, didn't install anything related to windows phone, so i left the project in the trunk but, as i said, if you really want to work on this i can provide you with the files and keys.
Click to expand...
Click to collapse
Well... I will take it!
Just upload it to a download server for example MEGA.CO.NZ
And and the download link to me via private messages.
If everything would succeed and I will finally make it to the finish, I will make a program that will install Astoria onto your phone via just pressing a button!
You can also check out my other software that I made and published to xda developers, I will be very happy if one of them will help you fixing problems with your phone (if you have problems of course) or installing Windows 10 Mobile onto your phone with just 3 clicks!
Good luck!
Sincerely
Gor Mirzoyan
(founder of XWintech Corporation)
(Birth year: 2005, yes I am actually 13 years old, it's not a joke)
I hope you manage to get this working!
Ever since its announcement I was hoping to see the day it gets out!
How's the progress? Nearly done?
Related
hi guys
first off...sorry for posting the usual question...its been done to death
i have been out of the xda-dev site for a while and have lost track of things.
i always hoped himalaya linux would get done.... but from what i can see its still lacking the key components (eg phone support under gpe).
i am a uni student on placement at a company that actually writes mobile phone radio stacks...so i am learning embedded c and about the interesting side of the hardware/software interface.... now i want to actually do something about this lack of a fully usable phone.
my questions go as follows..
1> what is the current stage of himalaya linux ... i have a feeling the wiki's are probably out of date
2> is anyone actually still working on it
3> i know only a little about haret i get the idea it is also able to watch hardware (and isnt just a bootloader)...where can i find docs about using it to do this.
4> was jtag ever found on the himalaya
5> of the code in the tree what files are specific to the himalaya
i have much to learn on writing drivers etc for linux...and alot to learn about embedded c, reverse engineering etc....ok so i have a hell of a lot to learn....but i'm willing to try! (i also have 3 himalayas (1 has a bust screen) so plenty of tinkering can be done)
any other tidbits of information would also be appreciated
i think my basic goal would be the phone working.
after that get the other little bits and pieces
get the backpack cf working
get sdio and wireless working.
but these are the kind of goals that will take a long time so we'll see
i'd also love to work on the UI one day.. GPE and OPIE just dont toot my horn enough yet.
thanks
Tim
tim_programmer said:
1> what is the current stage of himalaya linux ... i have a feeling the wiki's are probably out of date
Click to expand...
Click to collapse
It is out of date, but some parts are in a good shape.
2> is anyone actually still working on it
Click to expand...
Click to collapse
Yes, because it has many common hardware and features with blueangel.
The kernel source is not being fixed, because it is decided to make blueangel
work first, and then reuse and adapt the cleaned code for himalaya.
3> i know only a little about haret i get the idea it is also able to watch hardware (and isnt just a bootloader)...where can i find docs about using it to do this.
Click to expand...
Click to collapse
There are no "real" docs, only the source code. Many pxa27x functions are
implemented in haret, that either work or need minor changes for pxa26x.
4> was jtag ever found on the himalaya
Click to expand...
Click to collapse
Yes, it's in wiki since 3 years or so
5> of the code in the tree what files are specific to the himalaya
Click to expand...
Click to collapse
Blueangel is the authoritative source.
i think my basic goal would be the phone working.
Click to expand...
Click to collapse
AFAIK, the phone works. But not with the latest 2.6.18-hh0 kernel.
This one has a lot of audio problems anyway, so it's not a major concern right now.
get the backpack cf working
Click to expand...
Click to collapse
It's a bit challenging. The backpack is implemented in so-called ASIC5,
and there are no docs for it.
get sdio and wireless working.
Click to expand...
Click to collapse
You mean SDIO wifi card ?
The SDIO host can be done relatively easy, but good luck with the wifi part
I know 2 of them, one with the TI acx100 (should be doable, because
there is linux acx100 driver), another needs the firmware upload in Motorola
SREC format, maybe even prism2.
And there is no free software SDIO for linux, you need to do some heavy RE.
Hello guys,
I have got Himalaya and I would like to help with implementation of some driver/software that is needed.
So I have got a few questions (some of them are similar to tim_programmer's, but I don't know if there are not outdated):
1. Where is the current branch with Himalaya specific code?
I have found:
- K2-6-12-hh2-xda0-ba0 (http://xanadux.cvs.sourceforge.net/xanadux/linux-2.6-xda/) and
- K2-6-21-hh20 (http://handhelds.org/cgi-bin/cvsweb.cgi/linux/kernel26/)
Is himalaya specific code that is in K2-6-12-hh2-xda0-ba0 already included in K2-6-21-hh20?
Or what differences are between these branches?
2. Is somewhere available (SD card/NFS) image with kernel+initrd+GPE that is already running on Himalaya?
I have found:
- http://wiki.xda-developers.com/index.php?pagename=HimalayaLinuxBooting
It boots, but freezes during boot (after some changes in initrd it was possible to connect to the MDA with SSH via USB bus)
- http://wiki.xda-developers.com/index.php?pagename=HimalayaStandaloneGPEWithoutSD
Link to GPE is dead.
- http://handhelds.org/moin/moin.cgi/Himalaya
There are screenshots of GPE so it should be working image somewhere.
3. Is it posssible to boot some BlueAngel "distribution" on Himalaya? (Possibly with a little changes?)
I have found:
- http://handhelds.org/moin/moin.cgi/BlueAngelHowtoInstallLinux
Could it be used on Himalaya?
4. What is the current state of Himalaya support in Linux? What is already done and what not (or partially)?
I have found:
- http://wiki.xda-developers.com/index.php?pagename=HimalayaToDo
But there is not mentioned of what branch state it is.
5. Is any other bootloader than HaRET with that is possible to boot to Linux directly from SD card without Windows booting?
I have found:
- bootldr (http://xanadux.cvs.sourceforge.net/xanadux/linux-2.6-xda/bootldr/)
What is it?
A lot of information about Himalaya development is outdated and I don't know where to start :-( So any help is welcome
Thanks
Drasar
drasar said:
A lot of information about Himalaya development is outdated and I don't know where to start :-( So any help is welcome
Click to expand...
Click to collapse
join #htc-linux at freenode.
Thanks for the link..just joined
btw when i start Haret on my Hima..the Thermometer goes up and the eyes go red..and then few lines comes up and thats it..i have tried every thing but cant get Linux to work
waiting for the New Linux Mobile
ather90 said:
btw when i start Haret on my Hima..the Thermometer goes up and the eyes go red..and then few lines comes up and thats it..i have tried every thing but cant get Linux to work
Click to expand...
Click to collapse
What kernel have you tried? What was the last message on display? Some old HaRET versions (e.g. 0.3.6) have a problem with big kernel and boot fails on mounting root fs. So try the newest HaRET 0.5.1 that goes fine.
Thankxxx alot..u are rite i have 0.3.6
here is what i have :
haret-0.5.1.exe
initrd-2.6.12.gz
modules-2.6.12.tgz
zImage-2.6.12
are these all latest
ather90 said:
haret-0.5.1.exe
initrd-2.6.12.gz
modules-2.6.12.tgz
zImage-2.6.12
Click to expand...
Click to collapse
For kernel 2.6.12, follow How To Compile 4 Himalaya instructions. It works, I have tried it yesterday ;-)
Thanks alot..thankfully i have Ubuntu so compling is no big
i will contact u for more assistance
so i was wondering just how one would go about editing the flash lite cab floating around here to make it universally compatible amongst ppcs. is it outrageously complex?? are there liek any simple examples someone could give to show how the code might be changed?
i read a little about cab files but really felt like there had to be a simple solution to the overall buginess and unique situations needed for it to work. if some developers or techies can chime in on this ide love to learn a bit about how to accomplish these things. thanks in advance.
Why would you start a new thread rather than ask in the offical Flash Lite thread ?
Just Download OCP WinCe Cab Manger and open flash lite 3.1 and without modifying anything just press Save and now can install on PPC or SP
snachez said:
Why would you start a new thread rather than ask in the offical Flash Lite thread ?
Click to expand...
Click to collapse
just a general tendency of people when they want to make sure they're heard.
totally. i just dont want my question to get buried in the 20+ posts per day that thread already gets. ive posted twice with only one response to anything i mentioned in the post. so i really wanted to ask an important question seperate from just "getting it to work somehow". is it possible to modify the file to be more compatible with the Kaiser WM6.1 so that it will function well right off the bat.
is the real issue that this cab and the opera versions everyone is using are both unofficial? meaning they both still contain bugs and compatibility problems. i wish there was a way to maybe rewrite the Flash Lite program that extracted so that its more universal.
btw, what does the above mentioned software do exactly?? since its already installable, im wondering if someone could change the program itself to work better with wm6.1 roms, and the latest version of opera 99% of time.
wow i posted not too long ago, this thread is now 4-5 pages burried!! hehe. so many posters. i guess thats why i love this site. but then again, i just wish someone would throw out some suggestions.
bump...would like to see this get working on at least all wm6.1 devices.
Dear all,
as I wrote on this other post (excuse me for crossposting - please mods to close the wrong-placed one):
http://forum.xda-developers.com/showthread.php?goto=newpost&t=384850
there are two guys that recompiled Android for ARMv4 processor - like ARM920T, the trinity processor!!
Here you have the links:
http://benno.id.au/blog/
http://perpetual-notion.blogspot.com/2008/10/android-freerunnder-updates.html
They are working on the Freerunner and Neo1973 devices.. but the processor is the same..
Anyone out there wants Android on our beloved trinity?
At the moment I have no spare time (and skills) to take the challenge.. but I hope that someone will do.
I think that with the source code the CLZ and Thumb mode issues are completely addressed.
Anyone could confirm this to me?
Best regards,
s
Hi,
i'm also interested to see android on my htc hermes. i'm waiting benos new blog entries to see if he was able to run the code on "Neo1973".
What is the diference between htc hermes and htc dream (g1) regarding other chips beside the prcessor?
i don't think that drivers included in android can cover all chips in hermes. can someone maybe make an list of same and different devices(chips) in this 2 devices?
thanks
G phone?
So this is the same OS that the G phone is sporting yeah?
If The flashing process isn't harder than the current process then I'd be up for this. Also will it brick the phone?
Need some people to test.
Great Topic!
More information about this here:
http://lists.openmoko.org/nabble.html#nabble-td1368755|a1368755
http://review.source.android.com/user/sean,,mcneil.com
Since the openmoko is very like the p3600 I will give these patches a try. Let you know!
That would be awesome !
Please tel us your progression.
I'm waiting for a Android ROM for my Trinity ^_^
This is what we can try. The openmoke images are out. Since the openmoke is very like the p3600 we could give these images a try. The images are located over here.
http://people.openmoko.org/sean_mcneil/androidfs.jffs2
http://people.openmoko.org/sean_mcneil/uImage-android
We need haret for the images as well.
http://www.handhelds.org/~koconnor/haret/haret-0.5.2.exe
The thing we also need is to have a proper default.txt for haret. Who can help?
Hi piethein,
This will replace the rom we have installed in the trinity or is like an emulator running under wm ?
We dont loss any wm rom that we have installed ?
Dear all,
here you have some (bad) news:
http://groups.google.com/group/android-porting/browse_thread/thread/906dcae21176d4e9#
at the link above you will find a thread I started in adroid-porting developers group.
http://groups.google.com/group/android-porting/browse_thread/thread/0b3743f8151783f6#
at this link there are other infos, but let me report two msgs:
shaice:
Dear all,
sorry to bother you with (probably) silly questions but..
I own a HTC trinity that use the same ARM920T processor of Freerunner.
I saw benno's and christopher's posts on their blogs...
Is there any chance that your binaries will run on other ARM920T
phones?
Thank you in advance for any answer.
Best regards,
s
Christopher Friedt:
Hi Shaice,
In short, no (for now...)
Chris
sigh sob!
Now I'm searching for some fresh news.
Stay tuned!
s
uhmm reading somewhere in the group I found this post:
Jean-Baptiste Queru
3 Nov, 01:14
The shipping G1s have 192MB. Earlier development devices had 128MB,
and that wasn't quite enough to smoothly run the applications that
ship with the G1. Even if all the device's RAM could be allocated to
Android (no baseband, no framebuffer) 64MB would probably be very
tight, to the point where even foreground applications would risk
getting killed because of low memory conditions (the browser
especially comes to mind). In 32MB the system is likely to be
thrashing for memory even before it's done starting the system server
(if it can even start it at all).
JBQ
Mmmmh no good news for us.. :-/
s
Hi there,
basically these are great news!!!
piethein said:
This is what we can try. The openmoke images are out. Since the openmoke is very like the p3600 we could give these images a try. The images are located over here.
http://people.openmoko.org/sean_mcneil/androidfs.jffs2
http://people.openmoko.org/sean_mcneil/uImage-android
We need haret for the images as well.
http://www.handhelds.org/~koconnor/haret/haret-0.5.2.exe
The thing we also need is to have a proper default.txt for haret. Who can help?
Click to expand...
Click to collapse
....but forget about running exactly these images on your trinity units.
It won't work
I don't want to digg your hope but there's a lot to do to make it real.
First:
You'll need a kernel that suits to trinity and offer some features the android OS needs.
Second:
You'll have to modify the image in jffs2 format to get loaded on trinity or build up a tricky environment to mount these image files after booting the kernel.
Have fun!
scholbert
Android on Trinity wanted!!
now that the full Android code is out it's possible!!
we can have Android on Trinity!!
please help... I cannot stand anymore WM!!
IMHO there is no enough memory to run smoothly android on trinity...
but stay tuned..
s
Dear all,
there is no hope for trinity users like us to see android running on our wonderful device.
As stated here:
http://groups.google.com/group/android-internals/browse_thread/thread/788c201e75ca7351
Android don't run on the ARM920T used in Neo1973.
In the following site
http://en.wikipedia.org/wiki/ARM_architecture#ARM_cores there is a table
where are described all the ARM cpu.
Android framework is compiled for the ARMv5 architecture version, so run on
the all the processors that belong to this architecture version and also in
some cpu of the new architecture (ARMv6/v7).
Other information can be found on this site
http://elinux.org/Android_on_OMAP#Real_hardware.
Best Regards,
Andrea Bernardi
Click to expand...
Click to collapse
:-(
bye all
s
ehm...
on HTC vox wat i was using 2 weeks ago they builded a ADNROID rom !!! But they have only clock working but working !!! (no gsm,no edge,no menu,....)
http://forum.xda-developers.com/showthread.php?t=368014&page=14
didoop said:
on HTC vox wat i was using 2 weeks ago they builded a ADNROID rom !!! But they have only clock working but working !!! (no gsm,no edge,no menu,....)
http://forum.xda-developers.com/showthread.php?t=368014&page=14
Click to expand...
Click to collapse
a new step per day, some time good new, other time bad news..... lets get hope that android will run on trinity...
Hi all,
so I am new to the world of Windows Mobile - use to be a Symbian fan and then got the HTC Touch Diamond recently due to my Nokia dieing of old age.
I want to learn how to cook ROMs so I can customize what I want as I want. I tried sending Da_G a PM as he seems to be quite knowledable about cooking - although he seems to be MIA (his last post was a long time ago) and I have not gotten a reply yet.
So now onto some questions which are probably stupid, but I do not know the answers to.
So I have an HTC Touch Diamond which originally comes with Windows Mobile 6.1, I am using osKitchen as it seems really popular and it looks easy enough to use. I followed the guide which is here but it does not give me the complete info I want.
So in order to cook a ROM you first need to have an original ROM (so in my case an original ROM for the HTC Touch Diamond off the HTC site?)... I got that(RUU_Diamond_HTC_WWE-AFK_2.03.421.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe)
Then you open it up with osKitchen, it extracts it blah blah blah.
I then get a popup about a new ROM has been imported and it asks me if I want to automatically configure the project to use the ROM. I click yes.
Then it says the device profile currently selected uses a pre 6.5 kernel, module allocation space will be extremely limited. Do I want to auto enable module to file conversion for a list of files? Now I read somewhere that if you are using pre 6.5 kernel you want files, if you are using the 6.5 kernel you want modules? I am not sure what to click here as I want to upgrade to windows mobile 6.5 ...
So do I enable the conversion or not?
Then it pops up with the project settings, under SYS Packages I can see all of the phones services. OEM packages, I am not too sure what that is... One thing which is worrying is that there is a red circle with an X in it infront of OEM Drivers... If I hover over it, it says there are issues detected in the OEMdriers. They all seem to be errors detected in the registry and the registery key path entry is invalid due to 2 adjacent backslahes? So is this normal? What do I do?
Also there is a block "RecMod" under OEM Packages. What does that do and what is it used for?
EXT Packages, over here we have all of the applications which will be preinstalled when you flash the ROM? I know how to add .cab packages to it and it seems simple enough. Once again there is a RecMod with a tick box?
ROM Tweaking I have not really bothered with yet, would first like to learn the basics. Anything I should know about in ROM Tweaking?
Now back to SYS Packages. This is where you update/port/upgrade ? to newer windows mobile versions? Now I think if you are changing between window mobile major build versions or what ever you want to call it (like from 6.1 to 6.5) kernel changes perhaps? You call it porting? Anyways, so now I want to change to the latest build in WM6.5 .
I took a look at this thread: http://forum.xda-developers.com/showthread.php?t=650783
Now it seems like the first 3 digits indicate something, what exactly I am not too sure. Perhaps someone could explain?
There is HTC HTC which is made by HTC I think and possibly meant for HTC?
Then there is COM 2 and LG. Now since I have an HTC do I have to use the HTC one or not? Also it seems some have newer / higher WM builds? So why are there these many different builds and what difference does it make as to what they are? Also what are the COM 2, 3 and 5 ?
Anyways, I downloaded the HTC one. Now I want to port / upgrade to it. It is WM6.5 now as well. So I click Import, then goto Import a new WM build. Select the appropriate build dump, then click on start importing. It will import it and then what? Is there anything else I need to do?
I am assuming go back to Project Settings and under SYS build change it to the newer one which I have just imported? Although is this really all I need to do? Will I now have a proper functioning cooked ROM running WM6.5 with the new build?
Thanks
If you're cooking a 6.5 rom, and you have a 6.5 native kernel (there should be one out there, unless you're using a cdma diamond), then DO NOT RECMOD (convert to files). If you have to use a 6.1 kernel, then you have to recmod a lot of modules. Look around, there are threads with native kernels for many older devices. I'm not going to dig up a link, I'll let you find it. Just get the Diamond native kernel and use it.
If you have a cdma diamond, then I believe that people use the cdma raphael native kernel, but supposedly it's buggy.
OEM Drivers has an .rgu that usually has a few mistakes in it; that's probably the error you're getting. I wouldn't worry about it, but the kitchen may tell you which line the error appears in, and you can fix it.
As far as rom tweaking goes, all you need to know is that manila sucks, and Sense is blight on humanity. Good luck and have fun.
Real Beginners Stuff Please.
PsyCLown89 said:
Hi all,
so I am new to the world of Windows Mobile......
I want to learn how to cook ROMs so I can customize what I want as I want.....
So now onto some questions which are probably stupid, but I do not know the answers to......
...... I followed the guide which is here but it does not give me the complete info I want.....
..... What do I do?
..... What does that do and what is it used for?
..... would first like to learn the basics......
..... so now I want to change to the latest build in WM6.5 .
..... do I have to use the HTC one or not? Also it seems some have newer / higher WM builds? So why are there these many different builds and what difference does it make as to what they are? Also what are the COM 2, 3 and 5 ?
.....and then what? Is there anything else I need to do?
.....Thanks
Click to expand...
Click to collapse
Hi,
So many questions
I too am new to the world of Windows Mobile, and have learnt how to flash different ROMs sussessfully.
I have spent my time reading hundreds of threads about flashing, and having a go - the tutorials and threads have been great source of knowledge.
Now I want to start cooking a ROM and things are different..... I have read thousands of posts and tutorials and watched videos, but I haven't found a real Noobs method of: starting, choosing a kitchen, finding a ROM, importing the new bits, and making the changes. It all goes wrong right from the very start.
Choose a kitchen, and then what ? (exact steps, not just "find a ROM you like, then..", etc. etc.)
None of the threads I have read seem to be able to give the nitty gritty to start, they all skip over it.
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Please can someone give a REAL NOOBS guide to starting off.
Thanks & Regards,
It all comes down to the basics. If you do not know what a kitchen actually does, then there probably is no point in cooking to start of with.
Kitchens available today make a lot of things heaps easier than they were several years ago.
Try starting with this thread.... it is not for your device, but you get to learn the basics and actually understand what happens in the background.
http://forum.xda-developers.com/showthread.php?t=335631
Cooking is not just clicking around with your mouse.
pkoper said:
.... If you do not know what a kitchen actually does, then there probably is no point in cooking to start of with.
..... Cooking is not just clicking around with your mouse.
Click to expand...
Click to collapse
This may be new to me, but it also was to EVERY cook there is, or has been at sometime. We all learn something new at some time, and all I was asking for is a little starter to get me going. I realaise it isn't a point and click exercise, otherwise I would have made a ROM by now, and not asked for help. I didn't write the software for the kitchen, so I don't know how it works.
http://forum.xda-developers.com/showthread.php?t=335631
Click to expand...
Click to collapse
Thanks for that, I hadn't seen that one, but unfortunately, it also doesn't give the procedure for starting with a WM6.1 ROM and adding/changing files to end up with a WM6.5 Native Kernel.
Please, give me a break.
Fish-Man said:
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Click to expand...
Click to collapse
Using search you would have found the native kernel:
http://forum.xda-developers.com/showthread.php?t=619663
Fish-Man said:
Thanks for that, I hadn't seen that one, but unfortunately, it also doesn't give the procedure for starting with a WM6.1 ROM and adding/changing files to end up with a WM6.5 Native Kernel.
Click to expand...
Click to collapse
Thats exactly what I meant. Do you know what the kernel actualy is?
pkoper said:
Using search you would have found the native kernel:
http://forum.xda-developers.com/showthread.php?t=619663
Click to expand...
Click to collapse
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Thats exactly what I meant. Do you know what the kernel actualy is?
Click to expand...
Click to collapse
Yes, It's a piece of code, usually written in assembly language (for speed of execution), that sits between the hardware devices and the system drivers and programs, to translate what the programs want, to what the hardware can understand, and deliver the results from the hardware, back to the programs.
It is the core of the Operating System, and is the first thing that is loaded into memory when the system boots, and stays there until you turn off the device (unlike other programs that are loaded, and unloaded as needed). It is loaded into a seperate and protected area of memory, where it executes processes, handles interrupts, memory management, process management, file management and I/O management.
The User, cannot interract directly with the kernel (or hardware), but has to go via a seperate program (usually containing a GUI), that can send it's requests to the kernel for processing. After the kernel has processed the programs requests, the kernel gives the information to the program, which then outputs it to the User.
Is that enough of an explanation ? Sorry I had to simplify it, but there are a lot of other noobs here that may have gained some knowledge from that, so rather than blow thier minds with acronyms and babble, I thought it best to explain it simply.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Fish-Man said:
Hi,
So many questions
I too am new to the world of Windows Mobile, and have learnt how to flash different ROMs sussessfully.
I have spent my time reading hundreds of threads about flashing, and having a go - the tutorials and threads have been great source of knowledge.
Now I want to start cooking a ROM and things are different..... I have read thousands of posts and tutorials and watched videos, but I haven't found a real Noobs method of: starting, choosing a kitchen, finding a ROM, importing the new bits, and making the changes. It all goes wrong right from the very start.
Choose a kitchen, and then what ? (exact steps, not just "find a ROM you like, then..", etc. etc.)
None of the threads I have read seem to be able to give the nitty gritty to start, they all skip over it.
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Please can someone give a REAL NOOBS guide to starting off.
Thanks & Regards,
Click to expand...
Click to collapse
I don't think what you're looking for exist, persay. There are several kitchens out there to choose from. The only thing that helped me when starting out was frequenting the thread of the kitchen that I was using. It's in the kitchen's thread that you'll find all the nitty gritty answers you're looking for and other people that are in the same boat as you, and more experienced users of the same kitchen who would probably be more apt at answering questions about specific kitchen.
Fish-Man said:
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Yes, It's a piece of code, usually written in assembly language (for speed of execution), that sits between the hardware devices and the system drivers and programs, to translate what the programs want, to what the hardware can understand, and deliver the results from the hardware, back to the programs.
It is the core of the Operating System, and is the first thing that is loaded into memory when the system boots, and stays there until you turn off the device (unlike other programs that are loaded, and unloaded as needed). It is loaded into a seperate and protected area of memory, where it executes processes, handles interrupts, memory management, process management, file management and I/O management.
The User, cannot interract directly with the kernel (or hardware), but has to go via a seperate program (usually containing a GUI), that can send it's requests to the kernel for processing. After the kernel has processed the programs requests, the kernel gives the information to the program, which then outputs it to the User.
Is that enough of an explanation ? Sorry I had to simplify it, but there are a lot of other noobs here that may have gained some knowledge from that, so rather than blow thier minds with acronyms and babble, I thought it best to explain it simply.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Click to expand...
Click to collapse
Nice quick knowledge drop on kernel. It sounds to me like you already have a better grasp on things then some!
Fish-Man said:
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Click to expand...
Click to collapse
Thats because there is no stock 6.5 for the Kaiser. Not sure what "those WM6.5 files" are, but you do need the drivers for your device. Any leaked build will not contain those.
Dumping a stock rom will give you insight as to what is actually in the rom. When you then download one of the leaked builds you can you will recognize the files and hence see what needs replacing in order to upgrade.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Click to expand...
Click to collapse
What kitchen are you using? As there are obviously slight differences as to what is where.
I would just get a ready kitchen and study it.
http://forum.xda-developers.com/showthread.php?t=517957
for your reference maybe you should read this....
http://forum.xda-developers.com/showthread.php?t=901712
i had made the tutorial how to cook ROM, step by step. it has different device and different OS but worth to read.....
i don't have enough capability to Cook but i try to....
also in this http://forum.xda-developers.com/forumdisplay.php?f=385
some of members also made tutorial as well.......
i hope it can help.
I need help or some one can point me to the right direction.
One of my employee give me Nokia lumia 1520 window 8.1 he ask me If I can put Androids app to this phone. I never root this type of phone before ( only Samsung phone). Can some one tell me what I need to download or send me a link what steps I need to do in order to root and install android apps on this phone if is possible.
thanks in advance.
No dude. You cant install Android on Windows Phone. You need to buy Android Phones for that. In earlier versions of Wp10 it was possible but not now
Ajshal said:
No dude. You can't install Android on Windows Phone. You need to buy Android Phones for that. In earlier versions of Wp10 it was possible but not now
Click to expand...
Click to collapse
Something close is possible, You can install Appx File.... It's the Universal Apps : there might be some that have be converted from android to Windows phone.. Just google Appx Downloads and see if you can find something he wanted. If so, that is what is possible. The previous : A Older version of Windows on the phone had a special file/command, whatever you wish to call it. """Bash""". It allowed Linux to run on windows. Sadly they removed this, it would give programmers to do things Microsoft did not want to happen.
ryanromerosr said:
Something close is possible, You can install Appx File.... It's the Universal Apps : there might be some that have be converted from android to Windows phone.. Just google Appx Downloads and see if you can find something he wanted. If so, that is what is possible. The previous : A Older version of Windows on the phone had a special file/command, whatever you wish to call it. """Bash""". It allowed Linux to run on windows. Sadly they removed this, it would give programmers to do things Microsoft did not want to happen.
Click to expand...
Click to collapse
I think what you meant was sideloading apk using adb in W10 build 10149 . The Exploit which allowed more or less sandboxing of Android app. It Ran the basic Android Apps which didnt have much dependency on Google Play services and more in use by Project Astoria.That means if an android app that required the GMaps plug-in would crash in W10M. Well that's basically not possible now as they removed the Linux Subsytem. You cant install Android Apps now on Windows 10 (btw Nowadays which dev is spending time on Lumia devices? ) I dont think there would be more development of Windows 10 mobile in future as they have shown that Full blown Windows 10 would soon run on ARM devices which has SD835 or more( Just think SD835+6GB RAM+LQS)That would be amazing. But Microsoft Doesnt have the Required no. of Apps in store (Admitting, UWP was not a great success) and enough market share. But dev's like @feherneoh and @banmeifyouwant have done great thing in porting Android to SG Lumias. :cyclops:
feherneoh said:
SD835 might be a great SoC, but we'll have to wait and see. But that will give us x86 Windows apps, not Android
Yeah, there is the 52X port, but note that we have no connectivity at all....
Click to expand...
Click to collapse
Atleast if the perfomence if fine on SD835 soc , I Mean more than 2.5Ghz and enough page memory, I Think running or emulating Android apps would be smooth.Moreover if its full fledged Win10 the bootloader stuff Etc. would be easier to unlock and build Android for that. Yeah as you said we have to wait and see.
Yeah, Connectivity is major barrier on L52X Android Ports. If you guys could solve that, L52X Android port would the topic of debate and hopefully open the doors for future development. Good luck with connectivity though. Anyway you guys have done a great work on dead Lumias