• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM]CM10 - Boost Force[WIP]

I just saw your dmesg output and looks like more than just the module layout is disagreeing. if you had another module that had those same parameters that are erroring then the same trick might work, but I doubt any other modules contain cnss_wlan_register_pm_ops whatever others are erroring. Perhaps these could all be the same as the module layout? Probably not.

Cheers,
-SB
 
I just saw your dmesg output and looks like more than just the module layout is disagreeing. if you had another module that had those same parameters that are erroring then the same trick might work, but I doubt any other modules contain cnss_wlan_register_pm_ops whatever others are erroring. Perhaps these could all be the same as the module layout? Probably not.

Cheers,
-SB

dmesg was from the custom built from source one... not the stock one, so if you want to try the hex trick you can but when i tried it it caused more different errors and still couldnt load the module
 
dmesg was from the custom built from source one... not the stock one, so if you want to try the hex trick you can but when i tried it it caused more different errors and still couldnt load the module

ok, well if you already tried it, then I guess it won't work.

Was worth a shot I guess. I don't really have a way to test bc I am using DSF .7. I can't do CM10 bc I really need wifi.

I wish you guys luck in finding a solution.
Cheers,
-SB
 
Are there other phones out there using this same SOC like maybe the avid or droid incredible 4g lte the that maybe we could try using the pima wlan driver from their cm10 port and using the same module layout hack to try loading the module from?

Cheers,
-SB
 
There is a whole lot more dev happening on incredible 4g lte bc it's an HTC but the kernel and system layout are also quite different...

Possibly their cm port is using 3.4 kernel also bc I'm pretty sure HTC released that in an ota update. I haven't checked really.

I notice they definitely have kit Kat 4.4 aosp and cm11.

I really wish the ZTE dev community could equal that, but you have gotta expect more dev on an HTC :-(
 
the link posted is not working. says it is generating too much traffic. anyone have a mirror for this?
upload_2015-10-13_11-15-29.png
 
There is already a fully functional JB 4.1.2 rom for ZTE Force.

http://androidforums.com/threads/fi...an-rom-public-release-update-from-ics.886408/

It comes from an official? Textnow ZTE Force n9100.

The sawbones version has the issue with the upside down front camera.

My freedompop version has this fixed.

Root with Kingo root or any other. Copy the file below to your sd card. Hold down volume down key and power key at the same time you start up the phone. When it vibrates it means it is going to go to recovery. Freedompop already has Clockwork Mod 6.0.3.0 touch recovery on it. It has issues though. Go to restore and backup. Backup to external sd then wipe cache, wipe dalvik cache (advanced menu). wipe data/factory reset, and then install this zip from external sd card.

https://www.dropbox.com/s/6y2lu3s5qlen812/ZTE_FORCE_JB_Freedompop.zip?dl=0

Known Issues: (updated 3/21/2015)

1. ICCID in "Settings- About Phone - Status" shows as unknown (cosmetic only)
2. If your not paying FreedomPop for Wi-Fi tether, you can get it for free (will use data limit) using the included Wi-Fi Tether app.

Change Device profile to: Generic ICS/JB (wlan0)
Change Setup Method to: Netd-Ndc (master)
Check WiFi-driver reload (first one only)

These settings allow wifi tether but the only way to get Wi-Fi back after use is to reboot the phone.

If you feel like it, you may upgrade your recovery image to non touch 6.0.4.4. Everything appears to work in it.

http://androidforums.com/threads/recovery-unofficial-cwm-v6-0-4-4.749083/

If you want to go back to an ICS nandroid CWM backup run this zip first to restore the necessary ICS partitions:

https://www.dropbox.com/s/sf82i0c2sdpxxb9/ZTEForceICSPartitions.zip?dl=0


You can now have all the apps from the FreedomPop version without all the FreedomPop apps but with the Sprint Apps instead (Sprint Mobile ID, Sprint Voicemail, Sprint Zone).

Note: Sprint Zone does not appear in my list of apps on my FreedomPop phone. I think its suppose to show up as "Sprint Zone" for Sprint users, "Boost Zone" for Boost Mobile users, and "My Account" for Virgin Mobile users. Correct me if I am wrong and do let me know if this app does shows up on these carriers.

Instructions (works on Sawbones rom too to convert to Sprint, Boost, or Virgin):

Boot into recovery.
Wipe Dalvik Cache (advanced menu)
Wipe Cache.
Wipe Data/Factory Reset
Install the FreedomPop version rom or Sawbones rom.
DO NOT REBOOT YET!
Install one of the undo zips below.
Reboot.

Download the undo for your carrier:

Generic:
https://www.dropbox.com/s/eiqie21s3ckhr9t/undoFP.zip?dl=0

Sprint:
https://www.dropbox.com/s/b59uqfzc5wytz6y/undoFP - Sprint.zip?dl=0

Virgin Mobile:
https://www.dropbox.com/s/3amq6ed2wrlkqt8/undoFP - Virgin.zip?dl=0

Boost:
https://www.dropbox.com/s/y5gf2fgj973qou4/undoFP - Boost.zip?dl=0

The generic version will display the "android" boot animation just like the sawbones version and should be safe for all users.

The other carrier versions will display their own carrier's boot animation. Virgin Mobile even has its own boot sound. On Sprint's version, it also creates a slightly different Sprint Mobile ID app icon (normal icon but with a yellow outline).

I can not test whether the other carrier versions causes any ill effects (like MMS not working). If you have any issues please report them in this thread and go back to the generic version and see if that fixes your problem.
 
Last edited:
Junkie2100: Maybe you can use the version above to fix your issues.

Maybe your Wi-Fi issue may be related to the included wifi tether app not being able to restore Wi-Fi after use.

The upside down front camera I think was fixed by adding back library file(s) that were removed from the sawbones version.

Maybe this thread will help for the proximity sensor:

http://forum.xda-developers.com/showthread.php?t=1882725
 
Last edited:
Back
Top Bottom