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

Root [LINARO] AWEstruck v1.04 12/14/14 | [3.4.107] v1.05b6 5/30/15

Hey, all! I just got an Awe, and am very excited. After having been through the Optimus V (which was very nice, but physically bulky) and the Optimus Elite (simply craptacular), I am loving everything I see out of the Awe.

I am now running the AWEstruck beta for JB (KK didn't boot). It looks super smooth. One thing I am looking forward to is support for the 64 GB card I had in my Elite. So far, the phone is not seeing it. Is there any particular way it should be set up?
 
Upvote 0
Hey, all! I just got an Awe, and am very excited. After having been through the Optimus V (which was very nice, but physically bulky) and the Optimus Elite (simply craptacular), I am loving everything I see out of the Awe.

I am now running the AWEstruck beta for JB (KK didn't boot). It looks super smooth. One thing I am looking forward to is support for the 64 GB card I had in my Elite. So far, the phone is not seeing it. Is there any particular way it should be set up?
Still work in progress
 
Upvote 0
Hey, all! I just got an Awe, and am very excited. After having been through the Optimus V (which was very nice, but physically bulky) and the Optimus Elite (simply craptacular), I am loving everything I see out of the Awe.

I am now running the AWEstruck beta for JB (KK didn't boot). It looks super smooth. One thing I am looking forward to is support for the 64 GB card I had in my Elite. So far, the phone is not seeing it. Is there any particular way it should be set up?
I thought I had it working but haven't been able to test, my largest card is 32gb. Can you remove and reinsert the card, and grab me a dmesg and logcat? Thanks!
 
Upvote 0
Hey, all! I just got an Awe, and am very excited. After having been through the Optimus V (which was very nice, but physically bulky) and the Optimus Elite (simply craptacular), I am loving everything I see out of the Awe.

I am now running the AWEstruck beta for JB (KK didn't boot). It looks super smooth. One thing I am looking forward to is support for the 64 GB card I had in my Elite. So far, the phone is not seeing it. Is there any particular way it should be set up?
When u try to flash the kk ROM u have to do factory reset and I always format data I recommend using twrp recovery have less problems I found
 
Upvote 0
When u try to flash the kk ROM u have to do factory reset and I always format data I recommend using twrp recovery have less problems I found
Yeah, I thought I did, but it still didn't work. :( No biggie.

I thought I had it working but haven't been able to test, my largest card is 32gb. Can you remove and reinsert the card, and grab me a dmesg and logcat? Thanks!
last_kmsg.txt is below. You'll have to tell me how to get the other thing :)

But first, one big thing: Where is text messaging?? Did I delete something?

Code:
Format: Log Type - Time(microsec) - Message
Log type: B - since boot(excluding boot rom).  D - delta
B -         0 - SBL1, Start
B -       335 - scatterload_region && ram_init, Start
D -      1250 - scatterload_region && ram_init, Delta
D -         0 - HYJ:init_qd_cert.msm_hw_id[]=0x2bf90,0x7310e1
B -      3416 - sbl1_hw_init, Start
D -      8113 - sbl1_hw_init, Delta
B -     12352 - boot_flash_init, Start
D -    126697 - boot_flash_init, Delta
B -    154665 - Image Load, Start
D -    398391 - SBL2 Image Loaded, Delta
B -    554429 - default smpl time: 0x49
B -    555496 - real smpl time: 0x49
B -    556747 - hsu_boot_is_dc_charger_present=FALSE
B -    557662 - hsu_boot_is_battery_present=TRUE
B -    569923 - SBL1, End
D -    570502 - SBL1, Delta
                                                                                                                                                                                                                                                       
Format: Log Type - Time(microsec) - Message
Log type: B - since boot(excluding boot rom).  D - delta
B -    581604 - SBL2, Start
B -    582977 - scatterload_region & ram_init, Start
D -       488 - scatterload_region & ram_init, Delta
B -    586057 - sbl2_retrieve_shared_info_from_sbl1, Start
D -       884 - sbl2_retrieve_shared_info_from_sbl1, Delta
B -    589107 - sbl2_hw_init, Start
D -       488 - sbl2_hw_init, Delta
B -    590297 - boot_flash_init, Start
D -     28060 - boot_flash_init, Delta
B -    618479 - boot_config_data_table_init, Start
D -    205722 - boot_config_data_table_init, Delta
B -    824323 - sbl2_hw_init_secondary, Start
D -      1220 - sbl2_hw_init_secondary, Delta
B -    829081 - Image Load, Start
D -         0 - HYJ:ou_field_info.enable_jtag[]=0x0,oem_id = 0x4
D -     89823 - TZ Image Loaded, Delta
B -    918904 - tz_exec_func:enable_jtag= 0x0,oem_id = 0x4
B -    919239 - Tz Execution, Start
D -     83112 - Tz Execution, Delta
B -   1003084 - Image Load, Start
D -         0 - HYJ:ou_field_info.enable_jtag[]=0x0,oem_id = 0x4
D -     71278 - RPM Image Loaded, Delta
B -   1074393 - Image Load, Start
D -         0 - HYJ:ou_field_info.enable_jtag[]=0x0,oem_id = 0x4
D -    111294 - SBL3 Image Loaded, Delta
B -   1185718 - SBL2, End
D -    604144 - SBL2, Delta
                                                                                                                                                                                                              B -   2268041 - qfprom_read_fuse_secboot exit
B -   2268132 - check_parameter magic:0xffffffff,0xffffffff
B -   2268193 - qfprom_check_diag_parameter: no operation!
B -   2268224 - sbl3_qfprom_test exit
B -   2268986 - SBL3, End
D -   1080158 - SBL3, Delta
it, Delta
B -   1189774 - boot_flash_init, Start
D -    469944 - boot_flash_init, Delta
B -   1659779 - zte sbl3 keypad_detect v1.1...
B -   1779370 - boot_smem_init, Start
D -       701 - boot_smem_init, Delta
B -   1780163 - sbl3_hw_init_secondary, Start
D -    108763 - sbl3_hw_init_secondary, Delta
B -   2141466 - sbl3 power reason=0x1,zte_hw_reset_flag=0,start
D -         0 - Sbl3 power reason, Delta
B -   2142777 - Image Load, Start
D -         0 - HYJ:ou_field_info.enable_jtag[]=0x0,oem_id = 0x4
D -    122397 - APPSBL Image Loaded, Delta
B -   2265204 - sbl3_efs_handle_cookies, Start
D -       518 - sbl3_efs_handle_cookies, End
B -   2265784 - sbl3_wait_rpm_boot, Start
D -         0 - sbl3_wait_rpm_boot, Delta
B -   2265845 - sbl3_rollback_version_update, Start
D -         0 - sbl3_rollback_version_update, End
B -   2265936 - sbl3_qfprom_test enter
B -   2265967 - qfprom_read_fuse_simlock enter
B -   2266028 - qfprom_read_fuse enter
B -   2266912 - qfprom_read_fuse ext
B -   2267004 - read_simlock BL_VERIFY OK data[2]:0x418000,0x0
B -   2267034 - qfprom_read_fuse_simlock exit
B -   2267034 - qfprom_read_fuse enter
B -   2267888 - qfprom_read_fuse ext
B -   2267980 - read_secboot BL_VERIFY OK data[2]:0x31,0x0
           welcome to lk

platform_init()
target_init()
display_init(),target_id=7010.
lizhiye, enter display_init
lizhiye msm8960_mipi_panel_power 
Config MIPI_VIDEO_PANEL.

 panel  chip id is 0

 panel  chip id is 1e000022

 panel  chip id is 6125522

 lcd_panel_id =13
 mdp_dsi_video_config! in mdp4 

 pinfo->lcdc.h_back_porch  =100Turn on MIPI_VIDEO_PANEL.
Video lane tested successfully
read_boot_mode_mmc: boot_mode: 0
HYJ:boot_mode :0
HYJ:step03:
reboot_mode:0xef7bffef
HYJ: dload test 1
Power on reason 1
Power on reason 1
ZTE target_pause_for_battery_charge return 0 
read_sdlog_flag: sdlog flag: 0
ERROR: Image Invalid! Decryption failed!

kernel  @ 80208000 (8232008 bytes)
ramdisk @ 82200000 (690124 bytes)
cmdline = 'androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3'

Booting Linux
cmdline: androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.emmc=true androidboot.serialno=40535c40 androidboot.baseband=msm sdlog.flag=disable androidboot.mode=normal lcd_id=13
booting linux @ 0x80208000, ramdisk @ 0x82200000 (690124)
HYJ: dload test 3 machtype 7010   0x80200100

No errors detected
 
Upvote 0
I'm not dead yet. Getting that kernel to boot was a brick wall, but here's something to file under "good things come to those who wait." SuperR alerted me to ZTE releasing KitKat for the Boost Max that is also already working on the Warp. The boot code is in tact! What more, I can get it to boot. Still a barrier though, it won't display anything on the Awe. In any case it's a few steps closer...
 
Upvote 0
I figured this is the best place to ask this; What cpu does the Awe have under the hood? I can't find a reliable answer, CPUz says its an msm8930/Adreno 305, Zte's website says its an msm8960, I've also seen many other combos of more or less the same numbers, msm8690, msm8630... I'm inclined to believe its an S4 msm8930. Could someone clarify this/ confirm?
 
  • Like
Reactions: dvdavid888
Upvote 0
Yeah it's either an 8930 or a variant. It uses the 8930 code in the kernel. Where you'll see 8960 is from Qualcomm categorizing by the flagship soc of that generation. So the source code comes from the 8960 generation.

Ah! That explains a lot of what I see going on in the library files, I've noticed that many of them that are related to hardware have 8960 in the names. That wasn't helping the confusion either. Thank you for clearing that up, I figured you'd be well aware with all the kernel work you do.
 
  • Like
Reactions: dvdavid888
Upvote 0
Still trying to figure out why the n9520 kernel isn't displaying. In the meantime, I decided to port the n9520 audio drivers to the current kernel since if I had my volume on it had an annoying tendency to reboot on sounds. Testing over the last 5 days has been promising. I also took advantage and patched the kernel up as well as updating the toolchain. Links in op.
 
Upvote 0
I had another sound induced boot loop today, and no kernel panic. I think my next avenue of investigation will be to try the sound libs from the Warp 4G.


Im on LAwe as well and have had problems with bluetooth with the older builds and this one as well. It will randomly reboot. Here is the kmsg. Let me know if I can be of more help. And thanks again for all your hard work!!!

Culprit: [06-01 22:09:28.565] [0][128: kworker/u:3]Kernel panic - not syncing: wcnss_8960: SMSM reset request received from Riva

Looks like the WCNSS update I did a while back isn't working correctly on your phone. I'll try pulling the latest code, and maybe update the bluetooth drivers to be safe. Thanks for the log!
 
  • Like
Reactions: urrachris
Upvote 0
I had another sound induced boot loop today, and no kernel panic. I think my next avenue of investigation will be to try the sound libs from the Warp 4G.




Culprit: [06-01 22:09:28.565] [0][128: kworker/u:3]Kernel panic - not syncing: wcnss_8960: SMSM reset request received from Riva

Looks like the WCNSS update I did a while back isn't working correctly on your phone. I'll try pulling the latest code, and maybe update the bluetooth drivers to be safe. Thanks for the log!
Hey Spock how the oc kernal coming along?
 
Upvote 0
[QUOTE="Culprit: [06-01 22:09:28.565] [0][128: kworker/u:3]Kernel panic - not syncing: wcnss_8960: SMSM reset request received from Riva

Looks like the WCNSS update I did a while back isn't working correctly on your phone. I'll try pulling the latest code, and maybe update the bluetooth drivers to be safe. Thanks for the log![/QUOTE]

Awesome- Let me know if there's anything else I can do (or test).
 
Upvote 0
I just flashed this kernel, v. 1.05 beta 6, running L Awe rom. It is awesome, however I'd like to point out that the audio issue is not specific to Bluetooth, by my experience. My local MP3 files play only the right channel. The files are 320kbps, 44,100, Stereo. Lower bitrate, joint stereo files seem to produce correct stereo phasing. Additionally, streaming Pandora or Spotify seem to play audio on both channels, while streaming by way of Liquid Bear or NetEase Cloud Music only play the right channel. The issue seems to be related to the audio type. I will do some more investigating, and post an update if I make any additional discoveries. If you'd like me to produce any logs or anything, please let me know.
 
  • Like
Reactions: dvdavid888
Upvote 0
Hi spock1104, Thanks for your reply. I have found that the 1.04 and 1.05 beta 6 versions linked from the first thread post suffer from the audio channel issue previously mentioned, which I've been unable to mitigate entirely. I'll cruise through this thread more thoroughly and try to find an active link for an older version to try.
Regardless, the kernel is really nice. Thanks to spock1104 and the other developers for their hard work.

They have likely expired.
 
  • Like
Reactions: dvdavid888
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones