Related
Ok, I'm trying to do something fun with my phone... (Hisense EG909 MSM8625)
Since hisense is keeping the source code, so I'm trying to build the source from codeaurora.org ics branch M8625SSNSKMLYA1015 (to keep the same version with my current stock ROM)
I've successfully compiled the kernel with the ndk but I'm stuck on getting it to boot.
It just show the carrier logo (bootloader). I can't get the bootanimation to load.
I'm not expecting things like wifi / bluetooth or even the radio works... but I'm just trying to at least get it to boot the launcher
I have experience in c/c++ but I know nothing about android and just started to learn it...
Can anyone point me on how to debug or see what's wrong with the kernel?
Is there any way to show something on the screen? I mean turning on the frame buffer
I've search and tried many method like altering the command line "console=tty0", adding "CONFIG_MSM_FRAMEBUFFER", etc..
but seems like nothing works, it just stuck there...
the way I build is:
1. downloading code from caf
2. pulled config.gz from my working phone... but it require some hisense stuff. so I'm using the configs that come with the code
3. tried both msm7627a_defconfig and msm7627a-perf_defconfig,
4. extract current working boot.img
5. substitute the kernel with my compiled zImage, and repack the boot.img
Am I missing something here?
million thanks for your help...
Looks like you are missing some hardware drivers. Why not find the lines in defconfig mentioning "hisense stuff" and search at Google or "searchcode.org" to see if drivers are available. And then patch your source as necessary.
sharonsym said:
Ok, I'm trying to do something fun with my phone... (Hisense EG909 MSM8625)
Since hisense is keeping the source code, so I'm trying to build the source from codeaurora.org ics branch M8625SSNSKMLYA1015 (to keep the same version with my current stock ROM)
I've successfully compiled the kernel with the ndk but I'm stuck on getting it to boot.
It just show the carrier logo (bootloader). I can't get the bootanimation to load.
I'm not expecting things like wifi / bluetooth or even the radio works... but I'm just trying to at least get it to boot the launcher
I have experience in c/c++ but I know nothing about android and just started to learn it...
Can anyone point me on how to debug or see what's wrong with the kernel?
Is there any way to show something on the screen? I mean turning on the frame buffer
I've search and tried many method like altering the command line "console=tty0", adding "CONFIG_MSM_FRAMEBUFFER", etc..
but seems like nothing works, it just stuck there...
the way I build is:
1. downloading code from caf
2. pulled config.gz from my working phone... but it require some hisense stuff. so I'm using the configs that come with the code
3. tried both msm7627a_defconfig and msm7627a-perf_defconfig,
4. extract current working boot.img
5. substitute the kernel with my compiled zImage, and repack the boot.img
Am I missing something here?
million thanks for your help...
Click to expand...
Click to collapse
if you can't extract original defconfig (config.gz) from device, it would be hard to have bootable kernel.
Sent from my Oppo N1 using Tapatalk
Hi All,
Ive been trying to building AOSP myself and every time i boot it has no gsm. (phone is reporting IMEI as Unknown). I must be missing a step but I cant work out what.
My N5 is currently running the latest developer release of Lollipop including bootloader and radio.
Heres what I did:
1. Repo init with no branch set (master branch)
2. repo sync
3. extracted the binaries from my N5 using a modified 'generate_packages' (essentially it adb pull's the files from the connected N5)
4. setup build environment
5. lunch with aosp_hammerhead
6. make
I'm confident that i've done everything (looking at guides) but it still has no radio
eskemo said:
Hi All,
Ive been trying to building AOSP myself and every time i boot it has no gsm. (phone is reporting IMEI as Unknown). I must be missing a step but I cant work out what.
My N5 is currently running the latest developer release of Lollipop including bootloader and radio.
Heres what I did:
1. Repo init with no branch set (master branch)
2. repo sync
3. extracted the binaries from my N5 using a modified 'generate_packages' (essentially it adb pull's the files from the connected N5)
4. setup build environment
5. lunch with aosp_hammerhead
6. make
I'm confident that i've done everything (looking at guides) but it still has no radio
Click to expand...
Click to collapse
I'm just trying to figure out what Binaries I need for L too. I used the CM extract-files.sh which is very similar to what I imagine you've used, but it will only create /vendor/lge. I'm trying to work out what I need for /vendor/qcom anf /vendor/broadcom as they're missing. They could affect Radio if you haven't got them too...
I just used:
[aosp_folder]/device/lge/hammerhead/self-extractors/generate-packages.sh
But changed line 247 to:
adb pull $FILEDIR/$ONE_FILE
Obviously I had my N5 ruining the latest Dev preview attached
Sent from my Nexus 5 using XDA Free mobile app
eskemo said:
I just used:
[aosp_folder]/device/lge/hammerhead/self-extractors/generate-packages.sh
But changed line 247 to:
adb pull $FILEDIR/$ONE_FILE
Obviously I had my N5 ruining the latest Dev preview attached
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm didn't know that was there... Looks like it creates broadcom and qcom already
Edit, well that generate creates the same 3 shell scripts as I downlaoded here:
http://nosemaj.org/howto-build-android-kitkat-nexus-5
Do we know that qcom and broadcom are not version / branch specific? When I run the script, it creates KOT49H from source. What is that line 247 amendment actually doing?
The modification pulls the files from a connected device via and. So in my case it would pull the binaries for the developer preview and thus lollipop compatible drivers
Sent from my Nexus 5 using XDA Free mobile app
Search google "nexus binaries preview", try that
Sent from my Nexus 5 using Tapatalk
I tried those that's why I decided to extract from a device running the preview instead. Also I've read that the Google hosted binaries don't have all the files which is why extracting seems better.
Sent from my Nexus 5 using XDA Free mobile app
I used to use these for SlimRoms KK
<manifest>
<project name="TheLoonyBin/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="kk4.4" />
<project name="TheLoonyBin/proprietary_vendor_qcom" path="vendor/qcom" remote="github" revision="kk4.4" />
<project name="TheLoonyBin/proprietary_vendor_broadcom" path="vendor/broadcom" remote="github" revision="kk4.4" />
</manifest>
Apparently they have been updated to LP now, with the preview stuff, so if you pull from the correct branch, it should work. I'm going to try it.
I'll give it a go too. I may flash stock 4.4 first then my build. Maybe it's related to the radio version or bootloader
Sent from my Nexus 5 using XDA Free mobile app
eskemo said:
I'll give it a go too. I may flash stock 4.4 first then my build. Maybe it's related to the radio version or bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Shouldn't be if you flashed the preview.
I've still got my October 2013 Bootloader.... I flashed Preview via a zip with the radio. I guess as long as you have the latest radio, it cant be that...I've flashed AOSP builds (not by me) and they worked. Not sure where those guys are getting their binaries
Your build doesn't flash Cache does it?
Yeah on the loonybin just update the revision. Im at work now so probably wont get to do a good test until.. well weekend actually... I dont even know that my build env will work properly as I havent fully tested it since rebuild to Mint.
beekay201 said:
Search google "nexus binaries preview", try that
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks! Found this link:
https://developers.google.com/android/nexus/blobs-preview
I've been doing a flashall so it does flash boot, cache, user data, and system. Does that make a difference?
Sent from my Nexus 5 using XDA Free mobile app
eskemo said:
I've been doing a flashall so it does flash boot, cache, user data, and system. Does that make a difference?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
With your build?
Not in itself, however the IMEI etc symptoms you report in your OP have been seen regularly with a "bad" cache flash, so I suppose first thing to test is to take it back to a fully working state and flash just system and boot. If for no reason other than eliminating it as the cause.
I'll give that a go then. It seems quite likely by the sounds of things.
Sent from my Nexus 5 using XDA Free mobile app
No one have tried the new ROM Copperhead OS ?
Can i try to install it as secondary rom in MultiRom ?
I'm on Cyanogen CAF 12.1 now...
thank you all
chickygamon said:
No one have tried the new ROM Copperhead OS ?
Can i try to install it as secondary rom in MultiRom ?
I'm on Cyanogen CAF 12.1 now...
thank you all
Click to expand...
Click to collapse
Hi! I've installed it in multirom with a stock 5.0.1 as primary and it works, just tried it for few minutes.
just be sure to have the latest bootolader (HHZ12h) or installation will fail.
Flashing a bootloader
Hi,
I have a Nexus 5 and I use Multirom with it. My default ROM is Lollipop 5.1.1 and a secondary ROM, which I mostly use, is Marshmallow 6.0 (xTraSmooth). I want to install CopperheadOS, but it says when installing, that I must have HHZ12h bootloader in order to install (as stated in a previous post). My current bootloader is HHZ11k. If I install HHZ12h bootloader by flashing a zip file which includes LMY48B_Radio+Bootloader-HHZ12h will it cause anything that prevents Lollipop or Marshmallow to work properly?
ithippi said:
Hi,
I have a Nexus 5 and I use Multirom with it. My default ROM is Lollipop 5.1.1 and a secondary ROM, which I mostly use, is Marshmallow 6.0 (xTraSmooth). I want to install CopperheadOS, but it says when installing, that I must have HHZ12h bootloader in order to install (as stated in a previous post). My current bootloader is HHZ11k. If I install HHZ12h bootloader by flashing a zip file which includes LMY48B_Radio+Bootloader-HHZ12h will it cause anything that prevents Lollipop or Marshmallow to work properly?
Click to expand...
Click to collapse
You don't need to downgrade the bootloader, just modify the updater script of the rom ( deleting the string containing the bootloader version or replacing with your current version), then it will install just fine.
Can anybody provide link on COPPERHEAD OS ? CHEERS!
Pretoriano80 said:
You don't need to downgrade the bootloader, just modify the updater script of the rom ( deleting the string containing the bootloader version or replacing with your current version), then it will install just fine.
Click to expand...
Click to collapse
Thanks! I haven't tried that yet, but I will. First I thought I can just replace HHZ12h with HHZ11k using text editor, but then I noticed there are guides which suggest that it isn't quite that easy. I might be wrong about that, will see when I have enough time to read up on the subject.
Sent from my Nexus 5 using XDA Free mobile app
ithippi said:
Thanks! I haven't tried that yet, but I will. First I thought I can just replace HHZ12h with HHZ11k using text editor, but then I noticed there are guides which suggest that it isn't quite that easy. I might be wrong about that, will see when I have enough time to read up on the subject.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It's easy, just extract the rom, go to Meta-Inf/com/google/android and modify the "updater-script". That's all, rebuild the zip and flash in recovery.
Edit: you can do it without using a PC, by using a file manager on your device.
Ross Korolov said:
Can anybody provide link on COPPERHEAD OS ? CHEERS!
Click to expand...
Click to collapse
here it is
https://copperhead.co/android/
....
Is this rom any good?
bonedriven said:
Is this rom any good?
Click to expand...
Click to collapse
Just installed it on a Nexus 5x and it works flawless. It has most of the standard stuff but is different from the rest in that it is supposed to be security oriented. That means no default root (but rooting should be possible).
I didn't try to add Google stuff yet and probably won't even try to add that spyware but it does have the F-Droid app store.
There are some extra options to secure the memory if required, and the documentation is (so far) very good (for example the install guide and the technical overview).
Currently running it on my Nexus 5x and N5. works great. Anything you are missing you can find on F-Droid. I find the lack of data usage to be delightful; when facebook or ebaum videos auto load on other software, they are stopped on copperhead. very happy with the security.
The only thing i can not make work is voice to text, and I have a ticket in with copperhead. who cares, I have fast thumbs.
Nexus + Copperhead = Happy Gopher!
mg.degroot said:
Just installed it on a Nexus 5x and it works flawless. It has most of the standard stuff but is different from the rest in that it is supposed to be security oriented. That means no default root (but rooting should be possible).
I didn't try to add Google stuff yet and probably won't even try to add that spyware but it does have the F-Droid app store.
There are some extra options to secure the memory if required, and the documentation is (so far) very good (for example the install guide and the technical overview).
Click to expand...
Click to collapse
happy_gopher said:
Currently running it on my Nexus 5x and N5. works great. Anything you are missing you can find on F-Droid. I find the lack of data usage to be delightful; when facebook or ebaum videos auto load on other software, they are stopped on copperhead. very happy with the security.
The only thing i can not make work is voice to text, and I have a ticket in with copperhead. who cares, I have fast thumbs.
Nexus + Copperhead = Happy Gopher!
Click to expand...
Click to collapse
Thanks for the feedback. I guess manual apk installation is also possible?
I'm thinking about picking up a Nexus 5 as a backup device, and CopperheadOS seems like something fun to play with, instead of just installing CM13. Can I install TWRP as recovery on devices like the Nexus 5 that don't check for locked bootloaders? Can I run it as basically another ROM –*unlocked developer options, root, TWRP, etc.? I realize the OS exists for enhanced security, but I'd like to make a few tradeoffs.
Unfortunately, you can not run TWRP with copperhead, it wants full control of the phone for security reasons. Its not meant to be a developer OS with access to all the bits, so you kind of need to want a OS in a box that you can deal with.
But I have to say, despite its shortcomings of not having google services, it works pretty much flawless on my 5 and 5x. i miss google maps app, but it works 100% via chromium browser as a favorite, and I have only found 2 apps I can not import via apkmirror, one being Waze, the other is my local public transportation app. other than that, i feel like I'm safe from prying eyes.
Hg
happy_gopher said:
Unfortunately, you can not run TWRP with copperhead, it wants full control of the phone for security reasons. Its not meant to be a developer OS with access to all the bits, so you kind of need to want a OS in a box that you can deal with.
But I have to say, despite its shortcomings of not having google services, it works pretty much flawless on my 5 and 5x. i miss google maps app, but it works 100% via chromium browser as a favorite, and I have only found 2 apps I can not import via apkmirror, one being Waze, the other is my local public transportation app. other than that, i feel like I'm safe from prying eyes.
Hg
Click to expand...
Click to collapse
Thanks for your response. I'm a fan of CyanogenMod, and I'm not unhappy their security or features, but I wanted to play around with CopperheadOS. I understand the tradeoff between security and convenience, but I'm not willing to sacrifice TWRP in the mix. Oh, well – if I ever have need of an OS solely for its security track record, I know where to go.
It doesn't look to me like Copperhead is supporting the Nexus 5 anymore. Can somebody confirm or is there a link I'm missing somewhere to the ROM?
EDIT: Yep, I knew it was deprecated for a while now but they've even removed the deprecated ROM from the site now. I'd appreciate it if anybody has the last ROM if they could pass it my way.
NewDayRising said:
Thanks for your response. I'm a fan of CyanogenMod, and I'm not unhappy their security or features, but I wanted to play around with CopperheadOS. I understand the tradeoff between security and convenience, but I'm not willing to sacrifice TWRP in the mix. Oh, well – if I ever have need of an OS solely for its security track record, I know where to go.
Click to expand...
Click to collapse
Switch debugging OFF and don't lock bootloader after CopperheadOS install and u will be able to boot TWRP via
fastboot boot recovery.img [TWRP]
I'm currently experimenting with root privileges on CopperheadOS on Nexus 5X. Still haven’t tried xposed framework.
Security features r quite good, especially different lock code && encryption password and memory protection, but, there is a lack of fine privacy control (Privacy Guard) as in CyanogenMod and firewall, hence the need for root.
CopperheadOS on Nexus5
dnaod said:
It doesn't look to me like Copperhead is supporting the Nexus 5 anymore. Can somebody confirm or is there a link I'm missing somewhere to the ROM?
EDIT: Yep, I knew it was deprecated for a while now but they've even removed the deprecated ROM from the site now. I'd appreciate it if anybody has the last ROM if they could pass it my way.
Click to expand...
Click to collapse
I've been using CopperheadOS for a few weeks now on the Nexus5. Received the latests OTA a few days ago and applied without issue.
Installed it via TWRP. Have rooted the device with SuperSU, though have to re-root after re-flashing recovery after each OTA.
It's been working great.
Unfortunately I don't have the img any more
The one I flashed was https://builds.copperhead.co/builds/hammerhead-factory-2016.08.09.06.24.33.tar.xz
download link
dnaod said:
It doesn't look to me like Copperhead is supporting the Nexus 5 anymore. Can somebody confirm or is there a link I'm missing somewhere to the ROM?
EDIT: Yep, I knew it was deprecated for a while now but they've even removed the deprecated ROM from the site now. I'd appreciate it if anybody has the last ROM if they could pass it my way.
Click to expand...
Click to collapse
https:// builds.copperhead.co /builds/hammerhead-factory-2016.09.07.19.27.04.tar.xz
Remove spaces. I'm a new member and can't post links.
Update: I've started working on my own ROM. So, I'll be focusing on that project for a while. You can check it out here: http://forum.xda-developers.com/mot...rhinonized-textnow-rom-moto-e-surnia-t3418606
CM 13 offers AOSP type default build properties that at times pushes our Moto E over it's hardware limits, causing freezing, stuttering etc...
I've dealt with these issues constantly on CM 13 Nightly builds, during heavy usage. I decided to port Motorola's Stock Build tweaks to CM 13 to see if they helped the above issues, during heavy usage and I'm happy to report that it has increased CM 13's stability drastically. No more poor performance issues with multitasking!
I flash CM 13 Nightly daily, so, I'll post a new build.prop zip file after I flash, that you can flash, after flashing the new Nightly.
Instructions:
1. Flash the below zip file after flashing the correlating CM 13 Nightly, with matching build number. Example: 20160625.
2. Wipe Dalvik and Cache then reboot.
Note: Property changes are tagged in the below build.prop file. Please unzip and look over the file to review changes.
Sent from my XT1526 using XDA-Developers mobile app
Google CM 13 Smooth Project
I use Google Now and the Moto E on CM 13 has a lot of Google Now Launcher and Google App redraw issues, due to our RAM constraints, causing a sluggish experience when switching from memory intensive apps, especially when using encryption.
Here's a simple flashable zip, containing a local.prop file that attempts to lock Google Now in memory, reducing redraws, creating a much smoother experience for those that use Google's Launcher and CM 13 on the Moto E.
My goal in this thread is to provide simple flashable zips on top of CM 13 Nightlies that increase stability, when using Google and CM 13. ?
Instructions:
1. flash in your favorite recovery on top of any Lollipop/Marshmallow Rom, when using Google Now Launcher.
No Computer CM 13 Install
For those having issues installing CM 13, getting abort error ”Sprint CDMA variant detected! Reboot into Bootloader Mode, connect your device to PC” and don't have access to a computer, follow the steps below.
Instructions:
1. Install "RAR" from the Android market
2. Download CM 13
3. Open RAR
4. Remove/Rename .txt from the below updater-script
5. Cut and paste the below updater-script file in the CM 13 zip in this location: META-INF/com/google/android
Note: Do not unzip the CM 13 file, cut and paste the updater-script directly in the CM file using RAR to avoid corrupting the CM zip.
Side Note: The CM zip should recognize your carrier automatically during boot and use the proper apns-config.xml file. ?
Updater-script changes:
Replaced "abort" with "assert"
Reason: It's just the simplest way to force install CM 13 and still use Sprint during boot.
Reserved
Interesting find my friend, how did you think about doing it this way?
Awesome Thinking Going to test it soon
Can this fix work for other 6.0 based ROMs?
SykkNyzz said:
Can this fix work for other 6.0 based ROMs?
Click to expand...
Click to collapse
Which fix?
CM Nightly 20160707 mod added for download, check first post. Please look over Build.prop for changes.
Changes Include:
Dalvik Memory Optimized
Motorola Device Properties Added
and more...
dearmasfamily said:
Which fix?
Click to expand...
Click to collapse
Can this fix other Custom ROMs based on CM13... Or just CM13
SykkNyzz said:
Can this fix other Custom ROMs based on CM13... Or just CM13
Click to expand...
Click to collapse
I'm not sure what you mean but there's only one way to find out, make a backup of your current rom, then give what you're trying to do a try. If it doesn't work just restore your backup.
SykkNyzz said:
Can this fix other Custom ROMs based on CM13... Or just CM13
Click to expand...
Click to collapse
Theoretically, yes but I haven't tested it yet
i might try this with MM RR later today, ill try to edit if i need to. i have a good backup so if need be ill just go back
Sent from my XT1526 using Tapatalk
Tried got error 7 when flashing with replaced updater script after verifying updated image.
Sent from my XT1526 using XDA-Developers mobile app
I've got an XQ-AS72 and have been trying to build an AOSP rom based on instructions from Sony Developer.
The first go-round, I couldn't find the proper "vendor image" a.k.a. software binaries a.k.a. "oem partition" from the site, and I ended up flashing oem (a/b) with the UNSINned version of oem_X-FLASH-CUST-2389.sin that came with the 58.1.A.3.87 firmware that I downloaded with XperiFirm, along with the output of the build. No boot.
I then tried flashing a few different things to the oem partition (among them a couple of official images from other phones from this page (CAUTION! DO NOT USE!!)), which didn't work because of, I guess among other things, a kernel version mismatch (binaries built for 4.14, I built against 4.19). Stupid, stupid me
I ended up having to put the phone in FLASH MODE and using Xperia Companion to do a system restore after multiple failed attempts at re-flashing partitions in fastboot, which gave me 58.1.A.5.55. I was able to get the thing booted. Using NewFalsher with the last known good firmware I had downloaded didn't help me in this case.
I have now re-unlocked the bootloader, cleaned my local repo structure, found the proper binaries from the proper page and am awaiting the long slog of the build process.
So, my question is: has anyone successfully built AOSP for this device before? Is there a lot of fenaggling that needs to be done? Or can the build be run against the files as they come down from the repos?
One thing that worries me, going through the manifest XMLs, is that the build target doesn't distinguish between the different variants, only giving one target (the AS52 variant with a smaller onboard mmc). Is there a need to manually create a new device .mk file and modify other .mk or .xml files to get a proper build?
TL;DR have you successfully built AOSP for the Xperia EDO platform, and do you have any tips to share?