Release MIUI Multi-Lang ROM 2.7.13 [ICS]


Status
Not open for further replies.
So this is Sense Based on the HTC One S? With the Sense camera?

And on the HTC One S, it isn't needed to flash boot.img via Fastboot?
 
iBotPeaches thank you
and all translators for your hard work! Can you explain why you don't include res images (Drawable-Xx-hdpi/ Drawable-Xx)? All languages are separated...

And one more: my nick is "Vlaaaad", not "Vlaaad" :)
 
I have the greek translations ready since last week,even got a repo but i m not familiar with it.Anyone can guide me so i can sync my local files with the repo?
 
Montblanc0 said:
Thanks for your reply, iBotPeaches! You mean something like values_it, drawable_it? Is that all?
Click to expand...
No all wrong.
You have to compile values-it via apktool, because those are binary xmls. Drawable-it-hdpi you can just 7za into apk/res/

0. install framework-res.apk (apktool if framework-res.apk)
1. Decompile framework-res.apk (apktool d framework-res.apk)
2. Put values-it into /res
3. Compile (apktool b framework-res.apk)
4. copy resources.arsc from build folder into framework-res.apk (original) via 7za command
5. copy drawable images into /res via 7za command

(For how to use 7za just man page in linux, and apktool you can find everywhere in google)
 
  • Like
Reactions: Montblanc0
Vlaaaad said:
iBotPeaches thank you
and all translators for your hard work! Can you explain why you don't include res images (Drawable-Xx-hdpi/ Drawable-Xx)? All languages are separated...

And one more: my nick is "Vlaaaad", not "Vlaaad" :)
Click to expand...

Sorry for the nickname. Um, I thought our script handled Drawable-Xx-hdpi correctly. I'll double check.
 
I install this Rome for the first time
can someone please tell me how is the battery live!!!!!
or install a different kernel???
 
Hello,

can anyone confirm that this version is working on a Samsung Galaxy S3? I can't install the rom.. I'm getting an installation error in CWM.. I'm able to install other roms fine..

Best regards,

Marcel
 
Acid said:
No all wrong.
You have to compile values-it via apktool, because those are binary xmls. Drawable-it-hdpi you can just 7za into apk/res/

0. install framework-res.apk (apktool if framework-res.apk)
1. Decompile framework-res.apk (apktool d framework-res.apk)
2. Put values-it into /res
3. Compile (apktool b framework-res.apk)
4. copy resources.arsc from build folder into framework-res.apk (original) via 7za command
5. copy drawable images into /res via 7za command

(For how to use 7za just man page in linux, and apktool you can find everywhere in google)
Click to expand...

Thank you so much for your howto! Luckily, I can use apktool. :)
 
Xiaomi M1 endless boot

Yes, i renamed to update.zip
Yes, i did it from the MiRecovery
Yes, i already did Upgrade Partition
Yes, i tried brushing first a 2.7.13 Original China ROM (working) and then reflashed again this one but endless boot comes again
Yes, i tried brushing again and updating from the update app inside the phone... results: endless boot again
Yes, i'm using the latest MiFlash (2.7.13 Rom from China works....)

This is the only thing the logcat can log:

