2.11.2


Status
Not open for further replies.
Looks to me like your /data/system/theme/ folder doesn't exist or has insufficient permissions. See that's not the issue I'm experiencing because I run the following init.d script to check the folder exists at bootup.

Filename: "04defaulttheme"
Code:
#!/system/bin/sh
 
SYSTEM_FOLDER=/data/system
rm -r -f $SYSTEM_FOLDER/theme1
 
echo "dealing with default theme";
if [ ! -d $SYSTEM_FOLDER ];
  then
    mkdir -p $SYSTEM_FOLDER;
    chmod -R 777 $SYSTEM_FOLDER;
    chown system.system $SYSTEM_FOLDER;
fi
 
THEME_FOLDER=$SYSTEM_FOLDER/theme
THEME_BEGIN_FLAG=$SYSTEM_FOLDER/.theme_begin
THEME_END_FLAG=$SYSTEM_FOLDER/.theme_end
if [ ! -d $THEME_FOLDER ] || ( [ -f $THEME_BEGIN_FLAG ] && [ ! -f $THEME_END_FLAG ] );
  then
    rm -r $THEME_FOLDER;
    rm -r $SYSTEM_FOLDER/customized_icons_1;
    touch $THEME_BEGIN_FLAG;
    mkdir -p $THEME_FOLDER;
    chmod -R 777 $THEME_FOLDER;
    chown 1001.1001 $THEME_FOLDER;
    touch $THEME_END_FLAG;
fi
 
exit;

The issue I see in regards to Themes is related to the new DrmService, I've bypassed the online DrmService force close by deodexing the apk and making some modifications but they have some more checks in the way. I've bypassed some further background tasks which also fails but I need to force an integer to class any theme as valid.
 
Send me whole log? My ns didn't boot loop.

Sent from my MI 2 using Tapatalk 2
Sorry. I've lost logcat from terminal. My adb stopped working and I had to reboot. I've installed 2.11.2 after full wipe.
 
For me Xiaomi have made a great error!!! Miuiandroid.com is simply Miui on Europe and Mark & IbotPeaches have to be advised from Xiaomi. As Ibotpeaches says this looks like a slap in the face to all our communities. Then you require MiCredits that can only be purchased using a Chinese only service.
 
  • Like
Reactions: Quantum
this has to be by far the most failed update and disappointing too..I m back on 2.10.26.Just couldnt stand the new update.
 
Guys the workaround is pretty simple, 2.11.2 ThemeManager.apk is too screwed to fix via decompiling and smali editing (or atleast I'm not going to continue the headache).

IMPORTANT STEP: Navigate to [MENU KEY] > Settings > Apps > [ALL] > Locate and select 'Themes' > Select 'Force stop', followed by 'Clear cache' and finally 'Clear data'.

Now DO NOT open Themes app and instantly reboot straight into recovery.

Obtain 2.10.26 ThemeManager.apk from /system/app/ and content-types.properties from /system/lib/ - Using last weeks build (2.10.26) as the source for your device.

Within recovery ensure that the system partition is mounted.

Issue the following commands:

Code:
adb push /path/to/2.10.26/ThemeManager.apk /system/app/

followed by...

Code:
adb shell chmod 644 /system/app/ThemeManager.apk

and finally

Code:
adb push /path/to/2.10.26/content-types.properties /system/lib/

and reboot your device, enjoy your working ThemeManager!!

Please ensure to replace "/path/to/2.10.26/" with the path you saved your 2.10.26 files too.

NOTE: This guide presumes you have a working ADB Environment setup on your machine.

Lets hope MIUI fixes this issue for next week.

Courtesy of stickman89 / s89

Best Regards as always.
 
Oh, DRM now? I do not like the looks of this. What's next, pay for some critical service?

There are lots of other ROMs.
 
same problem too even with default themes and also with empty themes folder. still can't get rid the problem.

Using SGSII
 
Do what I mentioned above providing you have a working ADB environment, obviously skip the step where you clear Themes settings cache/data.
 
  • Like
Reactions: Quantum
Guys the workaround is pretty simple, 2.11.2 ThemeManager.apk is too screwed to fix via decompiling and smali editing (or atleast I'm not going to continue the headache).

IMPORTANT STEP: Navigate to [MENU KEY] > Settings > Apps > [ALL] > Locate and select 'Themes' > Select 'Force stop', followed by 'Clear cache' and finally 'Clear data'.
It works.
But theres FC when you choose full theme and hit icon with modules (bottom left corner). Its ok because you can choose the same within Mix tab.

Great idea. Thanks :)
 
so .. i can assume, that if they dont change that new policy of DRM themes, the next releases will have "this problem" to .. right
 
I believe it's down to the following:

ThemeManager\smali\miui\resourcebrowser\controller\online\DrmService*.smali tree
ThemeManager\smali\miui\resourcebrowser\view\ResourceOperationHandler*.smali tree

Basically removing all references to mService (DrmService Tree) within ResourceOperationHandler tree bypasses the Drm Service but then "onApplyEventPerformed()V" method within ResourceOperationHandler.smali calls for ResourceOperationHandler$CheckRightsTask*.smali tree for a response from mIsLegal to pass through which occurs doInbackground via Async. It doesn't catch a response and just force closes instead. Weird, I think they've missed some things from framework.jar @android/os/Environment.smali. Could be wrong though, I'm no smali expert. I understand quite a bit of it though and adapt quickly.
 
  • Like
Reactions: Quantum
Hey...all....I seem to have had the same problem of boot loop.....but i edited sony few things on update-script...and it installed fine...and am currently trying themes...and so far its upgrading themes....will see if it works fully....

Am using Sony Xperia S...
 
This is bullshit. Is there no way of fixing this without adb? My adb wont work in recovery so I'm basically stuck. Can't even downgrade.
 
so ... maybe change the thememanager from the last release to this new release in zip before flash ?
 
This is bullshit. Is there no way of fixing this without adb? My adb wont work in recovery so I'm basically stuck. Can't even downgrade.


hey.....if your problem is boot loop i can try help....

do u have a 7zip to unzip the file and edit Note++ to edit a few things i can suggest......???
 
Status
Not open for further replies.