[rom] Ivan's Aosp Lollipop 5.1


I'm on sMIUI 5.7.16 with merged partitions. At least I think so... btw, is there a safe way to test wether or not I'm on merged partitions?

With TWRP flashing of AOSP finally worked - but after booting into the new system there is no SD card detected...
 
Last edited:
I'm on sMIUI 5.7.16 with merged partitions. At least I think so... btw, is there a safe way to test wether or not I'm on merged partitions?

With TWRP flashing of AOSP finally worked - but after booting into the new system there is no SD card detected...
wrong layout of your Mi2S

there are 2 layouts the old one and the new one - for the new one are SDcard and appdata merged, you have to install the other layout rom
 
  • Like
Reactions: Matze002
wrong layout of your Mi2S

there are 2 layouts the old one and the new one - for the new one are SDcard and appdata merged, you have to install the other layout rom

Does the attached image tell?

EDIT: seems I got partitions merged, question now is, wether or not CM or AOSP are available for merged partitions... (as OP ROMs are for unmerged, correct?)

EDIT2: Here something in Chinese with regard to merged and non-merged partitions:
http://www.miui.com/thread-2559235-1-1.html

Could the OP please translate that and adapt the start post accordingly?
 

Attachments

  • Screenshot_2015-07-27-20-17-13.png
    Screenshot_2015-07-27-20-17-13.png
    90.3 KB · Views: 367
Last edited:
Hi, do you have any idea why I cant boot into custom recovery? I have tried both cwm and twrp. Windows and Linux. Get into fastboot mode, connect to pc, everything runs fine, no error messages. If I remove the battery and pres vol+ and power to boot into recovery the phone gets stuck with the MI picture and nothing happens. If I press power during fastboot mode, the phone just restarts and miui overwrites de recovery partition. Im on lollipop miui 5.7.26. Thank you!
 
Hi, do you have any idea why I cant boot into custom recovery? I have tried both cwm and twrp. Windows and Linux. Get into fastboot mode, connect to pc, everything runs fine, no error messages. If I remove the battery and pres vol+ and power to boot into recovery the phone gets stuck with the MI picture and nothing happens. If I press power during fastboot mode, the phone just restarts and miui overwrites de recovery partition. Im on lollipop miui 5.7.26. Thank you!
You have to unlock the bootloader (fastboot oem unlock)
 
You have to unlock the bootloader (fastboot oem unlock)
Apparently it was something about cwm not being compatible with lollipop miui. Installed an older miui with MiFlash and it works. I have TWRP and installed this rom but now, wifi wont connect. Detects networks, asks for password, but does not connect and im next to the router.
 
Sorry, it only proves how confusing it is for a noob like me...

I already asked on XDA for an easy-to-understand overview of AOSP and CM builds as well as the info whether or not those ROMs are for merged or un-merged partitions....

Cheers,

Mat

EDIT: Confusion is even bigger: I obviously mixed your and Ivans work as you both obviously provide AOSP and/or CM versions for Mi2(s). I fear my post appears to be useless and/or even stupid....
 
Last edited:
Does anyone still get random reboots with ivan's rom? I have the old partition layout. Flashed originally with cwm, and now with twrp 2.8.5.0. Full wipe, including formatting system. Everything works well, except I get at least one reboot every 24 hours, usually two (but never while I'm using the phone). I'm on 5.4.14, but I got it with 5.5.7 modified as well. Is there a reason for this, or maybe it's just hardware related?
 
Don't want to be polemical, but I really don't understand the point of a double ROM thread, is a mess.
I suggest to use this only for Ivan's AOSP.
 
Don't want to be polemical, but I really don't understand the point of a double ROM thread, is a mess.
I suggest to use this only for Ivan's AOSP.
you're right.
but at first, there was the need of having all 5.1.x based roms into one thread. now, I agree, it's a mess.

do you suggest to remove all m1cha's builds from OP and leave ivan's AOSPs only?
who else agrees?
 
Does anyone still get random reboots with ivan's rom?

I am on Ivan's 5.5.7, flashed with cwm 6.0.5.0., unmerged partitions, and have exactly the same problem. I don't know, I'm looking for the reasons of the reboots. I use only a couple of xposed modules (gravity box, greenify) which may also produce the problem and DisableService to disable some annoying background services from running on their own. On the other hand, it may have to do with the small partition size for data, since the ROM+Gapps take up almost all storage space.
 
CM12.1 thread was opened by spaxon a few months later than this one.
but I cleaned up OP and left only AOSP links.

so, we talk about ivan's AOSP here, and for CM12.1 discussions, we can point to spaxon's thread.
cheers.

Yes I know about that, but it was necessary because here was a little confusing.

Thank you, you've been understanding.
 
  • Like
Reactions: datu82 and cypher
this is not my own work. I am just mirroring Ivan's ROM published into other chinese forum channels.

this is bleeding edge android lollipop 5.1 for Xiaomi Mi2(s) codename aries.
don't use this build on other phones.
all credit goes to Ivan for this incredible work.

buglist:
- screen stucks blank for a while at first start [after flashing ROM], but no issue at all on further reboots/boot ups
- bluetooth stack is rather fragile
- you tell me! [scroll down the comments of this thread]

screenshots:

View attachment 9776 View attachment 9777 View attachment 9778 View attachment 9779 View attachment 9780 View attachment 9781 View attachment 9782 View attachment 9784 View attachment 9785

tools required:
- Xiaomi Mi2(s)
- CWM / TWRP recovery installed [tested on 6.0.5.1 and 2.5.8.0 versions]

instructions:
- download ROM
- download GAPPS
- move them into your phone's sdcard
- reboot to recovery
- wipe data
- install ROM .zip
- install GAPPS .zip
- reboot phone [wait a while for the boot process to end up] [fixed with 5.4.14 update]
- enjoy

here are the downloads:
AOSP 5.4.1 - md5 sum ce4098b3d16c63efe622146961852a87
AOSP 5.4.11 - md5 sum 62e3cb74ad608a95fd3ba32ff7958dcc
AOSP 5.4.14 - md5 sum 28221017787ad50fc1a888f83489cfc5
AOSP 5.5.7 - md5 sum b6107c7d61c9013d50b0e1e8bd6c438a
GAPPS [for AOSP] - md5 sum fed934824aaa6ac8acdadc64f1c6b056
CWM recovery 6.0.5.1 [patched by Furniel]
TWRP 2.8.5.0

notes:
this ROM is already rooted by default.

to install a custom recovery, follow this procedure:

- power off your phone and power it on in fastboot mode, pressing power + vol down for 2 seconds
- connect your phone to your PC [Windows]
- make sure that proper drivers are installed
- download this .zip archive
- extract it on your C: drive - so you have the directory C:\adb
- move into C:\adb the .img file of the recovery you want to flash
- shift+right click on an empty space into adb folder
- select "open command window here" from the context menu
- in CMD, type fastboot devices
- if the output shows an alphanumeric string, then the phone is correctly recognized, otherwise make sure your PC has your phone drivers correctly installed
- flash your recovery with this command:

fastboot flash recovery CWM_recovery_6.0.5.1_R11_furniel.img
or
fastboot flash recovery openrecovery-twrp-2.8.5.0-aries-20150221.img

- you're done. reboot your device and enjoy your new recovery.
Thank you for the tuto to install the recovery!
But I found that I need to do one step before flashing: "fastboot recovery erase"
Then it worked..

edit: It actually didn't work, I try on miui v6 global stable version...
 
Last edited:
Has someone here a solution regarding the massively delayed whatsapp messages? Very often I receive them only after turning the screen on. I have WiFi (always on) and data enabled all the time...

Regards
Stephan

Gesendet von meinem MI 2S mit Tapatalk
 
Has someone here a solution regarding the massively delayed whatsapp messages? Very often I receive them only after turning the screen on. I have WiFi (always on) and data enabled all the time...

Regards
Stephan

Gesendet von meinem MI 2S mit Tapatalk
https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer&hl=en
Try a lower than 5 min setting, i personally use 2 min and still sometimes exceeds that.Never tried 1 min if you do report about battery life.It's weird that only me and few others complained about this problem compared to the number of users using whatsapp which acoording to playstore is more than a billion.

Update : I'm using a 1 min interval for wifi and i can't see any difference in battery life.I'm on pacrom 4.4.4 so results may vary with your setup.
 
Last edited:
  • Like
Reactions: ErnieTSI