Hello!
Im currently trying to build a vannila froyo 2.2 rom from the source! How do i flash the images when im ready? Is there something like fastboot on the g1 or htc magic?
Landroid
I haven't had the time to try to build myself, but wouldn't you be better off starting with the Samsung open source for your carrier/model rather than trying to figure out all the changes you'd need to make to get AOSP to run on the Tab?
BuglessFan said:
I haven't had the time to try to build myself, but wouldn't you be better off starting with the Samsung open source for your carrier/model rather than trying to figure out all the changes you'd need to make to get AOSP to run on the Tab?
Click to expand...
Click to collapse
Erhh - Samsung open source only contains the kernel. You need the rest of Android, which is what the AOSP is for!
Regards,
Dave
Don't know about the others, but the one for the SCH-I800 on VZW is not just the kernel. All of the things like the custom notification bar/settings for white and black levels, et cetera, go well beyond vanilla android in the Tab. I haven't gone through the platform.tar, but it has notices about stuff for, TouchWiz, et cetera (now whether it can actually run as built directly from what they've made available all bets are off, I know a direct compile of the kernel code didn't work for me, but I haven't had time to do more than a simple straight attempt to build and may have screwed something simple up). It's around 85MB for the DJ11 code for Verizon.
Edit: I'd understand if you needed most of it from AOSP though for a full build, and stand corrected.
And how do i flash the created system.img and data.img? The kernel will be in the zImage format as im going to build the kernel from samsung's opensource files!
Landroid said:
And how do i flash the created system.img and data.img? The kernel will be in the zImage format as im going to build the kernel from samsung's opensource files!
Click to expand...
Click to collapse
You don't. Samsung uses different partition layout and formats.
Use the Samsung tar files to overlay over AOSP as described in their readme file.
Ah ok! Thank you
from Readme file:
How to build:
< Kernel >
1. Unzip SPH-P100_Kernel.tar.
( You can find SPH-P100_Kernel.tar in the same directory with this README.txt . )
2. Refer another "README.txt" in the tar file to build the kernel source code.
< Platform >
* NOTICE *
Galaxy Tab is launched in many countries, including Europe and North Amarica.
S/W is almost the same but there are some differences between the European version(GT-P1000) and the US Sprint version(SPH-P100).
The open source codes to be open here are only the differences.
1. Get Android open source code:
: version info - Android froyo 2.2 (android-cts-2.2_r2)
( Download site : http://source.android.com )
2. Get GT-P1000 open source code
: GT-P1000_OpenSource.zip
( Download site : http://opensource.samsung.com )
Unzip it, then you will see the file GT-P1000_Platform.tar.bz2 which includes the platform source code.
3. Overwrite GT-P1000 Platform OpenSource to the Android open source.
4. Get SPH-P100 open source code:
: SPH-P100_OpenSource.zip
( Download site : http://opensource.samsung.com , version info : DJ14 )
5. Overwrite SPH-P100_Platform_DJ14 OpenSource to the Android + GT-P1000(European) Platform open source code.
6. Overwrite the Platform source code that comes from the Sprint version(SPH-P100_Platform_DJ30).
7. Do "make"
Click to expand...
Click to collapse
Landroid said:
And how do i flash the created system.img and data.img? The kernel will be in the zImage format as im going to build the kernel from samsung's opensource files!
Click to expand...
Click to collapse
If I understand correct. (for the kernel at least) You could just take a package like monks then swap out the zImage and *.ko files for the samsung ones. resign the zip. Then flash it from the clockworkmod recovery.
I believe we need repo init -b android-cts-2.2_r2 ... and overlay the Samsung tar contents on top of it.
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
I have successfully upgraded my Ideos X5 U8800 to 2.3.5 official Gingerbread, rooted it, and then repartitioned it using Blepart recovery. Subsequently I have checked out cm11 source, including Blefish repositories/code for the U8800 (thanks for good work, by the way!), compiled/built and installed a ROM. This was my first build.
OK. Good so far. Only I am looking to build cm10.1 because my goal is to eventually get this handset running Ubuntu Touch. Therefore, the next step is to get it running on cm10.1.
My problem is that I cannot find the source I need. I have tried to set up a fresh source tree and check out cm10.1 source combined with Blefish's source by specifying branch cm10.1 for the latter, using the files I used in .repo/local_manifests to get the cm11 device source etc. from Blefish. However, something seems to be missing as the lunch command fails and compilation aborts. Also, I can see that development has been discontinued on this branch for the U8800.
Any suggestions?
The cm-10.1 branch is deprecated, and I am not planning to update it as cm-11.0 is better in any way.
Is the Ubuntu Touch source code only based on cm-10.1 code though? Maybe you could have success using the cm-11.0 code as it is right now? I am not familiar to how Ubuntu uses the lunch commands, it might be different than Android's default.
Blefish said:
The cm-10.1 branch is deprecated, and I am not planning to update it as cm-11.0 is better in any way.
Is the Ubuntu Touch source code only based on cm-10.1 code though? Maybe you could have success using the cm-11.0 code as it is right now? I am not familiar to how Ubuntu uses the lunch commands, it might be different than Android's default.
Click to expand...
Click to collapse
Thanks for the quick response!
The Ubuntu Touch guide specifically states cm-10.1, but I will sign up with their forums and check whether I can use cm-11.
The following passage from the Ubuntu Touch Porting Guide gives the impression I might be able to base my work on cm-11? Would you agree?
"For quick reference, these are the current components used from Android:
Linux Kernel (stock Android kernel provided by the vendor, with a few changes to support some extra features needed by Ubuntu, such as Apparmor)
OpenGL ES2.0 HAL and drivers
Media (stagefright) HAL, to re-use the hardware video decoders
RILD for modem support
As Ubuntu is running as the main host on top of an Android kernel and the communication between the Android services and HAL happens via Binder, Sockets and libhybris. "
I am hoping this could work, as it would be a tremendous help, now that I have a running ROM built on 20 May with your source tree for the device specific code etc. which works like a charm! :good:
Best regards,
aribk
CLOUD_COMMANDER GHOST
Hi guys,
For all those who have tried our previous releases here comes a new version 1.4 A.KA Ghost.
Upcoming features include improvement of remote view and keyboard.
Creating an open-source engine for multi-platform and api exposure to third party.
We are also going to separate the engine from the main application so that other developers can work on it and implement a common platform for processing and executing android commands from xmls, this will allow for a universal platform where by all developers can improve how commands are executed from the core and also that the engine can be used by any shell software out there, thus opening doors from multi-platform development of the engine.
The commands created in this software will be stored in our server for now in the future you might expect multiple servers from different vendors, if you use the other method (XML editing) which is not recommended, please share you files with your users.
All bugs should be reported to [email protected]
RESERVED SHELL WORDS
qbox1 = This denotes the first user input box.
qbox2 = This denotes the next user input box.
qsquote = This denotes a single quotes(').
quote = This denotes double quotes (").
NB: PLEASE DON'T SEND COMMANDS THAT ARE NOT TESTED PERSONALLY!
EDIT:
Version 1.2 does not update tables since we shifted our servers to cloudflare and has some minor engine flaws thus it's obsolete.
Download the latest version to maintain commands compatibility.
SCANNED WITH BIT-DEFENDER ANTI-VIRUS
MAKE SURE YOU UPDATE TABLES REGULARLY TO GET THE LATEST UPDATE
DOWNLOAD_LATEST_GHOST_HERE
XDA:DevDB Information
CLOUD_COMMANDER 1.4 a.k.a GHOST , android devices (see above for details)
Contributors
kenkit
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Current Stable Version: 1.4
Stable Release Date: 2016-03-25
Current Beta Version: 1.4
Beta Release Date: 2016-03-25
Created 2016-03-08
Last Updated 2016-03-08
Android Scriptmaker is a little software piece which is able to make the required lines to set the right permissions in a recovery script.
The idea behind this script is to be able to make a flashable .ZIP out of any ROM, such as stock ROMs, custom ROMs that are unavailable anymore, etc.
This script is COMPLETELY compatible with the Unix Shell without any previous modifications.
Required installed software: grep, wc and cat. The script will test if your device lacks support of any of them.
Read more (documentation, download and usage): https://github.com/FacuM/android_scriptmaker
XDA:DevDB Information
Android Scriptmaker, Tool/Utility for all devices (see above for details)
Contributors
facuarmo
Source Code: https://github.com/FacuM/android_scriptmaker
Version Information
Status: Stable
Created 2017-02-03
Last Updated 2017-02-03