Related
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.
Hi Friends i flashed miui firmware by stinx when i was on lineage rom to update the rom without any error.Then after flashed no mi logo no recovery no fastboot tooo Anyone pls tell solution for this to recover my device back
The Game 370 said:
Hi Friends i flashed miui firmware by stinx when i was on lineage rom to update the rom without any error.Then after flashed no mi logo no recovery no fastboot tooo Anyone pls tell solution for this to recover my device back
Click to expand...
Click to collapse
Are you able to see led blinking as red when you connect it to PC?
gulshanstrider said:
Are you able to see led blinking as red when you connect it to PC?
Click to expand...
Click to collapse
Yes but pc is not recognising
The Game 370 said:
Yes but pc is not recognising
Click to expand...
Click to collapse
Go to device manager and tell which Port it Is connected on ?
900E or 9008
gulshanstrider said:
Go to device manager and tell which Port it Is connected on ?
900E or 9008
Click to expand...
Click to collapse
Hi its not showing anything sorry if i am wrong
Do you have MiFlash tool ?
gulshanstrider said:
Do you have MiFlash tool ?
Click to expand...
Click to collapse
YES
The Game 370 said:
YES
Click to expand...
Click to collapse
Check if it is getting listed there.
If not try test point method
gulshanstrider said:
Check if it is getting listed there.
If not try test point method
Click to expand...
Click to collapse
No its not showing my device
The Game 370 said:
No its not showing my device
Click to expand...
Click to collapse
what is the current state of yr phone?
tell in details.
is it charging?
is mi logo appears when power button is pressed?
did u try pressing "vol down+power button"?
and what exactly did u do before the phone was dead?
any error occured during flashing?
Same with me
Try accessing fastboot, then reunlock your bootloader
Simoom Sadik said:
what is the current state of yr phone?
tell in details.
is it charging?
is mi logo appears when power button is pressed?
did u try pressing "vol down+power button"?
and what exactly did u do before the phone was dead?
any error occured during flashing?
Click to expand...
Click to collapse
No mi logo,no fastboot,no recovewry nd not charging too
Only red light blinking when connected to usb
I was on lineage rom nd tried to update that rom nd flashed miui 7.5.4 firmware by the stinx to get rid of error while flashing newer build of lineage rom
auliamaster74 said:
Same with me
Try accessing fastboot, then reunlock your bootloader
Click to expand...
Click to collapse
I am unable to access fastboot
The Game 370 said:
I am unable to access fastboot
Click to expand...
Click to collapse
try pressing power + vol down untill it boots into fastboot
at first, I thought I can't access fastboot, turns out I could
try it
auliamaster74 said:
try pressing power + vol down untill it boots into fastboot
at first, I thought I can't access fastboot, turns out I could
try it
Click to expand...
Click to collapse
Thanks i tried deep flash cable method but it didnt worked nd tried test point method Finally it worked
Also Fixed,but FW Flash is a problem
HI,
I just wanted to comment on this, in the hope that some more experienced member, or even TheStrix would see it.
I've had the exact same problem over the last few days, but have been able to fix it each time by reflashing recovery from miFlash in edl mode;
Flashing the firmware from TheStrix (Latest, kenzo) without fail, bricks the Redmi Note 3, only being able to get to FastBoot. I'm able to switch to EDL on the PC with that batch file that's floating about, and flash recovery through miflash. I've been on LineageOS14 for the past few weeks, but my phones been barely usable with lag. Switched to AOSPX the other day by first flashing the FW;
1. Reboot to recovery
2. Backups
3. Wipe everything except for sd
4. Flash FW
5. Flash AOSPEx
6. Flash Gapps
7. Clear Cache
8. Reboot
That was the first time, and brick... as described above, back to recovery- tried missing out GAPPS- same result..
I went through a few different combinaitons, so have gotten quite used to the EDL mode miFlash...
Back through EDL.. flash recovery.. JUST AOSPEx, booted fine. Setup, etc, back to recovery, GAPPS, reboot, setups, etc.All working good- Except no power button
So I once again went back to recovery and flashed just the FW (Fully expecting it might fail)- Sure enough.. BRICK... So just, I've gone back through the miFlash, installed recovery, but then just decided to try rebooting from recovery into my existing AOSPEx- All works fine- Even the power button now- Was that fixed by the FW? And the bigger thing I'm wondering, since everytime I've flashed the FW it's resulted in a brick-does that mean the FW's not working? When I re flash the recovery, am I back to original FW?
Am I now on the new FW?
Only other thing is I don't have root... I'll see if I can find a supersu to flash, I guess.
So tl;dr- I'm all up and working- but flashing the latest FW form TheStrix appears to brick the Note 3 every time. I can only get a rom to install by NOT first flashing the FW. Flashing the FW after a rom still bricks. And I don't know if it is actually flashed with the new fw after re-installing recovery.
Edd.
Edmundajw said:
HI,
I just wanted to comment on this, in the hope that some more experienced member, or even TheStrix would see it.
I've had the exact same problem over the last few days, but have been able to fix it each time by reflashing recovery from miFlash in edl mode;
Flashing the firmware from TheStrix (Latest, kenzo) without fail, bricks the Redmi Note 3, only being able to get to FastBoot. I'm able to switch to EDL on the PC with that batch file that's floating about, and flash recovery through miflash. I've been on LineageOS14 for the past few weeks, but my phones been barely usable with lag. Switched to AOSPX the other day by first flashing the FW;
1. Reboot to recovery
2. Backups
3. Wipe everything except for sd
4. Flash FW
5. Flash AOSPEx
6. Flash Gapps
7. Clear Cache
8. Reboot
That was the first time, and brick... as described above, back to recovery- tried missing out GAPPS- same result..
I went through a few different combinaitons, so have gotten quite used to the EDL mode miFlash...
Back through EDL.. flash recovery.. JUST AOSPEx, booted fine. Setup, etc, back to recovery, GAPPS, reboot, setups, etc.All working good- Except no power button
So I once again went back to recovery and flashed just the FW (Fully expecting it might fail)- Sure enough.. BRICK... So just, I've gone back through the miFlash, installed recovery, but then just decided to try rebooting from recovery into my existing AOSPEx- All works fine- Even the power button now- Was that fixed by the FW? And the bigger thing I'm wondering, since everytime I've flashed the FW it's resulted in a brick-does that mean the FW's not working? When I re flash the recovery, am I back to original FW?
Am I now on the new FW?
Only other thing is I don't have root... I'll see if I can find a supersu to flash, I guess.
So tl;dr- I'm all up and working- but flashing the latest FW form TheStrix appears to brick the Note 3 every time. I can only get a rom to install by NOT first flashing the FW. Flashing the FW after a rom still bricks. And I don't know if it is actually flashed with the new fw after re-installing recovery.
Edd.
Click to expand...
Click to collapse
It's because you haven't unlocked officially. TheStrix's firmware contains MM bootloader which relocks your bootloader if you're in LP bootloader(which is your bootloader if you've unlocked unofficially). If you've already unlocked officially then flash the latest MIUI dev ROM(which relocks your bootloader) then unlock again, TheStrix's firmware will now work.
Or you can just unzip the Firmware then remove emmc_appsboot.mbn(MM bootloader) then rezip it again. You'd still get problems flashing the latest LineageOS Roms if you don't update your bootloader though. So my advice is unlock officially.
Try This guide http://en.miui.com/thread-235865-1-1.html and this guide make a deep flash cable and download the latest fastboot rom and follow the first link http://en.miui.com/thread-380827-1-1.html
Hi all,
I need some help I think. I searched everywhere and I kinda lost hope.
I unlocked my bootloader of my G8341 and a few months ago I got a working version of AOSP, but all of a sudden my phone didn't get past the Sony logo. My data is already lost, that's no harm, of course I made tons of backups
Tried to get back to stock rom with the latest Flashtool, but with no succes.. I think the combination of oem/vendor/boot is not right.
Of course I know that this could be a consequence but I would like to get my phone up and running.
Would like to get some pointers.. Any help would be appreciated!
Try instal Twrp and wipe all partions
hungvip2001 said:
Try instal Twrp and wipe all partions
Click to expand...
Click to collapse
Tried that already
Also tried to flash all partitions with flashtool with firmware downloaded with xperifirm and tried to directly flash aosp rom with fastboot.
Hi. Do you get an error related to the model in flashtool? If so, flash it via newflasher. There are guides online on how to prepare the firmware. I had this issue after carbon rom.
emyjojo said:
Hi. Do you get an error related to the model in flashtool? If so, flash it via newflasher. There are guides online on how to prepare the firmware. I had this issue after carbon rom.
Click to expand...
Click to collapse
Appreciate the help, but same old.. Flashing seems to go fine according to newsflasher (just tried it), no errors, but when booting the phone, I only see the sony logo.
Use Emma from Sony. Its the official tool
https://developer.sony.com/develop/open-devices/get-started/flash-tool/
nelrulz said:
Use Emma from Sony. Its the official tool
https://developer.sony.com/develop/open-devices/get-started/flash-tool/
Click to expand...
Click to collapse
Huge thanks! I tried everything, XperiFirm, Newflash, Xperia Companion, Flash Tool (not Sony's flash tool), and this is the only tool that unbricked my Xperia 1ii, thanks thanks thankss!
After reviving my SGP311 with flashtool and firmware SGP311_10.4.B.0.577_Customized_NCB.ftf , I've decided to try TWRP and LineageOS, however after using flashtool and firmware SGP311_10.5.A.0.230_kernel I may have bricked it.
I've used Android 4.3.3 (SGP311_10.4.B.0.577_Customized_NCB.ftf) for a few days, but it's old as s* and I can't install anything on it.
After flashing SGP311_10.5.A.0.230_kernel the SGP311 got stuck in a boot loop after the Sony logo, briefly lighting up the screen over and over again. From this point onwards:
- flashtool fails with "The bundle does not match the connected device"
- Emma doesn't recognize the tablet model and fails with error "This phone is locked"
- Xperia companion complained that the tablet was locked and bootloader was locked.
Any additional tips? I'm open to suggestions ...
Thanks in advance!
I've tried again flashtool 0.9.18.6 with SGP311_10.5.A.0.230_kernel and it flashed sucessfully! But same boot loop problem. Tried to flash again SGP311_10.4.B.0.577_Customized_NCB.ftf and it also worked and it booted successfully! I can't figure out what changed. I'll try again to install TWRP and LineageOS ...
piludovski said:
I've tried again flashtool 0.9.18.6 with SGP311_10.5.A.0.230_kernel and it flashed sucessfully! But same boot loop problem. Tried to flash again SGP311_10.4.B.0.577_Customized_NCB.ftf and it also worked and it booted successfully! I can't figure out what changed. I'll try again to install TWRP and LineageOS ...
Click to expand...
Click to collapse
Glad you made it. I am also in process of reviving my 321. Flashtool fixed it and Emma worked fine after that.
TWRP does not work, spent lot of time with that. Let me know, if you make it through
Got it working! Follow this thread: https://forum.xda-developers.com/xp...de-tutorial-sony-xperia-tablet-z-lte-t3392831
The important part is, that the fastboot included there works, while the one provided by google do not. Do not ask me why...