Root [Boost Mobile] For Discussion of Development for CM7 Only

[hroark13]

I was able to do it before, I did the same edits to init.arthur.rc that you did. I really dont understand why it wont mount partitions at boot. I didnt do a mount command tho, so didnt really test. I feel like building the kernel again and checking if the default config has ext4 modules built in. Last time I built the kernel using the .config that was on the phone, it didnt have the ext4 modules selected.

i dont think it is ext4 because if it was I would not be able to mount and read the /system from adb

I was using the unmodified config from the phone


i think it is some type of security type stuff in the init file or something


I have not been able to make my own init file with CM7

I had to use the one from stock to be able to boot CM7

that is why most people trying to get CM7 to boot, were not able to, cause they were using the init that CM7 builds

 

[hroark13]

Im building cm7 using your source as I type to test that out, if that doesnt work ima try a few other things

oh by the way if you build CM7, you will want to MOD the update.script, because we need to set permissions to some files in the etc folder


I have a thread for CWM installer templates, so you can get a CM7 installer template from there

 

[shinru2004]

Sebastian is getting a warp so he can look into the issues personally

 

[Snake X]

I thought he already got one?

 

[shinru2004]

Nope, he just tweeted me yesterday. Said he was getting one

 

[QuietStorm1785]

well i figured out some of the ril issues, yes it was in the configuration of the system.prop. I used some of the default configuration for the zte warp. hroark, heres the settings in my system.prop:

#RIL properties

rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
DEVICE_PROVISIONED=1

persist.cne.UseCne=false
persist.cne.loadVendorCne=true
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=true
persist.cne.snsr.based.rat.mgt=true
persist.cne.bat.based.rat.mgt=true
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0

#Dalvik properties
dalvik.vm.heapsize=32m
ro.sf.lcd_density=240
ro.sf.hwrotation=180

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.baseband_version=N860B01
ro.build.software_version=N860V1.0.0B08c
ro.build.sw_internal_version=N860V1.0.0B20
ro.camera.video.size.mms=1048576
ro.camera.video.duaration.mms=40
ro.config.ringtone=Ring_Synth_04.ogg
ro.com.google.clientidbase=android-zte
ro.com.google.clientidbase.yt=android-boost-us
ro.com.google.clientidbase.am=android-boost-us
ro.com.google.clientidbase.ms=android-boost-us
ro.com.google.clientidbase.gmm=android-zte
ro.build.hardware_version=c4tB
ro.build.pri.version=61007
ro.com.google.clientidbase=android-zte
ro.com.google.clientidbase.yt=android-zte
ro.com.google.clientidbase.am=android-zte
ro.com.google.clientidbase.ms=android-zte
ro.com.google.clientidbase.gmm=android-zte
ro.config.notification_sound=F1_New_SMS.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.3_r7
persist.sys.usb.enable_switch=1
persist.sys.usb.linux_switch=1
persist.sys.usb.switch_pid=0x1354
persist.sys.usb.linux_pid=0x1350
persist.sys.usb.default.pid=0x83
ro.build.baseband_version=SPRINTB01
ro.build.software_version=GENERIC_SPRINTV1.0.0B01
ro.build.sw_internal_version=GENERIC_SPRINTV1.0.0B01
persist.sys.sdcard.mount=1
persist.sys.usb.switch_pid=0x1351
persist.sys.usb.unique_sn=1
persist.sys.usb.enable_cdrom=0x5656
net.bt.name=Android

ro.setupwizard.mode=DISABLED
dalvik.vm.stack-trace-file=/data/anr/traces.txt

calls work fine for me, have yet to test data tho, will update yall when I do.

[EDIT]
nope, data no worky. Still running some tests, gonna see what I can do within a 8 hour time period, gotta work later..x_x

 

[hroark13]

well i figured out some of the ril issues, yes it was in the configuration of the system.prop. I used some of the default configuration for the zte warp. hroark, heres the settings in my system.prop:

