Develop Bugs

Full Root for Sony Xperia M c1904 & c1905 models on JB 4.1

UPDATED INSTRUCTIONS 23/3/2014
Thought I would share this for anyone that's looking for a complete and full root of this phone, this is not my work I was given these instructions for full root of Sony Xperia M Phone by member xzn credits go to him and others mentioned within method here is the method as follows
- FULL ROOT XPERIA M -
material
- Download Framaroot 1.5.3(http://www.2shared.com/file/x5aus8Wd/comalephzainframaroot_153.html?)
- Busybox Pro v9.7.3 (http://www.2shared.com/file/gPQlU2-Q/BusyBox_Pro_9_7_3.html?)
- Busybox Free (https://play.google.com/store/apps/details?id=stericson.busybox)
- Tool By Anto Kus (download here http://www.2shared.com/file/e9sDTGJk/rootfixer.html?)
- some snacks and soda
steps
1. Install framaroot 1.5.3 ,open , then select install supersu, then select gandalf, if its failed, try, try n try until success notification appear and ask to reebot,your phone will reboot, after your phone on again , look for supersu app in menu , if supersu not appear in menu try,try n try again until supersu appears
2. Install BusyBox Pro v9.7.3 , if busybox ask for backup, select yes, then busyboz will loading, after 100%, MAKE SURE BUSYBOX IS INSTALLED IN SYSTEM/XBIN select install, select normal install, after success,reboot your XM
up here, Your phone was half rooted (what is half rooted? its mean that your phone can not edit system file, if you try to edit your system file your XM will sudden reboot) (THIS STEP IS SO YOU CAN CREATE A BACKUP OF YOUR SYSTEM SETTINGS BEFORE BUSYBOX IS INSTALLED BUT IF YOUR NOT BOTHERED ABOUT A BACKUP THEN YOU CAN SKIP INSTALLING THIS BUSYBOX VERSION AND DOWNLOAD THE BUSYBOX FREE AND USE THAT ONE TO INSTALL THE LATEST VERSION STRAIGHT AWAY)
3. eat your snack and drink your soda, stay relax 
4. Extact Tool by Anto Kus to your pc (you will get superuser.bat and supersu.bat), then connect your XM (connect by msc and you must have install pcc on your pc), then run supersu.bat when prompted grant root access on phone
your xm will reboot
Once phone reboots wait for pc to detect phone again then finish supersu.bat then unplug device, MAKE SURE TO RERUN THE. bat FILE AGAIN AFTER FIRST REBOOT TO DOUBLE CHECK THAT THE REBOOT FIX HAS BEEN INSTALLED CORRECTLY, BEFORE RUNNING THE SCRIPT AGAIN AFTER PHONE HAS BEEN DETECTED BY THE PC UNPLUG THE PHONE THEN RERUN THE .bat FILE.
5. DOWNLOAD THE LATEST BUSYBOX FREE FROM PLAY MARKET AND LET SMART INSTALL FINISH LOADING, ONCE LOADED SELECT LATEST BUSYBOX VERSION (CURRENTLY AT V1.22.1-stericson) AND MAKE SURE ITS INSTALLED IN SYSTEM/XBIN. ONCE INSTALLED REBOOT PHONE THEN YOUR DONE
Credit to
- Xzn
- Anto Kus
- Hendrico Andre and Muhammad Arif
from Sony Xperia M Indonesia :highfive:
EXTRA
1: BUSYBOX MUST BE INSTALLED TO SYSTEM/XBIN TO WORK IF NOT AND SYSTEM/BIN IS SELECTED THE PHONE WILL REBOOT AND BUSYBOX WILL NOT BE INSTALLED
2: ALL DRIVERS MUST BE INSTALLED ADB ETC...
3: USB DEBUGGING AND MSC MUST BE SELECTED AND TURNED ON
HOW TO UNROOT LONG VERSION:
*only if you used busybox pro*
1. go into busybox and click on restore, let it do its job. A confirmation popup will appear
2. Go into supersu>settings and scroll down to unroot, click it and let it finish
3. Reboot device (NOTE IF YOU'VE RESTORED VIA BUSYBOX THEN SYSTEM WILL BE VERY LAGGY)
4. Go into settings and carry out a factory reset to clear the device fully.
HOW TO UNROOT SHORT VERSION:
1. Refresh stock firmware via flashtool and select wipe cache and wipe data
2. Let device boot up, can take upto 5+ minutes to boot up.
Sent from My Sony Xperia M C1905

Indeed anyone tried binary4u?

Thanks for this detailed guide..

I have problem ( or better - my brother ) after succesfull root, run rootfixer, but thats not fix anything... phone still rebooting if i want change some in /system ...please help

icoolguy1995 said:
Indeed anyone tried binary4u?
Click to expand...
Click to collapse
Did you install busybox I have tried and tested this method several times and never had any problems follow instructions closely
Sent from my C2005 using xda premium

Ignore the quote as xda app giving me.issues and not selecting the correct post to quote
Sent from my C2005 using xda premium

yes, installed... (and backed up, and wait for 100% loading, then install - normal)
i folowed closely, and still have problem.

Installed busybox to system/xbin?
Sent from my C2005 using xda premium

dont know... but when i now open busybox pro, its pointing to system/bin ...So you think i have to change destination to xbin and install it again ?

Install busybox to system/xbin
You'll get a confirmation screen saying busybox has been installed successfully then reboot your phone once booted up rerun root fix for the superuser app you installed then once phone has booted up again try then
Sent from my C2005 using xda app-developers app

Any luck did that work?
Sent from my C2005 using xda app-developers app

Many THANKS !!! It working now !!!

mmm273 said:
Many THANKS !!! It working now !!!
Click to expand...
Click to collapse
Not a problem I'll try and update that section of the guide
My xda app is playing up everytime I click on original post it FC. I'll try on my laptop
Sent from my C2005 using xda app-developers app

Hello
I have installed supersu, and BusyB to xbin and after running supersu.bat (xm is connected in msc mode and pcc is installed correctly) i have that message like on scrrenshot and nothing happens

new version
delete:

Im using framaroot 1.6.0 (even 1.6.1 is out there) and its hals rooting my device (like in the guide)
After all operations i cant edit system files :crying:
Do i have to turn on USB Debugging ? Its not mentioned in the guide but i find it in this thread
http://forum.xda-developers.com/showthread.php?t=2450265
Im asking because i cant check it since 7 pm

i cannot access the server to the tool by anto kus
can anyone provide mirror for that link
thanks

Found it usb debugging needs to be enabled for root fix so enable it
I'll upload the tool when I get in from work I have it on my laptop
Sent from my C2005 using xda premium

aser44 said:
Hello
I have installed supersu, and BusyB to xbin and after running supersu.bat (xm is connected in msc mode and pcc is installed correctly) i have that message like on scrrenshot and nothing happens
Click to expand...
Click to collapse
Make sure USB debugging is enabled and that PCC has installed the drivers. It didn't work for me either but after PCC installed the drivers it found my device.
This message was brought to you by my Sony Xperia M (C1905), using the XDA app.

OK, finally it worked. Everything like in the guide + enabling USB Debugging

[LB/UB]MIUI Recovery for JB

Credit to @cray_Doze and @DooMLoRD and @wzhy90
Requires:
- rooted phone
- adb debug enabled
- busybox installed
- unknown sources enabled
How to install:
- download your version of rec from above.
- unzip it into a folder.
- there are batch files for windows users and also for linux users in both the zips.
- just execute the batch files and follow the messages if any.
How to enter rec:
- let the phone boot
- at sony logo, the phone will vibrate
- a blue led lights up
- press volume up immediately and keep pressing for a few seconds
- the rec does not come up immediately. after a few seconds delay, press vol up or vol down.
- you will enter MIUI recovery.
How to package to the rom:
-push chargemon,recovery.tar,stockchargemon to system/bin.
-set perm to 755.
Download:http://url.cn/JBa5Nz

Will apps like nandroid manager, and titanium backup be able to extract / access backups from this recovery?
Thanks!
Sent from my SeXperia Ion

Bugly Astard said:
Will apps like nandroid manager, and titanium backup be able to extract / access backups from this recovery?
Thanks!
Sent from my SeXperia Ion
Click to expand...
Click to collapse
You can backup and restore with this rec.

This recovery will not do anything, but I had cwm installed and flashed over it so many thats why? Ill try a clean install.

Bugly Astard said:
This recovery will not do anything, but I had cwm installed and flashed over it so many thats why? Ill try a clean install.
Click to expand...
Click to collapse
Hi Bugly Astard,
I can not say, i loved recovery. But i can say, its working without an error.
I tried all features like flash-wipe-reboot. Everything is okay.
If you use cwm, then dont waste your time about trying to use install script.
In MIUI recovery zip file, you will see recovery.tar
Copy it /system/bin - Overwrite
And done.

I did get it working, but not impressed. It doesn't see the external sd, and its glitchy. Thanks for this anyway, it's something new to try.
Sent from my SeXperia Ion

Bugly Astard said:
I did get it working, but not impressed. It doesn't see the external sd, and its glitchy. Thanks for this anyway, it's something new to try.
Sent from my SeXperia Ion
Click to expand...
Click to collapse
@Bugly Astard agreed with you..I was not able to flash any zip in my ion with existenz..don't know why it is not working...
Sent from my LT28h using XDA Premium 4 mobile app

Root and Dual Recovery for Locked Bootloader

Firstly a massive thanks to RyokoN and [NUT] - much more of this is their work than mine.
The end result is unbranded UK firmware (no docomo/jp apps etc.) 14.2.A.1.114 with SuperSU and NUT's Dual Recovery. The bootloader of course remains locked.
Downloads:
http://dl.weeaboo.com/Z1Compact/C6903_14.1.G.534_ianford10_UK Unbranded.ftf
http://dl.weeaboo.com/Z1Compact/D5503_14.2.A.1.114_Generic UK.ftf
http://dl.weeaboo.com/Z1Compact/SO-02F_14.1.H.1.281_docomo.ftf
http://dl.weeaboo.com/Z1Compact/z1c-43-uk.system.flashable.zip
SuperSU flashable zip from http://download.chainfire.eu/supersu
LATEST Z1C-lockeddualrecovery flashable and installer .zip from http://nut.xperia-files.com/ (thanks to [NUT])
FlashTool: http://www.flashtool.net/index.php
Process:
Copy UPDATE-SuperSU-v1.(...).zip, z1c-43-uk.system.flashable.zip and Z1C-lockeddualrecovery(...)flashable.zip to your external SD card.
Take a full backup, as all phone memory INCLUDING INTERNAL SD will be wiped.
Flash SO-02F_14.1.H.1.281_docomo.ftf (WIPE: select all, EXCLUDE: select none)
Boot and enable USB debugging and installation of apps from unknown sources
Flash C6903_14.1.G.534_ianford10_UK Unbranded.ftf (WIPE: select none, EXCLUDE: select all except system and kernel)
Turn phone on (display will be blank)
Run Z1C-lockeddualrecovery(...)installer.zip's install.bat, selecting option 3 (Installation on unrooted ROM).
Turn phone off using the power + vol up combination.
Flash D5503_14.2.A.1.114_Generic UK.ftf (WIPE: select none, EXCLUDE: select system only)
Boot to philz recovery by turning phone on normally then pressing vol up after the vibrate + green LED
Factory reset and clear for rom installation
Flash in this order without rebooting between each:
z1c-43-uk.system.flashable.zip
Z1C-lockeddualrecovery(...)flashable.zip
UPDATE-SuperSU-v1.(...).zip.
You're done

nice work

Thank you!
Not exactly noob-friendly....
But I will try it as soon as I can put my hands on my XZ1C!

sweet! gonna try this in a couple of days when i get a microsd card..
just to be safe though, because this is my first sony: ftf files are flashed with emma, right?
Sent from my D5503 using Tapatalk

Thanks, I am new to Sony too. Hope a video step by step tutorial will be appreciated.
Sent from my pigeon

labbe- said:
sweet! gonna try this in a couple of days when i get a microsd card..
just to be safe though, because this is my first sony: ftf files are flashed with emma, right?
Sent from my D5503 using Tapatalk
Click to expand...
Click to collapse
For the ftfs use flashtool in flashmode http://www.flashtool.net/index.php
Sent from my D5503 using Tapatalk

Hi! Great work.... haven't tried this yet, my first Sony, so a little outside my comfort zone.....
Have you tried backing up the TA partition? Thanks
Sent from my D5503 using XDA Premium 4 mobile app

nelvinchi said:
Hi! Great work.... haven't tried this yet, my first Sony, so a little outside my comfort zone.....
Have you tried backing up the TA partition? Thanks
Sent from my D5503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Haven't tried that yet as I don't plan on touching the bootloader (sony stock roms are excellent imo)
No reason why it wouldn't work, unless sony has added some sort of extra protection (unlikely).

i´ve problem with ddms, as log i can see i´ve installed needed parts, got those error messages:
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get view server version from device CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get view server protocol version from device CB5A1XBJ56
[2014-02-03 20:59:08 - ViewServerDevice]Unable to debug device: sony-c6903-CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Missing forwarded port for CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get the focused window from device CB5A1XBJ56
do you know what to do about it?

funiewski said:
i´ve problem with ddms, as log i can see i´ve installed needed parts, got those error messages:
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get view server version from device CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get view server protocol version from device CB5A1XBJ56
[2014-02-03 20:59:08 - ViewServerDevice]Unable to debug device: sony-c6903-CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Missing forwarded port for CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get the focused window from device CB5A1XBJ56
do you know what to do about it?
Click to expand...
Click to collapse
Not really sure what could cause that, are you able to connect to e.g. adb shell ok?

Darkimmortal said:
[*]Set up DDMS http://forum.xda-developers.com/showthread.php?t=2303834 and ensure it's working ok (you can see phone's screen on PC and can blindly tap on the touchscreen with response visible on PC)
Click to expand...
Click to collapse
DDMS is working (I have taken a screenshot of my phone), but whati is the command to view the phone screen on PC?

c_c_c_66 said:
DDMS is working (I have taken a screenshot of my phone), but whati is the command to view the phone screen on PC?
Click to expand...
Click to collapse
There is no realtime view, you can only refresh the screenshot
Sent from my D5503 using Tapatalk

Darkimmortal said:
Haven't tried that yet as I don't plan on touching the bootloader (sony stock roms are excellent imo)
No reason why it wouldn't work, unless sony has added some sort of extra protection (unlikely).
Click to expand...
Click to collapse
Thanks for that - I'll give your walkthrough a go tonight when I get home.... I'll report back on the results of attempting a TA partition backup....
Fyi, you note that the only thing "lacking" is a writeable /system - should anyone require to mount as rw, try this:
Install Android Terminal Emulator from the store, start it and do this:
su
mount -o rw,remount -t ext4 /system
Done!

nelvinchi said:
Thanks for that - I'll give your walkthrough a go tonight when I get home.... I'll report back on the results of attempting a TA partition backup....
Fyi, you note that the only thing "lacking" is a writeable /system - should anyone require to mount as rw, try this:
Install Android Terminal Emulator from the store, start it and do this:
su
mount -o rw,remount -t ext4 /system
Done!
Click to expand...
Click to collapse
Oi get on hangouts u Iggy can't wait to get the Z1C and try this out
Sent from my HTC One mini using Tapatalk

@Darkimmortal
Please replace the links in the OP for the official development thread and download page: http://nut.xperia-files.com as 2.7.80 is already outdated (TWRP has the wrong alignment and has been replaced by 2 improved versions already). That and I kindly requested not to mirror any of my files...
It's not to give you a hard time, but this way your users can NEVER be sure the files are from me or slightly modified by you to do some bad juju... This is my way to grant users somewhat of a quality control. I hope you understand.
I'll be opening a Q&A thread here soon though, for the official device specific support.

Problems
Hi
I'm getting problems on "14. Boot to philz recovery by turning phone on normally then continually pressing vol up after the single vibrate", the device only vibrates 2 times and the "sony" logo is on the screen but nothing happens.
Does anybody have a fix?

[NUT] said:
@Darkimmortal
Please replace the links in the OP for the official development thread and download page: http://nut.xperia-files.com as 2.7.80 is already outdated (TWRP has the wrong alignment and has been replaced by 2 improved versions already). That and I kindly requested not to mirror any of my files...
It's not to give you a hard time, but this way your users can NEVER be sure the files are from me or slightly modified by you to do some bad juju... This is my way to grant users somewhat of a quality control. I hope you understand.
I'll be opening a Q&A thread here soon though, for the official device specific support.
Click to expand...
Click to collapse
Certainly, I've updated that now
I only checked your download page for any no mirror warnings

torjohron said:
Hi
I'm getting problems on "14. Boot to philz recovery by turning phone on normally then continually pressing vol up after the single vibrate", the device only vibrates 2 times and the "sony" logo is on the screen but nothing happens.
Does anybody have a fix?
Click to expand...
Click to collapse
It may boot loop in this way a couple of times - try turning it off again with the power+vol up 3 vibrate combo
If you still can't get it into recovery, start over and ensure the recovery installer.zip step is performed correctly

Darkimmortal said:
Certainly, I've updated that now
I only checked your download page for any no mirror warnings
Click to expand...
Click to collapse
That's a good point, I'll add that warning soon
Thanks for updating the op guide :good:

Success :laugh:
Thanks for your work, ddms was a bit tricky, you need patience
No problem with making backup of ta partition
now unlocking bootloader
:good:

[Tool] [SS/DS] [LB] [Deprecated] Nicki Root - Full root on latest firmware

UPDATE: check out TowelRoot app by @geohot! One-click root solution that works with latest firmware released for Xperia M single/dual (provides half-root only, don't forget to apply root fixer)
Nicki Root is deprecated, it got merged in my new dd Flasher tool and works across many devices, not only Xperia M. The attachments and changelog from Nicki Root were kept below for archiving history, but I won't provide support for it anymore. For any problem you may encounter, go to dd Flasher thread. If you want to root Xperia M through dd Flasher, downgrade your device to Android 4.1 or 4.2.2 firmware, root it with Cydia Impactor and follow the instructions from dd Flasher thread.
Changelog
Version 2.0
• Nicki Root now is called dd Flasher
Old versions
Version 1.3.3
• Bugfixes for Linux script
• Updated SuperSU to 2.02
Version 1.3.2
• Make sure the temporary folder exists before pushing the script
Version 1.3.1
• Now compatible with Linux
Version 1.3
• Implement log capabilities (users can pull last log by selecting appropriate option in main menu)
• Drop "reboot in flash mode" (after using dd, system partition layout is different and device can't be rebooted)
• Check if LED can be used to indicate status, otherwise disable it
• Minor code changes
Version 1.2
• Rewrote most of the code
• Script now uses LED to indicate status
• By popular demand, dropped choice command in favour of set command (should work with Windows XP again)
• For every single command, script will now check if it failed or not and warn the user if anything get wrong
• Rewrote the mount/umount routine, loop device is selected automatically and resource busy issues are fixed now
• Can be used with half-rooted devices now (script check if device is fully rooted and apply root fixer at runtime if needed)
• Implemented "reboot in flash mode" command to avoid needing to pull/reinsert battery manually (experimental, sometimes doesn't work)
Version 1.1
• Make sure busybox is installed after first boot (previous versions pushed busybox but didn't install it)
• Drop choice32/choice64 applets and use built-in OS command (Windows XP no longer supported)
Version 1.0.1
• Typo fix (Nicky => Nicki)
• Updated busybox to 1.22.1
Version 1.0
• Initial release

Will test as soon as Indian Firmware Update show up...
Sent from my C2004 using Tapatalk

Well done @mbc07, this is great news. Dont forget to give credit to @joemarshall, afterall, he cane up with the idea . Thanks for testing it and creating this thread, nevertheless
sent from wadiya using my mafroom

I'll be trying this (probably) in the next hour, I'll post results for the Single SIM afterwards.
RESULTS TIME: This method of rooting worked and I am now running 4.3 with root access. Thank you.
Sent from my C1905 using xda app-developers app

Gonna test after I download 4.1.2 ftf, hope it works

rizla2 said:
Gonna test after I download 4.1.2 ftf, hope it works
Click to expand...
Click to collapse
It works perfectly, I'm now rooted on 4.3 thanks to this. The only error I had was when the tool first tried to push the system.ext4 to the SD Card, it said there wasn't enough space, I just deleted the incomplete copy and then ran the tool again and it worked.

Hmm, I'd not thought of mounting the image and doing dd, that is pretty tidy.
Balls, It didn't work for me first try, error mounting the loopback device, said it was busy. I'm re-flashing the phone back to 4.1 now. I've split the shell scripts into 2, first one does the modifications of system.ext4, second one does the dd flash, with a press any key between. That way if the modifications to system.ext4 fail, you're not stuck with an unrooted phone where system partition has already been written, and you can happily start again. I was flashing from sd card if that makes any difference.
Also, would it be possible to copy the reboot executable into your temp folder before you do the dd, so that you don't have to do the battery out reset in the middle of the process, or won't reboot work once you're in that state?
Edit: Second time lucky, thanks ever so much. Maybe I just needed to start from a blank slate version of 4.1, blimey that first boot takes some time though!
cheers,
Joe

mbc07 said:
It took me a lot of time and I tried a lot of methods but I finally managed to root the new 4.3 update without unlocking the bootloader, let's root that thing.
Requirements:
You will need FlashTool and the FTF file of 4.3 update for your phone
You should be running Android 4.1.2/4.2.2 firmware with full root. If you already updated to 4.3, sorry, you'll need to downgrade to 4.1.2/4.2.2 and root it, otherwise this method won't work
You should have at least 1.5GB of free space in your Internal Storage or in your SD Card. If you don't have enough space, the installation will be aborted and your phone will be left intact
Make sure you have full root (eg. your phone doesn't reboot when you remount /system with RW access). Using this method without full root may reboot your phone during the procedure, getting you in a bootloop
Currently the script works only on Windows, I'll try to get a Linux version soon
Getting system.ext4 file: before continuing, we'll need to extract system.ext4 from system.sin present in the update. Open the FTF it with WinRAR or 7-zip and extract system.sin somewhere, then open FlashTool, go to Tools => Sin Editor, locate the system.sin file extracted previously and then click in "Extract Data". You'll get system.ext4 in the same folder you extracted system.sin. Now you're good to go
Procedure:
Download the attached ZIP and unzip its contents somewhere
Move system.ext4 extracted previously to the same folder where root.bat is
Open root.bat and follow the instructions
After the process finished, the script will tell you and your phone will be in a frozen state (it's normal). At that point, you should manually remove the USB cable and then pull/reinsert your battery. DON'T TURN IT ON, we haven't finished yet (turning it on now will get you in a bootloop).
Open FlashTool again and flash the entire 4.3 FTF, but exclude system (if you forget to do so, the root will be removed and you'll need to start over)
After flashing finished, disconnect the USB cable and start your phone. If everything went well you should be in 4.3 now, with full root access
NOTE: I'm not that good with BASH/Shell scripts, and although I had implemented some sanity checks, something may have escaped that checks. So, if you do this procedure and the shell script finish with errors, it's better to start over since something may have not worked and you may be in a partial root state...
Click to expand...
Click to collapse
It worked for me thanks to you

About flashing 4.3 can I do a data and cache wipe?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka

iks8 said:
About flashing 4.3 can I do a data and cache wipe?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka
Click to expand...
Click to collapse
Flashtoll wil wipe data and cache when you flash 4.3 You don't need to do anything else.

paper13579 said:
Well done @mbc07, this is great news. Dont forget to give credit to @joemarshall, afterall, he cane up with the idea . Thanks for testing it and creating this thread, nevertheless
sent from wadiya using my mafroom
Click to expand...
Click to collapse
I still need to rework the OP, many people from Root for FTF 4.3 Update 15.4.A.0.23 LOCKED BOOTLOADER deserves credits, after all I wouldn't have that idea without their replies... Will get these guys credited in the OP soon
joemarshall said:
Hmm, I'd not thought of mounting the image and doing dd, that is pretty tidy.
Balls, It didn't work for me first try, error mounting the loopback device, said it was busy. I'm re-flashing the phone back to 4.1 now. I've split the shell scripts into 2, first one does the modifications of system.ext4, second one does the dd flash, with a press any key between. That way if the modifications to system.ext4 fail, you're not stuck with an unrooted phone where system partition has already been written, and you can happily start again. I was flashing from sd card if that makes any difference.
Also, would it be possible to copy the reboot executable into your temp folder before you do the dd, so that you don't have to do the battery out reset in the middle of the process, or won't reboot work once you're in that state?
Edit: Second time lucky, thanks ever so much. Maybe I just needed to start from a blank slate version of 4.1, blimey that first boot takes some time though!
cheers,
Joe
Click to expand...
Click to collapse
Thank you for the feedback, I'll try to add some sanity checks before using dd. About reboot, I tried using busybox reboot but nothing happened, the same for adb reboot. Apparently after using stop, the reboot command doesn't seems to work

Uh, I forgot... Anybody tried pushing to SD Card? Did it worked?

mbc07 said:
Uh, I forgot... Anybody tried pushing to SD Card? Did it worked?
Click to expand...
Click to collapse
Yes it did, sort of. The first time I did it I got an error saying there wasn't enough space (I had over 10GB free however). Once I got the error I deleted the incomplete file from my SD Card and then I ran the script again, this time it copied the file fully and then installed properly.
This occurred on the Single SIM C1905 Xperia M by the way.

Yes! Finally rooted. Thanks a lot!
Btw don't forget to change usb mode to mtp instead msc (I've tried msc and it can't copy files)

mbc07 said:
I still need to rework the OP, many people from Root for FTF 4.3 Update 15.4.A.0.23 LOCKED BOOTLOADER deserves credits, after all I wouldn't have that idea without their replies... Will get these guys credited in the OP soon
Thank you for the feedback, I'll try to add some sanity checks before using dd. About reboot, I tried using busybox reboot but nothing happened, the same for adb reboot. Apparently after using stop, the reboot command doesn't seems to work
Click to expand...
Click to collapse
At first time i've had also 'mount: mounting /dev/block/loop0 on /data/local/tmp/system failed: Device or res
ource busy'
Flash new, clean Android 4.1 solve problem.
Thank you very much.

Hey guys, does this give you full root?
sent from wadiya using my mafroom

paper13579 said:
Hey guys, does this give you full root?
sent from wadiya using my mafroom
Click to expand...
Click to collapse
Yes it does.

I'll check about the loop device errors (apparently they may occur in Xperia M single SIM), thanks for reporting guys...
paper13579 said:
Hey guys, does this give you full root?
sent from wadiya using my mafroom
Click to expand...
Click to collapse
Yes. I implemented the disable ric service method from [NUT] root fixer too

Man, this is a great achievement, you should be proud. Im about to try it now. Wish me luck
sent from wadiya using my mafroom

Before your script use dd it should check:
1. That there is no any apps mounted in /dev/block/loop0 (for example Swift Key). If yes, you will see 'mount: mounting /dev/block/loop0 on /data/local/tmp/system failed: Device or resource busy' (you can it by type losetup)
2. Phone is in MTP USB MODE. If you set to memory storage mode, Android will not access to sd card with system.ext4 image (script would check that can it access to /sdcard) and you will get mount argument error

[UPDATED v1.1] zROM+ Custom ROM for Z3+ E6553 - 28.0.A.8.251, Android 5.0.2

zROM+ 28.0.A.8.251 Android 5.0.2 - V1.1​Sony Xperia Z3+ E6553​
​
ROM Features
Based on Sony firmware 28.0.A.8.251 Generic Hong Kong
Aroma installer
Deodexed and zipaligned
Rooted with SuperSU preinstalled
Dual boot/ TWRP recovery environment
Custom kernel with runtime control of SELinux enforcing status and RIC disabled
Google apps updated and with customizable graphical installer for Gapps
Writeable external SD card
Xposed framework functional (in SELinux permissive mode)
Bloatware removed
The following apps and bloatware have been removed and can be installed directly from the Play store if desired. The first two are installable by selecting the appropriate option in the ROM installer
What's New
Xperia lounge
AVG Antivirus
AAStocks
Anonymous Data Collection
Facebook
Lifelog
Mobisystems File Commander
Mobisystems Office
MyXperia
Playstation App
Playstation Network Portal
Privilege Movies
Sketch
Socialife
Sony Movie Creator
Spotify
Trackid
Please hit the Thanks button if you use this ROM. Many downloads but few thanks....
Installation instructions
NOTE: You must perform a factory reset before install by wiping cache and data.
Click to expand...
Click to collapse
Step 1
Download the TWRP image for the Z3+ and unpack it
Download zROM+ and the zROM+ md5 file
Run a command shell
Code:
c:>adb reboot bootloader
c:>fastboot boot recovery.img
c:>adb push zrom-v1.1.zip /sdcard/zrom-v1.1.zip
c:>adb push zrom-v1.1.zip.md5 /sdcard/zrom-v1.1.zip.md5
The file is big, so it will take 5 or more minutes to complete the upload. If you're impatient put your external SD in a card reader and load it that way.
Step 2
In the interface for TWRP, navigate to Wipe and perform a factory reset
In the interface for TWRP, navigate to Install
Click install, select zrom-v1.1.zip from the internal storage
Swipe to flash
Read and follow the instructions
Reboot when complete
Click to expand...
Click to collapse
The first boot is painfully slow. It takes about 10 minutes, so just be patient. It will stay in the blue booting screen for a long time. This is normal. Do not reboot your phone. Just wait and it will eventually boot up. You can always rerun the installer to flash additional Google Apps. If you do so, be sure to deselect the install ROM option and do not do a factory reset.
Notes
This ROM has a kernel that supports runtime SELinux mode changes. The mode change is accomplished through a script /system/su.d/permissive.sh, which sets SELinux to permissive mode at boot time. If you wish to run Xposed, you must run SELinux in permissive mode. Failure to do so results in multiple system applications force closing at startup and a device that is locked up.
If you don't run Xposed I recommend that you keep SELinux in enforcing mode. To do so, go to Settings-->About and click multiple times on the Build number until it tells you that Developer mode is activated. When developer mode is activated, back out and select the Developer option and enable USB debugging. Now run an adb shell and remove the permissive mode script. Grant permission for USB debugging when the prompt comes up
Code:
c:>adb shell
[email protected]:/ $ su
Wait for the SuperSU prompt and grant permission to adb
Code:
[email protected]:/ # mount -o rw,remount /system
[email protected]:/ # rm -f /system/su.d/permissive.sh
[email protected]:/ # reboot
If you choose not to install any of the Google apps, a minimum core Google framework will be installed anyway. This includes Google framework, GmsCore, Google Play, Google Login Services, Google Contacts and Backup Sync, SteupWizard and OneTimeInitializer that runs after first boot. Apart from the Play store app and the first time setup apps, the rest of these apps are not visible in your app drawer.
While I have made every effort to test this ROM in a variety of different install scenarios, it is a beta ROM and you may experience some bugs. I make no warranty as to its fitness for purpose or its performance and you use it at your own risk.
PLEASE SEE NOTE BBELOW IN POST TWO ON USING XPOSED FRAMEWORK
This ROM now supports booting directly into TWRP recovery mode. To access recovery mode, power on the phone and when you see the yellow LED illuminate press the down volume button once or twice.
Downloads
TWRP v2.8.7.0 for Z3+
zROM+ v1.1 for Z3+ (md5: 999452b5ac29f92473b964af819a3cd6)
zROM+ v1.1 for Z3+ MD5
for GPL purposes, the kernel and associated dowloads
Changelog
Current changelog: -- 01 October 2015
01 October - Release v1.1
Add dual boot/recovery environment
Remove Android Pay due to Google restrictions on root
Update Google apps
19 September - Release v1 beta
Thanks To/Credits
amarullz for the Aroma graphical installer
The OpenGapps team at www.opengapps.org for the Gapps binaries for aarch64
osm0sis for some of the functions used in the installer script
XDA:DevDB Information
zROM+, ROM for the Sony Xperia Z4
Contributors
dl12345
ROM OS Version: 5.0.x Lollipop
Based On: 28.0.A.8.251
Version Information
Status: Beta
Current Beta Version: v1.1 beta
Beta Release Date: 2015-10-01
Created 2015-09-20
Last Updated 2015-09-19

Xposed framework v74 bootloops on Xperia Z3+. The reason for this is discussed in this post
To use Xposed on zROM+, please download the [UNOFFICIAL] xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929 for Xperia Z3+
You MUST do a wipe cache and dalvik after installation otherwise you will get errors including one that claims your storage space is full and another 504 error when installing anything from the Play Store
Please read the instructions in the referenced post

Have been waiting for this with baited breath. So far so good! Thanks for the great work!

Do need unlockbootloader to install rom?

manhhung1420 said:
Do need unlockbootloader to install rom?
Click to expand...
Click to collapse
Yes.

Thank you for your efforts.
Any chance that this ROM can work for E6533 (dual SIM) variant? Or can you plan to support?

Rookie123 said:
Thank you for your efforts.
Any chance that this ROM can work for E6533 (dual SIM) variant? Or can you plan to support?
Click to expand...
Click to collapse
Offhand, I'd say it's unlikely. Sony has a different firmware for this phone.
I'm unlikely to support a device I don't have access to. Apologies.

Works great thanks. Is there any way to make a sound mod to increase headphones volume?

pikeylfc said:
Works great thanks. Is there any way to make a sound mod to increase headphones volume?
Click to expand...
Click to collapse
There's probably something in the xposed repository for that....

Am so sorry to heard that I wanted to install a fresh rom on my hot phone

lilloscar said:
Am so sorry to heard that I wanted to install a fresh rom on my hot phone
Click to expand...
Click to collapse
Sorry to hear what?

dl12345 said:
Sorry to hear what?
Click to expand...
Click to collapse
That this rom wont support the dual version

Great work! finally working recovery...but please..cant access my external sd card! fix this please!

chrisss5000 said:
Great work! finally working recovery...but please..cant access my external sd card! fix this please!
Click to expand...
Click to collapse
No problem here accessing my external SD card in recovery mode and when booted in the ROM. Have you formatted your external card? In recovery mode, the path to the external SD card is /external_sd...

so weird...try to enable it..but it dosent work...and the rom cant start...stock at bot sony xperia logo...

chrisss5000 said:
so weird...try to enable it..but it dosent work...and the rom cant start...stock at bot sony xperia logo...
Click to expand...
Click to collapse
You likely didn't do a wipe. Go to advanced wipe. Wipe dalvik cache, system, data, cache. Reinstall the rom.

dl12345 said:
You likely didn't do a wipe. Go to advanced wipe. Wipe dalvik cache, system, data, cache. Reinstall the rom.
Click to expand...
Click to collapse
I have installed roms like hundrad times...I did a factory reset and I did advanced wipe etc...dosent work..so weird..
I guess something is wrong..something with premissions? Because every time I have wiped my phones it takes a while..But when I wiped now with this recovery it was done in a heart beat...

chrisss5000 said:
I have installed roms like hundrad times...I did a factory reset and I did advanced wipe etc...dosent work..so weird..
I guess something is wrong..something with premissions? Because every time I have wiped my phones it takes a while..But when I wiped now with this recovery it was done in a heart beat...
Click to expand...
Click to collapse
You're installing on a Z3+ e6553 single sim version, right? My wipes are pretty quick too....once the wipe is done, go to the mount option in recovery, mount the filesystems and make sure they're empty (well, they will contain a lost+found folder for the ext4 filesystems and your sdcard contents for the /data filesystem).
Permissions are unlikely to be the problem. The ROM is untarred from an ext4 filesystem copy, so original filesystem permissions are preserved. It also installs an updated file_contexts and does a selinux restorecon to make sure selinux contexts are correct...

dl12345 said:
You're installing on a Z3+ e6553 single sim version, right? My wipes are pretty quick too....once the wipe is done, go to the mount option in recovery, mount the filesystems and make sure they're empty (well, they will contain a lost+found folder for the ext4 filesystems and your sdcard contents for the /data filesystem).
Permissions are unlikely to be the problem. The ROM is untarred from an ext4 filesystem copy, so original filesystem permissions are preserved. It also installs an updated file_contexts and does a selinux restorecon to make sure selinux contexts are correct...
Click to expand...
Click to collapse
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...

dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
Yes it is Xpera Z3+ E6553
Okay I will test it now! I will come back with results
big thanks!!
---------- Post added at 08:05 PM ---------- Previous post was at 08:00 PM ----------
dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
Uhm should the installing just take 15 sec? I nearly drop my finger from the screen and it is wiped....something is wrong...
---------- Post added at 08:07 PM ---------- Previous post was at 08:05 PM ----------
dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
it dosent work...it only get stuck at sony loggo