• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[Development Stopped][JB 4.1.2][Xperia S/SL] MIUI V5 ML LB/UB [4.8.1] - STOCK BASED

BalcanGSM

Senior Member
Jan 29, 2006
629
1,683
0
Belgrade
adria.mobiledevs.net



DEVELOPMENT OF THIS STOCK BASED MIUI V5 ROM IS STOPPED
THANKS TO ALL ROM USERS FOR YOUR SUPPORT
TRY OUR KITKAT BASED MIUI V5 ROM LINK


ROM AUTHORS:

ROM INFORMATION:

- Rom Base:

- MIUI Base(Closed Source):

- ROM Build:

- Kernel Base:



ROM CREDITS:
  • Upper Mentioned Rom Authors -
Specially Thanks To Great Dev Midnight Souls (@ kin912)

Making Great MIUI Rom And Developing Patchrom For Adaptation And Porting MIUI To Many Devices

  • All Other Devs Which Help With Sony Xperia Custom Kernels,Rooting Methods,Recoveries And Advices
- @ lpws521
- @ DooMLoRD
- @ schickel
- @ RaymanFX
- @ Rimmer1966
- @ sijav
- @ letama
- @ panel1
- @ Novastylez
- @ ViPER
- @ djoliver




!!! THIS ROM IS IN STABILE STAGE WITH CONSTANT DEBUGGING AND UPGRADING TO LATEST MIUI RELEASES !!!

- All Files And Tutorials Except Rom Are Collected From Internet & Xda Forums,So All Credits Are Going To Their Authors. -

- I'm Not Responsible For Any Eventual Errors And Misbehaving Of Your Devices. -




- Xiaomi MIUI Is One Of The Greatest And Most Unique Custom Roms For Android Devices.

- MIUI Developement Team Abandoned Stock Based MIUI For Sony Xperia S/SL In MIUI Version V4

- Till Then Our Team Bringing You CM Based MIUI V5 Port Every Week.

- Our Team Is Group Of Enthusiasts Which Try To Bring Full MIUI V5 Experience On Xperia S/SL.

- Please Remember That Our Work Is Voluntary,And Not An Obligation.


ROM WORK FOR LOCKED/UNLOCKED BOOTLOADERS ON XPERIA S/SL DEVICES


IN ORDER TO KEEP THREAD CLEAN PLEASE:

  • Use Thanks Button If You Are Grateful For Rom Or Advice
  • For Viewing Screenshots & Bug Feedback Please Use Thread Nav - Bar




[REQUIREMENTS]


  • [*]Windows/Linux/Mac Powered Computer
    [*]Installed Latest Java Runtime Environment Depends Of Your Computer OS - LINK
    [*]Android Device Drivers Installed
    [*]Enabled Settings → Security → Unknown Sources & Settings → Development → Usb Debugging
    [*]Phone Battery Charged - 60% At Least.


[STOCK ROM & RECOVERY FLASH PROCEDURE]


  • [*]Download And Install Latest Flash-Tool Software Depends Of Your Computer OS - LINK
    [*]Download And Install Adb & Fastboot - WINDOWS LINK / LINUX & MAC LINK
    [*]Download Sony Stock FW 6.2.B.1.96 And Flash It Via Flash-Tool - LINK

- FLASHING RECOVERY -

UNLOCKED BOOTLOADER :

Download Advance Stock Kernel(FW .96 - CWM Recovery Included) - LINK
Reboot Device Into Fastboot Mode With Command:
Code:
adb reboot bootloader
Flash The Kernel Using Command :
Code:
fastboot flash boot kernel.elf
(Where Kernel.elf (.img) Is The Name Of The File You Downloaded)


LOCKED BOOTLOADER (Please Test It - I Dont Have Device With LB):

Root FW .96 Stock Rom Using Doomlord's Method - LINK
Download & Extract CWM Recovery For LB And Save It On C: - LINK
Go To Extracted Folder And Execute Cwm-Install-En.Bat
Follow The On-Screen Instructions



[FLASH MIUI ROM]

DOWNLOAD XPERIA S/SL MIUI V5 4.8.1 ROM Latest Stock Based Version

