Introduction
With every new release in Xperia lineup, the story repeats: device ships with latest security fixes, locked system partition, without root access. If you bought it from a retail store or without a contract, your device's bootloader can be unlocked and you can start messing with it (getting a custom recovery, gaining root access, etc) but as a trade off, your DRM keys are gone and some stock apps/features stops working. Even worse, if you bought your device from a carrier or with a contract it probably came with a permanently locked bootloader and there's nothing you can do about.
However, there's no software free of bugs, sooner or later an exploitable security bug appears and some talented developers may use that to get root access in locked devices. And time has come to Xperia E3, now the community have working exploits capable of getting root access on locked bootloaders and this tutorial will help you achieving that. Let's get started!
Overview
First off, Xperia E3 was released in several variants across the globe and the process differs a bit between them. Starting now, we'll group the variants in two groups:
• If you have D2202 or D2212, I'll refer to your device as HSPA variant
• If you have D2203, D2206 or D2243, I'll refer to them as LTE variant
This guide is mainly aimed at HSPA variants where the process involves downgrading to a initial firmware, running a modded version of giefroot and then using another tool (dd Flasher) to update to the latest firmware version without losing root access.
If you have a LTE variant, unfortunately, the modded version of giefroot we'll use to get root won't work but thanks to @nortonex you still can get root with a slight different process, involving cross flashing an exploitable version of Xperia M2 kernel to get root access and then reverting to the stock kernel and applying a patch to disable RIC protection (it's a Sony "feature" that prevents writing to system partition, even with root, similar to HTC's S-ON/S-OFF flags). So, if you have one of the LTE variants, follow his guide...
Requirements
To get root:
• Exploitable firmware (must be 18.4.B.1.20 -- region/market doesn't matter)
• FlashTool (0.9.18.4 or newer)
• Modded giefroot v3 (attached below)
To update to latest firmware after getting root:
• dd Flasher
• XperiFirm (optional)
Preparing the device
To start, we need to downgrade your device to the old 18.4.B.1.20 firmware, the only one exploitable by giefroot, so, if you need, make a backup of your device's data first, your content will be wiped during the downgrade. You can also use any other FTF that matches your region/market as long as it's 18.4.B.1.20...
• If your device is powered on, turn it off and disconnect USB cable (if connected) now. Now, start FlashTool and click in the Thunderbolt icon, then choose Flash Mode and press OK
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
• If needed, click on the "..." button and point FlashTool to the folder where you've downloaded the FTF linked in the Requirements section of this Tutorial. Then, choose the firmware in the list, mark "No final verification" and "Reset customizations" and press Flash
• Wait until FlashTool prepare the FTF to flash. When it's done, the screen below will appear. Now, with your device turned off, hold Volume Down button and plug the USB cable while you're holding the button. If you did right, the notification LED will briefly flash in green/red and FlashTool should start flashing the firmware
• After the flashing process finishes, close FlashTool, disconnect your device and turn it on. Remember that the first boot will take longer (5-10 minutes), that's normal.
Running the exploit
Now your device is running the exploitable firmware version, let's set up it to run the exploit and get root access...
On phone side:
• We need to "unlock" developer settings. You can do that by going to Settings => About phone and then tapping "Build Number" 7 times
• Now we can go to Settings => Developer Options. Here you should enable "Stay awake", "USB debugging" and "Allow mock locations". Then, disable "Verify apps over USB"
Now on computer side:
• Plug your device in the computer
• Extract the modded giefroot somewhere (it's attached in the end of this thread) and launch it by opening "install.bat" (or, if you're using Linux/Mac, start "install.sh" from Terminal)
• In your device, a small popup about ADB connection will appear, make sure you mark "always allow connection from this computer" and press OK
• From here, just wait until giefroot finishes. Your phone will reboot automatically, that's normal
Note: Sometimes you may not get root in the first attempt, that's normal, just run giefroot more two or three times and it'll eventually work
And that's it. Your device is now fully rooted, however, we are stuck in an older firmware version.
Update procedure
There's more than one way to upgrade to the latest firmware without losing root access and I'll try to explain all methods I know. Before continuing we'll regroup devices accordingly to the bootloader unlockability (you can check your device's bootloader state by entering *#*#7378423#*#* in the Dialer then going to Service info => Configuration)
If your device's bootloader is permanently locked (Bootloader Unlock Allowed: No), your only known option will be using dd Flasher (explained in the next chapter). If your device's bootloader is unlockable (Bootloader Unlock Allowed: Yes) then you can also use the unlock/root/relock procedure which involves backing up your TA partition with Backup TA, unlocking your bootloader, updating to the latest firmware normally (either with FlashTool or Sony PC Companion), flashing a custom recovery, installing SuperSU through it and then relocking your bootloader (restoring your DRM keys too) with the TA backup you took earlier.
I won't explain the unlock/root/relock procedure in details since it's a little trickier and won't work for devices with permanently locked bootloader, which is the main purpose of this tutorial. However, I attached a stripped down version of giefroot which only installs the wp_mod kernel module, in order to disable write protection to system partition. If you updated to the latest firmware with dd Flasher, there's no need to apply this patch, dd Flasher will automatically handle that for you, I posted that focused more on advanced users that opt to use unlock/root/relock procedure and are getting trouble when trying to write to system partition...
Using dd Flasher
This chapter is a little longer and sometimes you need to jump into different routes, because of that, it's splitted in smaller sections and jump notes in the start of each section...
Downloading latest firmware
Note: if you already have a FTF of the latest firmware for your device or if you prefer using XperiFirm to get latest firmware, skip this section and go directly to "Preparing system image"
First off, we need to get a FTF of the latest available firmware for your device/market. Below I explain how we get it using FlashTool, you can do that with XperiFirm or just download a FTF someone else have uploaded too. I'm focusing on FlashTool here since it's the only option for people using Linux/Mac (forget it, apparently XperiFirm also works on Linux/Mac now)
• Open FlashTool and go to Devices => Check Updates. Then, locate Xperia E3 in the list and double click on it
• Here, a small window with tabs for each variant will show. Go to the tab that corresponds to your device's variant, then double click the matching region/market of your device to check latest firmware version available in that region. After that, double click it again so it starts downloading the firmware from Sony servers
• After download and decrypt is finished, bundle creator will open automatically (you can also open it manually through Tools => Bundle creator). Most of the info here will be already entered, we only need to choose all files present in the panel from the left and click the little arrow to move all of them to the right panel. After that, press "Create" and wait until bundle creation (FTF) is finished. After that we're gonna extract system.ext4 (dd Flasher will need it), it's explained in the next section...
Preparing system image
Note: I'm assuming that you already have access to system.sin (and you have if you followed the instructions from previous section to get your FTF). If you don't have access to system.sin, you can extract it directly from the FTF file by opening it with WinRAR/7-Zip or anything capable of extracting ZIP files (yes, FTFs are just regular ZIP files with different extension)
At that point, we have a FTF of the latest firmware, however, dd Flasher doesn't work with FTF files directly, just with raw partition dumps, and we'll extract it from the update now
• Open FlashTool and go to Tools => Sin Editor. In the small window that will appear, click on "..." and point it to system.sin, then, press "Extract Data" (if you downloaded your firmware following the instructions from previous section, a copy of system.sin will be located in C:\Users\<username>\.flashtool\firmwares\Downloads\D22xx_xxxxxxxxx_xxxxxx\decrypted)
• After extraction finishes, a new file named system.ext4 will be created in the same folder where system.sin is. Extract dd Flasher somewhere and move system.ext4 to the same folder, it must be named system.ext4 (rename it if necessary, otherwise dd Flasher will fail) and should be next to dd_flasher.bat/dd_flasher.sh
Flashing new system image
Here's where the magic occurs. First off, make sure FlashTool is closed, otherwise it'll interfere with ADB connection and dd Flasher may fail. Then, follow the procedure:
• Start dd Flasher by opening dd_flasher.bat (or if you're on Linux, launch dd_flasher.sh from a Terminal -- sorry Mac users, dd Flasher isn't compatible with your OS yet)
• If everything is right, dd Flasher should ask you where the system image should be pushed. Remember that the selected location should have enough space to store system.ext4 before (and if you're pushing to SD Card, make sure phone's connection mode is MTP, otherwise dd Flasher will fail)
• After you selected the storage device, dd Flasher will do its work. Just wait until it's done, it'll take a while (about 10 minutes)
• After the process finishes, you should unplug your phone and turn it off through the Off switch found in the back, next to the SIM card (this step is very important!) and don't turn it on yet
Flashing the remaining components from the FTF
That's the last step, in current state your device has the system partition of the latest firmware version with su binaries (to get root access) but kernel, modem, baseband, etc. still are from the old firmware version and because of that it won't boot properly. Let's fix that:
• Start FlashTool and click in the Thunderbolt icon, then choose Flash Mode and press OK
• If needed, click on the "..." button and point FlashTool to the folder where you've downloaded the FTF of the latest update. Then, choose the firmware in the list, mark "Reset customizations" and make absolutely sure you mark "SYSTEM" in the Exclude panel too (if you forget to mark it, root will be lost and you'll need to start the whole tutorial again from beginning). After double checking, press Flash
• Wait until FlashTool prepare the FTF to flash. When it's done, the screen below will appear. Now, with your device turned off, hold Volume Down button and plug the USB cable while you're holding the button. If you did right, the notification LED will briefly flash in green/red and FlashTool should start flashing the firmware
• After the flashing process finishes, close FlashTool, disconnect your device and turn it on. Remember that the first boot will take longer (5-10 minutes), that's normal.
And this is the end of tutorial, your device will now be running the latest firmware version with full root access. Congratulations!
Frequently Asked Questions
Q: I have a D2202 variant, wouldn't crossflashing D2212 firmware brick it?
A: No, your device won't brick since the only difference between D2202 and D2212 is the dual SIM support. In the worst scenario you would see options and icons for second SIM functionality but they would disappear again after updating to the latest D2202 firmware with dd Flasher.
Q: I have a D2202 variant but now I'm stuck with D2212 firmware. How do I switch back to D2202 firmware without losing root?
A: Just follow "Using dd Flasher" chapter but instead of downloading firmware for D2212, download for D2202. If you already did "Using dd Flasher" chapter with D2212 firmware you can repeat this chapter but now selecting D2202 firmware.
Q: Help! I don't have a micro SD card and dd Flasher keeps failing to push system image. What sould I do?
A: The system image is generally around 1 GB but it can be larger depending of the market/branding. If you don't have enough space in Internal Storage, dd Flasher will fail. What you can do is downloading Titanium Backup or another similar app to remove as many bloatware as you can, until you have enough free space to temporarily store system image in Internal Storage.
Credits
Kudos to @zxz0O0 for giefroot and its promptly and helpful collaboration to get Xperia E3 working with it. Kudos also to @MohammadAG for its modded wp_mod kernel module which is used in giefroot and into the stripped down RIC disabler attached below. I would also like to thanks everyone from [Q] Root with locked bootloader? who helped directly or indirectly into this.
Downloads
Screenshots
Will upgrading cause lose to data and apps ?
pranayberry said:
Will upgrading cause lose to data and apps ?
Click to expand...
Click to collapse
By default, yes, everything will be wiped (except SD Card). You can try doing the downgrade/upgrade without wiping data by unchecking "Wipe DATA" option in FlashTool but it's not guaranteed to work (especially at the downgrade step)...
Will this firmware d2212 work on d2202
Sent from my D2202 using XDA Free mobile app
sjunaid1997 said:
Will this firmware d2212 work on d2202
Click to expand...
Click to collapse
Yes, it'll work. However, it's only needed to run the exploit. After getting root you can use a FTF from D2202 with dd Flasher to go back to official firmware, maintaining root access...
Thanks will try it tomorrow and let u know
Sent from my D2202 using XDA Free mobile app
---------- Post added at 08:21 PM ---------- Previous post was at 08:18 PM ----------
What if after rooting on d2212 firmware i back up my ta partion and unlock my bootloader then flash d2202 firmware then root it again
Sent from my D2202 using XDA Free mobile app
sjunaid1997 said:
What if after rooting on d2212 firmware i back up my ta partion and unlock my bootloader then flash d2202 firmware then root it again
Sent from my D2202 using XDA Free mobile app
Click to expand...
Click to collapse
This method works too (in fact it works with any Xperia device with unlockable bootloader). This procedure is not detailed in this guide because it's aimed most at people with permanently locked bootloaders, but it should be as simple as downgrading to the exploitable D2212 firmware to gain root with modded giefroot, backing up TA partition then unlocking the bootloader, updating to the latest firmware for your device and installing SuperSU through a custom recovery. To finish, reflash stock kernel and relock the bootloader with the TA backup you took earlier...
Thanks for the help have been waiting for this post i am new to flashing in xperia i used to flash roms on samsung it was easy as pie but sony with its locked bootloader made developers very hard to root it
Sent from my D2202 using XDA Free mobile app
stuck on boot
Everything went normal at update procedure on the final step Was stuck on boot after flashing the updated kitkat firmware kernel .... as this was my primary device i had to flash the stock rom again to use it can i back up ta partition on d2212 firmware will my drm keys be the same as the stock d2202 then unlock bootloader after backing up ta partition pls reply asap
sjunaid1997 said:
Everything went normal at update procedure on the final step Was stuck on boot after flashing the updated kitkat firmware kernel .... as this was my primary device i had to flash the stock rom again to use it can i back up ta partition on d2212 firmware will my drm keys be the same as the stock d2202 then unlock bootloader after backing up ta partition pls reply asap
Click to expand...
Click to collapse
TA backups (and consequently, DRM keys) are unique to each device. NEVER restore backups of another device, even if it's from the same model and variant, doing that would result in a hard brick. In other words, the firmware doesn't matter at all, as long as your TA backup is from the same unit, you can restore it without any troubles in whatever firmware/ROM you're running (as long as you have root access)...
Rooting was fine until...
Hi @mbc07
(I'm sorry that my first post was not a contribution to the community)
I Have the next problem:
-Using dd flasher to flash the new system.ext4 image didn't work
On dd flasher I get this message:
- SuperSU v2.46 (SELinux) cp: can't stat '/data/local/tmp/ddFlasher/system/bin/sh': No such file or directory
- And some other messages about cp
I followed your guide from beginning to end, everything was fine, but when updating with dd flasher to 18.5.A.0.26 (D2202, Orange DO) and flashing the rest of the .ftf with flashtool, my phone ran into the next situation:
-It just shows Sony and Xperia logo, after 30 seconds (aprox.) no screen change and with power button screen turns off and on but Xperia logo still on screen.
Also, after crossflashing D2212 (18.4.B.1.20) on D2202, trying to download Data services I get an error saying "Insert SIM card"
-Tried flashing 4.4.2 SS kernel on 4.4.2 DS firmware, didnt work.
-Tried flashing 4.4.2 SS firmware and rooting (didn't work).
Anyway, worked great on my D2212, but upgrading failed on D2202, thanks for the guide.
Greetings!
@DatchRM, that's a problem with current beta of dd Flasher =/
I already know what can be and should probably be fixed in the stable release of dd Flasher, however I have no ETA because I'm really busy with other stuff but it'll eventually get fixed...
where to store system image?
If i copy system image to sd card then if i removed sd card after will it effect my phone?
prathameshpatankar said:
If i copy system image to sd card then if i removed sd card after will it effect my phone?
Click to expand...
Click to collapse
No
What is wp_mod kernel, and how to use it?
Sent from my D2202 using XDA Free mobile app
Plzz help
When I was trying to update my e3 to 4.4.4 firmware using dd flasher all went fine but after flashing when I was trying to boot up my phone it's still on Sony logo even after 15 mins
Sent from my D2202 using XDA Free mobile app
Did dd Flasher throw some error at you? If yes, post it in dd Flasher thread, I'll take a look. Also, I didn't test but some users told me you should be able to get to the latest firmware via OTA after you got root in the initial 4.4.2 firmware...
No,not a single error, but i hav old 4.4.2 exploitable firmware did u updated that exploitable firmware after?and also i also not downloaded the wp mod is it happened due to that?
Sent from my D2202 using XDA Free mobile app
That's strange, did you reflash the FTF of latest firmware (excluding system partition) after using dd Flasher? Getting stuck in Sony logo generally occurs when the kernel doesn't match the ROM version, and that suggest you may have skipped the last step. About wp_mod, it's a stripped down package that contains only the root fixer, aimed mostly at the LTE variants that uses a different method. You don't need it because dd Flasher automatically applies that patch too...
Hello mates,
Can anyone help me ?
i tried to install MMA 5.1 on my D6633 but i did a mistake starting to install the patch zip before installing the main zip
after restarting the phone, it stucked on sony logo, i cant do a thing.
i've tried the Sony EMMA but the D6633 is not supported .
android commander doesnt detect it at all.
i'm out of trics
thanks in advance
old version 5.0.2 rooted
[email protected] said:
Hello mates,
Can anyone help me ?
i tried to install MMA 5.1 on my D6633 but i did a mistake starting to install the patch zip before installing the main zip
after restarting the phone, it stucked on sony logo, i cant do a thing.
i've tried the Sony EMMA but the D6633 is not supported .
android commander doesnt detect it at all.
i'm out of trics
thanks in advance
old version 5.0.2 rooted
Click to expand...
Click to collapse
Don't afraid it is mustn't be a big problem, can you enter recovery? If yes then flash a pre-rooted stock rom which is available in forums and if you don't have recovery, try flashtool. It must recognize phone in flash mode then use a FTF file (use a 4.4 FTF if you want to gain root and recovery to use zip files such as custom roms) and flash device. It must work.
agent.47 said:
Don't afraid it is mustn't be a big problem, can you enter recovery? If yes then flash a pre-rooted stock rom which is available in forums and if you don't have recovery, try flashtool. It must recognize phone in flash mode then use a FTF file (use a 4.4 FTF if you want to gain root and recovery to use zip files such as custom roms) and flash device. It must work.
Click to expand...
Click to collapse
unfortunately i dont have access to recovery i can only access flashmode (power botton+ volume -) but the flashtool doesn't seem to support my phone showing "no services matching the connected device "
[email protected] said:
unfortunately i dont have access to recovery i can only access flashmode (power botton+ volume -) but the flashtool doesn't seem to support my phone showing "no services matching the connected device "
Click to expand...
Click to collapse
Do you use latest flashtool?
If you are in windows 8 or newer try disabling driver signature check then install phone drivers.
agent.47 said:
Do you use latest flashtool?
If you are in windows 8 or newer try disabling driver signature check then install phone drivers.
Click to expand...
Click to collapse
did that also
i even tried pcc but it's telling me that update is impossible due to the modified softwear 'already installed
I have no idea anymore...
Try with another computer, and try more, sometimes it works for me
agent.47 said:
I have no idea anymore...
Try with another computer, and try more, sometimes it works for me
Click to expand...
Click to collapse
i tried that also
Seniors is anyone there, my phone is bricked :crying:
I fixed the problem
Sent from my D6633 using XDA-Developers mobile app
[email protected] said:
I fixed the problem
Sent from my D6633 using XDA-Developers mobile app
Click to expand...
Click to collapse
Next time read better the instructions.
Latest Android 6.0 Build No. MPSH24.49.18-4 for Moto X Style
Scenario:
While experimenting various stock roms for my Indian Version Moto X Style 1572, I flashed 1575 on my phone. Network did not work. But without trying to fix all the issues , I stepped back and flashed back to Indian Retail Version of Stock Rom XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip from this page. Everything worked but my Bluetooth stopped working. Then tried almost all custom roms and even cyanogen but BT never worked.
So now I was left for few days with BlueTooth issues in phone. Then after taking hints from various threads I managed to unbrick my phone to get latest stock build and May 2016 Android Secutity Patch Level
In short this guide unbricks Indian Moto X Style perfectly to resolve BlueTooth issues / IMEI Loss / other network related issues by flashing latest stock to Android 6.0
Advantages:
1) An important thing to remember, that above Indian stock rom, you will get Android Security Patch Level dated 1-February-2016. But I with files linked by me in this guide (Brazil Rom) so you will get Android Security Patch dated 1-May-2016 with more security
2) The rom is 3 months latest than Indian Stock and build is MPSH24.49.18-4.
3) Initial free space of usable internal memory is upto 75% out of 10GB, which is much higher than Indian Stock which gives only 50% usable space.
Resolution:
Taking idea from this EU (European) Single Sim version I decided to try BRAZIL's latest Dual Sim stock rom and then flash modem+baseband, and VOILA!! Everything Worked perfectly! No network and bluetooth issue anymore.
UNBRICKING STEPS:
So I thought to put these steps here following easy steps.
1) Download BRAZIL's latest official Dual Sim MM 6.0 firmware - MPHS 24.49-18-4 - RETLA-DS-Brazil (May) from here. Extract all files from rar file into new folder on desktop of pc.
2) Also Download Indian Baseband or Modem file called fsg.mbn (DOWNLOAD and extract "fsg.mbn" file in above new folder on your desktop by replacing over brazillian version of fsg.mbn
3) Start phone in Bootloader Mode (power off phone. Then press VolumeDown Key and Power Key both together to start phone in bootloader mode)
and then connect phone to pc with usb cable.
4) Now open command prompt windows on your pc and from the new folder, execute batch file named "Instalador.bat" at command prompt. Wait until all commands are executed which flashes all partition image files one by one. Press any key when prompted on screen to go ahead and wait until it finishes. When done phone will automatically restart. Now you can disconnect USB cable from phone.
Phone will start normally but WITH FULL NETWORK, Wifi and BLUETOOTH all working just fine.
5) Optional (rooting): First enable debugging mode in Settings >> Developer Mode. Restart phone in bootloader mode and connect to pc and from windows command prompt execute following commands to flash latest TWRP recovery file. (DOWNLOAD TWRP).
mfastboot flash recovery twrp-3.0.2-0-clark.img
Click to expand...
Click to collapse
Now start phone in TWRP RECOVERY mode and flash SuperSU flashable zip (DOWNLOAD)
You are done! Network will start showing properly and strongly in both sims Bluetooth also works fine as it should work.
===================================
*Note: 5th step is optional if you do not want to ROOT your phone.
THANKS TO
1) Luiz Augusto Cisneiros Christofoletti from facebook for exact Brazil Stock Link and European unbrick thread.
Reserved
Will I be able to get Ota updates in this rom in India.
[email protected] said:
Will I be able to get Ota updates in this rom in India.
Click to expand...
Click to collapse
No! You will not get OTA automatically but you can still flash new one manually over this rom. No need to worry when everything is possible with xda
In any case if you are rooting phone with last step then you will not get ota.
Can u post the process to flash the 6.0.1 build for the Moto X Style Indian Version. It is much more fast and stable than 6.0. It has already been provided for Moto X Pure so would I be able to flash it by changing modem ,if yes then please show the process, becasue no ROM has the stability which stock has and I didnt take the backup the day I rooted the phone.
Deleted
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
Code:
chintandavda said:
Can u post the process to flash the 6.0.1 build for the Moto X Style Indian Version. It is much more fast and stable than 6.0. It has already been provided for Moto X Pure so would I be able to flash it by changing modem ,if yes then please show the process, becasue no ROM has the stability which stock has and I didnt take the backup the day I rooted the phone.
Click to expand...
Click to collapse
https://firmware.center/firmware/Motorola/Moto X Style/Stock/
Check the phone version/ retail version and then u can flash it
Ps. There is no flashable stock rom available yet
U can follow the steps by
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
Thankyou
Sagar_1401 said:
https://firmware.center/firmware/Motorola/Moto X Style/Stock/
Check the phone version/ retail version and then u can flash it
Ps. There is no flashable stock rom available yet
U can follow the steps by
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
Thankyou
Click to expand...
Click to collapse
Can you please help me to locate Indian version as my baseband is retasia - MPHS24.49-18-4 but i cant find the same in the list provided. It'll be really greatfull if you can help me out here.
rockinsnake said:
Can you please help me to locate Indian version as my baseband is retasia - MPHS24.49-18-4 but i cant find the same in the list provided. It'll be really greatfull if you can help me out here.
Click to expand...
Click to collapse
bro why need
MPHS24.49-18-4 build where as u can flash latest 6.0.1
trust me
flash this https://firmware.center/firmware/Mo...HS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
refer this thread
Sagar_1401 said:
bro why need
MPHS24.49-18-4 build where as u can flash latest 6.0.1
trust me
flash this https://firmware.center/firmware/Mo...HS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
refer this thread
Click to expand...
Click to collapse
Is this more stable than the one installed?
Hope this will not messup any modem part. One guy on the mentioned thread faced issue while flashing:
http://forum.xda-developers.com//mo...moto-x-style-pure-stock-t3272486/post68936541
Instalador.bat?
Where is the Instalador.bat? it is not in the zip file.
If anyone have Moto x style August update india rom then please give me my IMEI is not working and I have to flash it with stock ROM please give me
[email protected] said:
If anyone have Moto x style August update india rom then please give me my IMEI is not working and I have to flash it with stock ROM please give me
Click to expand...
Click to collapse
I use this for my Indian Style
https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257
unfortunately its not working with me please help me out i cant install any custom ROM too
im stuck in stock mm without WiFi,network
Have now done the following .
1. Cell unroot per SuperSU ( If only a short note, then the app closed )
2. boot into TWRP manually and flashed Magisk - v6
3. next phh 's systemless superuser ) with Super SU magisk version already tried )
4. Mobile launched new
5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...
Anyone know what I'm doing wrong ?
Have a Sony Xperia Z3 D6603
gerooted and SuperSU ( 2.78 )
TWRP 3.0.2-0
Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )
Locked Blootloader
would be great if he had a solution for me ...
smellz said:
Have now done the following .
1. Cell unroot per SuperSU ( If only a short note, then the app closed )
2. boot into TWRP manually and flashed Magisk - v6
3. next phh 's systemless superuser ) with Super SU magisk version already tried )
4. Mobile launched new
5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...
Anyone know what I'm doing wrong ?
Have a Sony Xperia Z3 D6603
gerooted and SuperSU ( 2.78 )
TWRP 3.0.2-0
Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )
Locked Blootloader
would be great if he had a solution for me ...
Click to expand...
Click to collapse
I had the same, but maybe the SU can't uninstall. I'm on existenz Rom...
Don't you need an unlocked bootloader?
Sent from my D6633 using Tapatalk
at magisk was nothing about it because that an unlocked bootloader is required.
Yes unlocked Bootloader is required. My Bootloader is unlocked. But can't delete the superuser.apk. That's bad
Exactly the same happened to me. I tried SLiMM 3.1 and PureX V5. After installing Magisk in TWRP device is like dead - only led flashes. If I used Elite kernel, system boots, but the system gets random restarts. Now flashing eXistenZ.
Maybe cause you need to be on stock rom and stock kernel
I use the stock kernel with custom Rom based on the latest official version
Got same issue when using stock kernel on my Xperia Z2, switched to Advanced stock kernel Marshmallow 6.0.1 'cause it has Systemless root support and SElinux permissive and now everything works.
I have try it again, with unroot and install Magisk. Now it works with the advanced stock kernel. But I have some reboots when root is enabled.
Hi All,
I have the same problem, I can see S1 /SOMC Flash Device in Device Manager.
Could someone please post step by step instructions to restore a to Marshmellow?
Will I have to download an Image and a Flashtool?
I have D6603 with TWRP, I am not able to boot to recovery.
Z3- said:
Hi All,
I have the same problem, I can see S1 /SOMC Flash Device in Device Manager.
Could someone please post step by step instructions to restore a to Marshmellow?
Will I have to download an Image and a Flashtool?
I have D6603 with TWRP, I am not able to boot to recovery.
Click to expand...
Click to collapse
Resolved using Emma. I installed the S1 SOMC Flash Device Drivers and I was able to download lollypop.
I will attempt now to reinstall recovery, new rom, and Magisk
Hello all,
I hope someone can help since at the moment I can't do anything with my phone. I wanted to give a new live to my Sony XZP since I am tired of the phone, so I decied to unlock the bootloader and install twrp/root so I could test some of the available Android 10 roms here in XDA.
The unlock bootloader part was ok (once I realised that windows 10 wasn't installing the drivers properly and I sorted that), the problems started when I installed twrp twrp-3.3.1-0-maple, when I restarted into recovery twrp I couldn't see any of my files and there was actually an error saying can't mount /data and when I tried to do select storage everything said 0 MB.
I did what is mentioned on this post: https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
After this when I rebooted my phone was stuck on the Xperia screen, from there I just have been tried to restore anything there, however I am not an advanced users I tried a few things:
1- Used XperiFirm embeeded in Flashtool to download the Europe CE1 image for my device G8142 dual and tried to flash it using Flashtool but it seems the phone doesn't do anything after getvar-max-download-size or something similar
2 - Tried to use newflasher to flash the same image, but it also fails in the same step
AFter this I realised I could push files to the phone using ADB, so I tried the following:
3 - Pushed the SuperSU to the phone and flashed it
4 - Pushed a few roms (LineageOS 17.1 for XZP, eXistenZ Pie v10.0.0 47.2.A.10.107 )
5 - I tried to flash eXistenZ Pie v10.0.0 47.2.A.10.107 but the phone entered in a restart loop that was going always to the TWRP recovery
6 - I tried to flash LineageOS 17.1 for XZP but aftert reboot the phone doesn't do nothing, I can't power one, not fastboot, no flashmode nothing, now it seems that I really bricked.
Any help will be much appreciated.
Thanks in advance.
Hello,
This can be closed, I was able to restore my phone, I noticed flashmode still worked, once I found a tutorial explaining how to prepare the firmware downloaded by XperiFirm so it could be used with newflasher I was able to flash the most current CE1 firmware and the phone is working. I wanted to leave it here for someone else's reference.
However it would be nice to have a single article explaining how to unlock the booloader, install twrp and root and use that to flash a custom rom. If anyone knows about such article can you please share?
I searched the forum but I can only find bits and pieces nothing really explaining it in a simple way that someone that doesn't know much about this can use.
fattheman said:
Hello,
This can be closed, I was able to restore my phone, I noticed flashmode still worked, once I found a tutorial explaining how to prepare the firmware downloaded by XperiFirm so it could be used with newflasher I was able to flash the most current CE1 firmware and the phone is working. I wanted to leave it here for someone else's reference.
However it would be nice to have a single article explaining how to unlock the booloader, install twrp and root and use that to flash a custom rom. If anyone knows about such article can you please share?
I searched the forum but I can only find bits and pieces nothing really explaining it in a simple way that someone that doesn't know much about this can use.
Click to expand...
Click to collapse
Try using the twrp linked below, its an older version (3.2.1) but works flawlessly. Install it in fastboot mode, using the same command as the other recovery (fastboot flash recovery TWRPA10.img).
Twrp: https://drive.google.com/file/d/109obOcD_FVMg7rLP5g5wlxgpM9OsxZOG/view?usp=drivesdk
Also find magisk 20.4 attached below