#RIL properties

rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
DEVICE_PROVISIONED=1

persist.cne.UseCne=false
persist.cne.loadVendorCne=true
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=true
persist.cne.snsr.based.rat.mgt=true
persist.cne.bat.based.rat.mgt=true
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0

#Dalvik properties
dalvik.vm.heapsize=32m
ro.sf.lcd_density=240
ro.sf.hwrotation=180

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.baseband_version=N860B01
ro.build.software_version=N860V1.0.0B08c
ro.build.sw_internal_version=N860V1.0.0B20
ro.camera.video.size.mms=1048576
ro.camera.video.duaration.mms=40
ro.config.ringtone=Ring_Synth_04.ogg
ro.com.google.clientidbase=android-zte
ro.com.google.clientidbase.yt=android-boost-us
ro.com.google.clientidbase.am=android-boost-us
ro.com.google.clientidbase.ms=android-boost-us
ro.com.google.clientidbase.gmm=android-zte
ro.build.hardware_version=c4tB
ro.build.pri.version=61007
ro.com.google.clientidbase=android-zte
ro.com.google.clientidbase.yt=android-zte
ro.com.google.clientidbase.am=android-zte
ro.com.google.clientidbase.ms=android-zte
ro.com.google.clientidbase.gmm=android-zte
ro.config.notification_sound=F1_New_SMS.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.3_r7
persist.sys.usb.enable_switch=1
persist.sys.usb.linux_switch=1
persist.sys.usb.switch_pid=0x1354
persist.sys.usb.linux_pid=0x1350
persist.sys.usb.default.pid=0x83
ro.build.baseband_version=SPRINTB01
ro.build.software_version=GENERIC_SPRINTV1.0.0B01
ro.build.sw_internal_version=GENERIC_SPRINTV1.0.0B01
persist.sys.sdcard.mount=1
persist.sys.usb.switch_pid=0x1351
persist.sys.usb.unique_sn=1
persist.sys.usb.enable_cdrom=0x5656
net.bt.name=Android

ro.setupwizard.mode=DISABLED
dalvik.vm.stack-trace-file=/data/anr/traces.txt

calls work fine for me, have yet to test data tho, will update yall when I do.

[EDIT]
nope, data no worky. Still running some tests, gonna see what I can do within a 8 hour time period, gotta work later..x_x

we have been able to make phone calls, the problem is getting the CM7 to work in CDMA mode, and data and such

 

[QuietStorm1785]

we have been able to make phone calls, the problem is getting the CM7 to work in CDMA mode, and data and such

yeh i noticed, didnt read the past posts, right now im trying the ril files from the zte blade. gonna see if that works.

 

[hroark13]

yeh i noticed, didnt read the past posts, right now im trying the ril files from the zte blade. gonna see if that works.

ZTE Blade is a ARMv6 phone, those libs on that phone probably wont work on a ARMv7 phone

I appreciate you looking in to this and trying though

 

[QuietStorm1785]

ZTE Blade is a ARMv6 phone, those libs on that phone probably wont work on a ARMv7 phone

I appreciate you looking in to this and trying though

not the libs, the .cpp files in the libril folder on the blade. maybe we can modify the code from that folder for the warp.... like heres a tidbit from the ril_commands.h file:

/* //device/libs/telephony/ril_commands.h
**
** Copyright 2006, The Android Open Source Project
**
** Licensed under the Apache License, Version 2.0 (the "License");
** you may not use this file except in compliance with the License.
** You may obtain a copy of the License at
**
**     http://www.apache.org/licenses/LICENSE-2.0
**
** Unless required by applicable law or agreed to in writing, software
** distributed under the License is distributed on an "AS IS" BASIS,
** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
** See the License for the specific language governing permissions and
** limitations under the License.
*/
    {0, NULL, NULL},                   //none
    {RIL_REQUEST_GET_SIM_STATUS, dispatchVoid, responseSimStatus},
    {RIL_REQUEST_ENTER_SIM_PIN, dispatchStrings, responseInts},
    {RIL_REQUEST_ENTER_SIM_PUK, dispatchStrings, responseInts},
    {RIL_REQUEST_ENTER_SIM_PIN2, dispatchStrings, responseInts},
    {RIL_REQUEST_ENTER_SIM_PUK2, dispatchStrings, responseInts},
    {RIL_REQUEST_CHANGE_SIM_PIN, dispatchStrings, responseInts},
    {RIL_REQUEST_CHANGE_SIM_PIN2, dispatchStrings, responseInts},
    {RIL_REQUEST_ENTER_NETWORK_DEPERSONALIZATION, dispatchStrings, responseInts},
    {RIL_REQUEST_GET_CURRENT_CALLS, dispatchVoid, responseCallList},
    {RIL_REQUEST_DIAL, dispatchDial, responseVoid},
    {RIL_REQUEST_GET_IMSI, dispatchVoid, responseString},
    {RIL_REQUEST_HANGUP, dispatchInts, responseVoid},
    {RIL_REQUEST_HANGUP_WAITING_OR_BACKGROUND, dispatchVoid, responseVoid},
    {RIL_REQUEST_HANGUP_FOREGROUND_RESUME_BACKGROUND, dispatchVoid, responseVoid},
    {RIL_REQUEST_SWITCH_WAITING_OR_HOLDING_AND_ACTIVE, dispatchVoid, responseVoid},
    {RIL_REQUEST_CONFERENCE, dispatchVoid, responseVoid},
    {RIL_REQUEST_UDUB, dispatchVoid, responseVoid},
    {RIL_REQUEST_LAST_CALL_FAIL_CAUSE, dispatchVoid, responseInts},
    {RIL_REQUEST_SIGNAL_STRENGTH, dispatchVoid, responseRilSignalStrength},
    {RIL_REQUEST_REGISTRATION_STATE, dispatchVoid, responseStrings},
    {RIL_REQUEST_GPRS_REGISTRATION_STATE, dispatchVoid, responseStrings},
    {RIL_REQUEST_OPERATOR, dispatchVoid, responseStrings},
    {RIL_REQUEST_RADIO_POWER, dispatchInts, responseVoid},
    {RIL_REQUEST_DTMF, dispatchString, responseVoid},
    {RIL_REQUEST_SEND_SMS, dispatchStrings, responseSMS},
    {RIL_REQUEST_SEND_SMS_EXPECT_MORE, dispatchStrings, responseSMS},
    {RIL_REQUEST_SETUP_DATA_CALL, dispatchStrings, responseStrings},
    {RIL_REQUEST_SIM_IO, dispatchSIM_IO, responseSIM_IO},
    {RIL_REQUEST_SEND_USSD, dispatchString, responseVoid},
    {RIL_REQUEST_CANCEL_USSD, dispatchVoid, responseVoid},
    {RIL_REQUEST_GET_CLIR, dispatchVoid, responseInts},
    {RIL_REQUEST_SET_CLIR, dispatchInts, responseVoid},
    {RIL_REQUEST_QUERY_CALL_FORWARD_STATUS, dispatchCallForward, responseCallForwards},
    {RIL_REQUEST_SET_CALL_FORWARD, dispatchCallForward, responseVoid},
    {RIL_REQUEST_QUERY_CALL_WAITING, dispatchInts, responseInts},
    {RIL_REQUEST_SET_CALL_WAITING, dispatchInts, responseVoid},
    {RIL_REQUEST_SMS_ACKNOWLEDGE, dispatchInts, responseVoid},
    {RIL_REQUEST_GET_IMEI, dispatchVoid, responseString},
    {RIL_REQUEST_GET_IMEISV, dispatchVoid, responseString},
    {RIL_REQUEST_ANSWER,dispatchVoid, responseVoid},
    {RIL_REQUEST_DEACTIVATE_DATA_CALL, dispatchStrings, responseVoid},
    {RIL_REQUEST_QUERY_FACILITY_LOCK, dispatchStrings, responseInts},
    {RIL_REQUEST_SET_FACILITY_LOCK, dispatchStrings, responseInts},
    {RIL_REQUEST_CHANGE_BARRING_PASSWORD, dispatchStrings, responseVoid},
    {RIL_REQUEST_QUERY_NETWORK_SELECTION_MODE, dispatchVoid, responseInts},
    {RIL_REQUEST_SET_NETWORK_SELECTION_AUTOMATIC, dispatchVoid, responseVoid},
    {RIL_REQUEST_SET_NETWORK_SELECTION_MANUAL, dispatchString, responseVoid},
    {RIL_REQUEST_QUERY_AVAILABLE_NETWORKS , dispatchVoid, responseStringsNetworks},
    {RIL_REQUEST_DTMF_START, dispatchString, responseVoid},
    {RIL_REQUEST_DTMF_STOP, dispatchVoid, responseVoid},
    {RIL_REQUEST_BASEBAND_VERSION, dispatchVoid, responseString},
    {RIL_REQUEST_SEPARATE_CONNECTION, dispatchInts, responseVoid},
    {RIL_REQUEST_SET_MUTE, dispatchInts, responseVoid},
    {RIL_REQUEST_GET_MUTE, dispatchVoid, responseInts},
    {RIL_REQUEST_QUERY_CLIP, dispatchVoid, responseInts},
    {RIL_REQUEST_LAST_DATA_CALL_FAIL_CAUSE, dispatchVoid, responseInts},
    {RIL_REQUEST_DATA_CALL_LIST, dispatchVoid, responseDataCallList},
    {RIL_REQUEST_RESET_RADIO, dispatchVoid, responseVoid},
    {RIL_REQUEST_OEM_HOOK_RAW, dispatchRaw, responseRaw},
    {RIL_REQUEST_OEM_HOOK_STRINGS, dispatchStrings, responseStrings},
    {RIL_REQUEST_SCREEN_STATE, dispatchInts, responseVoid},
    {RIL_REQUEST_SET_SUPP_SVC_NOTIFICATION, dispatchInts, responseVoid},
    {RIL_REQUEST_WRITE_SMS_TO_SIM, dispatchSmsWrite, responseInts},
    {RIL_REQUEST_DELETE_SMS_ON_SIM, dispatchInts, responseVoid},
    {RIL_REQUEST_SET_BAND_MODE, dispatchInts, responseVoid},
    {RIL_REQUEST_QUERY_AVAILABLE_BAND_MODE, dispatchVoid, responseInts},
    {RIL_REQUEST_STK_GET_PROFILE, dispatchVoid, responseString},
    {RIL_REQUEST_STK_SET_PROFILE, dispatchString, responseVoid},
    {RIL_REQUEST_STK_SEND_ENVELOPE_COMMAND, dispatchString, responseString},
    {RIL_REQUEST_STK_SEND_TERMINAL_RESPONSE, dispatchString, responseVoid},
    {RIL_REQUEST_STK_HANDLE_CALL_SETUP_REQUESTED_FROM_SIM, dispatchInts, responseVoid},
    {RIL_REQUEST_EXPLICIT_CALL_TRANSFER, dispatchVoid, responseVoid},
    {RIL_REQUEST_SET_PREFERRED_NETWORK_TYPE, dispatchInts, responseVoid},
    {RIL_REQUEST_GET_PREFERRED_NETWORK_TYPE, dispatchVoid, responseInts},
    {RIL_REQUEST_GET_NEIGHBORING_CELL_IDS, dispatchVoid, responseCellList},
    {RIL_REQUEST_SET_LOCATION_UPDATES, dispatchInts, responseVoid},
    {RIL_REQUEST_CDMA_SET_SUBSCRIPTION, dispatchInts, responseVoid},
    {RIL_REQUEST_CDMA_SET_ROAMING_PREFERENCE, dispatchInts, responseVoid},
    {RIL_REQUEST_CDMA_QUERY_ROAMING_PREFERENCE, dispatchVoid, responseInts},
    {RIL_REQUEST_SET_TTY_MODE, dispatchInts, responseVoid},
    {RIL_REQUEST_QUERY_TTY_MODE, dispatchVoid, responseInts},
    {RIL_REQUEST_CDMA_SET_PREFERRED_VOICE_PRIVACY_MODE, dispatchInts, responseVoid},
    {RIL_REQUEST_CDMA_QUERY_PREFERRED_VOICE_PRIVACY_MODE, dispatchVoid, responseInts},
    {RIL_REQUEST_CDMA_FLASH, dispatchString, responseVoid},
    {RIL_REQUEST_CDMA_BURST_DTMF, dispatchStrings, responseVoid},
    {RIL_REQUEST_CDMA_VALIDATE_AND_WRITE_AKEY, dispatchString, responseVoid},
    {RIL_REQUEST_CDMA_SEND_SMS, dispatchCdmaSms, responseSMS},
    {RIL_REQUEST_CDMA_SMS_ACKNOWLEDGE, dispatchCdmaSmsAck, responseVoid},
    {RIL_REQUEST_GSM_GET_BROADCAST_SMS_CONFIG, dispatchVoid, responseGsmBrSmsCnf},
    {RIL_REQUEST_GSM_SET_BROADCAST_SMS_CONFIG, dispatchGsmBrSmsCnf, responseVoid},
    {RIL_REQUEST_GSM_SMS_BROADCAST_ACTIVATION, dispatchInts, responseVoid},
    {RIL_REQUEST_CDMA_GET_BROADCAST_SMS_CONFIG, dispatchVoid, responseCdmaBrSmsCnf},
    {RIL_REQUEST_CDMA_SET_BROADCAST_SMS_CONFIG, dispatchCdmaBrSmsCnf, responseVoid},
    {RIL_REQUEST_CDMA_SMS_BROADCAST_ACTIVATION, dispatchInts, responseVoid},
    {RIL_REQUEST_CDMA_SUBSCRIPTION, dispatchVoid, responseStrings},
    {RIL_REQUEST_CDMA_WRITE_SMS_TO_RUIM, dispatchRilCdmaSmsWriteArgs, responseInts},
    {RIL_REQUEST_CDMA_DELETE_SMS_ON_RUIM, dispatchInts, responseVoid},
    {RIL_REQUEST_DEVICE_IDENTITY, dispatchVoid, responseStrings},
    {RIL_REQUEST_EXIT_EMERGENCY_CALLBACK_MODE, dispatchVoid, responseVoid},
    {RIL_REQUEST_GET_SMSC_ADDRESS, dispatchVoid, responseString},
    {RIL_REQUEST_SET_SMSC_ADDRESS, dispatchString, responseVoid},
    {RIL_REQUEST_REPORT_SMS_MEMORY_STATUS, dispatchInts, responseVoid},
    {RIL_REQUEST_REPORT_STK_SERVICE_IS_RUNNING, dispatchVoid, responseVoid}

Thats in the cm7 source tree in the zte blade device folder...see if u might be able to pull something out of it, my programming skills are rusty as shit. who knows, it might work....

 

[hroark13]

ZTE Blade is a ARMv6 phone, those libs on that phone probably wont work on a ARMv7 phone

I appreciate you looking in to this and trying though

I was able to use the RIL files from the ZTE U960, but had the same issues

 

[hroark13]

not the libs, the .cpp files in the libril folder on the blade. maybe we can modify the code from that folder for the warp.... like heres a tidbit from the ril_commands.h file:

yeah, I took a look at that a while back and it did not seem like the commands matched up when I compared it to the de-compiled RIL.java

If you want to try using it, I am all for it.

I have not been spending that much time on the CM7 lately

I am trying to get the kernel source code working properly

 

[QuietStorm1785]

yeah, I took a look at that a while back and it did not seem like the commands matched up when I compared it to the de-compiled RIL.java

If you want to try using it, I am all for it.

I have not been spending that much time on the CM7 lately

I am trying to get the kernel source code working properly

Im building it now to see if it works, btw, nice work using the n850 source, i was thinking of doing the same, but never got to it... Hopefully it works out and we got a pimpin kernel source for this phone too. We need more people like you workin on this phone.

 

[shinru2004]

Maybe you could get Kouma or Shabby over here to this section to help you out. IDK but it seems worth a shot the more people we have the less of a load you will have, im still waiting to get an email about the screen wake issue

 

[QuietStorm1785]

well surprise surprise, Im back with a wee lil update, STILL didnt get ril working on cm7, been trying for a few days, and now doing a test build of cm9... so far i had to completely mod the cm9 source just so it can build for me... pretty gay, took me a couple days that i coulda spent tryin to fix the ril issues in cm7...- so far it's compiling as im typing, taking forever too, EVEN with an amd 8 core processor and 8 gigs of ram. goin on an hour compiling... I'll keep everyone updated

 

[Snake X]

awesome!! Good luck

 

[hroark13]

well surprise surprise, Im back with a wee lil update, STILL didnt get ril working on cm7, been trying for a few days, and now doing a test build of cm9... so far i had to completely mod the cm9 source just so it can build for me... pretty gay, took me a couple days that i coulda spent tryin to fix the ril issues in cm7...- so far it's compiling as im typing, taking forever too, EVEN with an amd 8 core processor and 8 gigs of ram. goin on an hour compiling... I'll keep everyone updated

I have messed with CM9 for the Warp,
The ROMS I produced are really buggy and do not even boot all the time, so I decided I need working kernel source code before I go any further

here is my CM9 device folder, it still needs a lot of work, it may or may not help you


arthurcm9.zip





.

 

[hroark13]

here is the CM9 ROM I made a while back

It is a weird ROM

This is what you have to do to get it to boot

make sure you have a good CWM backup before you install this

install the zip in CWM

DO NOT do a factory wipe before you install it

after you install it, it should boot and you will be able to browse around a bit, it will eventually freeze on you, and you will need to do a battery pull

and then it will not boot into CM9 again unless you go into CWM and format data and do an advanced restore of your stock ROMS data partition

I really do not like releasing crap like this, but a few people are getting interested in CM9

I am not going to work on CM9 until we have working kernel source, but maybe some of this stuff will help Quietstorm

warp_cm9_buggy ashell.zip




,

 

[bads3ctor]

Don't feel so bad...same thing happened to me when trying to boot CM9 on the Transform Ultra. If I flashed the CM9 /system without touching /data, it would boot into a buggy CM9. You format /data....no boot. You might want to send a pm to penguinrepair....he seems to have an explanation why it does this.

 

[mikegmoney]

Is cm7 ever gonna be stable enough to have on warp?

 

[Deleted User]

Is cm7 ever gonna be stable enough to have on warp?

Yes, in time. We needed a good kernel source before cm7 or cm9 becomes a possibility

 

[hroark13]

Is cm7 ever gonna be stable enough to have on warp?

the problem is not stability, its trying to get the hardware to work, mainly the radio, and it is not looking good

 

[Snake X]

.

 

[Deleted User]

.

..

 

[Deleted User]

the problem is not stability, its trying to get the hardware to work, mainly the radio, and it is not looking good

Well I assumed that the kernel source was to help get that on track? I'd have to go back and read through the posts on here, I've been waiting for the kernel to continue, hence my absence.