Root [ROM][PORT][FINAL] MIUI 1.11.25-Triumph | 113011-2 (GB 2.3.7 based)

[mantera]

This the error message I got:

CWM-based Recovery v5.0.2.3
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log

If I try some of the commands in the CWM the working logo appears and it freezes. v4.0.1.5 will work, but will not let me flash this ROM. What could I be doing wrong?

What exactly is this "working logo" that you are talking about? It sounds like you're not pressing the MENU key to select options and instead are pressing the Power key...

 

[ipaint666]

ya, it sounds like thats what he is doing.

Also, don't worry about those error messages,
I get those evey time I load CWM.
I don't know why... but I get them.

 

[Prey521]

Is anyone able to set Google Voice as their default dialer? I don't get the option at all when I make a call. All I get is Dialer and Skype options but not GoogleVoice. I've tried clearing all defaults and uninstalling/reinstalling but it's a no go. Any ideas?

 

[isaacj87]

I love MIUI.
But just so everyone knows, here are some possible security issues. Also, to expand on Isaac's suggestion not to feed sensitive data into MIUI. If MIUI becomes open source, we probably won't have to worry about this, but...

<snip>

I would be wary. Maybe it's just the paranoid side of me. But Isaac's build is awesome, and I'll stick with it until he does. This is just a message for you highly confidential CIA officers and business people, tin-hat-wearers, and paranoid people in general.

It seems pointless now, but I think this something that needs to be addressed. What you've posted is a regurgitation of borderline FUD (which is a big no-no in my book).

First off, we have a guy who made icons for MIUI (he didn't actually port MIUI, if I understand correctly). He claims that if you swapped kernels in MIUI, it would stop logging. Maybe the kernel he swapped had debugging disabled? He didn't mention whether or not logging was working with the "MIUI" kernel. This is strange to me.

Secondly, obviously, we're not using a "MIUI" kernel. This is a reworked kernel by me that was changed to work with MIUI. Obviously, logging is working. If it wasn't, I wouldn't be able to see what was borked. Ergo, nothing could be fixed. If you have ADB set up, you can see the logs for yourself. For example:

adb logcat -b events

or

adb logcat -b system

Now, admittedly, MIUI being closed-source really puts me off. I wholeheartedly mean that. Not only does it offend me that Xiaomi is taking advantage of a good thing, but it doubly pisses me off that they refuse to give back to the Android community (in this case, the CM team). Furthermore, I am a paranoid dude by nature. I personally went through the the decompiled smali code and checked to find anything unusual. I tried to check anything that looked strange to me. Of course, I didn't find anything, but after awhile it starts to blur together.

This situation reminds me of Schr

 

[dg61981]

Whenever I restore everything with the built-in Backup system, I get stuck in a bootloop. And have to wipe data and flash the rom again. :/ It only happens when I restore all system files, even though they're from literally 20 minutes ago and from the same ROM. So I usually just restore a few necessary ones like messages, notes, and desktop layout.

Use the miui built in backup feature and restore only what u need once u flash the newest build. Never restore system though(obviously) it screws everything up.

 

[isaacj87]

Whenever I restore everything with the built-in Backup system, I get stuck in a bootloop. And have to wipe data and flash the rom again. :/ It only happens when I restore all system files, even though they're from literally 20 minutes ago and from the same ROM. So I usually just restore a few necessary ones like messages, notes, and desktop layout.

I have the same thing happen to me too. I'm not sure what's going on with the backup tool. I never touched anything related to it. I'll try running it later and seeing if I can't catch the problem in the logs.

 

[Mobstergunz]

It seems pointless now, but I think this something that needs to be addressed. What you've posted is a regurgitation of borderline FUD (which is a big no-no in my book).

First off, we have a guy who made icons for MIUI (he didn't actually port MIUI, if I understand correctly). He claims that if you swapped kernels in MIUI, it would stop logging. Maybe the kernel he swapped had debugging disabled? He didn't mention whether or not logging was working with the "MIUI" kernel. This is strange to me.

Secondly, obviously, we're not using a "MIUI" kernel. This is a reworked kernel by me that was changed to work with MIUI. Obviously, logging is working. If it wasn't, I wouldn't be able to see what was borked. Ergo, nothing could be fixed. If you have ADB set up, you can see the logs for yourself. For example:

adb logcat -b events

or

adb logcat -b system

Now, admittedly, MIUI being closed-source really puts me off. I wholeheartedly mean that. Not only does it offend me that Xiaomi is taking advantage of a good thing, but it doubly pisses me off that they refuse to give back to the Android community (in this case, the CM team). Furthermore, I am a paranoid dude by nature. I personally went through the the decompiled smali code and checked to find anything unusual. I tried to check anything that looked strange to me. Of course, I didn't find anything, but after awhile it starts to blur together.

This situation reminds me of Schr

 

[isaacj87]

I don't see any security risk here but still isn't running anything other then stock android bad? i think we shouldn't worry about it

i trust that your decision to port miui was well researched and looked into

Personally, I've always been trustful of anything with the words open-source attached to it. All ROMs start off at AOSP, but the main difference is whether or not the devs are willing to share what they changed. For example, there isn't anything funny going on with CM7. I can say this for sure. How? https://github.com/CyanogenMod <---

I can look at every nook and cranny of the CM source. There isn't any mystery at all.

 

[poler166]

I know were talking about all these sucrity worrys and our naked pic being posted on Facebook but do you think tthis rom will ever support HD games its the only thing holding me back to going back to this rom from cm7

 

[Mobstergunz]

I know were talking about all these sucrity worrys and our naked pic being posted on Facebook but do you think tthis rom will ever support HD games its the only thing holding me back to going back to this rom from cm7

HD games work fine for me

EDIT: i play asphalt and dead space and they work flawlessly

 

[Mobstergunz]

Personally, I've always been trustful of anything with the words open-source attached to it. All ROMs start off at AOSP, but the main difference is whether or not the devs are willing to share what they changed. For example, there isn't anything funny going on with CM7. I can say this for sure. How? https://github.com/CyanogenMod <---

I can look at every nook and cranny of the CM source. There isn't any mystery at all.

i see your point, maybe they just dont like like people poking at there software or they fear we will make it better then they do idk

 

[djboi2011]

It seems pointless now, but I think this something that needs to be addressed. What you've posted is a regurgitation of borderline FUD (which is a big no-no in my book).

First off, we have a guy who made icons for MIUI (he didn't actually port MIUI, if I understand correctly). He claims that if you swapped kernels in MIUI, it would stop logging. Maybe the kernel he swapped had debugging disabled? He didn't mention whether or not logging was working with the "MIUI" kernel. This is strange to me.

Secondly, obviously, we're not using a "MIUI" kernel. This is a reworked kernel by me that was changed to work with MIUI. Obviously, logging is working. If it wasn't, I wouldn't be able to see what was borked. Ergo, nothing could be fixed. If you have ADB set up, you can see the logs for yourself. For example:

adb logcat -b events

or

adb logcat -b system

Now, admittedly, MIUI being closed-source really puts me off. I wholeheartedly mean that. Not only does it offend me that Xiaomi is taking advantage of a good thing, but it doubly pisses me off that they refuse to give back to the Android community (in this case, the CM team). Furthermore, I am a paranoid dude by nature. I personally went through the the decompiled smali code and checked to find anything unusual. I tried to check anything that looked strange to me. Of course, I didn't find anything, but after awhile it starts to blur together.

This situation reminds me of Schr

 

[Prey521]

Is anyone able to set Google Voice as their default dialer? I don't get the option at all when I make a call. All I get is Dialer and Skype options but not GoogleVoice. I've tried clearing all defaults and uninstalling/reinstalling but it's a no go. Any ideas?

I tried a couple of different things like changing the 3rd Party setting, but it's neither in the Call Settings Menu nor is it in the GVoice entry in the SuperUser app. Very frustating and def a deal breaker. Will have to revert back to CM if there isn't a fix

 

[wsimon]

It seems pointless now, but I think this something that needs to be addressed. What you've posted is a regurgitation of borderline FUD (which is a big no-no in my book).

First off, we have a guy who made icons for MIUI (he didn't actually port MIUI, if I understand correctly). He claims that if you swapped kernels in MIUI, it would stop logging. Maybe the kernel he swapped had debugging disabled? He didn't mention whether or not logging was working with the "MIUI" kernel. This is strange to me.

Secondly, obviously, we're not using a "MIUI" kernel. This is a reworked kernel by me that was changed to work with MIUI. Obviously, logging is working. If it wasn't, I wouldn't be able to see what was borked. Ergo, nothing could be fixed. If you have ADB set up, you can see the logs for yourself. For example:

adb logcat -b events

or

adb logcat -b system

Now, admittedly, MIUI being closed-source really puts me off. I wholeheartedly mean that. Not only does it offend me that Xiaomi is taking advantage of a good thing, but it doubly pisses me off that they refuse to give back to the Android community (in this case, the CM team). Furthermore, I am a paranoid dude by nature. I personally went through the the decompiled smali code and checked to find anything unusual. I tried to check anything that looked strange to me. Of course, I didn't find anything, but after awhile it starts to blur together.

This situation reminds me of Schr

 

[isaacj87]

I am a pretty trusting guy (maybe too trusting) and so I am not too worried about this kind of stuff. Honestly, this could be the case for any rom and pretty much anyone who touches the rom before it gets into our hands. Just because something is open-source, doesn't make it immune to malicious developers, it just makes it a little harder to hide and easier to find. While CM7 is open source, who's to say they don't add in some keylogging code without releasing the source to that part of it and include it in their releases for their supported devices (obviously this doesn't apply to the MT). And TickerGuy could do the same thing, include some code that he never commits to his repo which could do ultimately anything.

I'm sure even you Isaac, if you put your mind to it, could use smali and disassemble something from MIUI, add in some malicious code and re-assemble without anyone knowing better (don't get any ideas!).

Obviously, there are reasons to have something closed source that do not include trying to hide something in their code. While I am pro-open-source and I believe MIUI should be open-source, there are sensible reasons for them to keep it closed source, most of which are probably monetary reasons.

I agree with you, but when commits are pushed to Github, there is explicit diffs of before and after. Here's an example: https://github.com/ikarosdev/triumph-kernel-msm7x30/commit/f8b0312c17a7d4f471ea925258b14d5e1c222884

Furthermore, since I'm a transparency kind-of-guy, I can't even build without pushing everything to Github first. My manifest is tied to my repos on Github. So if you guys followed my building CM7 tutorial, you're building the exact same thing I would be building. I do this for 3 reasons:

1) To keep things organized and log everything so I can remember it later.
2) Leave the source exactly where I left it so others can pick up where I left off.
3) Be transparent for curious users who want to know exactly what they're getting.

I'll admit, you're right. The "official" builds of CM7 could have something malicious in them (not that they do). However, savvy Android user could easily build their own package and side-step that. Detailed instructions are found on their wiki: Building from source - CyanogenMod Wiki

That aside, I think MIUI probably has a good reason for closing their source. Besides the simple fact that they can (Apache License != GPL), I remember reading that MIUI was intended to be sold to larger manufacturers to be used on devices. Similar to TouchWiz by Samsung or SenseUI by HTC. I think an angel investment company gave Xiaomi a nice chunk of change to work on this. It wouldn't be in their best (business) interest to make their work open source. Just imagine what people would do to MIUI if they let it out in the open (this can be good or bad). It's curious though, where are Xiaomi's changes to the kernel? That's GPL...

I figured I'd address tusing's post before people go crazy and run around with underwear on their heads throwing cats at old people.

 

[Svein10]

The recovery version I have posted is 5.0.2.6. Where did you get v5.0.2.3?

OOPS it's a typo, I copied the text from someone else and did not see that... It's the 5.0.2.6. Anyway, I was able to flash the bROM v1.0 by b_randon14 with the 4.0.1.5 and that installed 5.0.2.6 and now it works. I don't know what I did wrong, but I am happy now!! Thanks a lot!

 

[Svein10]

What exactly is this "working logo" that you are talking about? It sounds like you're not pressing the MENU key to select options and instead are pressing the Power key...

It could just be that I did... Thanks! OLD WM school new to Android, but I am getting there, I have done a lot of restore today, and that works like a charm

 

[Svein10]

ya, it sounds like thats what he is doing.

Also, don't worry about those error messages,
I get those evey time I load CWM.
I don't know why... but I get them.

Yep an old newbie like me..., at least with Android, but give me a WM and I am at the upper level... Thanks, then I know about the error messages!

 

[pandacookie]

It seems pointless now, but I think this something that needs to be addressed. What you've posted is a regurgitation of borderline FUD (which is a big no-no in my book).

