Related
Installing the new Sony Bootloader and Recovery
THIS IS FOR ALREADY UNLOCKED DEVICES!
DO NOT TRY THIS ON A GPE!Since a lot of people seem to have problems keeping their recovery when flashing Lollipop-ROMs i decided to put up this little guide...
You can also Skip this whole guide, by just flashing the newest stock-FW at least once!
First off, as already said, this is for already unlocked devices. You can use this Guide until "Install Custom ROM", except the rooting part, for rooting use this, if you haven't already!
Don't do it if you don't atleast somewhat know what you are doing.
I am not responsible for bricked devices, or whatever you might end up with.
So, lets get started.
1. Download Sonys FlashTool "EMMA" and install it: http://developer.sonymobile.com/downloads/tool/flash-tool-for-xperia-devices/
In the .zip file from the FlashTool you'll find a File "customization.ini"
Copy this file to the installation directory of EMMA, usually "C:\Program Files (x86)\Sony Mobile\Emma"
If you don't copy that file, Emma will ask you for a login, don't create an account there, you will NEVER get any activation-email!
2. Open EMMA and boot your Phone into FlashMode (Power off your device -> Press and hold volume DOWN -> while pressing volume DOWN insert USB-Cable)
3. Emma should now recognize your device, but you have to select it manually tough. Select your EXACT model number. Again, I am not responsible for any bricked devices or whatever you end up with!
Now select the "(Open Devices) TA update" and click "Apply Service"
It should take a few seconds and should then display SUCCESS.
You can now close Emma
4. If you haven't already download FastBoot and Drivers: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
(Run as Administrator!)
5. Download the newest version of twrp and put it somewhere:
New Inoffcial twrp-3.0.0 build by me: http://forum.xda-developers.com/xperia-z-ultra/development/togari-twrp-recovery-3-0-0-t3314440
Old official versions: https://twrp.me/devices/sonyxperiazultra.html
6. Finally boot up you Phone in FastBoot-mode (Power off -> press and hold volume UP -> while pressing wolume UP insert USB-Cable
Your LED should now light up blue
Shift+Rightklick in the Folder where you have put TWRP recovery, and select "Open Commandprompt here"
Now write "fastboot flash recovery FILENAME_OF_TWRP_FILE"
You can now unplug your USB-Cable and boot into recovery and continue from there.
Your recovery will be permanent, meaning you won't loose it or replace with any other recovery that might come with your ROM.
I hope this was somewhat helpfull
Any one can flash this to C6806?
jacklau2000 said:
Any one can flash this to C6806?
Click to expand...
Click to collapse
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
alia5 said:
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
Click to expand...
Click to collapse
tried, but no luck. thanks.
It's really weird, I used emma, and installed their latest ta update. Now I can get into fastboot mode, all commands execute successfully, but the recovery never takes. The vol down + Power doesn't work, nor does 'adb reboot recovery'. Am I missing a step somewhere? This isn't my first android device, but from where I sit, it seems like something is up with my xzu.
If I try and install the 14.4* update through emma, it goes through the whole process, completes "successfully", then boots into 14.5. Something is clearly not working here.
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
teddy74eva said:
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
Click to expand...
Click to collapse
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Hermann1222 said:
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Click to expand...
Click to collapse
I will try to compile one because, you know, summer holidays and no school however I don't know if I will make it.
Regards
Is there any (wish for TWRP) recovery for togari, which use the new bootoader?
FYI:
My device is a brazilian c6843.
Emma recognizes the device automatically and indicates with an exclamation point that there is no services available to the unit.
In the case someone doesn't know, it's basically the c6833 with DTV 1seg. It's totally compatible with c6833 firmware, losing TV, of course.
You sir are the real hero! Thank you!
I have a xzu running cm12.1, and I have 2 quick questions for those with more knowledge than me
Is it possible to flash the new bootloder using the open source FlashTool?
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
pbgapski said:
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
Click to expand...
Click to collapse
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
missing clues on new recovery partition
alia5 said:
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
Click to expand...
Click to collapse
I followed your advice, but it seems I am missing a few clues.
My sirius was on cm12.1. I backedup and flashed D6543_23.4.A.1.232_1281-5466_R6C.ftf with flashtool on linux. I tried to use emma (several times) afterwards to check for any TA updates, but all I got was "no services matched this device" or something like that. Google tells me I am not the only one with this issue with emma
Then I used fastboot to install twrp 3 from twrp.me to recovery partition, but I could not access twrp.
I fastbooted recovery again with twrp 2.8.7, and this time I could enter twrp and reflashed CM.
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
pbgapski said:
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
Click to expand...
Click to collapse
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
why it said my phone have no available service, i am on c6833
alia5 said:
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
Click to expand...
Click to collapse
I have the same problem but not bootloop just stuck at starting apps screen,BTW did you have a TWRP scripts for flashing TWRP 3.0 into FOTAkernel
hi .. after this update can i relock my phone and restore drm functions?! or phone go to unlocked forever?!
pls help i need answer
erfanzz said:
pls help i need answer
Click to expand...
Click to collapse
Search the forums on how to backup TA partitions. I have mine but never tried to restore them
Root the M4 Aqua E2303 Locked Bootloader/Install TWRP on 2.167/3.92
Before we begin:
Make sure you have the following:
•A Windows PC
•Flashtool (https://drive.google.com/file/d/0B_d8uWGbkaetTnhWX0J5UG5hN28/view?pref=2&pli=1)
•The .128 firmware (https://drive.google.com/file/d/0BzVQf67OZ9NtMFotOXRycTZoSlk/view?pli=1)
•Patience
•A good internet connection
•15 to 20 minutes
• The M4 Aqua Root Toolkit (https://www.dropbox.com/s/edse0h6b02odzn1/rootkitXperia_E23xx.zip?dl=0)
•ADB Drivers (https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view?pref=2&pli=1)
•TWRP Toolkit (https://www.dropbox.com/s/yomdwq3p2le9hvi/M4Aqua-lockedTWRP-0.1-installer.zip?dl=0)
How are we going to do it:
The procedure is pretty straight forward, as the M4 Aqua is only on Android™ 5.0 we can take the kernel of the older versions of firmwares so we could root the device, while keeping the firmware version to the newest release (2.167/3.92). The method has been only tried on the E2303, there may be chances of it working for the E2306.
Let's begin! Part 1, Changing the Kernel:
First, we need to install the latest Flashtool version (link above), after you proceed with the installation of Flashtool, you need to install the Flashtool drivers, which can be found in C:/Flashtool/drivers or the path you selected flashtool to be installed. Once you open Flashtool drivers you want to select FLASHMODE DRIVERS, this is only so that the M4 will be recognised while in flashmode. After the drivers have been installed, you want to move the downloaded .128 firmware to C:/Users/*YourName*/.flashtool/firmwares or you can use the other method I will show later. Once you have done that you want to open Flashtool and wait for the Sync to finish. After that has finished, you will see a lighting icon in the top-left corner, you want to press the icon and select flashmode, now the second method, at the top you will see a path leading to the generic .tft folder in which Flashtool belives the .ftf files are located by default. You can change that by pressing the button on the right and lead the program to the path of the .128 ftf file. After you have selected your .tft file you will see on the right a lot of options *everything that the .ftf file contains*, if you want to keep the data on your device you can tick the first two options, a bit down on the right you will see a lot of options, including system.bin, you want to tick everything EXCEPT for the kernel.sin, this is the most crucial part. After that is done you want to let the program prepare the files, mean while you want to power off your M4 Aqua, after the process on Flashtool is done you want to press the VOLUME DOWN button while connecting the phone to the PC, once you see the green led light you can leave the button, if everything was done right the process of flashing should begin. If everything went well the kernel should be flashed and the phone should safely power on. Now we can proceed to the second part. Rooting the phone.
2ND METHOD
You can downgrade to .128 firmware and download the .167 or .92 firmware and update everything except for the kernel. You can do this by going into Flashtool, and doing the steps above but TICKING the kernel.sin. Try this if the first method doesn't work.
Part 2, Rooting the phone:
Now that we have changed the kernel we can use the root toolkit to root the device. Download the root toolkit from the link above, but before you do anything you want to go to Settings>About Phone, scroll down to Build number and press it 7 times, after that is done you want to go back to Developer options, and you want to tick USB Debugging, after you have done that you need to install the ADB Drivers from the link above, after that is done you can connect the phone to the computer, now you want to extract the toolkit and run install.bat *No administrator rights needed*, and then you should see a screen on your phone asking if you want to trust the computer, you want to tick the box saying always and you want to press yes, now the rooting process should begin and your phone to be rooted. After this is done we can proceed to the part 3, installing TWRP
Part 3,Installing TWRP:
Now, that we have root we can install TWRP using another toolkit. This part is optional but if you want any custom ROM's you need this. This part is the easiest, you need to download the toolkit from the link above and just run the script. We don't need any additional steps as we did them in Part 2.
If everything went well you should now be rooted and have TWRP with a locked bootloader and on the newest firmware.
In case of bricking you can use the Sony PC Companion tool and repair my phone/ tablet option. YOU WILL LOSE ANY DATA SAVED ON YOUR PHONE.
sir , can this apply to D2353?
I have only tried on E2303, but you use the right .ftf files the procedure should work
im flashed 128 kernel on 3.92, phone not booted stuck boot animation..
fix this after root random reboots? im rooted on 128 and upgrade 3.92 by twrpreroot, phone randomly reboots..
edit: im flashed 128 kernel on 2.167, phone not booted
osman.by said:
im flashed 128 kernel on 3.92, phone not booted stuck boot animation..
fix this after root random reboots? im rooted on 128 and upgrade 3.92 by twrpreroot, phone randomly reboots..
edit: im flashed 128 kernel on 2.167, phone not booted
Click to expand...
Click to collapse
Root and flash stock kernel tft u use
I'm having issues with this also. Downgrading the kernel only causes a boot loop animation. I can downgrade everything to 128 and it works. Going back up to latest with everything BUT kernel causes boot animation loops also.
EDIT!
Oh heck yes, I did it! For anyone stuck in a logo boot loop despite following the above, here is how I did it:
- Use Flashtool to completely flash my .167 E2303 to .128.
- Use above tools to root and install TWRP.
- Use Flashtool again, but this time in Fastboot mode. I extracted the system.sin file from a .167 ftf and then flashed system using Flashtool.
- Reboot the phone into TWRP. Clear cache, dalvik. I did NOT clear data.
- Install M4 extras. Install AOSGP. Clear cache, dalvik.
- Reboot took about 15 minutes, probably less.. and BINGO.
Thanks to all.
d0mokun said:
I'm having issues with this also. Downgrading the kernel only causes a boot loop animation. I can downgrade everything to 128 and it works. Going back up to latest with everything BUT kernel causes boot animation loops also.
EDIT!
Oh heck yes, I did it! For anyone stuck in a logo boot loop despite following the above, here is how I did it:
- Use Flashtool to completely flash my .167 E2303 to .128.
- Use above tools to root and install TWRP.
- Use Flashtool again, but this time in Fastboot mode. I extracted the system.sin file from a .167 ftf and then flashed system using Flashtool.
- Reboot the phone into TWRP. Clear cache, dalvik. I did NOT clear data.
- Install M4 extras. Install AOSGP. Clear cache, dalvik.
- Reboot took about 15 minutes, probably less.. and BINGO.
Thanks to all.
Click to expand...
Click to collapse
When i upgraded from 128 to 167, phone works well but random reboots. Any fix this issue?
Clean install of .167 and .92. Flashing the .128 kernel causes the blue boot animation to hang (the start up sound cuts off half way). Flashing the previous kernel back over works.
Same happens when I flash .128 then everything but the kernel from .167 and .92.
Unsure what the FSC script option does, but yes or no makes no difference.
d0mokun said:
I'm having issues with this also. Downgrading the kernel only causes a boot loop animation. I can downgrade everything to 128 and it works. Going back up to latest with everything BUT kernel causes boot animation loops also.
EDIT!
Oh heck yes, I did it! For anyone stuck in a logo boot loop despite following the above, here is how I did it:
- Use Flashtool to completely flash my .167 E2303 to .128.
- Use above tools to root and install TWRP.
- Use Flashtool again, but this time in Fastboot mode. I extracted the system.sin file from a .167 ftf and then flashed system using Flashtool.
- Reboot the phone into TWRP. Clear cache, dalvik. I did NOT clear data.
- Install M4 extras. Install AOSGP. Clear cache, dalvik.
- Reboot took about 15 minutes, probably less.. and BINGO.
Thanks to all.
Click to expand...
Click to collapse
EDIT: Someone re-uploaded the M4 rootkit: http://forum.xda-developers.com/m4-aqua/general/guide-t3130092/post65486499#post65486499
bootloop on E2303 Tried both methods
Hey all. Trying to root my E2353 on 26.1.A.1.112. Ran install.bat with all drivers installed, with adb, but all I'm getting is this. Any suggestions?
drunkenlo said:
Hey all. Trying to root my E2353 on 26.1.A.1.112. Ran install.bat with all drivers installed, with adb, but all I'm getting is this. Any suggestions?
Click to expand...
Click to collapse
enable usb debugging and unlock the phone and accept the popup message when plugged in
Jevinruv said:
enable usb debugging and unlock the phone and accept the popup message when plugged in
Click to expand...
Click to collapse
I have usb debbugging enabled and the phone unlocked but I don't get a popup message. Tried disabling and re-enabling usb debugging but still nothing.
drunkenlo said:
I have usb debbugging enabled and the phone unlocked but I don't get a popup message. Tried disabling and re-enabling usb debugging but still nothing.
Click to expand...
Click to collapse
Revoke USB Debugging authorization from developer Settings
Random Reboots
Any fix for the random reboots as of yet?
could u fix the dropbox link, it isnt working for me - Error (429)
This account's links are generating too much traffic and have been temporarily disabled!
I'm getting an error when installing the flashmode drivers, it just says failed after I tick the box and continue. Can anybody help me please? I've tried rebooting my PC, running as admin and even tried compatibility options but it doesn't help.
osman.by said:
When i upgraded from 128 to 167, phone works well but random reboots. Any fix this issue?
Click to expand...
Click to collapse
kgalv419 said:
Any fix for the random reboots as of yet?
Click to expand...
Click to collapse
If your random reboots usually happen while downloading or updating apps in the play store, you should try this. Make sure you backup your data first just in case.
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Hello. Please help. I got softreboot everytime I try to call someone
Sent from my E2303 using Tapatalk
Hello,
thank you for this guide. I have a question: why not extracting the old kernel and just flashing the kernel.sin?
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
@KaiserSnorezay
XZDR is still not compatible with MM, that's why you got a bootloop...
Also you can't install the "regular" TWRP with twrp manager on a LB as there is no recovery partition... it won't work and probably will mess your phone in the process.
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770
Just did it exactly this way yesterday on my friends d6503 (minus the d6502 patch obviously) had 0 troubles MM, root and recovery working perfectly.
Thanks, will try this today. Is wiping data required or can i get by by just flashing the older one?
ptmaniac said:
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
Click to expand...
Click to collapse
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
KaiserSnorezay said:
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
Click to expand...
Click to collapse
Weird, after you have your phone rooted it should be simple to install xzdr... just enable usb debugging in the phone and make sure you have the adb drivers correctly installed in your pc.
Download the latest xzdr from nut's thread ( http://forum.xda-developers.com/showthread.php?t=2261606 ) unzip it and run install.bat . After a successful install the phone should reboot to twrp automatically and it's done.
Okay, I fixed it..using Flashfire! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
KaiserSnorezay said:
Okay, I fixed it..using ! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
Click to expand...
Click to collapse
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
dodge911 said:
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
Click to expand...
Click to collapse
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
KaiserSnorezay said:
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
Click to expand...
Click to collapse
okay. you mean flashing any old firmware ( which i did and still in bootloop ) & root it. Then installing recovery for the same firmware ?
with "recovery" will i be able to get back my whole data ?
KaiserSnorezay said:
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
Click to expand...
Click to collapse
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
DedSec_35 said:
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
Click to expand...
Click to collapse
Sorry, I ditched my Z2 for a Oneplus 3 in August 2016. Learnt my lesson, only going to use phones with easily unlockable bootloaders.
I have been using the prerooted .575 ROM by kulvertti (http://forum.xda-developers.com/xpe...lipopprerooted231a128z2-tabletsgp511-t3100821) with the bootloop fix in the last week, and decided to reflash the rom without the bootloop to test whether it works without it.
After the advanced wipe of everything including internal memory and flashed the .575 rom, my tablet can no longer boot up. It just stayed in the Sony Xperia screen. Tried to ADB to it, but gets the "device null not found error", nor the adb devices showed it was connected to the PC.
What can I do to get me out from this now? or at least how can I install TWRP recovery so I can try flash again? Much appreciated.
Try to restore with flashtool https://talk.sonymobile.com/t5/Andr...ony-Flash-tool-for-Xperia-devices/td-p/307318
dataplays45 said:
Try to restore with flashtool https://talk.sonymobile.com/t5/Andr...ony-Flash-tool-for-Xperia-devices/td-p/307318
Click to expand...
Click to collapse
Thanks, but EMMA won't work. It is for unlocked bootloader. I managed to download the flashing tool 0.9.22.3 by Androxyde and get everything back to normal, though I still need to flash the bootloop fix for the .575 ROM.
please help urgently :'(
i have flashed system UI mod which seems to be corrupted
phone gave a message of system UI error
so in recovery ..i went to advanced format then formatted system and cache etc
pressed reboot and message of are you sure to reboot ..no OS
i rebooted and screen stuck at the first black screen and could not shut down or restart :'(
good day,
If your bootloader is unlocked you can flash recovery via fastboot mode and in recovery flash a rom of your choice. If bootloader locked you'll have to go the flashtool way and if I may ask why did you reboot a systemless phone?
Hayeni said:
good day,
If your bootloader is unlocked you can flash recovery via fastboot mode and in recovery flash a rom of your choice. If bootloader locked you'll have to go the flashtool way and if I may ask why did you reboot a systemless phone?
Click to expand...
Click to collapse
thanks for your gentle reply
i have bought it new then I did root and recovery
i don't know if bootloader locked or not cause i don't even know what does it mean
forgive me as i'm a newbie
i rebooted it while it is systemless cause i'm reckless
where can i got the recovery to flash
my mobile is z2 6503
Ok check under Xperia Z2 General for FTF Z2 stock firmwares and download one of them. After that download and install the latest flashtool, which will assist you with installing the FTF firmware.
You can use Xperia Companion app on your computer to perform a software repair. Install the latest version of Xperia companion app from the Sony site. Once it's installed, open it and click software repair. It will ask you to connect the phone in flash mode in due time; at that point connect to your PC with a USB cable while pressing the Volume Down button. The Companion app will download the stock rom and flash it on its own. You just have to wait until the process is over. This will delete all the data on your device though.