Related
The last 2 days I started playing around with Aurora rom both DZO's and Sakura's.
I was curious enough to try some "crazy" things and flashed some roms modded by me.
I tried the following.Unrared the DZO aurora rom and edited the updated script with notepadd ++. I changed the model from u8800 to u8800pro (you can copy-paste the 1st line which is what we need from a sakura aurora updater script) and then I rezipped the dzo aurora rom with winrar and it flashed normally.It even booted normally!
I also tried copying the boot.img from DZO release to Sakura release.Again the rom flashed ok.
But the 2 modded roms have these problems in common(other things I tried like camera,messaging were working normally):
1) No bluetooth working (it just writes turning on).Sometimes the phone reboots.
2) No wifi working. Same as bluetooth. Just turning on and phone reboots sometimes. Also tried with new wifi driver option.
I also provided a screenshoot from the second method I used(sakura rom with 3.0.8 kernel).
Anyway.Maybe the day that we can use 3.0.8 kernel in our phones isn't far away from us.Moreover it may also be possible to "port" the x5 aurora to our x5 pro without having to rely any more on the chinese guys(seriously I hate it everytime I flash a sakura rom that i have to change the language ).
Well hope that this thread will be the start for a better aurora rom for the u8800 pro
It is more safe if you dont unrar the rom. Just open in a window and drag n drop the files you want to change.
For the language, open the build.prop file and change the following lines:
ro.product.locale.language=zh
ro.product.locale.region=CN
to:
ro.product.locale.language=en
ro.product.locale.region=US
ela re patrioth
i know that I can change the language even before flashing the rom but that's not the reason I started this thread. I started just to prove that 3.0.8 kernel can also run on our phones because I have seen a lot of posts in different forums complaining about u8800 PRO not getting a 3.0.8 kernel release
Oraios...but can you fix those bugs or just post it here!!!
I tried to do it,but I failed.After some flashing I got a not working phone.
You can help me at this thread here if you like : http://forum.xda-developers.com/showthread.php?p=25748225#post25748225
Edit: Problem solved and phone working. But guess I will do a break after this little adventure and will start modding again in the near future.
Maybe it's better because aurora and the kernel will be even better then
Moihack said:
The last 2 days I started playing around with Aurora rom both DZO's and Sakura's.
I was curious enough to try some "crazy" things and flashed some roms modded by me.
I tried the following.Unrared the DZO aurora rom and edited the updated script with notepadd ++. I changed the model from u8800 to u8800pro (you can copy-paste the 1st line which is what we need from a sakura aurora updater script) and then I rezipped the dzo aurora rom with winrar and it flashed normally.It even booted normally!
I also tried copying the boot.img from DZO release to Sakura release.Again the rom flashed ok.
But the 2 modded roms have these problems in common(other things I tried like camera,messaging were working normally):
1) No bluetooth working (it just writes turning on).Sometimes the phone reboots.
2) No wifi working. Same as bluetooth. Just turning on and phone reboots sometimes. Also tried with new wifi driver option.
I also provided a screenshoot from the second method I used(sakura rom with 3.0.8 kernel).
Anyway.Maybe the day that we can use 3.0.8 kernel in our phones isn't far away from us.Moreover it may also be possible to "port" the x5 aurora to our x5 pro without having to rely any more on the chinese guys(seriously I hate it everytime I flash a sakura rom that i have to change the language ).
Well hope that this thread will be the start for a better aurora rom for the u8800 pro
Click to expand...
Click to collapse
You have to grab dzo kernel 3.0 sources, also extract the config file for 2.6.35 u8800pro kernel (with extract-ikconfig, using zImage from boot.img), and start compiling the 3.0 kernel generating modules for wifi&bt.
I'm also pretty sure that the non working wifi and bt have something to do with the modules (wifi is system/lib/modules I think) and maybe some init.rc and huawei.rc in the boot.img.
I messed a little with them and the results were not pleasant according to my above post. I will definitely try modding again in the future although
i think it would be easier to collect some money from all interested users and pay DZO to make 3.0 kernel for Pro users
Hi all.
I have successfully flashed PsychoGame's CyanogenMod 7 ROM for GT-s5360 together with its kernel.
Now i would like to make some changes in the source code of CM7 and to build it from source. Unfortunately i have spent already 4 days without success.
Those are the steps that i did:
1. I have downloaded CM7 source code from git://github.com/CyanogenMod/android.git -b gingerbread
2. I have cloned PsychoGame's totoro device code into /devices/samsubg/totoro
3. i have connected my device via USB and run the script extract-files.sh which successfully extracted all files.
4. during the building i realized that the above script extract all essential files (like camera related), so i cloned PsychoGame's vendor directory from github.com/PsychoGame/android_vendor_samsung_totoro.git
5. now i realized that the file cyanogem_totoro.mk in the directory vendor/cyanogen/products is missing. where i can find a suitable file?
i have found somewhere such file and succeeded to build an ROM, unfortunately CWM does't let me to flash it because the assert command checks that the current device in "totoro" but it fails. i have tried to open the zip file of the ROM and to delete the assert command but CWM still can''t flash the new ROM.
can somebody please help me with some guild about how PsychoGame built his last vertion of CM - CyanogenMod 7 Alpha 5 Release
Thank you very much!
Use percys source code - It has more fixes
Compare build.prop and update binary & scripts for cwm flashing
marcussmith2626 said:
Use percys source code - It has more fixes
Compare build.prop and update binary & scripts for cwm flashing
Click to expand...
Click to collapse
Hi, thank you for the information about gigngerDX. i found the github of the device but can you please tell me where to find all other files to build this rom? do i need to buld it without the kernel? how to do that?
thank you again!
yuripo said:
Hi, thank you for the information about gigngerDX. i found the github of the device but can you please tell me where to find all other files to build this rom? do i need to buld it without the kernel? how to do that?
thank you again!
Click to expand...
Click to collapse
Percys github is
https://github.com/percy-g2
I haven’t compiled a Cyanogen rom before
If you would like to contribute to the building of Cyanogen roms the best person to talk to is percy
I haven’t compiled a Cyanogen rom before
If you would like to contribute to the building of Cyanogen roms the best person to talk to is percy[/QUOTE]
can please somebody explain how to build only Percys ROM without the kernel?
thank you
Hi all.
Can somebody please give a small guide for how to build percy's CM7 ROM from source?
which directories in the CM7 i should replace? does the process of building is the same as with official ports?
Thank you!
Hello again:
Build B2G for ZTE Open (inari) is tricky. People who want to develop applications with firefox's app-manager extension need to wait for ZTE upgrades or build their own system, which involves some permission modifications in boot.img and some tweaking to recover the bootanimation (lost on custom builds) among other things.
But hey, I've build a production pre-release of firefox os 1.2, and so far so good , and I like to share it with you via a flashable .zip file. Remember this file can be installed ONLY from CWM recovery, cause its not signed
features:
Version 1.2-prerelease (user release):
Build with blobs from version 1.1.0B02 (also known as 1.1.0B06) for ZTE Open (EU version)
Multilanguage - upgradeable through B2G nightlies (for both gecko & gaia)
Compatible with firefox app-manager (firefox 26+)
Includes su & busybox binaries ( busybox is linked with clear, grep, head, less, lsmod, more, nohup, pidof, ping, printf, pstree, sysctl, tail, telnetd, tftpd, traceroute, uname & usleep, for debugging via adb)
No carrier branding, just official firefox os branding
Fastboot enabled | ADB rooted
does *NOT* overwrite your recovery partition (you won't loose CWM recovery )
known bugs: isn't a bug but a security feature: "ADB should not be allowed to connect when device is locked in production builds"
FAQ:
I'm on version 1.x.y of 'some-carrier' build, Will this zip work in my case: Yes, only and just only if you have CWM installed.
There are a lot of strange files inside .zip, why ? this is because ZTE provides upgrades with radio & bootloader firmware (incompatibles between versions) If I want to support this ROM I need to make sure everyone have the same version ( the version that matches with the blobs )
Of course, YOUR WARRANTY IS VOID, and if you brick your phone , this is NOT MY FAULT
the link to the zip file: ul.to/2jwkruhj
Feedback is welcome
paziusss said:
Hello again:
Build B2G for ZTE Open (inari) is tricky. People who want to develop applications with firefox's app-manager extension need to wait for ZTE upgrades or build their own system, which involves some permission modifications in boot.img and some tweaking to recover the bootanimation (lost on custom builds) among other things.
But hey, I've build a production pre-release of firefox os 1.2, and so far so good , and I like to share it with you via a flashable .zip file. Remember this file can be installed ONLY from CWM recovery, cause its not signed
...
Feedback is welcome
Click to expand...
Click to collapse
Runs great, I will use your build to test and mod some apps with the app-manager.
And please, stay at this good work (updates etc?!)
---edited:
Is your build a development build (of FFOS 1.2)? I cant't open certified apps with the app-manager (I have changed the pref "devtools.debugger.forbid-certified-apps" to false in my profile. But there is no certified app to see or to open in the app-manager. If not, can you - or somebody else - build this development build of FFOS 1.2?
ROM is pretty stable. I don't know if I'm the only one having this issue, but it looks like my data is connecting but then it isn't working. I'm connected to AT&T right now. When I pull down the notification bar, I see that I am getting an "H" (HSPA+) signal but if I try to open firefox and hit a site, it says I'm not connected to the internet.
I'm aware that this is in a prerelease state but do you know how I could fix this?
@martin_s5670: AFAIK there are three types of builds: engineer builds, userdebug builds and user builds. This is an user build, but you can also test privilegied (aka certified) apps on it. If you want to see your installed system apps I'm sorry but you can't do it in this way
@ryanolson7: could you please test your connection via a ping
adb shell
ping www.google.com
if you can't reach google, then I would appreciate if you paste somewhere your logcat in this way:
adb logcat | grep RIL > file.log
and just deactivate data, wait a few seconds, and activate it again.
---
I'll do some further tests on this branch (because some blobs may change from 1.0.1) but here in Spain both 3G & 2G data seems to works well, need to find a place with HSPA+.
Are you in the USA? I'm asking because this rom is based in open_eu release ( AFAIK they are the same except for radio capabilities )
Thanks for the feedback
Great Job!
Thanks! Tried and working. I have even received a update, and still working smooth!
can you tell me about the creating this ROM process?
I'm using US rom, I just want to use these blobs to make a custom builds, but flashing all the images bricked my phone. Can you explain me about the steps you did to package this ROM?
paziusss said:
...
Feedback is welcome
Click to expand...
Click to collapse
@ paziusss:
Maybe a littele bug: The app "calendar" starts everytime when your build will be booted - without open it separetly.
im new here
i want to know if i can use this in my nexus 4 multirom android 4 KK
Need FF OS 1.3
Can anyone please provide me zip file of FF OS 1.3?
Thanks
LinuxHolic said:
Can anyone please provide me zip file of FF OS 1.3?
Thanks
Click to expand...
Click to collapse
Not quite a zip, but, https://daylightpirates.org/b2g_inari_nightly_builds/
Bad Luck
Deathwish238 said:
Not quite a zip, but, https://daylightpirates.org/b2g_inari_nightly_builds/
Click to expand...
Click to collapse
I flashed the latest nightly build and everything went fine but my mobile is sitting on Fox now and restarts constantly
Look
LinuxHolic said:
I flashed the latest nightly build and everything went fine but my mobile is sitting on Fox now and restarts constantly
Click to expand...
Click to collapse
groups [dot] google [dot]com/d/msg/mozilla.dev.b2g/dENpc-7Fbi4/80t6EyS6bwIJ
is the included radio for european or american zte opens?
@hecatae:
blobs were pulled from 1.1.0B02 - UK but radio firmware should be the same for both UK and US versions
paziusss said:
Hello again:
Build B2G for ZTE Open (inari) is tricky.
Feedback is welcome
Click to expand...
Click to collapse
HI!
Can you build with added Russian keyboard?
I wanna use 1,2. Because it have RU locale, but have not keyboard.... (((
At 1.1. have not RU locale, but it have RU keyboard
FM radio doesn't work, no sound.
Japanese?
Could someone enable the Japanese keyboard and provide a ROM? I can explain how to do it, just can't build for it
thanks
thanks for your rom
Hi all!
As Sony has posted instructions on how to compile Android Pie for our XZ (among others), I just wondered if anyone here has tried it?
The posted guide looks quite straight forward, but as I have no experience on using fit-repost and such I'm not sure I'm up for the challenge of taking this project on.
If tried, what could be expected to work? I know that for all previous Xperia devices, camera and wifi components has always been weak-points in AOSP-roms..
Please discuss and advice!
Regards, Static.
I'm currently trying to build android P for XZ with the guide from Sony.
I'm downloading the code ATM.
I'll give you feedback about my journey to Pie ^^
Awesome!
I'm eager to hear about your endeavors in this!
L'ily said:
Hey me too, do you have a single- or dual-SIM variant?
Click to expand...
Click to collapse
I have a single sim variant
L'ily said:
Nice, I have the F8332 so we can test on both models. I have no idea what I'm doing though and whilst an unofficial GApps 9 build is available (albeit only in Stock) it doesn't appear Sony have released the vendor images yet so even if we successfully build I'm disinclined to believe they'll boot, although I'm going to try with the last release anyway.
Click to expand...
Click to collapse
Didn't Sony released beta vendor images for kernel 4.9 ?
I thought that would be compatible with pie.
That being said, it should be bootable without it. We will just have to check the kernel version and flash the vendor image accordingly.
@L'ily and I have been trying to build Pie for F8331 and F8332 but sadly it didn't work ...
The first issue we had was with the repo syncing. On my end it took an incredible 48h (@400KB/s peak) and also failed 3 times but by relaunching it I made it to the end. My partner however had a worst yet faster time with syncing. Maybe it is due to localisation (Australia and France) . We think it is simply because the repos weren't ready. I mean they are still no vendor files for Pie.
Second issue was with building. None of us could get through it. We kept having an error (see screen shot). It seams like it is a file missing but we didn't know we're to look for it as the sync was complete.
We tried both engendering build and userdebug. Same error.
@L'ily also tried build Oreo but it didn't work either ...
If anybody has an input on what we could do we would be grateful
Cheers,
Ickule
Here is the screenshot I mentioned in my previous post.
I forgot to include it ...
Ok so I managed to get through the building process. The missing files have matching name with files in an other folder (4.4 instead of 4.9).
That being said it sadly didn't boot.
That was kind of expected if you ask me ^^'
Still I don't get why i didn't had the files in the first place ...
Any input guys ?
I'm currently trying to build Pie myself (for the 309234023492094th time in the last two days) with other errors every time I set up a new machine. But what I can say about the error with the missing kernel file is that there's a script in the sony repos that looks like it'd be building the missing file, although I'm not sure if we have to call it manually first
31, so single-sim and unfortunately, I don't have the logs anymore as I always started with fresh machines.
I'm currently checking the other forums because I'm not really satisfied with the solution of using 4.4 kernel binaries with a 4.9 build
Edit: I might have achieved something, I compiled the kernel from 4.9 sources I hope and it's now building. Fingers crossed ?
Edit 2: It boots!
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Ickule said:
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Click to expand...
Click to collapse
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Magic-Fabi said:
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Click to expand...
Click to collapse
So you managed to get Pie working or only compiling the kernel ?
Thanks for clarifying the 31 thing
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Xperia z1 has carbon Android pie and gapps link
This may help you.
Magic-Fabi said:
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Click to expand...
Click to collapse
That's awesome !
Did you dio anything special aside from the instructiosn sony gave ?
I try to build Pie and the Kernel by the books but i always seam to fail for some reason ^^'
I'm usung Ubuntu 18.04 for the building OS.
No, all I used was Sony's guide and referenced Google's build instructions for the libraries I have to install. For the missing kernel file I used their (manual!) Kernel compilation guide
I used Ubuntu 18.04 LTS as well, the only "unusual" thing I did was that I didn't install any openjdk version and even deleted the one preinstalled as they have openjdk bundled with aosp ?*
Edit: Note that you have to copy and rename the compiled kernel file in arch/arm64/boot/Image.gz-dtb to kernel-dtb-kagura in /kernel/sony/msm4.9/common-kernel. You can easily read past that as I did in the beginning
Well let's assume I had a bad syncing time or something cause I followed the very same instructions ^^'
Anyway, it seam like we still miss the vendor files from sony so ...
I'll give it another shot when they'll be out.
Just a curious thing, will GCam work on Pie like it did on AOSP Oreo?
I believe the requirement for GCam is Camera API 2 and raw support which is built into AOSP.
It surely will be compatible.
Hello
For the past couple (weeks) I've been trying to compile Android 10 for tenderloin using the Android 9 sources but it's not going so well. First thing I ran into multiple sepolicy errors and I feel as if I fixed them in inappropriate ways but the errors went away. Other errors regarding camera and audio and such, that are regarding that tenderloin no longer uses the legacy audio format. Made me confused because I used the device sources form Evervolv and DIrty unicorns and if i'm correct they built it exactly the same way they uploaded it. After these errors were wrapped up, I got a error at zipping the rom that it could not zip due to failure of being able to read build.prop. This made me believe that the sources are not correctly formatted. If anyone can help me find a manifest, I can build for all you guys. Please keep tenderloin alive!
Now, I did something and I'm getting plenty of perl errors. Maybe I'm just very unlucky. I'm gonna attempt to reinstall on a fresh drive on my server.
If its anyone's concern, I was building lineage 17.1. I noticed for example, Lineage's "qcom-device" repo was shaped completely differently than Evervolvs qcom-device repo.
This led me to thought that Android 10 is going to be extremely difficult because of all the upstream dev changes that was pushed to Q. If any of you would like, I could probably push out March patches Pie rom because over there I'm mostly safe of complying with the source.
My manifest shape
DirtyUnicorn's device-tree
DirtyUnicorn's device-tree-common
DirtyUnicorn's htc-msm8960-kernel
Evervolv's vendor
And dirty unicorn's atheros wlan driver
I have been changing up the device tree so much, it almost looks ridiculous . From what I heard lots of properties on the device tree haven't been touched for years. Maybe tomorrow I can try Evervolv's Q rom. If you guys can help me build up my manifest, we can push out a fully working Q rom for tenderloin. And it would be just in time when Android 11 comes out. Thank you everyone!
I wish that I could offer any help, but I never tried to compile any Android ROM or for the HP_TP.
To my knowledge the only users that I know that could offer some insight on the process would be:
@flintman
@elginsk8r
Also the LuneOS project could offer some help:
https://pivotce.com/tag/luneos/
If Android Q(10) can not be ported to the HP_TP, then at least P(9) is a good ROM to keep updating that could provide many years of App support.
Theres no reason why exactly it cant,, because lots of roms I hear were built off the original TP sources (From 2011!). It was only around 2016 when guys around here had to change it up so much that they should've been so surprised that it worked. I can try and temporarily maintain P roms until the boys around here push out sources for Q!
djared704 said:
Theres no reason why exactly it cant,, because lots of roms I hear were built off the original TP sources (From 2011!). It was only around 2016 when guys around here had to change it up so much that they should've been so surprised that it worked. I can try and temporarily maintain P roms until the boys around here push out sources for Q!
Click to expand...
Click to collapse
To my limited knowledge is all about Hardware -->> Drivers -->> ( Kernel ).
The reason that Bluetooth and camera does not work on newer Android version is due to the old (proprietary drivers) and the Kernel. That takes more dedication and work than the ROM. The same rules applies to the desktop, older processors does not support certain features and the Operating System will not run. It is possible to disable the features in the kernel so that it does not check the hardware and make it run, but it will be unstable.
Everything could be possible with plenty of time, knowledge and dedication.
HP_TOUCHPAD said:
To my limited knowledge is all about Hardware -->> Drivers -->> ( Kernel ).
The reason that Bluetooth and camera does not work on newer Android version is due to the old (proprietary drivers) and the Kernel. That takes more dedication and work than the ROM. The same rules applies to the desktop, older processors does not support certain features and the Operating System will not run. It is possible to disable the features in the kernel so that it does not check the hardware and make it run, but it will be unstable.
Everything could be possible with plenty of time, knowledge and dedication.
Click to expand...
Click to collapse
When I look at the tenderloin source, the script to gather the camera driver is disabled. Camera isnt a huge deal though because its only 1.3 MP. However we use the MSM 8960 kernel from HTC and that is the one m7,, but the one m7 is a SD 600 device so it loses sense. I was gonna get some help with one of my kernel developer buddies to dev a kernel for android 10 for tenderloin. If you see the one m7 has Lineage 17.1 available and even though it doesnt have same chipset, if im correct both chipsets went off of the same assembly line process. Lineage 17.1 for the one m7 also packages it as a "uimage" which is what we use. I believe this was only a very small select of devices. Yeah about that ive been getting so many complaints during build about "mkimage" which should've been a prebuilt tool in the lineage source. Don't know why they removed it, or if our developers added it in by their selves, etc. Anyways I fixed that error by just "allowing" mkimage in one of the permission files in my environment. But yeah i went as far as the build packaging the ROM and it complaining it cannot read build.prop. Note the build.props are generated by the environment , not the source (even though the device data is gathered by the source, its not what im talking about). I even go to the directory it was complaining about and it was all there. One of my friends suggested a permission error. I changed permissions to 777 (rw to all users) and it would still output that error. By that point I trashed my build meaning I may of done something wrong early on. I will let someone else continue building 10 but I will continue building 9 with latest patches.
It will be extremely impressive if any kernel developer will update the HP Touchpad Kernel or tweak it for future release, well everything will stop once Android becomes 64 only.
I am sure you are very well aware, but I will suggest using this built:
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512
I was able to do the following playing around recompiling the Kernel. I recompile almost all the ROM and incorporated the same kernel changes.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Ramdisk is also very easy to unpack and repack:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
There is no need to get the original Camera or Bluetooth working, only sound and WiFi.
HP_TOUCHPAD said:
It will be extremely impressive if any kernel developer will update the HP Touchpad Kernel or tweak it for future release, well everything will stop once Android becomes 64 only.
I am sure you are very well aware, but I will suggest using this built:
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512
I was able to do the following playing around recompiling the Kernel. I recompile almost all the ROM and incorporated the same kernel changes.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Ramdisk is also very easy to unpack and repack:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
There is no need to get the original Camera or Bluetooth working, only sound and WiFi.
Click to expand...
Click to collapse
I think I probably stated somewhere, but Evervolvs "device" tree would just spit out hundreds of errors, and I fixed this by switching to Dirty Unicorns device tree. I also tried flintman's device tree and it didn't spit out many errors. Thanks for this though.
djared704 said:
I think I probably stated somewhere, but Evervolvs "device" tree would just spit out hundreds of errors, and I fixed this by switching to Dirty Unicorns device tree. I also tried flintman's device tree and it didn't spit out many errors. Thanks for this though.
Click to expand...
Click to collapse
I have only recompile the Kernel and all of them work, but the correct branch must be use. I can not say about building a ROM, never done it.
But Evervovs Pie by elginsk8r works very well and stable as it uses the same kernel, but the framework is different. I guess elginsk8r will be the only that can guide you on the right direction or flintman.
Have fun learning, it takes a lot of TIME!