Database Users

(SOLVED) ICS CM9 ROM, status 6 error on attempted install

Hey guys,
I can't post in the development section, so I have to put it here. I am trying to flash the alpha preview of the ICS CM9 ROM. I was getting a status 7 error, so I commented out the first line in the installer script using Notepad++, and re saved, per ker2sgr's post here: http://forum.xda-developers.com/showthread.php?t=1490831&page=10. Now I am getting a status 6 error. I also tried re saving the file with different encoding (ANSI, unicode), and got the same result. Can anyone help?

Does it say anything more in the error message?

It (CWM) just says "installation aborted, and the status 6 error code. From what I have read, this is an encoding issue. I tried editing the file with Windows Notepad app, as well as with Notepad++. I tried flashing the ROM as it was originally written, and it gave the status 7 error, even with the assert check disabled.

This pre alpha build is for the thinkpad only and even then its not intended for all thinkpads just us and uk
Sent from my Galaxy Nexus using Tapatalk

I should have provided more info. I have a US version 32GB, with the latest update installed. Koshu helped me to solve it. I had only commented out the first line in the updater script, when I needed to uncomment the first two lines. I got it to install now! Thanks!

prosparky said:
I should have provided more info. I have a US version 32GB, with the latest update installed. Koshu helped me to solve it. I had only commented out the first line in the updater script, when I needed to uncomment the first two lines. I got it to install now! Thanks!
Click to expand...
Click to collapse
I thought u were someone asking me in a pm about me porting cm9 to the k1 (which I'm not) and thought this was about that glad u got it solved
Sent from my Galaxy Nexus using Tapatalk

[Thinktank]Bringing Jellybean to the Play -- Alpha GSM/CDMA [8/22]

Xperia Play Users,
I am currently working on bringing CM10 to the Play, and I'm looking for input from anybody else who has ideas.
The Rules:
Post something constructive, no "Good Luck" "reserved" etc. this thread is for working through problems when building CM10
That said.
Update: I'll be posting errors here, so it'll be easy to keep track of.
First error I hit (& fixed? (compiler hasn't failed yet on this one)) deals with hardware/qcom/display/libcopybit where copybit_c2d.cpp fails to compile with a couple of errors related to "KGSL_USER_MEM_TYPE_ION" is not declared. (iirc)
I fixed this (I think) by replacing CM10's qcom/display with caf's qcom/display
Second error: (Erroring out right now)
In-line kernel building. I'm getting a (possible) GCC compiler false error where it says
Code:
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c: In function 'wl_iw_set_pmksa':
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c:5335:5: error: array subscript is above array bounds [-Werror=array-bounds]
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c:5338:5: error: array subscript is above array bounds [-Werror=array-bounds]
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c: At top level:
cc1: error: unrecognized command line option "-Wno-unitialised" [-Werror]
Possible fix: for now turn off in-line kernel building until either error is solved.
Error 3 -- Removed in-line kernel building, but forgot to set device/semc/zeusc/prebuilt/kernel to copy to out/target/product/zeusc/kernel ... whoops
Error 4 -- The way things are sent to logcat has been changed from ICS
Code:
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function write_string:device/semc/msm7x30-common/liblights/lights.c:87: error: undefined reference to 'LOGE'
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function write_int:device/semc/msm7x30-common/liblights/lights.c:66: error: undefined reference to 'LOGE'
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function set_light_backlight:device/semc/msm7x30-common/liblights/lights.c:131: error: undefined reference to 'LOGV'
Fixed by copying over liblights/ from jellybean version of msm7x30-common/
Error 5 -- Same error happens with msm7x30-common/libsensors/
Fixed the same way as error 4
Error 6 -- Last error I'm gonna talk about tonight:
I did (apparently) a half baked revert to using a prebuilt kernel & it just bit me in the butt. I'll fix it tomorrow & keep updating this.
Fixed it by using half of FXP's custombootimg.mk where it calls (PRODUCT_OUT)/kernel instead of (TARGET_PREBUILT_KERNEL)
Anybody else up for learning with me & briniging JB to the Play?
Pax
UPDATE: Pre-alpha release are available here: http://www.mediafire.com/?6ggud46a7c6cq
Latest kernel is here: http://forum.xda-developers.com/showpost.php?p=29498363&postcount=233
Remember, this is an alpha, a lot of stuff does not work. Please logcat any errors you find, otherwise (unless it's something like baseband unknown) I WILL IGNORE THEM
What Works:
CDMA Data
Calls
SMS
AUDIO!!
HW Video
GPS
What Doesn't Work:
Haven't tested to much, you guys tell me

I came across this by googling, hope that helps :
http://forum.xda-developers.com/showthread.php?t=1104142&page=4
Cheers, I'm willing to learn if you don't mind teaching a newbie in dev
Sent from my Play using xda app-developers app

sasukekun67 said:
I came across this by googling, hope that helps :
http://forum.xda-developers.com/showthread.php?t=1104142&page=4
Cheers, I'm willing to learn if you don't mind teaching a newbie in dev
Sent from my Play using xda app-developers app
Click to expand...
Click to collapse
Thank you, I think for JB CM wants to use -O2 when compiling so I'm not gonna touch that one (for now)
A Good place to start would be with Keiran's building ICS tutorial with some changes.
First off, I'm using Ubuntu 10.04 LTS, but Ubuntu 12.04 LTS *should* work (no guarantees)
To download the vendor tree (vendor/semc)
use this instead of what Keiran has (koush cleaned out a lot of the vendor trees out of his git, and mine is outdated)
Code:
git clone https://github.com/kali-/proprietary_vendor_semc.git -b ics semc
also, I'm using the ICS device tree (same as keiran) instead of JB because the JB tree's are not 100% functional right now.
Pretty much if you follow that (& I suggest instead of doing make -j# bacon do mka bacon) & run into any errors, i'll help with whatever suggestions I might have (or anybody else)
Note: If somebody needs help trying to build AOKP, I'll help, but I'm not as familiar with the source as I am with CM
Pax

Also, before I forget, here a how-to sync caf's (code aurora forums) repo (similar to cm/AOSP/etc)
https://www.codeaurora.org/xwiki/bin/QAEP/
The branch I synced was jb.
Pax
Sent from my R800x using Tapatalk 2

First build is complete, I'm need to make a nanadroid & flash a new kernel (I'm on keics/CNA right now so it'll be a little bit before I post results )
Pax

hi,
it won't boot on sony ericsson hdpi devices without msm.... changes (look at mini pro thread you will find a lot of usefull information about it)
you need to enable triple buffer in the kernel

Thanks Nickholtus, i'll look into it.
Status 6 error in the update-script (really? off the cm-10 building ?!?!) so i'm working on that now...

if you can fix the framebuffer error in the kernel we have a fully booting rom
kamarush made a build for me (from cm10 sources) with play device tree (his own)
only that error is preventing a boot
edit: can you upload your current kernel?
i know a ugly fix to get it at least booting, but i am on holiday now and i only have a windows pc with slow internet and no kernel

nickholtus said:
if you can fix the framebuffer error in the kernel we have a fully booting rom
kamarush made a build for me (from cm10 sources) with play device tree (his own)
only that error is preventing a boot
edit: can you upload your current kernel?
i know a ugly fix to get it at least booting, but i am on holiday now and i only have a windows pc with slow internet and no kernel
Click to expand...
Click to collapse
I'll probably base it off either FXP or Mjolnir's kernel (sorry Lupus)
[sritke]Do you have a link with a how-to add in triple buffer? [/strike] CAF!! - https://www.codeaurora.org/gitweb/q...it;h=50c3bc621e2cf0c3587b1827d931738d148c33d8
UPDATE: Nickholtus, it's not this easy, is it?!?! https://www.codeaurora.org/gitweb/q...;hpb=1125e58c5744e1ad833e30e5d2a74eb6dca1ca20
Also, if anybody wants to try to fix the update-script, i've attached it

no i don't know, we think it is in msm_fb.c in the kernel source
see this post for more info: http://forum.xda-developers.com/showpost.php?p=29062634&postcount=177
edit:
i don't think so, but i can't try it.
kamarush couldn't find it (how to enable triple buffer) but if that's it it is an easy fix

nickholtus said:
no i don't know, we think it is in msm_fb.c in the kernel source
see this post for more info: http://forum.xda-developers.com/showpost.php?p=29062634&postcount=177
---------- Post added at 09:03 PM ---------- Previous post was at 08:58 PM ----------
i don't think so, but i can't try it.
kamarush couldn't find it (how to enable triple buffer) but if that's it it is an easy fix
Click to expand...
Click to collapse
Here's the best diff (all 3) i've found for the commit
https://www.codeaurora.org/gitweb/q...ff;h=acffb1675f468a85f528e01707f3fa98f45b77f8

i am going ask kamarush and see what he thinks
he thinks it can probaply fix it

While I'm no help for this, for the script stuff, can't you enlist the help of the supercharger guy? He seems to be pretty adept with script lark.
Obviously, that's coming from an outsider.

Sythedragon said:
While I'm no help for this, for the script stuff, can't you enlist the help of the supercharger guy? He seems to be pretty adept with script lark.
Obviously, that's coming from an outsider.
Click to expand...
Click to collapse
hahaha, different type of scripts, but thanks for the idea
Pax
Also: Made the changes in the kernel I have on hand, fxp's from cm9/10 source. I've added in the correct stuff to cyanogen_zeus_defconfig & mach-msm/board-semc_zeus.c as soon as I'm done downloading Doom's ndk, i'll try & build it & see if it works
Pax

kamarush is making the kernel for me, with triple buffer enabled
edit: haha you was faster

nickholtus said:
kamarush is making the kernel for me, with triple buffer enabled
edit: haha you was faster
Click to expand...
Click to collapse
I was, then I got arrowed in the knee
Or i would be, but then my git clone downloads at ~200 kb/s

Nickholtus,
Here's a test kernel, the changes are in the zImage, the ramdisk is FXP's from well, it's a source build off code from yesterday.

thanks
going to try it now
still the same error
edit: i need to get adb working
doesn't find the device

Lemme look into it, i'll test it out shortly (trying to get my build of cm10 to install )
Pax
Edit: Nickholtus, could you post a link to your build, mine just doesn't want to work
Pax
Edit 2: I think it's because i'm coming from CNA to CM10, i'm gonna build cm9 then retry with that
Pax

i can't upload my build, the upload speed here is 15kbps atm

Dolphin browser testers needed!

I'm looking for anyone running Android 4.1 JellyBean thats willing to report issues/bugs to the Dolphin Team thru logcat.
Logcat for JellyBean can be explained here http://forum.xda-developers.com/showthread.php?t=1847541

oops........
tarroyo said:
I'm looking for anyone running Android 4.1 JellyBean thats willing to report issues/bugs to the Dolphin Team thru logcat.
Logcat for JellyBean can be explained here http://forum.xda-developers.com/show....php?t=1847541
Click to expand...
Click to collapse
the link u gave does not work

nexussgeek said:
the link u gave does not work
Click to expand...
Click to collapse
I apologize, I updated the OP with a working link.

I can test for you....but I'd like to also make a request.
Can we please get the option to use flash back?? I understand it's not officially supported in JB, but it still works on our device on JB if you check the option to load flash content manually
I've got logcat set and ready to go. I'll update dolphin and post one shortly

hp420 said:
I can test for you....but I'd like to also make a request.
Can we please get the option to use flash back?? I understand it's not officially supported in JB, but it still works on our device on JB if you check the option to load flash content manually
I've got logcat set and ready to go. I'll update dolphin and post one shortly
Click to expand...
Click to collapse
There's a workaround to get flash working on JellyBean for Dolphin Browser.
http://forum.xda-developers.com/showthread.php?t=1846225
Send the logcat via pm, Be sure to provide a description of the bugs/issues you're seeing.

Radio issue (not recognised) Find5 4.4 build

Hello Entropy & Omni team,
I have an issue when building find5 KK. In fact no really building as i manage to get the homemade zip file, manage to flash it, it boots ok, everything is working except that my radio is not recognised so no IMEI and no mobile network, wifi is ok. Here is a link to my own build witch has exactly the same size in KB that the official nightly. Strange stuff is that if i flash the official nightly over my build then no issue, and the radio is recognised.
Blobs are coming from donkey github
I tried to flash from aokp 4.3 build, then also from Color OS, same result.
Flashed maxwen radios 4.1 and 4.2 over my build same issue
I'm building from virtual box ubuntu 12.04, JDK 1.6 update 45, on a Mac.
The only thing i see that may be wrong is that at the end of each build before the package is delivered i see no radio.img found, skipping install, but i've read that it was coming without radio.
Tried to add a line in the build.prop to disable selinux "ro.boot.selinux=disabled" i did not help.
I use maxwen TWRP patched recovery, but also tried with last cwm recovery and same result.
With the same build environment i manage to build I9300 omni kitkat without issue.
Any idea what could be wrong?
Many thanks in advance, and also thanks for the great job you all with Omni

Do you have logs?

I did not search for logs as everything is working fine except the fact it boots without baseband but I can search for it. What kind of logs?
Thanks.
Sent from my GT-I9505 using xda app-developers app

jejecule said:
What kind of logs?
Click to expand...
Click to collapse
logcat -b radio

maxwen said:
logcat -b radio
Click to expand...
Click to collapse
Thanks Maxwen! I've built today again...and it's working now, no issue anymore, my baseband is recognised after flashing 04/12 build. Were there some sources changes yesterday?
I will build again tomorrow morning to check if it's definitely solved.
Thanks a lot guys for your great job and support:good:

jejecule said:
Thanks Maxwen! I've built today again...and it's working now, no issue anymore, my baseband is recognised after flashing 04/12 build. Were there some sources changes yesterday?
I will build again tomorrow morning to check if it's definitely solved.
Thanks a lot guys for your great job and support:good:
Click to expand...
Click to collapse
Nothing I know of... Maybe something in your build system temporarily derped.

Oppo find 7

Hi,
Any suggestion for a stable ROM ?
Thank you all

You are asking what ROM to run in the paranoid android forum section.... What rom do you think we would suggest? Paranoid android of course....
#stayparanoid

Sorry and thanks

Paranoid is by far the best rom I had
Can't live two days on the stock rom (Sony)

Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks

ma8ash said:
Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks
Click to expand...
Click to collapse
I'm using The latest version of PA 4.6 beta on my find 7 QHD as my daily driver and love it.
Haven't noticed any major issues, battery life is really good. Wifi, 3G, and bluetooth all work flawlessly. (I haven't tried LTE because I haven't got it on my mobile plan)
The only issue that I've encountered is that, on a couple of games I have, sometimes they become slow and unresponsive (family guy game and 2014), I didn't have these problems on ColorOS.
PA 4.6 is currently beta so I'm not really concernecd and I think the minor issues will be ironed out in future updates.

Thank you very much

I have tried PA 4.6 Beta 5 today
My story here
T

Paranoid and mahdi room

ma8ash said:
Anyone with OPPO find 7 is running Paranoid ROM can tell us how is it and if there are any issues . thanks
Click to expand...
Click to collapse
Had a very bumpy ride with the first installation. I think I forgot to reset to factory settings, so it might be my fault.
Second installation was better. There are certain things I don't love:
Chrome browser runs on windowed version, no matter what setting you try to change.
Battery seems very short. I need to recharge halfway through my day.
I can't get the gestures to work when the screen is off. (double tap works great, nothing else).
Everything else is buttery smooth. Maybe I'm just unlucky with a few glitches here and there.

Chrome issue happens on any ROM with floating mode implemented. Its a google chrome issue. They have fixed it in their latest beta.
#stayparanoid

I just can advice you to use PA. It's my personal favorite

PA Lollipop where?
I have searched high and low. Where can I find PA 5.0.x for my Find 7?

flemmingski said:
I have searched high and low. Where can I find PA 5.0.x for my Find 7?
Click to expand...
Click to collapse
We haven't released any pa 5.0....on any device.
#stayparanoid

Error downloading rom
Whenever I try to download the latest paranoid android rom for the find7s (qhd), I get an "error executing updater binary" message. I looked up and saw that you had to install the latest cyanogenmod nightly first, which I did, but I still couldn't get it to work. I first wiped everything (data,dalvik,cache) then I installed the cyano nightly, then I wiped the data, then I installed paranoid android and I still get the error. I am also running the latest twrp recovery (2.8.6.0). Thanks in advance for anyone that can help me out

chair96 said:
Whenever I try to download the latest paranoid android rom for the find7s (qhd), I get an "error executing updater binary" message. I looked up and saw that you had to install the latest cyanogenmod nightly first, which I did, but I still couldn't get it to work. I first wiped everything (data,dalvik,cache) then I installed the cyano nightly, then I wiped the data, then I installed paranoid android and I still get the error. I am also running the latest twrp recovery (2.8.6.0). Thanks in advance for anyone that can help me out
Click to expand...
Click to collapse
Use the legacy build.