What's needed:
latest Android Pie firmware for Xperia XZ1 (I used 47.2.A.4.41_R4C UK or any version of the 47.2.A.6.30) from XperiFirm
newflasher_v13 tool here
Minimal ADB and Fastboot
TWRP Recovery here
last Magisk.zip here
first copy Magisk.zip to the sd card and insert it into the device
Install TWRP:
launch flashtool and download the latest firmware 47.2.A.4.41_R4C with XperiFirm ....
follow the path C: users / name / .flashTool / firmwares / Download
locate the unzipped firmware, open the folder and delete all the .ta files; then open the boot and partition folders and do the same thing
search the internet or XDA newflasher_v13 tool and place all 7 files in the C: users / name / .flashTool / firmwares / Download / 47.2.A.4.41_R4C folder
connect the device in flash mode
launch the .exe command
press "n" and again "n"
finished the firmware flash unplug the phone
When the first ignition is finished, open the debug and connect the mobile phone to the PC
open the folder Minimal in the path C: Program / Minimal and paste in the folder the recovery.img, run cmd.exe type the following commands
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery namerecovery.img
fastboot reboot
finished the start of the phone, turn it off and go into recovery mode (volume down + power button)
flash Magisk from the sd
turn on the cell phone and the root is done
Special thanks
oF2pks for the TWRP
munjeni for the newflasher
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
I have pie stock...can i start guide from point 10 ?
lilbrat said:
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
Click to expand...
Click to collapse
look at this thread for backup/restore your DRM keys
lilbrat said:
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
Click to expand...
Click to collapse
In my experience I can tell you that nothing is lost on the camera neither in the sound effects nor the color effects on the photos ...
ilblago81 said:
I have pie stock...can i start guide from point 10 ?
Click to expand...
Click to collapse
Absolutely yes
From the use I note that the recovery doesn't read the internal data, but only the sd card. I still don't understand if it's the firmware that has bugs or the twrp that still isn't calibrated for Adroid Pie.
Edit: I found in the XDA site the recovery for the new firmwre and everything works fine here
Would this work on SOV36 (AU XZ1)?
sinkoo1979 said:
Would this work on SOV36 (AU XZ1)?
Click to expand...
Click to collapse
Honestly I don't know, but if in your device install the firmware that we install in the g8341 means that you can. I'm thinking it's the same thing!
Sorry, but the requirement is always with unlocked bootloader?Thanks
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
dwang040 said:
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
Click to expand...
Click to collapse
Are your drivers properly installed reason I am asking is you're not getting a return when you type in fastboot devices, go back to you developer setting, revoke your debugging , then reinstall your drivers turn on USB debugging and see what happens?
lilbrat said:
Are your drivers properly installed reason I am asking is you're not getting a return when you type in fastboot devices, go back to you developer setting, revoke your debugging , then reinstall your drivers turn on USB debugging and see what happens?
Click to expand...
Click to collapse
Hmm, I think I know why it wasn't working? I got the xperia xz1 drivers off of the sony developer website, and I went to device manager and tried to do the legacy driver install, but I keep getting "This device cannot start (code 10)" Maybe that's the issue? And if so, am I installing it wrong or something?
dwang040 said:
Hmm, I think I know why it wasn't working? I got the xperia xz1 drivers off of the sony developer website, and I went to device manager and tried to do the legacy driver install, but I keep getting "This device cannot start (code 10)" Maybe that's the issue? And if so, am I installing it wrong or something?
Click to expand...
Click to collapse
What OS is on your computer?
lilbrat said:
What OS is on your computer?
Click to expand...
Click to collapse
Windows 10
dwang040 said:
Windows 10
Click to expand...
Click to collapse
Did you disable the driver verification signature?
(https://www.howtogeek.com/167723/ho....1-so-that-you-can-install-unsigned-drivers/) then reinstall min adb fastboot drivers and Sony companion and let it detect your phone..
chiacla said:
Sorry, but the requirement is always with unlocked bootloader?Thanks
Click to expand...
Click to collapse
you have to unlock the bootloader
dwang040 said:
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
Click to expand...
Click to collapse
did you install flashtool? did you install the drivers from the flashtool "drivers" folder? Did you unlocked the bootloader? ther'is no need to work on win10 signature
theflanker said:
did you install flashtool? did you install the drivers from the flashtool "drivers" folder? Did you unlocked the bootloader? ther'is no need to work on win10 signature
Click to expand...
Click to collapse
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
theflanker said:
you have to unlock the bootloader
Click to expand...
Click to collapse
He won't be able to unlock his bl till he figures out the issues with his drivers.. whether he uses the ones in flashtool, installs min adb and fastboot drivers or the android sdk..
---------- Post added at 05:34 PM ---------- Previous post was at 05:29 PM ----------
dwang040 said:
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
Click to expand...
Click to collapse
Once you get your driver's fixed, just follow the directions given by Sony.. Your phone screen will remain black as all info will be done on your computer..
dwang040 said:
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
Click to expand...
Click to collapse
Absolutely no, flashtool doesn't need to unlock the bootloader, rather serves to re-lock it in some xperia devices. To unlock it you have to use cmd commands in adb & fastboot, but you can find it here in the XZ1 section.
The cell screen remains black and a blue led appears if you connect in fastboot mode, if you connect in flash mode the screen remains black, but a green LED appears.
if you have problems with the recognition of the device on your PC I can link my guide, it's in italian but if you use google translator you understand it well here
arslancn said:
look at this thread for backup/restore your DRM keys
Click to expand...
Click to collapse
I've checked out the thread but it appears only a few with the xz1 have tried it and they didn't report the outcome, well except one who somehow managed to turn his device in an expensive paperweight.. But I will check it out this weekend..
Related
http://forum.xda-developers.com/m4-aqua
I have just successfully completed all 3 steps in the title and would like to compile the information so that more people can report more success. Many thanks and all credit to the threadstarter of this guide, the devs of the amazing Flashtool, and the dev of this newly created TOUCH version of the TWRP recovery (finally!)
Code:
DISCLAIMER:
[B]Your warranty is now void. [/B][U]DO THIS AT YOUR OWN RISK.[/U]
I am not responsible for bricked devices, bootloops, dead SD cards, thermonuclear war,
or you getting fired because the alarm app failed.
Please do some research if you have any concerns about any of the steps in this guide before performing them!
YOU are choosing to make these modifications,
please own your actions and don't be a baby about it.
Bootloader Unlock (instructions taken from this guide)
0. First check if your phone allows unlocking by dialing *#*#7378423#*#* , when Service Menu opens, go to Service Info, then Configuration; scroll down to read Rooting Status.
If "Bootloader unlocked" says yes, skip to the next section on Root.
If it says no (unlocked allowed), great, proceed on to next step.
If it says no (unlocked disallowed) or something like that, I'm sorry, unlocking won't work on your phone. Lodge a complaint with your mobile provider for locking it.
Getting the unlock code (skip to Step 5 if you already have it)
1. Go to Sony's official bootloader unlocking website.
2. Select Xperia M or M2 in the dropdown.
3. Follow all the steps (including *#06# to note your phone's IMEI number)
4. COPY the unlock code and paste and save it in a text file on your desktop.
Ensuring Flashtool recognises phone
5. Download Flashtool here and install it.
(To apply the 0.9.19.10 patch, install 0.9.19.8 and replace x10flasher.jar with the one from the patch. Default install folder is C:\Flashtool , don't change it)
6. Open Flashtool, connect your phone via USB. (Make sure USB Debugging is enabled in Developer Options). If Flashtool warns that ADB driver is not installed, go to the Sony website to download them. If Flashtool recognises phone, skip to Step 11.
7. Unzip the Sony drivers into a folder.
8. Boot into Advanced Startup on Windows and disable signed driver enforcement (I'm sorry, you have to Google this for your specific Windows installation)
9. When Windows has restarted, go to Device Manager, click on the ADB Interface item with the yellow questionmark, click Update Drivers, Search Manually, Have Disk, and then open the folder where the Sony driver inf is. select the ADB inf and install it. Warnings will pop up but install the drivers anyway. When done, the yellow questionmark will be replaced by something normal.
10. Verify that Flashtool recognises phone by connecting the USB cable when phone is on. You should see information about phone kernel and ROM version.
<Congratulations for making it this far>
Setting up Flashtool for use
11. With Flashtool open and phone connected, click on Devices in Flashtool menu > Check Drivers.
12. More information will pop up. Under ADB Devices, your phone's serial number will be stated (something like 10 digits and letters). Copy that serial number.
13. Go to %USERPROFILE%\.flashTool\mydevices .
14. Create a new folder in here and rename it to the serial number.
15. Open the serial number folder, create a new text file and rename it "ulcode.txt" (without the quotes).
16. Open the text file, paste your bootloader unlock code, save and close the file.
For step 16, as a precaution, copy and paste the serial number folder inside registeredDevices too. I didn't test which folder was being used by Flashtool for the unlock.
Actual unlocking of bootloader
17. With Flashtool open and phone connected, click on the BLU button. Follow all instructions. One involves VOL UP, the other involves VOL DOWN (for fastboot), please take note to do both, it's not deja vu.
18. When you have done so correctly, Flashtool will pop a small dialog with your IMEI and unlock code already pasted inside.
19. Take a deep breath and click unlock.
20. Check in main window that bootloader has indeed been unlocked.
21. Unplug the USB cable and boot your phone to check that everything should be normal.
CONGRATULATIONS, YOUR WARRANTY IS NOW VOID. :laugh:
Installing TWRP recovery (with touch capability but NO external SD card mount yet as of 13 Nov 2015)
0. Make sure your bootloader is unlocked before proceeding.
1. The download link is from the M4 Aqua Marshmallow Site, scroll to the bottom. (XDA thread is here)
2. Download and save the recovery.img file anywhere you like.
3. Copy and paste recovery.img to C:\Flashtool\x10flasher_lib .
4. Install the recovery using fastboot using the instructions based on this website (thanks and credits to Shyam Karnani):
Flashtool comes with its own ADB interface so we don't need to install any new ones or the bloated Android SDK.
a) Open a command window inside the folder C:\Flashtool\x10flasher_lib (shift-rightclick and select "open command window here")
b) Connect phone to the computer using the USB cable.
c) type "adb reboot bootloader" (without quotes) in the command window and press enter (if asked to allow USB debugging in the phone screen, touch ok)
d) when the phone has entered fastboot, type "fastboot flash recovery recovery.img" (without quotes) and enter. Check that there are no errors produced by the flashing.
e) type "fastboot reboot" and enter.
The phone now has TWRP recovery but NO ROOT.
To boot into recovery
1. Simultaneously press the Power button and Volume down until your device vibrates.
2. Quickly release the Power button, but keep pressing Volume down.
3. When you see the TWRP screen, release Volume down. You have now successfully entered recovery mode.
(Instructions from Sony Developer website)
Rooting using SuperSU
0. Check that you have flashed a custom recovery. If not, please refer to steps right above.
1. Download SuperSU from the official website.
2. Connect your phone and transfer the zip file to the INTERNAL storage (because no recovery can mount external SD card yet as of 13 Nov 2015).
3. Power off phone and boot into TWRP recovery.
(An info dialog will popup asking if you want to keep read-only for /system. I chose NOT to keep, but need someone with knowledge to explain if read-only will block rooting procedure. It will, right?)
4. Touch the Install button and scroll to find the supersu zip.
5. Install the supersu zip. When done, clearing cache/Dalvik is optional (can be done using Titanium Backup anyway once you have root).
6. Reboot system.
Enjoy your root! :good:
Good work, but is it for the M4 Aqua E2353 only?
adejager1 said:
Good work, but is it for the M4 Aqua E2353 only?
Click to expand...
Click to collapse
Of course, that's what the title says lol. I cannot vouch for the other models.
I think the instructions can be modified, like for example different serial number for different model.
I'm having problem after clicking the BLU button, I'm doing what it said "Unplug USB cable, power off, hold vol down, connect USB cable" but will have an error USB not recognized, check flashtool screen it said usb debugging is off, make sure your not in MTP, I already turn usb debugging on. I'm stuck here.
btw I disable signed driver enforcement already and installed the ADB, but still no luck
Running OS windows 10
help please, :crying: if you can make a video it may help. thanks!
Everything went well for me thanks a lot.
i'm on windows 8 64bits
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
jmikaii said:
I'm having problem after clicking the BLU button, I'm doing what it said "Unplug USB cable, power off, hold vol down, connect USB cable" but will have an error USB not recognized, check flashtool screen it said usb debugging is off, make sure your not in MTP, I already turn usb debugging on. I'm stuck here.
btw I disable signed driver enforcement already and installed the ADB, but still no luck
Running OS windows 10
help please, :crying: if you can make a video it may help. thanks!
Click to expand...
Click to collapse
Have you installed the drivers in -> C:\Flashtool\drivers
select :
Flashmode Drivers (1st line)
Fastboot Drivers (2nd line - this one will be used)
Common drivers Nicky (11th line)
Yes i install it all, guys do you think because the os im using? "windows 10"?
Thanks a ton, bro successfully rooted my Sony Xperia M4 Aqua Dual (E2363).
jmikaii said:
I'm having problem after clicking the BLU button, I'm doing what it said "Unplug USB cable, power off, hold vol down, connect USB cable" but will have an error USB not recognized, check flashtool screen it said usb debugging is off, make sure your not in MTP, I already turn usb debugging on. I'm stuck here.
btw I disable signed driver enforcement already and installed the ADB, but still no luck
Running OS windows 10
help please, :crying: if you can make a video it may help. thanks!
Click to expand...
Click to collapse
I also find a problem of unable to unbrick my bricked my old sony device on windows 10 with flashtool.
I also get the same error.
Try on windows 8.1.
failed unlock
i have problem when trying to unlock the bootloader. it says "failed <remote: commend not allowed>" in flashtool
can someone help me?
thanks
alvind27 said:
i have problem when trying to unlock the bootloader. it says "failed <remote: commend not allowed>" in flashtool
can someone help me?
thanks
Click to expand...
Click to collapse
IS bootloader unlock allowed : yes ?
Go to calls,enter *#*#7378423#*#* and go to service info-configuration
angelus-95 said:
IS bootloader unlock allowed : yes ?
Go to calls,enter *#*#7378423#*#* and go to service info-configuration
Click to expand...
Click to collapse
yes, I already check it at first and it say "yes"
i search in google there's no answer too for this. i really really need to root my phone because i'm running out of internal memory
Same issue with alvind27
Same issue as alvind27 has there been a fix yet.
my model is the same as yours
Works fine with my 2303
Great tutorial. Thank you so much. I forgot many things since someone has stolen my Xperia S. Root revived this phone. Android 6 + root is great future but now I am happy with that, too.
Working on my E2303. If someone has problem then he/ she has to learn more about it. Just follow steps slowly and everything is gonna be fine.
I had the same problem but also on windows 10, flashed in a windows 8 computer without any major issues.
I have a problem. Me appears seen, how can I fix?
C:\Flashtool\x10flasher_lib>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device unauthorized. Please check the confirmation dialog on your device.
C:\Flashtool\x10flasher_lib>adb reboot bootloader
C:\Flashtool\x10flasher_lib>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (32650 KB)...
OKAY [ 1.032s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.032s
Click to expand...
Click to collapse
Stuck at Bootloader Unlocking...
Hi, I have a problem here. I have the E2353 Xperia M4 Aqua and use the mac version of Flashtool
I've followed every step from checking whether or not the phone's BL can be unlocked (it is allowed) to putting all the necessary text files in the "mydevices" and "registeredDevices" folder. Problem is when I press and hold the VOL Down key and plug the USB in...nothing happens, it's just stuck there at the instructions screen while I keep holding the down volume key. I expected to see the Bootloader Unlock Wizard but it doesn't appear
Is there something I missed? What should I do?
Worked on e2363!
I managed to work on my E2363, though at the beginning I had problems and errors (when using fasboot to record TWRP.img got the error "unable to record the image").
In step 0, i got YES, but the error I mentioned persisted.
So did all the steps again (assuming in step 0 I would have gotten "no") and worked, the TWRP was recorded.
mikaaa6 said:
I have a problem. Me appears seen, how can I fix?
Click to expand...
Click to collapse
are you already unlock the bootloader first before flash recovery?
alvind27 said:
yes, I already check it at first and it say "yes"
i search in google there's no answer too for this. i really really need to root my phone because i'm running out of internal memory
Click to expand...
Click to collapse
what mean your bootloader say "yes"
check your bootloader again and maybe this can your answer
silencar said:
are u sure that it is unlocked? there are 3 kinds of status:
Bootloader unlock allowed: No - u can't unlock BL
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
Bootloader unlocked: Yes - BL is unlocked
Click to expand...
Click to collapse
sent from E2353 using bootloader
mufhm said:
are you already unlock the bootloader first before flash recovery?
I did every step to unlock the bootloader without any error, however Rooting Status spent UNAVAILABLE
Click to expand...
Click to collapse
My phone is stuck on bootloop. I have cyanogenmod 13 installed on my moto g 3rd gen(2015). I can't seem to get into my system recovery either, which is now twrp and it just shows the logo for twrp recovery. I also for some dumb reason disabled my usb debugging mode, so i can't flash my phone either. Help plzz
Maybe go to bootloader and reflash TWRP
minimale_ldz said:
Maybe go to bootloader and reflash TWRP
Click to expand...
Click to collapse
Doesn't work, can't connect to bootloader
znyght said:
Doesn't work, can't connect to bootloader
Click to expand...
Click to collapse
So, if you turn the phone off and then hold "power" and "volume down" untill it boots, nothing happens?
minimale_ldz said:
So, if you turn the phone off and then hold "power" and "volume down" untill it boots, nothing happens?
Click to expand...
Click to collapse
of course, it goes into bootloader but my PC can't recognize anything. So I can't flash anything. USB Debugging is disabled. If there was a way to force connect that would be great
znyght said:
of course, it goes into bootloader but my PC can't recognize anything. So I can't flash anything. USB Debugging is disabled. If there was a way to force connect that would be great
Click to expand...
Click to collapse
You don't need USB debugging to use fastboot when your phone is booted into bootloader. What you need there is a fastboot tool and drivers. I'm using this one:
http://forum.xda-developers.com/showthread.php?p=48915118
and if it doesn't install correct drivers for you, you can get them here:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
first thing to do is check what fastboot returns after this command:
Code:
fastboot devices
if it shows your device ID you're good to go
I'd suggest downloading stock firmware first and flashing it before messing with custom recovery. Just remember Motorola often updates bootloader with new firmware so don't flash anything older than you had on your phone before.
Good luck
EDIT: you can also use RSD Lite to flash a new software, it basically automates fastbooting proccess, so theres no risk of misspelling or doing other stuff wrong
EDIT2: firmware is here:
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
also, the OP (lost101) is a great, helpful guy who may give you some advice if you need
Thanks I'll give them a try
Originally Posted by minimale_ldz
You don't need USB debugging to use fastboot when your phone is booted into bootloader. What you need there is a fastboot tool and drivers. I'm using this one:
Click to expand...
Click to collapse
I've tried these but they didn't seem to work
Yesterday I tried to flash a a new rom on my Xperia Z2 (unlocked bootloader).
From TWRP I did an advanced wipe and selected basically everything except my mircoSD (because it has the new files).
After a long time of waiting I tried to flash the ZIP file and it gave me an error. I thought this had to do with the wipe so I decided to reboot my phone.
As you can imagine, it got stuck on the Sony logo (because system would be empty).
From this moment I couldn't do anything with my phone, except from the tool Emma.
I now have some clean installation of Sony their Android 6.0.1 for the Z2 (23.5.A.0.570) but Im unable to flash TWRP through fastboot.
The command adb devices shows my phone, fastboot devices gives an empty response.
When I restart to the bootloader from adb and try to flash TWRP I get the message "< waiting for device >".
I tried on three different PCs including a clean install of Windows with all kind of different drivers, yet I cant get fastboot to work.
Am I stuck with this unrooted version of Android now or do you guys have any suggestions for me?
Thanks in advance!
Install drivers correctly
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
As I said I've tried all kind of different drivers (Android tools, Sony drivers and flahstool drivers). So for me it's hard to tell what I'm doing wrong.
My computer notices the phone (if I hold volume up and attach the charger), it just doesn't show up under fastboot devices.
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
PaulusE said:
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
Click to expand...
Click to collapse
Manually boot into recovery by booting up your device normally and when you see a violet LED, press vol+.
i tried to do it my self. follow an instruction from a official website and other
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
https://www.getdroidtips.com/how-to...-plus-i3213-i4213-i4293-i3223/#Pre-Requisites
which i got stuck at, when i boot into bootloader mode . the phone seem to restart and appear only black screen with blue indicator.
then i tried to check if it still connect to adb or not, with {adb devices} its not listed there
PS.
-the drivers work fine
-my Xperia 10 plus model is I4293
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Zaben said:
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Click to expand...
Click to collapse
one thing weird
i using a Xperia Tool (Xperia Companion) and it display the text that my phone need to unlock the screen or allow to use data tranfer
which i already check a USB debugging to be on, and every time i connect it to my PC, it still ask me a permission to be allow or not
maybe this is a problem here ?
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Haxk20 said:
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Click to expand...
Click to collapse
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
ZimpleThing said:
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
Click to expand...
Click to collapse
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Haxk20 said:
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Click to expand...
Click to collapse
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
ZimpleThing said:
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
Click to expand...
Click to collapse
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Haxk20 said:
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Click to expand...
Click to collapse
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
ZimpleThing said:
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
Click to expand...
Click to collapse
There is a thanks button. Hit it instead of saying it.
Haxk20 said:
There is a thanks button. Hit it instead of saying it.
Click to expand...
Click to collapse
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Glad I could help
I know its been a long time but maybe someone can help me.
I can get into the bootloader but when I trie to use the unlock code, mentioned above, and the sony unlock key it always says waiting for device but nothing happens. Any clue?
Edit fixed the Problem
Xperia 10 plus stuck on waiting for device
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
I was using windows 10. From what I can remember, my problem is that I didn't install driver correctly (I'm not sure which one). I am not really sure if this fastboot driver the one I used. I saw my device in Device Manager, but I got waiting on device... just like you. So what I have done was locate my device in Device Manager and install the sony driver over that device. If sony's driver was not the correct one, then it was another driver that I can't remember, but the instruction still the same. Sorry for an unclear message, but I can barely remember anything now.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
Go in Windows Device Manager and check the device . If needed install drivers manually
Hey everyone. Today I've finally unbricked my Zenfone 7 after my dumbass locked the oem with fastboot since I've already rooted my phone and didn't want to use adb anymore (I was getting tired of the warranty voided message at boot too). Right after locking the oem, the phone booted and displayed a message that says: " Your device is corrupted. It cannot be trusted and won't boot". You already could tell I was scared as hell, so all I did the past hours was to look around until I found this solution!
Have in mind I'm not an expert or a developer, I'm only hoping you find this thread if you ever find yourself locked in fastboot with no access to recovery, oem, adb or usb debugging, just fastboot commands.
Having said that, you need to flash the raw firmware for your device. For the Zenfone 7 the one you need is "WW__ZS670KS_29.14.53.5_MR1.3_20201111_release-user.raw".
You also need:
- Android sdk and platform tools (minimal adb works too but I recommend original google software)
- Usb asus drivers
- Usb google drivers (installable from android studio just like sdk and platform tools)
Turn on your device on fastboot and connect it to your pc, then open cmd or powershell on your platform-tools folder and execute
Code:
fastboot devices
to check if your zenfone is detected. Close the command prompt.
Now, on the raw rom folder open flashall_AFT.cmd as administrator, then it should start flashing all of the stock firmware files. Once the prompt closes itself, reboot your phone using volume keys and power button to select.
In my case, right after booting, the phone displayed a message that said "your phone is corrupted" but with a wipe data option this time around. Choose wipe data/factory reset (all your data will be gone).
There you go! The phone should reboot into stock clean rom now.
I get Flashing is not allowed in Lock State
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
did you unlock bootloader?
IronSingh said:
did you unlock bootloader?
Click to expand...
Click to collapse
No, to do so I need go get into developer tools,
wich I can't because android won't boot
[ROM][OFFICIAL] Omnirom for zenfone7/7pro [Android-13.0]
What is Omnirom ? Selinux Status: Enforcing Instructions : Follow this Steps by steps You need to be lastest firmware on both slots Please. How to have lastest FW on both slots: Reboot twrp Flash stock + twrp on opposite reboot recovery do...
forum.xda-developers.com
RickJF said:
No, to do so I need go get into developer tools,
wich I can't because android won't boot
Click to expand...
Click to collapse
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
What is the problem?
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
RickJF said:
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
Click to expand...
Click to collapse
DM me, make sure you are able to do test Point, we can fix it via EDL