Code: 
logcat
shell@android:/ $ logcat
--------- beginning of /dev/log/system
Vold    (  140): Vold 2.1 (the revenge) firing up
Vold    (  140): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
Vold    (  140): Volume udisk state changing -1 (Initializing) -> 0 (No-Media)
Vold    (  140): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
Vold    (  140): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
RPC    (  155): 3000008c:00050000 sending call (XID 1).
ONCRPC  (  175): Setup RPC Call for task 40145270
ONCRPC  (  175): oncrpc_xdr_call_msg_start: Prog: 30000048, Ver: 00040001, Proc: 00000000
ONCRPC  (  175): xdr_std_msg_send_call: Sent Xid: 0, Prog: 30000048, Ver: 00040001, Proc: 00000000
ONCRPC  (  175): xdr_std_msg_send_call: Received Reply Xid: 0, Prog: 30000048, Ver: 00040001, Proc: 00000000
ONCRPC  (  175): Setup RPC Call for task 40145270
ONCRPC  (  175): oncrpc_xdr_call_msg_start: Prog: 30000048, Ver: 00040005, Proc: 0000001d
ONCRPC  (  175): xdr_std_msg_send_call: Sent Xid: 1, Prog: 30000048, Ver: 00040005, Proc: 0000001d
ONCRPC  (  175): xdr_std_msg_send_call: Received Reply Xid: 1, Prog: 30000048, Ver: 00040005, Proc: 0000001d
ONCRPC  (  175): Setup RPC Call for task 40145270
ONCRPC  (  175): oncrpc_xdr_call_msg_start: Prog: 3000000e, Ver: 00090001, Proc: 00000009
ONCRPC  (  154): Setup RPC Call for task 40151270
ONCRPC  (  154): oncrpc_xdr_call_msg_start: Prog: 300000b5, Ver: 00020001, Proc: 00000000
ONCRPC  (  154): xdr_std_msg_send_call: Sent Xid: 0, Prog: 300000b5, Ver: 00020001, Proc: 00000000
ONCRPC  (  175): xdr_std_msg_send_call: Sent Xid: 2, Prog: 3000000e, Ver: 00090001, Proc: 00000009
ONCRPC  (  154): xdr_std_msg_send_call: Received Reply Xid: 0, Prog: 300000b5, Ver: 00020001, Proc: 00000000
ONCRPC  (  154): Setup RPC Call for task 40151270
ONCRPC  (  154): oncrpc_xdr_call_msg_start: Prog: 300000b5, Ver: 00020001, Proc: 00000004
ONCRPC  (  154): xdr_std_msg_send_call: Sent Xid: 1, Prog: 300000b5, Ver: 00020001, Proc: 00000004
ONCRPC  (  154): xdr_std_msg_send_call: Received Reply Xid: 1, Prog: 300000b5, Ver: 00020001, Proc: 00000004
ONCRPC  (  154): Setup RPC Call for task 40151270
ONCRPC  (  154): Setup RPC Call for task 40151270
ONCRPC  (  154): rpc_handle_rpc_call: for Xid: a, Prog: 310000b5, Vers: 00020001, Proc: 00000001
ONCRPC  (  154): rpc_handle_rpc_call: Find Status: 0 Xid: a
ONCRPC  (  154): oncrpc_proxy_handle_cmd_rpc_call: Dispatching xid: a
ONCRPC  (  154): rpc_handle_rpc_call: for Xid: b, Prog: 310000b5, Vers: 00020001, Proc: 00000001
ONCRPC  (  154): rpc_handle_rpc_call: Find Status: 0 Xid: b
ONCRPC  (  154): oncrpc_proxy_handle_cmd_rpc_call: Dispatching xid: b
ONCRPC  (  175): xdr_std_msg_send_call: Received Reply Xid: 2, Prog: 3000000e, Ver: 00090001, Proc: 00000009
RPC    (  155): 3000008c:00050000 received REPLY (XID 1), grabbing mutex to wake up client.
RPC    (  155): 3000008c:00050000 call success.
ONCRPC  (  175): Setup RPC Call for task 40145270
ONCRPC  (  175): oncrpc_xdr_call_msg_start: Prog: 3000000e, Ver: 00090001, Proc: 00000009
ONCRPC  (  175): xdr_std_msg_send_call: Sent Xid: 3, Prog: 3000000e, Ver: 00090001, Proc: 00000009
ONCRPC  (  175): xdr_std_msg_send_call: Received Reply Xid: 3, Prog: 3000000e, Ver: 00090001, Proc: 00000009
ONCRPC  (  175): Setup RPC Call for task 40145270
ONCRPC  (  175): oncrpc_xdr_call_msg_start: Prog: 30000048, Ver: 00040001, Proc: 00000012
ONCRPC  (  175): xdr_std_msg_send_call: Sent Xid: 4, Prog: 30000048, Ver: 00040001, Proc: 00000012
ONCRPC  (  175): xdr_std_msg_send_call: Received Reply Xid: 4, Prog: 30000048, Ver: 00040001, Proc: 00000012
ONCRPC  (  175): Setup RPC Call for task 40145270
ONCRPC  (  175): oncrpc_xdr_call_msg_start: Prog: 30000048, Ver: 00040001, Proc: 00000017
ONCRPC  (  175): xdr_std_msg_send_call: Sent Xid: 5, Prog: 30000048, Ver: 00040001, Proc: 00000017
ONCRPC  (  175): xdr_std_msg_send_call: Received Reply Xid: 5, Prog: 30000048, Ver: 00040001, Proc: 00000017
ONCRPC  (  175): Setup RPC Call for task 40145270
ONCRPC  (  175): oncrpc_xdr_call_msg_start: Prog: 3000000e, Ver: 00090001, Proc: 00000009
ONCRPC  (  175): xdr_std_msg_send_call: Sent Xid: 6, Prog: 3000000e, Ver: 00090001, Proc: 00000009

