Develop Bugs

[Q] Rom from wildfire without sene

want anyone try port from wildfire without sense? exactly rom is OpenFire. i had ported it..

Michga said:
want anyone try port from wildfire without sense? exactly rom is OpenFire. i had ported it..
Click to expand...
Click to collapse
sure post it up i will give it a shot, i mean without sense its just reg Aosp like fresh froyo and a few of the other builds. i dont think there is much differnce

okey but later.. now im working on rom with sense

i have still 2 problems..
1. phone cycle in bootanimation and in console is link:: notfound
or
2. init: unable to open persistent property directory /data/property errno: 2

Michga said:
i have still 2 problems..
2. init: unable to open persistent property directory /data/property errno: 2
Click to expand...
Click to collapse
add this in sysinit.rc under # create basic filesystem structure
mkdir /data/property 0700 root root
See if that helps. Goodluck!

Does wifi not work under any ICS rom

ive installed most of the ics ports on all of them they state working wifi
now on my phone it only works when it wants to but gingerbread and below its perfect
is this the same for everyone or just me and something that will improve over course of rom development

Only tried Sandvolt's ICS-Rom, but I did not have any problems with WiFi.
Do you run a full wipe before flashing roms?
Sent from dGB using Transparent XDA App

yes i did a full wipe as well as dalvik
it did work today though but after a reboot its back off
its also a gsm desire pvt4 with s-off if that helps but it leads me to belive its more of a software issue rather hardware as stock ruu and other roms work perfect apart from ics it is pretty volitile it either works or doesnt

I've tried two different variants of ICS Roms and I had the same experience. Under gb the wifi works, but under ics I'm getting a very weak signal.

WiFi appears to be a bit hit and miss
I'm running Sandvolt's ICS ROM, I find about half the time WiFi works properly, and the rest of the time I have to drop back to 3G (which can be pretty average at times).

Could you specify what exactly do you mean with "doesn't work"? Can you switch it on? Does it remains on and can you set up/edit a new/existing profile? Advanced WLAN and profile settings are correctly set up?

[email protected] said:
Could you specify what exactly do you mean with "doesn't work"? Can you switch it on? Does it remains on and can you set up/edit a new/existing profile? Advanced WLAN and profile settings are correctly set up?
Click to expand...
Click to collapse
yer it just will not enable heres the logcat from adb
as you can see below it cant load the drivers is this normally a kernel problem i have been flashing by wiping all data and then dalvik i even returned to stock re rooted and reflashed i think its more a software error as any other rom excluding ics roms works perfect for wifi
E/WifiStateMachine( 181): Failed to load driver!
E/WifiStateMachine( 181): DriverFailedState
D/CAT ( 332): CatService: ril message arrived
D/CAT ( 332): CatService: ril message arrived
D/CAT ( 332): CatService: SESSION END
D/SurfaceTexture( 115): [Toast] this:0xa776a0 SurfaceTexture::abandon
D/dalvikvm( 181): GC_CONCURRENT freed 717K, 9% free 14566K/15943K, paused 12ms+
5ms
E/WifiStateMachine( 181): Failed to load driver!
E/WifiStateMachine( 181): DriverFailedState
D/dalvikvm( 933): GC_CONCURRENT freed 127K, 3% free 9694K/9927K, paused 3ms+3ms
I/power ( 181): *** set_screen_state 0
D/SurfaceFlinger( 115): About to give-up screen, flinger = 0xa06918
E/libEGL ( 115): validate_display:188 error 3008 (EGL_BAD_DISPLAY)
D/AK8973 ( 122): Compass CLOSE
^C
C:\Users\sean\Desktop\SuperOneClick 2.3.1.0\ADB>

Maybe you find a solution here (SPACE=/):
http: code google com p android issues detail?id=1124
*Sorry, cannot yet post any link.

I'm using BravoCM b0.3.5_1, WiFi worked perfectly right from the start - no errors, good signal, and Google backup-restore even remembered all the passwords I configured in my old rom.

solved faulty SD card mounting as read only
Sent from my Spaceship using XDA App

seanpr92 said:
solved faulty SD card mounting as read only
Sent from my Spaceship using XDA App
Click to expand...
Click to collapse
could you mind posting the solution here? because i have the same problem with the current release of sanvold ics. how did you find out the problem is wit hsd, and how did you corrected it?
thanx a lot