First off, we have a guy who made icons for MIUI (he didn't actually port MIUI, if I understand correctly). He claims that if you swapped kernels in MIUI, it would stop logging. Maybe the kernel he swapped had debugging disabled? He didn't mention whether or not logging was working with the "MIUI" kernel. This is strange to me.

Secondly, obviously, we're not using a "MIUI" kernel. This is a reworked kernel by me that was changed to work with MIUI. Obviously, logging is working. If it wasn't, I wouldn't be able to see what was borked. Ergo, nothing could be fixed. If you have ADB set up, you can see the logs for yourself. For example:

adb logcat -b events

or

adb logcat -b system

Now, admittedly, MIUI being closed-source really puts me off. I wholeheartedly mean that. Not only does it offend me that Xiaomi is taking advantage of a good thing, but it doubly pisses me off that they refuse to give back to the Android community (in this case, the CM team). Furthermore, I am a paranoid dude by nature. I personally went through the the decompiled smali code and checked to find anything unusual. I tried to check anything that looked strange to me. Of course, I didn't find anything, but after awhile it starts to blur together.

This situation reminds me of Schr

 

[pandacookie]

It seems pointless now, but I think this something that needs to be addressed. What you've posted is a regurgitation of borderline FUD (which is a big no-no in my book).

First off, we have a guy who made icons for MIUI (he didn't actually port MIUI, if I understand correctly). He claims that if you swapped kernels in MIUI, it would stop logging. Maybe the kernel he swapped had debugging disabled? He didn't mention whether or not logging was working with the "MIUI" kernel. This is strange to me.

Secondly, obviously, we're not using a "MIUI" kernel. This is a reworked kernel by me that was changed to work with MIUI. Obviously, logging is working. If it wasn't, I wouldn't be able to see what was borked. Ergo, nothing could be fixed. If you have ADB set up, you can see the logs for yourself. For example:

adb logcat -b events

or

adb logcat -b system

Now, admittedly, MIUI being closed-source really puts me off. I wholeheartedly mean that. Not only does it offend me that Xiaomi is taking advantage of a good thing, but it doubly pisses me off that they refuse to give back to the Android community (in this case, the CM team). Furthermore, I am a paranoid dude by nature. I personally went through the the decompiled smali code and checked to find anything unusual. I tried to check anything that looked strange to me. Of course, I didn't find anything, but after awhile it starts to blur together.

This situation reminds me of Schr

 

[tusing]

It seems pointless now, but I think this something that needs to be addressed. What you've posted is a regurgitation of borderline FUD (which is a big no-no in my book).
<snip>

Hmm, sorry. I didn't know that- I guess I should stop using random XDA commenters for my data again, lol. Stupid move on my part.

I would love if you continue on MIUI. It's amazing, actually. I just got a bit paranoid when I was searching for themes and saw a link to that quote. MIUI is awesome, and honestly, don't discontinue it. It's arguably the best ROM out there, far better than CM7 IMO. It has a far more active development and community, and is amazing. Hopefully you can erase my post from your mind!

I didn't know that it had to do with the kernel. I guess I should do a bit more research next time

 

[isaacj87]

Hmm, sorry. I didn't know that- I guess I should stop using random XDA commenters for my data again, lol. Stupid move on my part.

I would love if you continue on MIUI. It's amazing, actually. I just got a bit paranoid when I was searching for themes and saw a link to that quote. MIUI is awesome, and honestly, don't discontinue it. It's arguably the best ROM out there, far better than CM7 IMO. It has a far more active development and community, and is amazing. Hopefully you can erase my post from your mind!

I didn't know that it had to do with the kernel. I guess I should do a bit more research next time

Make no mistake, there wasn't anything wrong with your concern. In fact, I have the same one. I wouldn't dare put anything sensitive in MIUI, but then again, I wouldn't put anything sensitive on my phone on any ROM. I won't sit here and tell you that your paranoia is unfounded. I feel the same way as you. In fact, a lot of people feel the same way as us.

One thing is for sure, I always keep an out for anything malicious (this is with anything Android related). Ya know, I am runnning the same ROM as you guys! lol. Your problems are mine as well. However, this "MIUI fear" has been going on for a long time now (years almost) and still nothing. I find a lot of reports like this:

We and lots of "miui friends" hack the sh*t out of miui week after week, and yes we don't get to see the source code but I'm pretty sure if anyone discovered anything "untoward" buried in the code we would hear about it pretty quickly.
Its fair to say that almost any app could possibly be keylogging and I guess that's the chance you take when you use an open source operating system (or jailbreak your iPhone)

Source: http://forums.whirlpool.net.au/archive/1643833

For now, I'm gonna take my tin-foil hat off and hug me some MIUI. You can't see it, but I'm hugging my phone.

 

[Chairshot215]

With Tickerguy leaving us for T-Mobil I think the least anyone who is using this Rom can do is throw Isaac a few dollars to make his continued efforts worth the trouble. I honestly believe without him and Tickerguys work the $300 we put out for our phones would have been worthless as the stock Rom was both an embarrassment and an insult to both the user and the phones hardware. Anyway I&#8217;m just saying that after shelling out $300 the least we can all do is shell out a few dollars to make it work.

 

[poler166]

Well when I first got the rom there were reports that HD games were not working and its still in the problem list but if they are working I might go back go this rom

 

[tusing]

With Tickerguy leaving us for T-Mobil I think the least anyone who is using this Rom can do is throw Isaac a few dollars to make his continued efforts worth the trouble. I honestly believe without him and Tickerguys work the $300 we put out for our phones would have been worthless as the stock Rom was both an embroilment and an insult to both the user and the phones hardware. Anyway I&#8217;m just saying that after shelling out $300 the least we can all do is shell out a few dollars to make it work.

what! Ticker is leaving? NOO

At least we have Isaac. if it wasn't for him we wouldn't have tickers ROM in the first place.