P.D: and.... YES!. i did all wipes
 
ehrans said:
after few mins without touch it, the logcat show more things.... a bootloop

http://www.mediafire.com/download.php?25k3tkjhlr5jo2j

there is the log
Click to expand...

Code: 
F/libc    1450: Fatal signal 11 SIGSEGV at 0x5941a282 code=1

We don't modify any of the libs in any of our builds. ever. Why your lib is corrupted makes no sense. I know you said, "yes I did this", but did you check the MD5 sum of the ZIP? Looks like a classic corrupted ZIP file to me.
 
ifrid89 said:
Try substitute your NetworkLocation.apk with the one in this attachment (extracted from a previous version of Miui).
You should use an app like Root Explorer for the substitution ;)
I always reccommend a backup before doing so
Click to expand...

This also works on Sensation? o_O
 
Someone can help me to create the Framework-Fix-File. I use Italian language on Samsung i9100.
Thanks.

R.
 
Hello,

I finally was able to install this rom.. But I have a strange problem.. (with each MIUI ROM) After doing a reboot, the statusbar stopped working (i'm getting an error) Does anyone know this problem? Another problem is that the automatic app killer that you can open by keeping the homebutton pressed doesn't work anymore after a reboot.

The logs are saying this:

java.lang.RuntimeException: Unable to create service com.android.systemui.SystemUIService: java.lang.SecurityException: invalid status bar icon slot: bluetooth_handsfree_battery
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2277)
at android.app.ActivityThread.access$1600(ActivityThread.java:128)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1215)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4514)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:993)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:760)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.SecurityException: invalid status bar icon slot: bluetooth_handsfree_battery
at android.os.Parcel.readException(Parcel.java:1327)
at android.os.Parcel.readException(Parcel.java:1281)
at com.android.internal.statusbar.IStatusBarService$Stub$Proxy.setIcon(IStatusBarService.java:372)
at android.app.StatusBarManager.setIcon(StatusBarManager.java:148)
at com.android.systemui.statusbar.phone.PhoneStatusBarPolicy.<init>(PhoneStatusBarPolicy.java:210)
at com.android.systemui.statusbar.phone.PhoneStatusBar.start(PhoneStatusBar.java:349)
at com.android.systemui.SystemUIService.onCreate(SystemUIService.java:93)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2267)
... 10 more
 
Aaaah thanks! So it's not because of my phone..

I will install this version for now, and do not reboot the device for now.. Can I do a live update saturday with the device enabled? Or do I have to download the ROM again and install it from the recovery..
 
powermarcel10 said:
Aaaah thanks! So it's not because of my phone..

I will install this version for now, and do not reboot the device for now.. Can I do a live update saturday with the device enabled? Or do I have to download the ROM again and install it from the recovery..
Click to expand...

We don't OTA MULTI ROMs, as they are still considered Release Candidates. You may download from your device. Reboot into recovery. Flash from sd card.
 
Status
Not open for further replies.

Similar threads

ingbrzy
  • Sticky
HyperOS 2.0 HyperOS 2.0 STABLE RELEASE
Replies
655
Views
326K
HyperOS
Murke
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
330K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
43K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
44K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.6.3
Replies
46
Views
46K
HyperOS
din.ibrahim
D
Top Bottom
Back