ahmad598 said:
could you mind posting the solution here? because i have the same problem with the current release of sanvold ics. how did you find out the problem is wit hsd, and how did you corrected it?
thanx a lot
Click to expand...
Click to collapse
if you are flashing Sandvold ICS rom, try typical installation. you can take the logcat by connecting your device to pc via usb cable and run following:
###assuming you have android sdk downloaded and installed
c:\%android_sdk\platform-tools\adb logcat >> logfile.txt

mt25i
seanpr92 said:
ive installed most of the ics ports on all of them they state working wifi
now on my phone it only works when it wants to but gingerbread and below its perfect
is this the same for everyone or just me and something that will improve over course of rom development
Click to expand...
Click to collapse
I have exactly the same problem.
---------- Post added at 07:28 AM ---------- Previous post was at 07:20 AM ----------
ahmad598 said:
could you mind posting the solution here? because i have the same problem with the current release of sanvold ics. how did you find out the problem is wit hsd, and how did you corrected it?
thanx a lot
Click to expand...
Click to collapse
kmaq said:
if you are flashing Sandvold ICS rom, try typical installation. you can take the logcat by connecting your device to pc via usb cable and run following:
###assuming you have android sdk downloaded and installed
c:\%android_sdk\platform-tools\adb logcat >> logfile.txt
Click to expand...
Click to collapse
Thank you my friend.
Where do I type this command:fingers-crossed:

Dalvikvm errors

What does all this mean and how do I fix it? I'm porting a ROM to the S3 and I get all the way to the boot anim then it freezes. I know that could be any number of things but i'd like to start with this first as it happens first. I've swapped out the .jar files with those from cm9 as they are confirmed working. and the port ROM is ics as well. Cache is also cleared 3 times before install.
E/dalvikvm( 316): DexOpt: build rev does not match VM: 27 vs 28
W/dalvikvm( 206): DexOpt: --- END 'core.jar' --- status=0xff00, process failed
E/dalvikvm( 206): Unable to extract+optimize DEX from '/system/framework/core.jar'
D/dalvikvm( 206): Unable to process classpath element '/system/framework/core.jar'
D/dalvikvm( 206): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 206): ODEX file is stale or bad; removing and retrying (/cache/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 206): DexOpt: --- BEGIN 'core-junit.jar' (bootstrap=1) ---
E/dalvikvm( 322): DexOpt: build rev does not match VM: 27 vs 28
W/dalvikvm( 206): DexOpt: --- END 'core-junit.jar' --- status=0xff00, process failed
E/dalvikvm( 206): Unable to extract+optimize DEX from '/system/framework/core-junit.jar'
D/dalvikvm( 206): Unable to process classpath element '/system/framework/core-junit.jar'
Click to expand...
Click to collapse
Specifically this:
E/dalvikvm( 322): DexOpt: build rev does not match VM: 27 vs 28
Click to expand...
Click to collapse
and this:
D/dalvikvm( 206): DexOpt: incorrect opt magic number (0xff ff ff ff)
Click to expand...
Click to collapse
I feel like those 2 are the big ones. If i can fix those the others should get fixed as well. Feel free to correct me if im wrong and offer up and suggestions. any advice will be appreciated. Thanks.
here is the full log if interested:
http://pastebin.com/9hfTtaMN

Bump
Sent from my SPH-L710 using xda app-developers app

Well from looking at the source code for where that happens:
http://in-the-box.googlecode.com/svn-history/r6/trunk/InTheBoxSim/dexopt/OptMain.c
It seems that it doesn't want to accept the ICS version (revision 17) when it is running JB (revision 23)
I wouldn't know how to fix it, but this is a start.
As for the the "incorrect magic" error, try taking a look here:
https://groups.google.com/forum/m/?fromgroups#!topic/android-platform/oy4trrd0eKw

Thanks for the reply. They are both running ics. I'm porting sense from the evo 4g lte. I didn't mention that in my original post because the minute I mention sense people get all scared and think "oh I don't know anything about sense I can't help" but it's a problem that occurs on a lot of roms especially new ones. The reason I haven't figured this out yet is because no one ever mentions how to fix it and if they do then I can't quite figure out the search terms to use to find it lol. But any who. What we have done is used an already started sense port that uses a custom cm9 kernel that from all I can tell only had the bootclasspath changed to match the sense kernel. The first test got us to the beginning of the boot animation. Replacing libs in the lib folder got us a tad further in the boot animation but freezes half way. The rom is deodexed. We are gonna try reodexing and see what happens. But until then all of our test involved the error above. My buddy added the ODEX files back and the 27 vs 28 simply swapped places to 28 vs 27. We found that rather odd as well.
So as it stands we get this error. Plus a seg fault. We think the dalvik error may be tied to the fact that the rom is deodexed. Gonna try reodexing.
The two roms are both ics as I mentioned before. So how could the build rev be different? What could I change to get them the same? How do I find out what caused the initial DexOpt write failure that lead to the other magic number errors?
Sent from my SPH-L710 using xda app-developers app

We fixed the magic number issue by injecting the ODEX files back into the rom but still have a version mismatch. Gonna start from scratch with an the stock odexed jb update and see if we can eliminate the problem all together.
Sent from my SPH-L710 using xda app-developers app

Sorry for not replying, but other than the version mismatch, I am out of my area of expertise by a longshot but this stuff is interesting to me so I'll read up on it and see if I can help

Thanks. Ill keep you posted on any progress I make wit this if you'd like. Anybody else that is interested feel free to jump in.

GRock84 said:
We fixed the magic number issue by injecting the ODEX files back into the rom but still have a version mismatch. Gonna start from scratch with an the stock odexed jb update and see if we can eliminate the problem all together.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I know this is an old thread, but I'm having magic number issue on a port I'm doing. Can you explain how you injected the odex files back into the ROM?

[REFERENCE] [PRIMOC] HTC One V

This thread will be a reference for all the information I know and find out about the HTC One V. I will update it as I gain knowledge. I only own the cdma one v so this may be specific to the primoc. Dont ask for primou, just do it yourself.
Partitions List:
Code:
*= write protection
/dev/block/mmcblk0 - Every partition combined to one
/dev/block/mmcblk0p1 - unknown*
/dev/block/mmcblk0p2 - Blank
/dev/block/mmcblk0p3 - SBL*
/dev/block/mmcblk0p4 - Unknown (has a bianary in it towards the end, though)
/dev/block/mmcblk0p5 - Radio Related(elf binary)*
/dev/block/mmcblk0p6 - Unknown
/dev/block/mmcblk0p7 - Contains CID/Security flag*
/dev/block/mmcblk0p8 - Unknown
/dev/block/mmcblk0p9 - Contains NV items, basically NV dump ** See p9 info at bottom of post (NEVER GIVE ANYONE ELSE THIS PARTITION)
/dev/block/mmcblk0p10 - Blank
/dev/block/mmcblk0p11 - Blank
/dev/block/mmcblk0p12 - Blank
/dev/block/mmcblk0p13 - This is basically a back up of 9(13).. or maybe vice versa. They do differ a bit, but they contain a lot of the same info
/dev/block/mmcblk0p14 - This is basically a back up of 13(9).. or maybe vice versa. They do differ a bit, but they contain a lot of the same info
/dev/block/mmcblk0p15 - Blank
/dev/block/mmcblk0p16 - Blank
/dev/block/mmcblk0p17 - Misc partition (blank... maybe htc is tricking us?)*
/dev/block/mmcblk0p18 - Hboot*
/dev/block/mmcblk0p19 - Splash1.nb0*
/dev/block/mmcblk0p20 - Partially Unknown. Partially resembles a Misc partition. Contains board version
/dev/block/mmcblk0p21 - Recovery
/dev/block/mmcblk0p22 - Boot
/dev/block/mmcblk0p23 - Contains board version, serial no., board serial no, MEID, and a lot of other things important to radio
/dev/block/mmcblk0p24 - Blank
/dev/block/mmcblk0p25 - System
/dev/block/mmcblk0p26 - Userdata
/dev/block/mmcblk0p27 - Swap
/dev/block/mmcblk0p28 - Cache
/dev/block/mmcblk0p29 - Local (blank)
/dev/block/mmcblk0p30 - Devlog (sense uses this to save system and kernel logs)
/dev/block/mmcblk0p31 - Blank
/dev/block/mmcblk0p32 - Pdata (blank)
/dev/block/mmcblk0p33 - Fat
/dev/block/mmcblk1 - Your SD
The stock RUU:
android-info.txt
Code:
modelid: PK7630000
cidnum: SPCS_002
mainver: 1.08.652.6
hbootpreupdate:12
DelFat:1
DelCache:1
Files in the rom.zip:
Code:
boot_signed.img
dzdata_3g.hdr
dzdata_3g.img
dzdata_4g.hdr
dzdata_4g.img
hboot_1.53.0000_signedbyaa.nb0
NV_MFG_VM_3.46_0503_PRL61008.nb
radio.img
ramdisk.img
recovery_signed.img
splash1.nb0
system.img
tp_PRO_HM8526A0F.img
tp_SYN3201.img
OTA Info:
android-info.txt
Code:
modelid: PK7630000
cidnum: SPCS_002
mainver: 1.08.652.11
hbootpreupdate:12
files in the ota firmware.zip:
Code:
boot.img
radio.img
recovery.img
OTA Notes:
This ota causes reboots if your kernel's battery driver isn't updated.
Extra Info:
I think the unsure ones are related to security.
Also, partition 33 can be bind mounted to partition 26 for 100 mb of extra space for apps.
There is an OTA that updates the radio making it unable to boot non sense roms/kernels. This is due to a NPE in the battery drivers. It is being worked on and looked into.
Special notes about p9
(offset is around 7579) has your SPC
to find your aaa key, locate vmug33k close to that (a little bit after) you will find a few letters and or symbols. This is your precious AAA key. BACK THIS PARTITION UP AND SAVE IT EVERYWHERE!

Re: [REFERENCE] HTC One V
Thanks for the list. Just a heads up but as far as I know that OTA is for CDMA only maybe you could specifically state that? Else I can guarantee you that you'll get questions about it by primou users
Sent from my One V using xda premium

OP updated with SEVERAL new finds, including but not limited to where your AAA, SPC, HA, Serial number, ect. are. These partitions are from an OTA'd one v, complements of beyond!
Also, title will be changed to primoc for those concerned

I found my MSL/SPC in hex offset block 7584-7589. I had some issues with it at first as I had set it to "dec" for the offset not "hex" but I swear I thought I checked both...oh well.
simonsimons34 said:
Special notes about p9
offset 7579 has your SPC
to find your aaa key, locate vmug33k close to that (a little bit after) you will find a few letters and or symbols. This is your precious AAA key. BACK THIS PARTITION UP AND SAVE IT EVERYWHERE!
Click to expand...
Click to collapse

It could vary from device to device
Sent from my One V using Tapatalk 2

New information posted about ruu and ota

I see the radio.img. does that mean someone could flash the downgraded radio without running the ruu then re unlocking? Or will fastboot not flash radio.img
Sent from my One V using xda premium

Unless you are soff you can't. But no need now. I have been running 15 hours on the new radio with my updated kernel
Sent from my One V using Tapatalk 2

Sweet.
Sent from my One V using xda premium

Hi Simon, great work! Which version of your kernel is currently working with the updated radio? I'd really like to get the newest available radio running but, obviously, having a cool ROM is much more important so I'm still running the ruu version. ;P
simonsimons34 said:
Unless you are soff you can't. But no need now. I have been running 15 hours on the new radio with my updated kernel
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse

My new code fire nightly for the primoc runs it great
Sent from my One V using Tapatalk 2

i stumbled across this for the one s... probably no help, but i figured i'd try to help
http://forum.xda-developers.com/showthread.php?t=1674202

That link will not help us, but thank you for your contribution. We are always glad to take a look at anything
Sent from my One V using Tapatalk 2

simonsimons34 said:
My new code fire nightly for the primoc runs it great
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
I tried to delete this post, but it won't let me. lol Moving on...

Re: [REFERENCE] [PRIMOC] HTC One V[REFERENCE] [PRIMOC] HTC One V
I'd prefer if everyone stayed on task here. I currently am maintaining code fire ion for primoc. Please pm me if you have questions and don't post in the wrong thread. I don't want you to get in trouble with the moderators, nor do I want someone to make there job harder back on topic now
Sent from my One V using Tapatalk 2

im stuck on the new radio after updating and trying to put a rom on, cant get anything to boot and ruu doesnt work, any help?

Use a kernel with my fix for the NPE in the Maxium battery driver. The SickleKernels repo on github should be a good start if you want to try to compile on your own
Sent from my One V using Tapatalk 2

simonsimons34 said:
Use a kernel with my fix for the NPE in the Maxium battery driver. The SickleKernels repo on github should be a good start if you want to try to compile on your own
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
Do you have a standalone kernel that will work with iCa/sense.
Sent from my HTC One V using xda app-developers app

No such thing as stand alone for this phone
Sent from my One V using Tapatalk 2

simonsimons34 said:
No such thing as stand alone for this phone
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
I meant like the old sick06.zip that just has the modules and the boot.img.
Sent from my HTC One V using xda app-developers app

[CM 13.0] Error while building persist.img..

Hi everybody !
I'm Androlark, a young french developper, who need your help today..
All yesterday long (I don't if syntax is correct but I don't care) I've been trying to port CyanogenMod to my device, the HTC Desire 820 a51_ul.
I think I'm not that far from success, 'cause my out folder near the 28 Gb, and this is a good new !
I'm asking you some help today, to help me to fix that error, and if my build finally works, I'll share it.
So, here's my problem:
Code:
Target persist fs image: /home/androlark/android/system/out/target/product/htc_a51ul/persist.img
Usage:
mkuserimg.sh [-s] SRC_DIR OUTPUT_FILE EXT_VARIANT MOUNT_POINT SIZE [-j <journal_size>]
[-T TIMESTAMP] [-C FS_CONFIG] [-D PRODUCT_OUT] [-B BLOCK_LIST_FILE] [-L LABEL] [FILE_CONTEXTS]
make: *** [/home/androlark/android/system/out/target/product/htc_a51ul/persist.img] Error 1
I'm using the "brunch cm_htc_a51ul-eng" command, and I've took the kernel and the device repo from fergy's github (cannot post links :crying
I'm compiling with Ubuntu 14.04 btw.
I hope somebody is gonna help me, and thanks for your time.
PS: My Skype is on my profile, if you prefer Skype ^^'.

@fergy @Thecrazyskull
Sent from my HTC Desire 820 using XDA Free mobile app

Use my trees

https://github.com/Thecrazyskull/device_htc_a51ul
Sent from my HTC Desire 820 using XDA Free mobile app

Thank you for your answers, I'm trying it.

Back to you guys, I got a new error:
Code:
/home/androlark/android/system/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /home/androlark/android/system/out/target/product/a51ul/obj/ETC/sepolicy_intermediates/policy.conf
HOSTCC scripts/basic/fixdep
device/htc/a51ul/sepolicy/rmt_storage.te:2:ERROR 'unknown type mmc_block_device' at token ';' on line 27077:
#line 1 "device/htc/a51ul/sepolicy/rmt_storage.te"
allow rmt_storage mmc_block_device:blk_file { { getattr open read ioctl lock } { open append write } };
checkpolicy: error(s) encountered while parsing configuration
make: *** [/home/androlark/android/system/out/target/product/a51ul/obj/ETC/sepolicy_intermediates/sepolicy] Erreur 1
I'm doing some researches by my side, and thanks again.

Send later your results
Sent from my HTC Desire 820 using XDA Free mobile app

It's fixed, I just took the rmt_storage.te from @fergy 's Github.

Good. Will you compile?
Sent from my HTC Desire 820 using XDA Free mobile app
---------- Post added at 12:34 PM ---------- Previous post was at 12:22 PM ----------
We are waiting

FYI: my trees are made for cm12.1 not cm13, so dont expect to boot cm13 with my trees

Yeah, so the only way to fix it is to use your trees, but I can't use them.. :c

Androlark said:
Yeah, so the only way to fix it is to use your trees, but I can't use them.. :c
Click to expand...
Click to collapse
Build cm12.1, boot cm12.1 then move onto cm13

(post edited)

Hi guys, I just got a new issue:
Code:
Target userdata fs image: /home/androlark/android/system/out/target/product/htc_a51ul/userdata.img
Build image output_image_file from input_directory and properties_file.
Usage: build_image input_directory properties_file output_image_file
make: *** [/home/androlark/android/system/out/target/product/htc_a51ul/userdata.img] Error 1

Did you fix?
Sent from my HTC Desire 820 using XDA Free mobile app

Pls try make cm12.1 or aosp 5.0.2. This roms haven't problem because kernel is ok. You edit kernel and make cm12.1 rom.

Dragonfail said:
Did you fix?
Sent from my HTC Desire 820 using XDA Free mobile app
Click to expand...
Click to collapse
I haven't fix it yet, sorry..

I know you're expecting a lot of me, but know that I've a life behind and I'm not all day long here to work..

Emresaygin said:
Pls try make cm12.1 or aosp 5.0.2. This roms haven't problem because kernel is ok. You edit kernel and make cm12.1 rom.
Click to expand...
Click to collapse
I've decided to answer to your request. I'm gonna try to build CM 12.1 for D820, and from there I may try to build CM 13.
(Got the impression that my english sucks a little bit.. x))

And what's results?
Sent from my HTC Desire 820 using XDA Free mobile app