Root MS323 System UI FC FIX?

[vm03]

@zlaja84 @crutchcorn @LitrosNub
Better use /dev/block/platform/msm_sdcc.1/by-name/aboot and another partition "by-name". It less dangerous! On ms323 and d320 number of partition is different!

 

[Member1771050]

He's got a point, I haven't thought about that.

 

[LitrosNub]

@vm03 @zlaja84 Holy Holy Holy, can someone give me all the commands to do. I know the backup the Aboot, but how to flash? Give me a rundown of the commands. I got completly confushed when VM said the other command.

 

[Member1771050]

@vm03 @zlaja84 Holy Holy Holy, can someone give me all the commands to do. I know the backup the Aboot, but how to flash? Give me a rundown of the commands. I got completly confushed when VM said the other command.

I assume you already copied aboot to internal.
Luckily, aboot is on the same partition for both d320 and ms323, BUT to be sure:

(via PC):
adb shell
su
dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot

 

[LitrosNub]

I assume you already copied aboot to internal.
Luckily, aboot is on the same partition for both d320 and ms323, BUT to be sure:

(via PC):
adb shell
su
dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot

Ah, alright. Thanks for clearing that up. Doing it now.

 

[LitrosNub]

@zlaja84 @vm03 Aboot done! Time to test it out by updating, want me to flash a new ROM or update by OTA?

 

[Member1771050]

A

@zlaja84 @vm03 Aboot done! Time to test it out by updating, want me to flash a new ROM or update by OTA?

Anyway is fine, aboot isn't touched by flash process.

 

[LitrosNub]

A

Anyway is fine, aboot isn't touched by flash process.

Doing the final CM12 OTA (Not 12.1) right now. Wish me luck (was on 2-19)

 

[LitrosNub]

A

Anyway is fine, aboot isn't touched by flash process.

...

annnd it failed.

want me to flash something like nameless? OTA cm said NOPE.

 

[Member1771050]

...

annnd it failed.

want me to flash something like nameless? OTA cm said NOPE.

Just flas anything

 

[LitrosNub]

@zlaja84 guess it's a no go. nothing worked. aboot is not the problem.

 

[xRaZeR_FuZioNx]

@zlaja84 guess it's a no go. nothing worked. aboot is not the problem.

We will get to the bottom of this. That means what you said about it being in the CM kernel could be true, since every FCing ROM uses a CM-based kernel.

 

[LitrosNub]

We will get to the bottom of this. That means what you said about it being in the CM kernel could be true, since every FCing ROM uses a CM-based kernel.

Look here, @Bad_MOFO_33 found the bug (MAYBE) http://androidforums.com/threads/unofficial-d320n-d325-ms323-5-1-1-namelessrom-2-1.915761/ Page 3-4. @zlaja84 will maybe have a build out without the file that's causing it tomarrow.

 

[xRaZeR_FuZioNx]

Look here, @Bad_MOFO_33 found the bug (MAYBE) http://androidforums.com/threads/unofficial-d320n-d325-ms323-5-1-1-namelessrom-2-1.915761/ Page 3-4. @zlaja84 will maybe have a build out without the file that's causing it tomarrow.

Just made an edit to the msm8610.mk for Resurrection Remix, building now. Will post results tommorow. *Prays for no errors, battery depletion, or FC's*

 

[xRaZeR_FuZioNx]

Sadly, it didn't work for me.

 

[LitrosNub]

Sadly, it didn't work for me.

:/

 

[metrohackz]

I still think somebody should emergency cs flash 10a then regular emergency flash 10b

 

[Member1771050]

Sadly, it didn't work for me.

My laptop thanks you, you spared him of few hours of constant 95°C

I'm still gonna try switching keymaster to slim's and then build though.

 

[vm03]

Removing keymaster we get less security...
http://nelenkov.blogspot.ru/2013/08/credential-storage-enhancements-android-43.html
keymaster code is small https://github.com/CyanogenMod/android_hardware_qcom_keymaster

 

[LitrosNub]

Any of you guys, I got back to stock 10a, any test you want me to do?

 

[xRaZeR_FuZioNx]

Any of you guys, I got back to stock 10a, any test you want me to do?

Try what @metrohackz suggested.

 

[LitrosNub]

Try what @metrohackz suggested.

Results: Emergency_CS flashed from 10a to 10b, then unlocked bootloader and all the usuall stuff. Flashed CM12.1, Still FC.

@metrohackz @xRaZeR_FuZioNx

 

[xRaZeR_FuZioNx]

Results: Emergency_CS flashed from 10a to 10b, then unlocked bootloader and all the usuall stuff. Flashed CM12.1, Still FC.

@metrohackz @xRaZeR_FuZioNx

[emoji20] I guess we need to wait for @vm03 to get his MS323 and find the problem.

 

[metrohackz]

Results: Emergency_CS flashed from 10a to 10b, then unlocked bootloader and all the usuall stuff. Flashed CM12.1, Still FC.

@metrohackz @xRaZeR_FuZioNx

No man you were supposed to just emergency flash

 

[bogarty]

MS323 System UI FC FIX?

Yes. Flash "SlimLP Alpha" by zlaja84. It does not have FC issues on MS323. Didn't have to touch aboot either. Just flash with TWRP only though, not CWM. CWM leaves you with buttons that don't work in rom on ms323. Rear camera & flash are the only things that don't work(as everyone knows) & super user was kind of buggy at first. Binary didn't want to install until after a few reboots, but after it did everything has been pretty smooth.