Hi there
I am struggeling with the root process of my XA Ultra F3211 (running 7.0 Nougat) and I just don't find a solution for my problem on the internet.
I hope y'all can help me with this one..
I read several guides how I can manage to root my phone, I think the basic points are the following:
- USB debugging has to be enabled - there's no problem with that one
- bootloader has to be unlocked (if possible) - it is possible for my phone and I did it
- USB drivers have to be installed - i installed the whole Android Studio including the SDK manager where I could choose to install the Google USB drivers
- you need the flashtool (I installed v. 0.9.23.1), a boot.img, a custom recovery.img and magisk or SuperSU
1. then you should flash only the boot_delivery.xml from the Marshmallow firmware in flash mode (I guess you need to do that because it's not possible to root Nougat without this step)
2. afterwards you should flash the boot.img and recovery.img in fastboot mode using a command line and the fastboot commands (fastboot flash boot boot.img / fastboot flash recovery recovery.img)
3. after you have done this the custom recovery should be installed and you should be able to boot into it to wipe the phone and flash magisk / SuperSU
That's the road so far.
I've tried these steps but I am not able to boot my Xperia into recovery mode. I think the problem is the boot_delivery.xml because when I tried to flash it from a 36.0.A.2.109 (Marshmallow) firmware (it's named customized_UK, I'm from Germany but I did not find a MM FW for Germany) the flashtool gave me the following information:
- Parsing boot delivery
- No flash script found.
- Flash script is mandatory. Closing session
- Ending flash session
- Flashing finished
I found those lines in some posts on the internet but I did not find any information. Someone said that he copied the default.fsc from the C:\Users\YourUser\.flashTool\devices\F31XX to the F32XX directory and renamed it into device and firmware versions. I did not find any default.fsc in this directory so I copied the one from the F33XX directory and named it "F3211_36.0.A.2.109.fsc" and guess what? I started flashtool and the fsc file was deleted. Even if I created it again while the flashtool was already running the tool never asked me if it should use a script - it just tries to flash and gives me the lines I listed above.
I'm not sure if this is the problem, but flash mode seems to work (the Xperia's LED is glowing green) - so does fastboot mode (blue LED) and for both: no unknown devices in Windows' devicemanager.
Maybe it did already work and I just can't manage to boot into recovery but I tried everything (vol down + powerbutton, vol up + powerbutton, powerbutton and repeatedly vol down or vol up when the screen turns on, hold all three buttons at once) - I think vol down + powerbutton should work, the phone vibrates and shows the Sony logo, I let off the buttons, the screen turns off again, then the Sony logo appears again and the phone starts normally into Android.
Does anyone have an idea what I can try to get my Xperia rooted?
Am I wrong in any point?
Looking forward to reading your answeres and thanks in advance
@dionarap, if the guide explains that you have to use Flashtool v0.9.23.2 why are you using v0.9.23.1 ?? Update it, download firmwares again from included Xperifirm, use FSC script when asked and all should be fine
rrvuhpg said:
@dionarap, if the guide explains that you have to use Flashtool v0.9.23.2 why are you using v0.9.23.1 ?? Update it, download firmwares again from included Xperifirm, use FSC script when asked and all should be fine
Click to expand...
Click to collapse
Thank you very much for your fast response
Well, you got me there. I forgot to exchange the x10flasher.jar in the flashtool directory.. *facepalm*
I'll try it when I'm at home again - but I have one more question before I'll do that.
When I start XperiFirm (through flashtool) and choose my device (F3211) the only entry for the Market "Germany" is build nr. 36.1.A.1.86 / R1B - according to another post that's also Nougat.
So which firmware do I need and could I choose a firmware for any Market if I only need to flash the boot_delivery.xml? Or can I use a downloaded ftf-file from another source? I found the 36.0.A.2.109 firmware (which seems to be MM 6.0.1) but it's named "...Customized_UK" and the at the download source the region was entitled "Russia" so I'm not really sure if I should use this ftf-file. I can find a firmware 36.0.A.2.109 / R6A for the Market "Costa Rica" in the XperiFirm - should I rather use this one?
Is it basically possible to tell which Android version a build nr. like 36.1.A.1.86 (Nougat) or 36.0.A.2.109 (MM) has or did I get something wrong?
Edit: I tried the "Costa Rica" firmware and it worked for me - rooting done
Thanks for the assistance!
dionarap said:
Thank you very much for your fast response
Well, you got me there. I forgot to exchange the x10flasher.jar in the flashtool directory.. *facepalm*
I'll try it when I'm at home again - but I have one more question before I'll do that.
When I start XperiFirm (through flashtool) and choose my device (F3211) the only entry for the Market "Germany" is build nr. 36.1.A.1.86 / R1B - according to another post that's also Nougat.
So which firmware do I need and could I choose a firmware for any Market if I only need to flash the boot_delivery.xml? Or can I use a downloaded ftf-file from another source? I found the 36.0.A.2.109 firmware (which seems to be MM 6.0.1) but it's named "...Customized_UK" and the at the download source the region was entitled "Russia" so I'm not really sure if I should use this ftf-file. I can find a firmware 36.0.A.2.109 / R6A for the Market "Costa Rica" in the XperiFirm - should I rather use this one?
Is it basically possible to tell which Android version a build nr. like 36.1.A.1.86 (Nougat) or 36.0.A.2.109 (MM) has or did I get something wrong?
Click to expand...
Click to collapse
You are on the right way
Yes you can know the Android version with the firmware build numbers.
For the MM firmware, you can download it with any customization/build it's not important we only need boot_delivery.xml
For the N firmware, you have to use the same as flashed in the device. You can download (and flash) it with an other customization too, the differences are small like LTE/4G icon, some apps are different like Spotify, Gameloft, AVG and the APN settings can be missing for your network provider (easy to add).
I don't recommend to download firmwares from the web because you will not have the FSC file who is very important to avoid hard brick. There is a way to manually add it but I will not explain how to do because I really dislike this way.
Thanks again! rooting is complete I think I just was too blind to notice this mistake after googling, reading and trying different things for several hours.. Again thanks for the assistance
@rrvuhpg Please Help buddy..
i've followed all your step but ending with white Sony logo
i can't enter recovery or else. where did i go wrong and what todo?
Please Help... Please
Edit: If I Re-Flash with different regional firmware, will it brick?
anybody please provide link for official N firmware..
Thanks in advance
Hi there
How far did you go? Did you already flash recovery and did you already enter it once? What was your last step before you got the sony screen? I'm not sure if reflashing can harm your phone but I think you should use a firmware downloaded via XperiFirm (it's integrated in Flash Tool). To get a Nougat firmware for Xperia XA Ultra look for build nr. 36.1.A.0.182.
Hope this helps - good luck mate!
Related
Title says it all...almost.
Was already rooted on 4.4.2.
I did a TA backup.
Then I followed the instructions located here to get custom XZDualRecovery .
All worked great!
Was able to boot into TWRP and Philz successfully.
Performed a full backup in TWRP onto a thumb drive over OTG cable.
Then wiped everything via TWRP in preparation for a CM11 rom.
Rebooted before trying to flash CM11.
Now can only boot to sony logo, fastboot, and "System Recovery" mode. (the mode that has 'continue power up' 'safe mode' 'factory reset' and 'power down'
I, like all the other noobs who didn't RTFM, missed the ''Be sure to flash XZ/ZL/TabZ/Z1/ZU-lockeddualrecovery[VERSION]-BETA.flashable.zip from http://nut.xperia-files.com after installing the ROM and before you reboot, this way you will not lose recovery!'' part of the XZDualrecovery post. =(
Now, my questions is, what if you DID forget to flash dual recovery after wiping?
What happens now?
I am thinking, is there a way to flash XZ/ZL/TabZ/Z1/ZU-lockeddualrecovery[VERSION]-BETA.flashable.zip via fastboot?
If so, how?
Thanks for your time and be gentle.
after 8 days with no help, I read 10 different threads on 10 different issues that KIND of pertained to my problem.
Wrote all Pertinent info down on a sheet of paper over the course of 4 days of searching.
And then started piecing together a solution.
Here's what I did to fix my issue for anyone who has the same problem.
1. Download xperifirm and select correct firmware for device
2. used Flashtool to convert above downloaded firmware to FTF
3 put tablet into flashmode
4. flash FTF file via flashtool
5. viola!
Thanks..I think.
eldiablo1 said:
after 8 days with no help, I read 10 different threads on 10 different issues that KIND of pertained to my problem.
Wrote all Pertinent info down on a sheet of paper over the course of 4 days of searching.
And then started piecing together a solution.
Here's what I did to fix my issue for anyone who has the same problem.
1. Download xperifirm and select correct firmware for device
2. used Flashtool to convert above downloaded firmware to FTF
3 put tablet into flashmode
4. flash FTF file via flashtool
5. viola!
Thanks..I think.
Click to expand...
Click to collapse
Had a similar situation, sorry I didn't see this earlier to help out. No need to convert firmware, you can use Flashtool to download your carriers latest FTF
blaze82 said:
Had a similar situation, sorry I didn't see this earlier to help out. No need to convert firmware, you can use Flashtool to download your carriers latest FTF
Click to expand...
Click to collapse
Thanks for the reply!
I do have a question about the ''you can use flashtol to download your carriers latest ftf" part.
are you referring to being able to download the firmware from the flashtool site here?
Or can you actually do it directly from the flashtool program?
My 2 problems are, 1. I do not see ANY firmware for my SGP561 (verizon) tablet on the website
and 2. I do not see any options for firmware download in the flashtool program
EDIT: Found it! Flashtool program > Devices > Check Updates
Is there a way to flash downgrade your firmware to a lower build number so you can officially unlock through Sony's dev site?
I have unlocked my tablet using Sony Developer tools. I then tried to downgrade with flashtools to a kitkat firmware . I tried 2 different firmwares for SGP 321 but both give me a boot loop.
I am using flashmode to flash , should I use fastboot mode?
any other firmware I should try or settings in the flashtool?
these are the ones I tried: SGP321_4.4.2 _10.5.A.0.233 3AT .ftf. SGP321_10.1.1.A.1.307_Customized_FR.ftf
All I want is a rooted tablet z with whatever firmware on it.
Appreciate your help
When you say boot loop, do you mean the screen goes black and starts to boot again?
Or do you mean the boot animation is repeating for a long time?
The first time you boot up after flashing an ftf will take a long time. It can range from a few minutes up to tens of minutes.
Did you select wipe USERDATA when you flashed the ftf in flash mode?
Try that if you haven't. See attached screenshot.
Checking it will wipe all your apps, data and internal storage.
I'd recommend you use the latest ROM, 10.7.A.0.228. Root and Xposed works on Lollipop 5.1.1.
Here is a Generic Germany FTF 10.7.A.0.228.
You'll need to root it by flashing supersu zip in recovery.
If you don't have a recovery flashed/installed, you should flash one.
Let me know if you need instructions on installing a recovery.
fantastic, that little trick did the job and I am now on 4.1 .
I am considering now to flash your firmware but could you give me some detailed instruction on what to do please, especially the recovery part.
thanks a lot again.
No problem.
Requirements
Program to open ZIP files
Flashtool (flashtool.net/downloads.php)
Flash mode and Fastboot drivers installed (Comes with Flashtool. Find the installer at C:\Flashtool\drivers\)
A few things you should know about recovery
If you plan on using an official Sony ROM with an unlocked bootloader, the recovery needs to be part of the kernel image.
Sony's official kernel images do not contain a recovery.
The kernel gets overwritten when you flash new ROMs (Official and Custom), so you will lose recovery every time you flash a ROM.
Thus you must reflash the kernel with recovery every time you change ROMS.
Kernel's for different versions of ROMs should not be used interchangeably.
It always best to use the kernel made for the ROM.
Flash official ROM before flashing recovery
If you are planning on using an official ROM, flash the official ROM in Download Mode before flashing the recovery (for the reason mentioned above - kernel gets overwritten).
You should wipe USERDATA to minimise compatibility issues.
Do this first before proceeding.
Downloading a kernel with recovery
Fellow xda member [NUT] has an awesome kernel builder tool which allows you to create kernel images with built in recoveries.
Head over to nut.xperia-files.com and navigate to XZDualRecovery > Kernel Builder
Check the checkbox "Yes, I have unlocked my bootloader!".
Select the Make and model of your device (Xperia Tablet Z SGP321 in your case).
Then select the firmware version you will be using (10.7.A.0.228 in your case).
Cross your fingers. If someone has already uploaded the kernel for that version, you can simply download the link provided. Otherwise you will need to upload the kernel. If you have an FTF, simply open it as a zip file and upload the kernel.sin inside.
Flashing Kernel with Recovery
Open the zip file downloaded from the Kernel Builder and open the tmp folder. Extract the boot.img file inside the tmp folder to somewhere on your computer.
Open Flashtool.
Click on the Flash Icon.
Select Fastboot mode.
Click "Select Kernel to Flash".
Put device into Fastboot mode. (2012+ devices: Press and hold VOL+ button while plugging in USB cable)
Once connected, a file selection dialogue will show. Select the boot.img file extracted earlier. You may need to select the type of file (sin, elf, img) before you can see the file in the explorer.
Flashing will start immediately after selection. Check the log and ensure there are no errors.
Unplug the USB cable.
You now have recovery (Two recoveries to be specific - as XZDualRecovery has PhilZ and TWRP).
I would recommend TWRP as it is easier to use and has more features than PhilZ (Based on CWM).
The VOL+ key is associated with PhilZ and the VOL- key for TWRP.
To enter recovery, simply turn the device on and when the notification LED turns Magenta (Pink) start pressing the button associated with the recovery you want to use.
e.g. Press VOL- a few times for TWRP.
Flashing zips
Copy your ZIPs to your SD card.
In TWRP, tap the Install button.
Select the zip file you want to flash
Swipe to the right to start flashing.
Rooting
Download the latest SuperSU zip (download.chainfire.eu/supersu)
Copy to SD card.
Flash zip in recovery.
Enjoy root.
about to start the process, just wanted to clarify some things:
what zip files are you talking about putting on my sd card? is this the file I downloaded from NUT?
thanks again for your help
Just in general, to flash a zip, you would perform those steps.
You would want to flash the SuperSU zip to get root.
You can also flash the file downloaded from NUT.
It will install a program called NDRUtils which will allow you to reboot into recovery from within Android.
I just saw when I wanted to flash the firmware from your link above (Here is a Generic Germany FTF 10.7.A.0.228.) that this identifies as for device C6603. But I have SPG321.
Do you have a link to a firmware which would work with your way and is for my device?
Oh, sorry about that. Forgot to check the model. I grabbed it from XperiaBlog.
I think I should just explain how to download and create an FTF for yourself from Sony's servers.
Install the latest Flashtool if you haven't already.
Start Flashtool
Click on the XF icon (The rightnost icon)
In XperiFirm, select the series and model of your device (Xperia Tablet Z > SGP321)
Then select the Market+Operator for your country/region. The market only differs by the apps that are pre-installed, which can be removed. Your region may not have the latest firmware available, so you can click the "Check All" button to get the versions of all the markets. You may wish to avoid commercial Operators as they can have different boot logos etc. Download a "VMo" or "Customized" operator if possible. The 228 firmware is only out in a few regions at the moment, so Germany VMo DE would be a good choice.
After selecting a row for the firmware you want, click on the latest version near the top right corner.
A window will show the details of the ROM. Click Download to start downloading. The downloads will get saved to FlashTool's Firmware Download folder.
Once the download completes, close XperiFirm.
In Flashtool, Click Tools > Bundles > Create.
Select the downloaded folder (Which should be in C:\Users\<Username>\.flashTool\firmwares\Downloads).
Double click in the device field to select the model of your device
Branding should be set to the Operator you downloaded (e.g. Generic DE)
Version should be set to the ROM version (e.g. 10.7.A.0.228)
Then in the folder list, select every item except for .ta files (e.g. cust-reset.ta, fota-reset.ta). Click the -> button to add to the Firmware Content.
Click create.
An FTF file will get created in the firmware folder. You can start flashing it in Download Mode.
If you need some screenshots. The procedure may differ slighty.
xperiablog.net/2015/03/17/guide-to-installing-xperia-lollipop-using-xperifirm-and-flashtool/
pls erase fwinfo.xml file from bundle pack of sgp321 firmware and again flash
Bilbo0a said:
I have unlocked my tablet using Sony Developer tools. I then tried to downgrade with flashtools to a kitkat firmware . I tried 2 different firmwares for SGP 321 but both give me a boot loop.
I am using flashmode to flash , should I use fastboot mode?
any other firmware I should try or settings in the flashtool?
these are the ones I tried: SGP321_4.4.2 _10.5.A.0.233 3AT .ftf. SGP321_10.1.1.A.1.307_Customized_FR.ftf
All I want is a rooted tablet z with whatever firmware on it.
Appreciate your help
Click to expand...
Click to collapse
pls erase fwinfo.xml file from bundle pack of sgp321 firmware and again flash from flash tool
Hello guys!
I am very new to this sony stuff and I decided to root my phone. I have the e2353 model and I planned to use flash tool to flash the .112 firmware I got from xperia blog. But, flash tool detects the downloaded tft as a tft for the xperia M2 2303 model. Should I go ahead and flash this one? One more thing, When I attempt to flash it, flash tool complains that it has finished processing "loader.sin" with errors then says I should install the correct flashtool drivers for my device. I believe that one can be fixed by just simply installing the drivers included in flashtool's "drivers" folder, yes?
Thank you!
-TAM
The Android Manual said:
Hello guys!
I am very new to this sony stuff and I decided to root my phone. I have the e2353 model and I planned to use flash tool to flash the .112 firmware I got from xperia blog. But, flash tool detects the downloaded tft as a tft for the xperia M2 2303 model. Should I go ahead and flash this one? One more thing, When I attempt to flash it, flash tool complains that it has finished processing "loader.sin" with errors then says I should install the correct flashtool drivers for my device. I believe that one can be fixed by just simply installing the drivers included in flashtool's "drivers" folder, yes?
Thank you!
-TAM
Click to expand...
Click to collapse
Try searching Xperifirms for the files. Better be safe - flashing a wrong tft files means a bricked device... Also :
"Instructions
I found this guide very helpful and thus you can refer it here :
http://forum.xda-developers.com/showthread.php?t=928343
SOME CONSIDERATIONS :
1.Make sure you choose the FTF file for your device or you can risk bricking your phone forever.
At the moment, there are no FTF files so you will need to be patient.
2. Make sure all drivers are properly installed
3. To boot into flashmode/fastboot, you will need to turn off device.Hold volume up OR volume down and then connect your device while holding the volume key.
Volume up would take you to flashmode while volume down would take you to fastboot mode. Remember, you will need fastboot/flashtool drivers before you can flash anything.
here is another guide for you just as reference.
http://forum.xda-developers.com/xper...cking-t2337955 "
-From the post by hnk1 in the General thread.
Goodluck!
AndyPhoenix9879 said:
Try searching Xperifirms for the files. Better be safe - flashing a wrong tft files means a bricked device... Also :
"Instructions
I found this guide very helpful and thus you can refer it here :
http://forum.xda-developers.com/showthread.php?t=928343
SOME CONSIDERATIONS :
1.Make sure you choose the FTF file for your device or you can risk bricking your phone forever.
At the moment, there are no FTF files so you will need to be patient.
2. Make sure all drivers are properly installed
3. To boot into flashmode/fastboot, you will need to turn off device.Hold volume up OR volume down and then connect your device while holding the volume key.
Volume up would take you to flashmode while volume down would take you to fastboot mode. Remember, you will need fastboot/flashtool drivers before you can flash anything.
here is another guide for you just as reference.
http://forum.xda-developers.com/xper...cking-t2337955 "
-From the post by hnk1 in the General thread.
Goodluck!
Click to expand...
Click to collapse
Alright then. I'll download the firmware from xperia firm instead maybe that'll give me the correct one.
Do I set it to "unpack automatically" or no?
Hi guys,
Just unlocked my bootloader and began the root process.
I followed part of this guide but without backing up my DRM keys. http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
I flashed my kernel and the recovery O.K.
fastboot flash recovery recovery.img
flashboot flash boot boot.img
I've tried two versions of TWRP and two different versions of the kernel AndroPlus.
When performing fastboot reboot after flashing both files my phones LED blinks RED once and then does nothing.
Dramatic and scary. What can I do to fix this? When trying to boot without the cable in my phone just vibrates once and does nothing. Screen doesn't light up at all. I'm so worried.
MatMew said:
Hi guys,
Just unlocked my bootloader and began the root process.
I followed part of this guide but without backing up my DRM keys. http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
I flashed my kernel and the recovery O.K.
fastboot flash recovery recovery.img
flashboot flash boot boot.img
I've tried two versions of TWRP and two different versions of the kernel AndroPlus.
When performing fastboot reboot after flashing both files my phones LED blinks RED once and then does nothing.
Dramatic and scary. What can I do to fix this? When trying to boot without the cable in my phone just vibrates once and does nothing. Screen doesn't light up at all. I'm so worried.
Click to expand...
Click to collapse
did you try to flash first the boot.img and after the recovery ?
acabreram said:
did you try to flash first the boot.img and after the recovery ?
Click to expand...
Click to collapse
I've tried another kernel and it's booting but hanging at the three dots. (bootscreen) been waiting a few minutes. hopefully it gets to system.
MatMew said:
I've tried another kernel and it's booting but hanging at the three dots. (bootscreen) been waiting a few minutes. hopefully it gets to system.
Click to expand...
Click to collapse
Ok yo can try this too
Y tried and working fine root & xposed
It's tus stock kernel but with the habilita to support root
Similar issue for me
I've had almost exactly the same issue today:
- I unlocked boatloader using Sony standard process
- I followed the steps under 'How to Install CM13' within CTXz's guide here
- After flashing the Kernel and THEN the TWRP, I reboot and the phone flashes red LED, then green, then off, then red and then stays on green for a while (screen is blank). My computer registers that there is a new connection by making a sound but doesn't show up any devices that I can see.
- Periodically, I get the device disconnection sound and the green LED goes off, then red comes on, then solid green again until next cycle.
- If I disconnect the cable, the LED goes off. When I try to turn the phone on without cable attached, it buzzes but does nothing - no LEDs. I can't tell whether it is on or not, except that doing hard reset with PWR+Vol.Up gives no reaction.
- When I re-attach cable normally, the red/green LED sequence starts immediately with no need to turn PWR on, which would suggest that the phone is perhaps on.
- I am able to get into bootloader as normal and fastboot registers the device just fine.
- There is no yellow LED
I started with Kernel AndroPlus v24 and TWRP 3.0.0.0.
Failing that, I tried Kernel v20. Then I tried AndroPlus' twrp-2.8.7.0-E5823-32.0.A.6.152.
Have also tried Kernels v20 and v21 with TWRP 3.0.0.0.
I haven't had any fast boot errors - all flashes come back 'OKAY'.
I'd be very grateful for any help? Have I missed something?!
update to my post above:
I used: 'fastboot boot recovery.img' and this fired up the Sony logo with white screen and blue LED. However, after 10 mins of waiting, there was no change in status and I still couldn't get into TWRP with pressing Vol buttons, even after several restarts and unplugging, replugging etc.
Then, I realised the stock ROM on my phone before this whole process was Lollipop 5.1.1 Build 32.0.A.6.200. So, I flashed older versions of the Kernel and TWRP. Now, I can boot into the ROM and use the phone (almost) as normal except, being plugged in, it keeps re-detecting the USB cable. I now also get the Sony boot screen followed by yellow LED.
If I don't touch anything, it boots into the ROM. However, if I press a Vol button while the yellow LED is on during boot, then it just resets.
Thus, I still cannot get into the TWRP interface. Perhaps I need a TWRP version that is specific to my build - the one I have is from AndroPlus website and refers to the previous build (twrp-2.8.7.0-E5823-32.0.A.6.152.img)?
okay, further update (to save someone replying!)
I managed to boot into the system using AndroPlus Kernel v05a (I had Lollipop build ###.200), but still couldn't get into any TWRP.
I then followed the general process explained in this thread, albeit had to do a heck of a lot of research to understand the detail that is omitted from that (otherwise very useful and concise) original post. For example:
- how to actually use Flashtool (installing drivers and then getting hold of the right firmware from within the program);
- the difference between Fastboot and Flashmode;
- having to plug in the phone while it is loaded into the system before then flashing the selected firmware with Flashtool and ONLY THEN unplugging, switching off and booting into Flashmode.
- loading up the system after flashing the Kernel and TWRP so that I connect to computer and re-copy the erased SuperSU .zip file back onto storage, and then re-booting into TWRP and how to flash a zip file with TWRP.
Having now got a stock Marshmallow firmware rooted, my next step is to go back to the original guide I was following and try to install Cyanogen!
Thank you to all the people who have posted help guides throughout this site so that I could piece together what I needed to do - even though it has still taken me about 30 hours of my life to learn all this!
Hopefully my experience might help someone else in due course...
robledog said:
okay, further update (to save someone replying!)
I managed to boot into the system using AndroPlus Kernel v05a (I had Lollipop build ###.200), but still couldn't get into any TWRP.
I then followed the general process explained in this thread, albeit had to do a heck of a lot of research to understand the detail that is omitted from that (otherwise very useful and concise) original post. For example:
- how to actually use Flashtool (installing drivers and then getting hold of the right firmware from within the program);
- the difference between Fastboot and Flashmode;
- having to plug in the phone while it is loaded into the system before then flashing the selected firmware with Flashtool and ONLY THEN unplugging, switching off and booting into Flashmode.
- loading up the system after flashing the Kernel and TWRP so that I connect to computer and re-copy the erased SuperSU .zip file back onto storage, and then re-booting into TWRP and how to flash a zip file with TWRP.
Having now got a stock Marshmallow firmware rooted, my next step is to go back to the original guide I was following and try to install Cyanogen!
Thank you to all the people who have posted help guides throughout this site so that I could piece together what I needed to do - even though it has still taken me about 30 hours of my life to learn all this!
Hopefully my experience might help someone else in due course...
Click to expand...
Click to collapse
I had the same problem and solution is as is written here.
I had to flash Stock Firmware Marshmallow via Flashtool. After this I flashed kernel(boot) and recovery without problems and yellow icon will displayed.
Don't want to warm up this kind of old thread, but I have exactly the same issue (E8523). Would any of you mind to post their (stock) ROM versions which finally worked? I tried almost every combination that came to my mind (Customized CE1 32.2.A.0.224 => v31, several LP versions => more or less 20 to 32...).
Currently after installing the MM I mentioned the stock kernel worked, but when I flash the AndroPlus kernel (fastboot flash boot /path/to/boot.img) it won't boot up, black screen, looks like no dtb found (doesn't even try to load). This is also the message I get when I try to boot this img via fastboot directly.
I am sure I am missing something really stupid (quite new to android devices), but what?
IGNNE said:
Don't want to warm up this kind of old thread, but I have exactly the same issue (E8523). Would any of you mind to post their (stock) ROM versions which finally worked? I tried almost every combination that came to my mind (Customized CE1 32.2.A.0.224 => v31, several LP versions => more or less 20 to 32...).
Currently after installing the MM I mentioned the stock kernel worked, but when I flash the AndroPlus kernel (fastboot flash boot /path/to/boot.img) it won't boot up, black screen, looks like no dtb found (doesn't even try to load). This is also the message I get when I try to boot this img via fastboot directly.
I am sure I am missing something really stupid (quite new to android devices), but what?
Click to expand...
Click to collapse
Pro tip: hold shift and right click inside folder with recover.IMG or voot.IMG to open command prompt from that folder. Then all you have to do is type fastboot flash boot boot.IMG. I suggest trying to put a custom recovery like twrp on and flashing the xpower ROM from that, it will give you everything in one package.
Edit: fwiw I'm pretty sure custom recoveries have been able to flash .IMG fils for a few years now but I've never actually tried it. Might be worth a shot.
Thanks, but I haven't found cmd.exe on my linux machine yet^^ (I suppose wineconsole is cheating )
I know how to flash *stuff* to my phone, but that *stuff* seems only to work if some specific version of stock rom was installed previously. My best guess is the bootloader changes and supports different dtb formats on every version.
Stock Marshmallow 6.0.1 Customized CE1 32.2.A.0.224 does _not_ work for installing any version of AndroPlus kernel (tried a few...). It fails at boot (does not even load system, probably dtb).
Just in case someone might run into similar issues: What finally worked was Stock MM 6.0.1 Customized DE 32.2.A.0.224 with AndroPlus v31. It seems to be some older release (?), it says R2C instead of R9C for Customized CE1.
I could not find this information anywhere on the net (maybe its me), so for those with a slow internet connection the above version should work. You don't have to actually boot it, flashing is enough.
Thanks for sharing the information in this tread, it really helped me to unbrick my phone!
I started with Lollipop on my brand new Z3C and tried to root using AndroPlusKernel v31 / TWRP 3.0. This resulted in a softbick state, only being able to boot in fastboot mode.
After many hours struggling, an upgrade to stock Marshmallow (E5823_32.2.A.0.224) did the trick. This somehow seems ta make the device ready for the new kernel and recovery (I guess it has to do with the partitions in the filesystem).
Anyway, from stock Marshmallow I could start all over and succeeded to flash a custom bootloader, recovery and now have the ability to flash any desired rom! Thanks again.
To updrade to stock MM I used the instructions in this thread:
[GUIDE][18th Dec][4Noobs] Flashing A FTF File Using Flashtool
To set up TWRP recovery I used the instructions in this thread:
[ROM][UNOFFICIAL][6.0.1][E5823/E5803] CyanogenMod 13 for the Sony Xperia Z5C [ALPHA]
The stock rom I used for my E5823 is "E5823_32.2.A.0.224_R1C_CIS Generic_1298-5167.ftf" from xperiablog.net
Since I'm a new registered member I can't post external links
Google it and you're set!
IGNNE said:
Just in case someone might run into similar issues: What finally worked was Stock MM 6.0.1 Customized DE 32.2.A.0.224 with AndroPlus v31. It seems to be some older release (?), it says R2C instead of R9C for Customized CE1.
I could not find this information anywhere on the net (maybe its me), so for those with a slow internet connection the above version should work. You don't have to actually boot it, flashing is enough.
Click to expand...
Click to collapse
I'm having the same problem, where did you get that MM stock version from?
And what do you mean by "you don't have to actually boot it"?
Search for XperiaFirm and Flashtool. There is plenty.
You don't have to start your freshly installed Stock Rom version "...". You just have to flash it (write it to your phone) Now you boot your phone in fastboot mode and flash your custom kernel and mod rom of your choice. Seems to be some incompatible whatever between not matching kernel versions and the "stuff" flashing installs (suspect sth like bootloader, but no idea).
I have flased boot.img nd recovery.img on android 7.1.1 z5 compact my phone won't pass the sony logo
any help ?
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
starchild78 said:
I have flased boot.img nd recovery.img on android 7.1.1 z5 compact my phone won't pass the sony logo
any help ?
Click to expand...
Click to collapse
I've just discovered I can boot into twrp
anything I can do to fix this from there ?
[oreo]XZ1-drmfix-root-ricoff
Available for any version of the official 8.0 oreo
First you have twrp https://forum.xda-developers.com/xperia-xz1/development/twrp-t3716488
Be sure to use the zip I provided,Make sure your rom is clean.If you want wipe data,cache and dalvik, please execute it first.
1，flash drmpatch.zip
2，flash SuperSU.zip
3，flash RicOff.zip
4，reboot
Perfect, please enjoy.
download
https://mega.nz/#F!s8QlGD7S!cSlNJcZArwwdvZGGE5sVdA
drmfix.so/drm****.so thank @sToRm// :good:
The secd of 47.1.A.12.34 is the same as 47.1.A.8.49.
secd original file（G8441_47.1.A.8.49_CE） https://mega.nz/#!IpYg1Q4Q!ONXXqHoP6JkrFQ9jGUHMMXlzHcPAfog3ISrMgogO8go
modify
E803003206000014E8031F3204000014E807003202000014E8031E32
for
08008052060000140800805204000014080080520200001408008052
drmpatch.zip
Install XperiFIX
In C:\XperiFIX\DATA\XZP\G8142\Oreo2
Modify the update binary
ui_print "******************************"
ui_print "Sony XZ Premium *OREO* DRM restore by //sToRm"
ui_print "******************************"
change
ui_print "******************************"
ui_print "Sony XZ1/XZ1C *OREO* DRM restore by //sToRm"
ui_print "******************************"
/ system
change
/vendor
And replace secd
Click to expand...
Click to collapse
SuperSU.zip
Modify init.supersu.rc.24 and init.supersu.rc.24.bindsbin
on post-fs
exec u:r:supersu:s0 root root -- /sbin/fbe_bypass.sh
export LD_PRELOAD drmfix.so:drm****.so
#RIC disable
mount securityfs securityfs /sys/kernel/security nosuid nodev noexec
write /sys/kernel/security/sony_ric/enable 0
Click to expand...
Click to collapse
RicOff.zip
The status of SELinux changes to permissive
Click to expand...
Click to collapse
The original machao44 account is lost
I do not know how to misunderstand me
前來支持個~~
謝馬大
How do I get root and Kernel to xperia xz1 g8342 ?
How do I get root and Kernel to xperia xz1 g8342 ?
sofyanpall said:
How do I get root and Kernel to xperia xz1 g8342 ?
Click to expand...
Click to collapse
Unlocked bootloader and as it says here gives you root on stock kernel.
Use [RECOVERY] TWRP 3.2.1 twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img from just that post if you´re at FW 47.1.A.8.49 due to EXT4 File Based Encryption (FBE)
If you´re on older FW use twrp-3.2.1-0-poplar-patchlevel-2017-11-05.img
or simply upgrade to 47.1.A.8.49 before proceeding
thank you for your reply Senior Member
pergoteborg said:
Unlocked bootloader and as it says here gives you root on stock kernel.
Use [RECOVERY] TWRP 3.2.1 twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img from just that post if you´re at FW 47.1.A.8.49 due to EXT4 File Based Encryption (FBE)
If you´re on older FW use twrp-3.2.1-0-poplar-patchlevel-2017-11-05.img
or simply upgrade to 47.1.A.8.49 before proceeding
Click to expand...
Click to collapse
I opened bootloader , my phone 47.1.A.2.374 I tried to flash 47.1.A.8.49 flashtool does not work in xperia g8342
At the start of the show the message glows ( your device hes been unlocked and can"t be trusted - your device will boot in 5 Seconds ) Currently I can not access developer options and the camera picks up green images
What should I do؟
all Respect and appreciation for you Senior Member
sofyanpall said:
I opened bootloader , my phone 47.1.A.2.374 I tried to flash 47.1.A.8.49 flashtool does not work in xperia g8342
At the start of the show the message glows ( your device hes been unlocked and can"t be trusted - your device will boot in 5 Seconds ) Currently I can not access developer options and the camera picks up green images
What should I do؟
all Respect and appreciation for you Senior Member
Click to expand...
Click to collapse
.
Green pictures are because you unlocked bootloader. Will be fixed by DRMFix.
your device hes been unlocked and can"t be trusted-message will allways be there on unlocked BL
Download G8342_MY_47.1.A.8.49 .rar according to this post, it contains latest ROM and newflasher
You need to install drivers for flashtool. It may be a little tricky and it was soooo long ago I set it up myself I simply do not remember. Google it. Maybe This or http://www.**********.com/setup-androxyde-flashtool-sony-xperia-devices-windows/may help.
With drivers installed:
Turn off phone. Hold Vol down while connecting USB to computer (Green light on phone). Open commandprompt on computer and cd to unpacked G8342_MY_47.1.A.8.49 .rar directory. Run
Code:
newflasher.exe
.
This installs lastest stock kernel and firmware.
When finished reboot phone
Download DRMPatck package , unpack it and move the three zip files to phone
Turn off phone
Download twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img and move the file to the same directory on computer where flashtool is installed
Commect the phone to computer USB while holding Vol UP (Blue light on phone)
Open commandprompt on computer and cd to flashtool directory (where also twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img exists)
Run command
Code:
fastboot flash recovery twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img
Disconnect phone.
Hold Vol Down while starting the phone which brings you to TWRP.
Flash DRMFix according to OP.
DONE
Next maybe custom rom?
Wysłane z mojego G8342 przy użyciu Tapatalka
Hopefully
Any chance to backup TA Partition?
root xperia xz1 g8342
pergoteborg said:
.
Green pictures are because you unlocked bootloader. Will be fixed by DRMFix.
your device hes been unlocked and can"t be trusted-message will allways be there on unlocked BL
Download G8342_MY_47.1.A.8.49 .rar according to this post, it contains latest ROM and newflasher
You need to install drivers for flashtool. It may be a little tricky and it was soooo long ago I set it up myself I simply do not remember. Google it. Maybe This or http://www.**********.com/setup-androxyde-flashtool-sony-xperia-devices-windows/may help.
With drivers installed:
Turn off phone. Hold Vol down while connecting USB to computer (Green light on phone). Open commandprompt on computer and cd to unpacked G8342_MY_47.1.A.8.49 .rar directory. Run
Code:
newflasher.exe
.
This installs lastest stock kernel and firmware.
When finished reboot phone
Download DRMPatck package , unpack it and move the three zip files to phone
Turn off phone
Download twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img and move the file to the same directory on computer where flashtool is installed
Commect the phone to computer USB while holding Vol UP (Blue light on phone)
Open commandprompt on computer and cd to flashtool directory (where also twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img exists)
Run command
Code:
fastboot flash recovery twrp-3.2.1-0-poplar-1-patchlevel-2017-12-01.img
Disconnect phone.
Hold Vol Down while starting the phone which brings you to TWRP.
Flash DRMFix according to OP.
DONE
Click to expand...
Click to collapse
Thank you so much pergoteborg
I followed the instructions and my phone works well and the camera works without problems
Before the operation you have repaired the phone system on a program ( emma )
:good::good::good:
The only remaining problem is developer options and not a necessity
sofyanpall said:
Thank you so much pergoteborg
I followed the instructions and my phone works well and the camera works without problems
Before the operation you have repaired the phone system on a program ( emma )
:good::good::good:
The only remaining problem is developer options and not a necessity
Click to expand...
Click to collapse
Go into settings -> system -> about phone and click repeatibly on version at the bottom to open up developer options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Send from my Xperia XZ1 Dual (G8342) using Tapatalk
root xperia xz1 g8342 47.1A.2.374
pergoteborg said:
Go into settings -> system -> about phone and click repeatibly on version at the bottom to open up developer options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Send from my Xperia XZ1 Dual (G8342) using Tapatalk
Click to expand...
Click to collapse
I changed the phone language from Arabic to English and the developer options worked well
I can confirm that the method of M-Rom works perfectly fine for my G8341 Xperia XZ1 with Android 8.0.0.
Additionally I wanted to add: For those who did not already solve the Google USB driver phenomenon for fastboot to detect Sony devices: See here: https://forum.xda-developers.com/xperia-u/issues/guide-how-to-install-fastboot-xperia-t2170114. This is the guide I followed to do it. You can get the file needed for that guide here, as the link provided there is no longer active: https://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Thanks a bunch M-Rom and sToRm// for saving my phones life (and mine, too :good: )
Hello guys, can someone explain me how to install TWRP?
unlock bootloader from developed options?
after flashing twrp via fastboot? like fastboot flash recovery (recovery name.img)??
and what the features of drmfix ricoff?
does google camera HDR+ works?
Thanks!
georgesalo said:
Hello guys, can someone explain me how to install TWRP?
unlock bootloader from developed options?
after flashing twrp via fastboot? like fastboot flash recovery (recovery name.img)??
and what the features of drmfix ricoff?
does google camera HDR+ works?
Thanks!
Click to expand...
Click to collapse
Yes, you're exactly right. Boot into the unlocked bootloader:
Adb reboot bootloader
(Next command)
Fastboot flash recovery name/and/location/of/recovery/image.img
Not sure if hdr+ works as I believe it uses api2 (I could be way wrong on that name) but I believe it uses something that this device doesn't support but I could be wrong.
DRM ricoff reactivates the Sony features and the Sony camera to full functionality. Basically once you've flashed TWRP then you can flash the root and DRM fix and you have root and fully working camera and features even though you've lost the DRM keys. The only difference between this method and the method created by Storm for the XZP is that on the XZP you can backup the TA partition whereas we haven't figured out how to do that yet but the result is still exactly the same.
Hey, can i flash Magisk instead of SuperSU, or does the DRM Fix need SuperSU to work?
Unfortunately the DRM fix needs SuperSU to work, the package comes with a special version of SuperSU to make it work. Hopefully if @aledoom gets some time he can try build a new version of the Andro+ kernel for our phone running the latest 8.49 firmware that will support Magisk and the DRM fix. He doesn't own an xz1 himself so testing isn't easy butt I'm sure one of us will be happy to help with that. I know I will for sure.
If he gets a working kernel built then we can have the DRM fix with Magisk instead of SuperSU, which I think we all would love.
The problem is that Magisk doesn't work on the stock kennel. In fact it causes a bootloop so don't try flashing it.
M-Rom said:
[oreo]XZ1-drmfix-root-ricoff
Available for any version of the official 8.0 oreo
First you have twrp https://forum.xda-developers.com/xperia-xz1/development/twrp-t3716488
Be sure to use the zip I provided,Make sure your rom is clean.If you want wipe data,cache and dalvik, please execute it first.
1，flash drmpatch.zip
2，flash SuperSU.zip
3，flash RicOff.zip
4，reboot
Perfect, please enjoy.
download
https://mega.nz/#F!s8QlGD7S!cSlNJcZArwwdvZGGE5sVdA
drmfix.so/drm****.so thank @sToRm// :good:
Click to expand...
Click to collapse
Is this DRM-fix/patch working on the latest XZ1 firmware?
xFirefly93 said:
Is this DRM-fix/patch working on the latest XZ1 firmware?
Click to expand...
Click to collapse
Yes, it is working. Tested it with my G8341 XZ1 with latest firmware on 8.0.0.
Camera works again and you can set the X-Reality display saturation again.
CoinsClassic said:
I can confirm that the method of M-Rom works perfectly fine for my G8341 Xperia XZ1 with Android 8.0.0.
Additionally I wanted to add: For those who did not already solve the Google USB driver phenomenon for fastboot to detect Sony devices: See here: https://forum.xda-developers.com/xperia-u/issues/guide-how-to-install-fastboot-xperia-t2170114. This is the guide I followed to do it. You can get the file needed for that guide here, as the link provided there is no longer active: https://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Thanks a bunch M-Rom and sToRm// for saving my phones life (and mine, too :good: )
Click to expand...
Click to collapse
If you're having trouble installing the fastboot / flashmode drivers from Sony because of driver signing issues, the answer should never be to disable driver signing altogether.
Instead you should look at the answer here and use the open-source tool it describes to install the driver with a self-signed certificate.
Of course, Sony should be doing a better job and releasing signed drivers so we wouldn't be in this situation to begin with.