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

Root [BETA][4.4.2] Stock KitKat

spock1104

spock1104

Android Expert
Warp speed Mr. Sulu

Here are the results of what I call project Sulu, bringing the Warp 4G stock ROM to the AWE. Thanks to SuperR for the Warp 4G ROM and modhatter6811 for schooling me on how to recompile framework-res.apk without it crashing. Just like my Cyanogenmod version, this uses the kernel from the N9520 Max.

Partially working:
Camera: Stock app doesn't work, use any other

Not working:
Keystore - Security menu crashes, no sideloading without a PC, can't uninstall apps

Working: everything else

http://www.mediafire.com/download/8ujcazsyvmwqkld/awe_stock_442_beta1.zip
MD5: 4E3D5AC520F5E6BE88C6CCBA8B51DC24

kernel source: https://github.com/spock1104/android_kernel_zte_msm8930/

I need to talk about they keystore for a moment, as that's the achilles heel of this ROM. If I or anyone else (please please please) can figure out how to resolve this the ROM will more or less be complete. Since the Awe never got past 4.1 officially, we never received a modem with keymaster files. I've grabbed them from the Warp 4G modem and placed them in /system/vendor/firmware/keymaster and set permissions on them. This itself doesn't seem to be an issue, I verified that both the Warp 4G and the Max use the same keymaster files. However, the logcat shows that the keystore fails to load with "operation not permitted" and unfortunately I've forgotten what the dmesg error is. Yes, the internet will tell you that this is a permissions issue, but I've tried that and still not gotten past the error. I think this could be an app or library checking the phone model, but that's just speculation, I really don't know. So to avoid delays I'm releasing this to the community and hoping someone (anyone, please! bueller?) will be able to solve the last piece.
 
dmesg shows this, starting to wonder if there's either a kernel issue or kernel workaround.

Code: 
<4>[10-03 15:58:06.826] [0][4371: keystore]QSEECOM: qseecom_load_app: App (keyma
ster) does'nt exist, loading apps for first time
<3>[10-03 15:58:06.836] [0][4371: keystore]QSEECOM: qseecom_load_app: scm_call f
ailed resp.result unknown, -12
<3>[10-03 15:58:06.836] [0][4371: keystore]QSEECOM: qseecom_ioctl: failed load_a
pp request: -14
<4>[10-03 15:58:06.836] [0][4371: keystore]QSEECOM: qseecom_release: data->relea
sed == false
<3>[10-03 15:58:06.836] [0][4371: keystore]QSEECOM: qseecom_release: Unsupported
clnt_handle_type 4
<4>[10-03 15:58:06.836] [0][4371: keystore]QSEECOM: qseecom_release: data->relea
sed == false
<3>[10-03 15:58:06.836] [0][4371: keystore]QSEECOM: qseecom_release: Unsupported
clnt_handle_type 4attempt_reverse_boost_fix

looks to be a problem with the trustzone judging by the scm_call failure ?? Admittedly very lost right now
 
Last edited:
This part from the logcat seems important too

Code: 
D/QSEECOMAPI: ( 3255): QSEECom_start_app sb_length = 0x2000
D/QSEECOMAPI: ( 3255): App is not loaded in QSEE
E/QSEECOMAPI: ( 3255): Error::Load image request failed ret = -1, errno = 14
E/QSEECOMAPI: ( 3255): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 3255): QSEECom_start_app sb_length = 0x2000
D/QSEECOMAPI: ( 3255): App is not loaded in QSEE
E/QSEECOMAPI: ( 3255): Error::Load image request failed ret = -1, errno = 14
E/QSEECOMAPI: ( 3255): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 3255): Loading keymaster app failied
 
spock1104 said:
If anyone is daring enough to risk bricking an AWE for science, there's a possibility that flashing SuperR's partition updater will fix this. I am not so daring.

http://androidforums.com/threads/rom-warp-4g-stock-b12-kitkat-4-4-2-deodexed-and-unmodified.878797/

In case you need to switch back and end up in a state where you can flash files, this will undo the damage:

http://www.mediafire.com/download/cd6q1xy0q13rgdl/N800_B07_Partitions.zip
Click to expand...
I try it when I get home
 
You must log in or register to reply here.
Back
Top Bottom