[QRCODE]http://miuirom.xiaomi.com/rom/u101516757/4.8.1/miui_26_cheng_4.8.1_f9dad992d6_4.1.zip[/QRCODE]


DOWNLOAD XPERIA S/SL MIUI V5 4.7.25 MULTILANGUAGE ROM (No OTA Support - Repacked Rom ) - Latest Stock BasedVersion

(Flash It Via Recovery And Apply Language Via Set Locale App If You Cant See It In Language List)
[QRCODE]https://goo.im/devs/ibotpeaches/miuiandroid/releases/4.7.25m/xiaomi.eu_multi_LT26i_4.7.25_jb-4.1.zip[/QRCODE]


1. Put XXX.Zip Copied To The Root Directory Of Cell Phone (That Is A Direct Copy)
2. Enter Recovery (Twrp Or Cwm) (Turn Off, Turn On & Repeatedly Keep Pressing Vol+)
3. Select [Wipe Data / Factory Reset] → [Yes]
4. Select [Wipe Cache Partition] → [Yes ]
5. Select [Advanced] → [Wipe Dalvik Cache] → [ Yes ] → Back
6. Select [Install Zip From Sdcard] → [Choose Zip From Sdcard] → [XXX.Zip] → [Yes]
7. Wait Flash Finished, Press Back And Select Reboot System Now [], The Phone Going To Automatically Restart With Installed Miui Rom.

First Boot Need ~ 3 - 5 Min.



- FLASH GAPPS -

DOWNLOAD 4.1.2 GAPPS

[QRCODE]http://d-h.st/CAg[/QRCODE]

1.After First Boot Reboot Your Phone To Recovery Again.
2.Select [Install Zip From Sdcard] → [Choose Zip From Sdcard]→ [Miuiandroid_Gapps-4.1.2-Small_Signed.Zip] → [Yes]
3. Wait Flash Finished, Press Back And Select Reboot System Now [], The Phone Going To Automatically Restart With Installed Gapps.
4.Set Up Your Google And Xiaomi Accounts(For Themes).



DOWNLOAD WSM TOOLS FOR ADDING VARIOUS OPTIONS FOR MIUI - LINK


Current Rom Status:

  • Rom Proper (Without Errors) Builded With MI Code Patchrom
  • Rom Partially Debugged Before Patchrom FullOTA Build
  • Rom Hardly Debugged And Fixed For Everyday Use > 300MB Of Free RAM
  • ? - EVERYTHING IS WORKING - ?
  • Taking Screenshot Will Reboot Device- FIXED
  • Auto Brightness Disabled- FIXED
  • MTP Connection FC - FIXED
  • All Sounds Muted Upon First Boot - You Must Set Them Manualy- FIXED
  • No Mobile Data Signal - FIXED
  • Lockscreen Not Showed Up - FIXED
  • Camera Dont Work - Only Black - FIXED
  • Home Key Dont Work - FIXED
  • When Somebody Call You Its Always Busy - FIXED
  • Browser FC - FIXED
  • Provision App FC - FIXED
  • Cant Change Rom Language Bug - FIXED
  • Input Method Dont Work - FIXED
  • Rom Booted With Lot Of Bugs - FIXED
  • Constantly Bootloop On System Start - FIXED
  • ADB Logcat Not Working - FIXED

OFFICIAL MIUI CHANGELOG



XDA:DevDB Information
[Development Stopped][JB 4.1.2][Xperia S/SL] MIUI V5 ML LB/UB [4.8.1] - STOCK BASED, ROM for the Sony Xperia S

Contributors
ghetto_thug, FD-GHOST, kin912
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Sony Stock FW 6.2.B.1.96 + Recovery
Based On: Official Sony Stock FW 6.2.B.1.96

Version Information
Status: Stable
Current Stable Version: 4.8.1
Stable Release Date: 2014-08-01

Created 2013-09-30
Last Updated 2014-08-19
 

Attachments

Last edited:

karellang

Senior Member
May 2, 2012
233
66
0
Is there bootlop on Sony logo or MIUI logo ?

I had some problems with bootlop on sony logo when I have tried to repack kernel.

Sent from my LT26i using xda app-developers app

This same problem. Bootlop on miui logo.
Full wipe (dalvik, cache, data, system) before install.

ROM is without kernel . which kernel should I use?
 
Last edited:

Olivier

Recognized Developer / Retired Forum Moderator
Nov 6, 2011
2,657
6,884
113
Do you think it's possible to get it booting without any modifications in the kernel? I tried to port MIUI v5 for LB in August but failed (bootloop).

Gesendet von meinem LT26i mit Tapatalk 4
 
  • Like
Reactions: BalcanGSM

Rimmer1966

Senior Member
Oct 14, 2010
487
949
93
Do you think it's possible to get it booting without any modifications in the kernel? I tried to port MIUI v5 for LB in August but failed (bootloop).

Gesendet von meinem LT26i mit Tapatalk 4
It's definitely possible. I've got an Xperia T and managed to get v5 booting on a stock base using the stock kernel.. It's not perfect, have some issues with the notification led's and some bugs with the audio, but everything else works fine..
 
  • Like
Reactions: Olivier

RaymanFX

Inactive Recognized Developer
Jan 8, 2011
1,122
16,501
0
24
Hannover
I don't have any time to mess with MIUI at the moment, but I hope I can provide some guideance out of the blue:

* Yes, you can run MIUI on a stock kernel. But not using a stock boot.img. You need to modify the ramdisk (at least that's what I found when I worked on my own patchrom).
* To get adb logcat and things working, you need to set ro.secure to 0 in the ramdisk. It's probably set to 1.
 

Olivier

Recognized Developer / Retired Forum Moderator
Nov 6, 2011
2,657
6,884
113
But I now that we're talking about MIUI for Xperia S, I remember there is MIUIv4 for devices with locked bootloaders. I even tested it and it was working like a charm. As my device's bootloader is "ununlockable" but it worked, I guess a Stock boot.img has been used. Or am I wrong when I say that each little modification in the kernel renders it unusable for devices with LB (because of a special fingerprint/signature whatever of Sony that gets lost)?

Gesendet von meinem LT26i mit Tapatalk 4
 
Last edited:

RaymanFX

Inactive Recognized Developer
Jan 8, 2011
1,122
16,501
0
24
Hannover
But I now that we're talking about MIUI for Xperia S, I remember there is MIUIv4 for devices with locked bootloaders. I even tested it and it was working like a charm. As my device's bootloader is "ununlockable" but it worked, I guess a Stock boot.img has been used. Or am I wrong when I say that each little modification in the kernel renders it unusable for devices with LB (because of a special fingerprint/signature whatever of Sony that gets lost)?

Gesendet von meinem LT26i mit Tapatalk 4
You are right with your last point, but remember: we're talking about MIUI v5 here.
And MIUI 5 definately needs a different ramdisk than MUIU 4.
So regarding MIUI on locked bootloaders, it more ore less depends on the OEM (read: Sony) if you're able to get it working or not, because they decide what the stock ramdisk will contain, afterall.

There might be workarounds to this (hijacking the ramdisk using init.d scripts), but I did not test those as my device was unlockable right from the start. It might also be possible to get MIUI 5 running without any ramdisk additions at all, but that needs to be tested excessively, for which I sadly lack time at the moment.
 

panel1

Senior Member
Jun 10, 2009
444
159
0
Bratislava
www.panel.sk
I don't have any time to mess with MIUI at the moment, but I hope I can provide some guideance out of the blue:

* Yes, you can run MIUI on a stock kernel. But not using a stock boot.img. You need to modify the ramdisk (at least that's what I found when I worked on my own patchrom).
* To get adb logcat and things working, you need to set ro.secure to 0 in the ramdisk. It's probably set to 1.
I will try to do this tomorrow. I have no time too, but will try to find some time. Thanks for guide :)
 

kin912

Senior Member
Apr 23, 2011
466
673
0
Foshan
I don't have any time to mess with MIUI at the moment, but I hope I can provide some guideance out of the blue:

* Yes, you can run MIUI on a stock kernel. But not using a stock boot.img. You need to modify the ramdisk (at least that's what I found when I worked on my own patchrom).
* To get adb logcat and things working, you need to set ro.secure to 0 in the ramdisk. It's probably set to 1.
I had ported some roms from nozomi to aoba,like tita rom and baidu os,all base on stock ICS.When I used the stock ramdisk the phone bootloop and the adb shell did not start.So I must add the shell in ramdisk and the rom work well.

I also ported the miui v5 base on cm.I did not add the shell in ramdisk and it stop at the "mi" bootanimation.But the key lights on and I can get the log.

About this miui v5 base on stockJB,I modify the ramdisk or not all bootloop.The worse thing is the adb logcat can not work.So I think the problem is the micode port in the .jar files.

@Rimmer1966 @djolivier @sijav

I need the keypoint.Nomaly a rom make out can boot at less the adb logcat work
 

Rimmer1966

Senior Member
Oct 14, 2010
487
949
93
I had ported some roms from nozomi to aoba,like tita rom and baidu os,all base on stock ICS.When I used the stock ramdisk the phone bootloop and the adb shell did not start.So I must add the shell in ramdisk and the rom work well.

I also ported the miui v5 base on cm.I did not add the shell in ramdisk and it stop at the "mi" bootanimation.But the key lights on and I can get the log.

About this miui v5 base on stockJB,I modify the ramdisk or not all bootloop.The worse thing is the adb logcat can not work.So I think the problem is the micode port in the .jar files.

@Rimmer1966 @djolivier @sijav

I need the keypoint.Nomaly a rom make out can boot at less the adb logcat work
I had the same problem with the logcat. What I did was use a Kernel with an unsecure ramdisk, DoomKernel for example. I modified it to start the logcat earlier, even then the logcat only works properly on Linux. Once I'd worked out the bugs I was able to switch back to a stock kernel without making any modifications.
Hope this helps you..
 
  • Like
Reactions: Olivier

Olivier

Recognized Developer / Retired Forum Moderator
Nov 6, 2011
2,657
6,884
113
Also as @RaymanFX has already mentioned, it is possible to modify the ramdisk without de- and recompiling the kernel using init.d scripts. But @Rimmer1966's method seems more likely to work...
Unfortunately, I don't have access to a computer ATM (mine is being repaired) and also, my bootloader cannot be unlocked (...easily), which means I'll have to try the init.d script method (as soon as I get my laptop back).

Gesendet von meinem Sony Xperia S mit Tapatalk 4
 
Last edited:

kin912

Senior Member
Apr 23, 2011
466
673
0
Foshan
I had the same problem with the logcat. What I did was use a Kernel with an unsecure ramdisk, DoomKernel for example. I modified it to start the logcat earlier, even then the logcat only works properly on Linux. Once I'd worked out the bugs I was able to switch back to a stock kernel without making any modifications.
Hope this helps you..
I had set ro.secure=0,ro.debuggable=1,persist.service.adb.enable=1 in the ramdisk.But the fact is the adb service is not start when the phone boot.
So I can not get the logcat.

I think when you port the phone is stop at the bootanimation,the notification led is on too.You can get the logcat.
@djolivier The init.d support start later than the adb support,I think your method is not work.

If I can get the logcat,I can handle this by myself.I had ported many times.I have no idea and I want to give up now.
 

sijav

Senior Member
Sep 3, 2012
903
954
0
29
Tehran
I had ported some roms from nozomi to aoba,like tita rom and baidu os,all base on stock ICS.When I used the stock ramdisk the phone bootloop and the adb shell did not start.So I must add the shell in ramdisk and the rom work well.

I also ported the miui v5 base on cm.I did not add the shell in ramdisk and it stop at the "mi" bootanimation.But the key lights on and I can get the log.

About this miui v5 base on stockJB,I modify the ramdisk or not all bootloop.The worse thing is the adb logcat can not work.So I think the problem is the micode port in the .jar files.

@Rimmer1966 @djolivier @sijav

I need the keypoint.Nomaly a rom make out can boot at less the adb logcat work
sorry for delay (I lost my computer and didn't get internet and so on), I'm not sure if you figure it out by now or not, you should put those lines on in build.prop in the room (because those values will be over written by build.prop in rom)
so you should look for ro.debuggable and persist.sys.usb.config and change them to (or create if not exists):
Code:
ro.debuggable=1
persist.sys.usb.config=adb
good luck
 
Last edited: