Any idea how to root Sony Xperia Go?
You already got yours? Cool.
Well I think it's a bit early, just wish the Xperia community was bigger.
So nice phones but Sony aren't that big in US.
superoneclick?? unlock root??
Yes, i got it....
Have try superoneclick and many more from the forum but no one work for this...... Need help to root, and i cant find any firmware or rom for this.... But i hope some one will fix this soon
Sent from my ST27i using xda premium
One way is unlocked bootloader and try make a cuslom kernel with recovery but i don't know how make custom kernel
you tried flashtool?? maybe it's supported since its an xperia phone
Sent from my E15i using xda premium
And Sony haven't posted anything?
Any idea?
I have try everything on this forum but cant find any one to work. Hope someone will come with working root to xperia go soon
Sent from my ST27i using xda premium
How to root Xperia GO
pajoneer said:
Any idea how to root Sony Xperia Go?
Click to expand...
Click to collapse
Whether you are on GB or ICS? Have you tried this? It also has a tutorial for rooting ICS. But in either case, you need have your GB ROM.
I dont have the ROM and i cant find any
Sent from my ST27i using xda premium
pajoneer said:
Any idea how to root Sony Xperia Go?
Click to expand...
Click to collapse
- Reflash your phone with current firmware using Sony Update Service
- Copy the blobs Update Service caches from the update to local directory
- Use Flashtool to decrypt and recreate the tft from the blobs
- Unzip the ftf and unpack the boot image together with to kernel
- Edit /default.prop and set ro.secure=0
- Repack the root initramfs file system
- Create a new boot image with the root filesystem and the kernel
- Unlock the boot loader
- fastboot the new image (no need to flash it)
- "adb shell" to the phone, you are now the root user
- remount /system read-write
- add busybox, su and whatever you like
Check www.youtube.com/watch?v=bB77gWRUI_A for details about getting your original image.
See http://developer.sonymobile.com/wp/2011/05/06/how-to-build-a-linux-kernel/ about building the boot image.
Search this forum about how to unpack the .sin-files
kuisma said:
- Reflash your phone with current firmware using Sony Update Service
- Copy the blobs Update Service caches from the update to local directory
- Use Flashtool to decrypt and recreate the tft from the blobs
- Unzip the ftf and unpack the boot image together with to kernel
- Edit /default.prop and set ro.secure=0
- Repack the root initramfs file system
- Create a new boot image with the root filesystem and the kernel
- Unlock the boot loader
- fastboot the new image (no need to flash it)
- "adb shell" to the phone, you are now the root user
- remount /system read-write
- add busybox, su and whatever you like
Check www.youtube.com/watch?v=bB77gWRUI_A for details about getting your original image.
See http://developer.sonymobile.com/wp/2011/05/06/how-to-build-a-linux-kernel/ about building the boot image.
Search this forum about how to unpack the .sin-files
Click to expand...
Click to collapse
Thanks!
But now to next problem... If i run Sony PC Companion I will get anser NO FW found for your device???? (i select repair)
and if i use Sony Update Service i dont get any repar or reinstall it says you already have the last FW........
holst75 said:
If i use Sony Update Service i don't get any repair or reinstall it says you already have the last FW........
Click to expand...
Click to collapse
Ah, strange. Update Service is supposed to reinstall the same version already installed. Maybe Sony not yet updated their servers.
Still I believe you can work around this. The nice thing about Sony Xperia is that when you unlock its bootloader, you can boot your phone over usb using fastboot without having to flash the image. I.e. a single one-time-boot of your image, without any permanent modifications of your phone.
This means you can always try booting another boot image than the original. It don't have to work perfect, just brining the devices up so you can access it via usb and "adb shell". It need to use the same disk devices (mount right partition at right mount point), so try using a image from another Xperia and hope for the best. You can check the mount points using the command "mount" in the shell, compare with the mount points of some other Xperia you can get the ROMs to.
So download a Xperia ROM from XDA, edit ro.secure=0, recompile the boot image again and try fastboot the phone (do not flash it!). If it boots, don't care if everything things isn't working properly, just transfer su and busybox to /system/bin and then halt and restart the phone - this time from the internal flash (= original image), and you got the phone using its original image, but with the su and busybox you need to become root.
Again - do not flash your image, only boot the phone with it. If you flash it, and don't got the original image to restore back, your phone is bricked.
Problem solved.
I have downloaded firmware from Sony ...link will be soon ... but i have problem with rooting system, Please, can somebody help me with them?
I hope we can root woth out unlock bootloader.....
Sent from my ST27i using xda premium
holst75 said:
I hope we can root with out unlock bootloader.....
Click to expand...
Click to collapse
Myself I actually prefer the official way instead of hacks I don't know what side effects they may or may not have, but that's me. I'm sure it's possible using some exploit, but I can't help you there, sorry.
Hi guys,
I created ftf from blobs and unzip ftf.
I used Nero Young guide to make custom rom (kernel), but when I need to add boot.img to my kitchen folder, I can't find it.
I tried to follow this guide http://developer.sonymobile.com/wp/2011/05/06/how-to-build-a-linux-kernel/, but without success. I also try SIN2IMG, mkbootimg... but nothing
Can someone tell me another way to make boot.img, or upload boot.img for ST27i.
driversax said:
Hi guys,
I created ftf from blobs and unzip ftf.
I used Nero Young guide to make custom rom (kernel), but when I need to add boot.img to my kitchen folder, I can't find it.
I tried to follow this guide http://developer.sonymobile.com/wp/2011/05/06/how-to-build-a-linux-kernel/, but without success. I also try SIN2IMG, mkbootimg... but nothing
Can someone tell me another way to make boot.img, or upload boot.img for ST27i.
Click to expand...
Click to collapse
Could you post your FTF ?
pajoneer said:
Could you post your FTF ?
Click to expand...
Click to collapse
There you go:
sendspace.com/file/vks58a
sendspace.com/file/f1uvog
Related
Here is the tutorial for Installing stock 4.0.2.A.0.62 ROM plus root and CWM. I am not responsible or anyone mentioned below for bricking your phone in case, tested on my Xperia ray with unlocked bootloader using S1 tool.
Requirements
Unlocked Bootloader (preferred) although there is a work around for locked bootloader
4.0.2.A.0.62 FTF files
Flashtool
recoveryRay.img by and Rootxperia.zip b1n4ry (for rooting)
CWM
Installation:
How to Install stock 4.0.2.A.0.62 ROM:
Download this stock 4.0.2.A.0.62 ROM. Thank you Aire for providing the link.
After download you will have a zip file. Extract it.
Download flashtool here and extract it.
Create FTF file using flashtool from the 4.0.2.A.0.62 ROM zip you extracted earlier. Now if you don't know how to create FTF files, there's a good tutorial here.
If you successfully created FTF file, you should see a file with extension “.ftf” in the “firmwares” folder inside “FlashTool” folder
Run the executable “X10FlashTool.exe” located in the FlashTool folder
Now click “Flash” button and select flashboot. Now select the firmware from the popup menu. Make sure “Wipe user data” box is checked and then click “OK”.
The application will ask you to put your Ray in flashboot mode, to do this turn off the phone, hold the volume down button while while connecting the USB cable to your computer.
Follow the on screen instruction and your device will reboot. Notice that the reboot process will take longer at first.
How to install Root
Please note that this is only applied to devices with unlocked bootloader. Alternately, you can just install a custom kernel and root using zergrush method but if you want to try the .62 kernel from this stock rom then do this.
Download rootxperia.zip here and place it in your sd card
Enter device in fastboot mode. Turn off phone, hold volume up while you connect the USB cable to computer
Download the recoverRAY.img provided below, you will get a zip file, extract it.
Open folder inside Flashtool where fastboot.exe exists (/FlashTool/x10flasher_lib)
Place the recoveryRAy.img inside the folder
Open command line in this folder
Test if it recognize your device, to do this type fastboot devices, if there is a result here proceed.
Now here's the tricky part, to enter a temporary recovery type fastboot boot recoveryRAY.img
*Notice that we didn't use fastboot flash boot ****.img here because as bin4ry said this recovery is designed to work just as recovery, if you flash it to your device it will NOT boot system anymore! This is just a temporary recovery for you so be careful not to flash it.
Now wait and your phone will reboot, you will see the FREE XPERIA splash screen and your device will now enter temp CWM recovery
On your phone choose install custom zip, locate the rootxperia.zip you added earlier in your SD card and flash it.
Reboot, your device is now rooted.
*to root your device with locked bootloader, they say you can install previous stock kernel and root using zergrush method.
How to install CWM
Download this then extract
Make sure you enabled USB debugging, and also you need to set Screen timeout to 10 minutes so you don't miss the superuser promt
Run install-cwm1.cmd from the folder
Follow screen on screen instruction, reboot.
idareyoutoclickthis said:
Here is the tutorial for Installing stock 4.0.2.A.0.62 ROM plus root and CWM. I am not responsible or anyone mentioned below for bricking your phone in case, tested on my Xperia ray with unlocked bootloader using S1 tool.
Requirements
Unlocked Bootloader (preferred) although there is a work around for locked bootloader
4.0.2.A.0.62 FTF files
Flashtool
recoveryRay.img by and Rootxperia.zip b1n4ry (for rooting)
CWM
Installation:
How to Install stock 4.0.2.A.0.62 ROM:
Download this stock 4.0.2.A.0.62 ROM. Thank you Aire for providing the link.
After download you will have a zip file. Extract it.
Download flashtool here and extract it.
Create FTF file using flashtool from the 4.0.2.A.0.62 ROM zip you extracted earlier. Now if you don't know how to create FTF files, there's a good tutorial here.
If you successfully created FTF file, you should see a file with extension “.ftf” in the “firmwares” folder inside “FlashTool” folder
Run the executable “X10FlashTool.exe” located in the FlashTool folder
Now click “Flash” button and select flashboot. Now select the firmware from the popup menu. Make sure “Wipe user data” box is checked and then click “OK”.
The application will ask you to put your Ray in flashboot mode, to do this turn off the phone, hold the volume down button while while connecting the USB cable to your computer.
Follow the on screen instruction and your device will reboot. Notice that the reboot process will take longer at first.
How to install Root
Please note that this is only applied to devices with unlocked bootloader. Alternately, you can just install a custom kernel and root using zergrush method but if you want to try the .62 kernel from this stock rom then do this.
Download rootxperia.zip here and place it in your sd card
Enter device in fastboot mode. Turn off phone, hold volume up while you connect the USB cable to computer
Download the recoverRAY.img provided below, you will get a zip file, extract it.
Open folder inside Flashtool where fastboot.exe exists (/FlashTool/x10flasher_lib)
Place the recoveryRAy.img inside the folder
Open command line in this folder
Test if it recognize your device, to do this type flashboot devices, if there is a result here proceed.
Now here's the tricky part, to enter a temporary recovery type fastboot boot recoveryRAY.img
*Notice that we didn't use fastboot flash boot ****.img here because as bin4ry said this recovery is designed to work just as recovery, if you flash it to your device it will NOT boot system anymore! This is just a temporary recovery for you so be careful not to flash it.
Now wait and your phone will reboot, you will see the FREE XPERIA splash screen and your device will not enter temp CWM recovery
Choose install custom zip, locate the rootxperia.zip you added earlier in your SD card and flash it.
Reboot, your device is now rooted.
*to root your device with locked bootloader, they say you can install previous stock kernel and root using zergrush method.
How to install CWM
Download this then extract
Make sure you enabled USB debugging, and also you need to set Screen timeout to 10 minutes so you don't miss the superuser promt
Run install-cwm1.cmd from the folder
Follow screen on screen instruction, reboot.
Click to expand...
Click to collapse
Thanks for this.. but.. i wonder what happened if i update from SEUS.. :-/ and also, is the kernel from aire already support Overclocking?
hansip87 said:
Thanks for this.. but.. i wonder what happened if i update from SEUS.. :-/ and also, is the kernel from aire already support Overclocking?
Click to expand...
Click to collapse
Aire said, his current kernel supports .62 but they are currently working for repack based on this new firmware.
I haven't tried installing any custom firmware at the moment, I want to test this stock firmware for changes and improvement especially the baseband and battery consumption.
Sent from my ST18i using xda premium
Hm ok, btw, can you post the original link for rootxperia.zip?
EDIT: sorry you already did that thanks!
UPDATE: I'm trying to do SEUS update now though. Hope this thing won't brick..
UPDATE 2: SEUS update won't brick our phone if it uses the Testpoint method O what a happy day it is.. Let's see if i can flash aire kernel back.
is that a global version or what ? some people said, that version has some bugs..
can we root this version with the new DoomLord v4 Root ?
from the Arc forum, i found that they can root their device with .62 firmware just by using flashtool.. can we do that so ?
thx
hansip87 said:
Hm ok, btw, can you post the original link for rootxperia.zip?
UPDATE: I'm trying to do SEUS update now though. Hope this thing won't brick..
UPDATE 2: SEUS update won't brick our phone if it uses the Testpoint method O what a happy day it is.. Let's see if i can flash aire kernel back.
Click to expand...
Click to collapse
Wow that is good news. Update is still not available in my region.
adarwis said:
is that a global version or what ? some people said, that version has some bugs..
can we root this version with the new DoomLord v4 Root ?
from the Arc forum, i found that they can root their device with .62 firmware just by using flashtool.. can we do that so ?
thx
Click to expand...
Click to collapse
The firmware is provided by Aire, however if you encounter ftf generic firmware, it will be nice if you post it here.
As to bugs, I'm using this firmware for a day now and I noticed improvement in battery and speed, no bugs so far. I haven't tried the doomlord v4 root, but rooting via recovery is easy.
Sent from my ST18i using xda premium
idareyoutoclickthis said:
Wow that is good news. Update is still not available in my region.
The firmware is provided by Aire, however if you encounter ftf generic firmware, it will be nice if you post it here.
As to bugs, I'm using this firmware for a day now and I noticed improvement in battery and speed, no bugs so far. I haven't tried the doomlord v4 root, but rooting via recovery is easy.
Sent from my ST18i using xda premium
Click to expand...
Click to collapse
Yep it is I have already flashed back aire's kernel and it is flawless no more test point required. Yay! Thanks for all the devs.
Xperia blog says the firmware is targeted for users in Middle East North Africa region.
Users else where may see little if any noticeable change
sent from my gorgeus Xperia Ray
Does this not work if we previously updated the phone to 4.0.2.A.0.62 using SEUS?
Coz i got the following error when i ran the "fastboot boot recoveryRAY.img" command..
FAILED (remote: The Device must be rooted first)
San.subs said:
Does this not work if we previously updated the phone to 4.0.2.A.0.62 using SEUS?
Coz i got the following error when i ran the "fastboot boot recoveryRAY.img" command..
FAILED (remote: The Device must be rooted first)
Click to expand...
Click to collapse
O that.. That means you need to unlock the bootloader (at least with Test Point method). Never thought that won't work before.
most download link from MultiUpload cannot download the firmware 4.0.2.A.0.62 ROM, any alternative link?
Thanks.
San.subs said:
Does this not work if we previously updated the phone to 4.0.2.A.0.62 using SEUS?
Coz i got the following error when i ran the "fastboot boot recoveryRAY.img" command..
FAILED (remote: The Device must be rooted first)
Click to expand...
Click to collapse
If your bootloader is still locked you can not root your device using that method. The only work around is to install previous kernel and root using zergrush method.
hansip87 said:
O that.. That means you need to unlock the bootloader (at least with Test Point method). Never thought that won't work before.
Click to expand...
Click to collapse
idareyoutoclickthis said:
If your bootloader is still locked you can not root your device using that method. The only work around is to install previous kernel and root using zergrush method.
Click to expand...
Click to collapse
Thank you "idareyoutoclickthis" and "hansip87" for your replies.
In fact I had rooted my Ray earlier 4.0.2.A.0.42ver using the zergrush method using DooMLoRD_v4_Root Which I lost when I upgraded to 4.0.2.A.0.62ver. Now DooMLoRD_v4_Root won't work with 4.0.2.A.0.62ver update.
Now what about the bootloader thing? Sorry for being so dumb. Can you please elaborate a bit? I've got only got to the point wherein i checked the status using the service menu (*#*#.....#*#). It only says Rooting Status: Bootloader unlocking allowed: Yes.
What do I have to do now? Please help.
San.subs said:
Thank you "idareyoutoclickthis" and "hansip87" for your replies.
In fact I had rooted my Ray earlier 4.0.2.A.0.42ver using the zergrush method using DooMLoRD_v4_Root Which I lost when I upgraded to 4.0.2.A.0.62ver. Now DooMLoRD_v4_Root won't work with 4.0.2.A.0.62ver update.
Now what about the bootloader thing? Sorry for being so dumb. Can you please elaborate a bit? I've got only got to the point wherein i checked the status using the service menu (*#*#.....#*#). It only says Rooting Status: Bootloader unlocking allowed: Yes.
What do I have to do now? Please help.
Click to expand...
Click to collapse
Indeed .62 is the latest built which include alot of improvements specially on batter issue.
If you don't want custom rom and kernel and is contented with the stock ROM and kernel then you don't need to unlock your bootloader.
to root your device, you need to flash stock 4.0.2.A.0.42 kernel only, you can do this with locked bootloader and root using zergrush method.
idareyoutoclickthis said:
Indeed .62 is the latest built which include alot of improvements specially on batter issue.
If you don't want custom rom and kernel and is contented with the stock ROM and kernel then you don't need to unlock your bootloader.
to root your device, you need to flash stock 4.0.2.A.0.42 kernel only, you can do this with locked bootloader and root using zergrush method.
Click to expand...
Click to collapse
Do I lose root if I restore the .62 kernel after rooting?
slimfady said:
Do I lose root if I restore the .62 kernel after rooting?
Click to expand...
Click to collapse
I'm afraid yes but i never tried it though cause my bootloader is unlocked.
hi, what is the work around for locked bootloader , i am using 4.0.2.A.0.62, i dont want to use any custome rom or mod i want only root intalled on this. i use ARC -S
Regards,
M.Baradharajan
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
hi, where can i get the original stock 4.0.2.A.0.42 ROM, not modified one to reflash from 4.0.2.A.0.62 rom.
Regards,
M.Baradharajan
baradharajan said:
hi, what is the work around for locked bootloader , i am using 4.0.2.A.0.62, i dont want to use any custome rom or mod i want only root intalled on this. i use ARC -S
Regards,
M.Baradharajan
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
hi, where can i get the original stock 4.0.2.A.0.42 ROM, not modified one to reflash from 4.0.2.A.0.62 rom.
Regards,
M.Baradharajan
Click to expand...
Click to collapse
Ask in the Arc forum please.
even i got the same error remote: device must be rooted first... my bootloaders are unlocked.. wht shud i do now
*Notice that we didn't use fastboot flash boot ****.img here because as bin4ry said this recovery is designed to work just as recovery, if you flash it to your device it will NOT boot system anymore! This is just a temporary recovery for you so be careful not to flash it.
I dont read careful this note and now my phone's brick. I cannot access flashmode or fastbootmode anymore. Now my phone only log in temRECOVERY
Can anyone help me. From vietnam
Ok i need some suggestions.
i have an unlock-able boot loader but have rooted.
out of boredom i figured i would change my fonts and copied them with file explorer, made sure permissions were set to rw-r-r.
now im stuck in a boot loop, i'm guesing it's because i'm on a stock ics rom.
my hardware is xperia s, rogers is my carrier, i'm rooted running ics.
is my fear of having to reinstall true? or is there another way to fix this?
thanks
hackit said:
Ok i need some suggestions.
i have an unlock-able boot loader but have rooted.
out of boredom i figured i would change my fonts and copied them with file explorer, made sure permissions were set to rw-r-r.
now im stuck in a boot loop, i'm guesing it's because i'm on a stock ics rom.
my hardware is xperia s, rogers is my carrier, i'm rooted running ics.
is my fear of having to reinstall true? or is there another way to fix this?
thanks
Click to expand...
Click to collapse
Nope..I guess reinstalling is the only way bro
Sent from my LT26i
ashqmallik said:
Nope..I guess reinstalling is the only way bro
Sent from my LT26i
Click to expand...
Click to collapse
is ADB on if so you could adb shell and dd them back in during the bootup i have recovered like this before
Pvy.
Adb = fastboot=anytime..but Fastboot method? U cld try but I prefer reinstalling a fresh ftf..in dis way u won't have even da slightest possibility of error occlusion as ur SEUS didn't work either so I prefer, reflash. U can try by goin to fastboot mode and push ur system.sin file through adb..see If it works
Sent from my LT26i
Uncheck the wipe data option in flashtool and Flash the ftf. This way you won't lose your data
Tapatalked !!
Rapier07 said:
Uncheck the wipe data option in flashtool and Flash the ftf. This way you won't lose your data
Tapatalked !!
Click to expand...
Click to collapse
thanks for the replys guy's, this way i can keep my root right?
hackit said:
thanks for the replys guy's, this way i can keep my root right?
Click to expand...
Click to collapse
If you re-flash then you will loose your root access but you can always gain it back. You just need to download the kernel (ICS/GB have different kernel) then flash it through fastboot. Though, if you want to keep ur stock kernel a.k.a ICS/GB kernel then u can do it too. Just let us know which one you want to do and we can guide u through :highfive:
Kernel Download:
DoomKernel (GB)
Xperia SSpeed (ICS)
Advanced Stock Kernel Build 14/15 (ICS)
Click to expand...
Click to collapse
have fun :highfive:
Rapier07 said:
Uncheck the wipe data option in flashtool and Flash the ftf. This way you won't lose your data
Tapatalked !!
Click to expand...
Click to collapse
ashqmallik said:
If you re-flash then you will loose your root access but you can always gain it back. You just need to download the kernel (ICS/GB have different kernel) then flash it through fastboot. Though, if you want to keep ur stock kernel a.k.a ICS/GB kernel then u can do it too. Just let us know which one you want to do and we can guide u through :highfive:
Kernel Download:
have fun :highfive:
Click to expand...
Click to collapse
yeah i'm stuck with a locked boot-loader so stock kernel for me.
thanks
hackit said:
yeah i'm stuck with a locked boot-loader so stock kernel for me.
thanks
Click to expand...
Click to collapse
You gotta locked bootloader or an unlocked one Dont worry, u can root both anywayz .
ashqmallik said:
You gotta locked bootloader or an unlocked one Dont worry, u can root both anywayz .
Click to expand...
Click to collapse
my boot-loader is not unlock-able. i'm waiting for a way to unlock my boot-loader.
so with s1 server gone from se maybe it wont happen.
ashqmallik said:
You gotta locked bootloader or an unlocked one Dont worry, u can root both anywayz .
Click to expand...
Click to collapse
this so sucks, i flashed gb instead of ics (i was on ics), so alot of force closes.:silly:
so i immediately flashed ics wiping the phone. now i have no root and the 3 step root is not working.
i guess i need to start all over right, go back to gb and then to ics?
i think i will now try another rom like XcreaM or maybe muiu..
hackit said:
this so sucks, i flashed gb instead of ics (i was on ics), so alot of force closes.:silly:
so i immediately flashed ics wiping the phone. now i have no root and the 3 step root is not working.
i guess i need to start all over right, go back to gb and then to ics?
i think i will now try another rom like XcreaM or maybe muiu..
Click to expand...
Click to collapse
U dont need to go over GB to get ICS!! u can just flash ICS and root it . Am using 6.1.A.2.45 Generic NL stock firmware with custom KA v6 kernel and both of them are working pretty nicely without any hitch so far. Anywayz, heres what you do if you have an unlocked bootloader. Dial *#*#7378423#*#* to check your Bootloader status
Flash Firmware:
#Download stock ICS Firmware from here as an ftf.zip file. (I recommend 6.1.A.2.45 Generic NL)
#Downlaod and install latest Flashtool, unzip the ftf file and save the ftf file over at the 'firmware' folder in Flashtool.
#Connect your phone via usb to pc and let flashtool recongnize it
#Click the Thunder button in flashtool and choose Flashmode.
#Choose the ftf file. Dont click or touch anything else. Hit OK
#The flashtool will ask you to disconnect your phone.
#Disconnect your phone from usb. Turn it off.
#Hold down Power+Volume Down and connect the phone via usb to the pc. Green led (flashmode) will light up.
#Flashtool will automatically start flashing the new firmware.
#After finished flashing the firmware. Take it off from the usb and Reboot.
#Let our phone boot then go to Settings>Developer Options>tick right USB debugging (MUST)
Click to expand...
Click to collapse
U'll need the below fastboot binaries and ANY ONE kernel to root your ICS (Any one)
#Fastboot Binaries (MUST)
#Xperia SSpeed v6 1.89GHz (KERNEL) (Highly Recommended if u want overclocked CPU, am using it and its clear and totally bug free)
or
#Advanced Kernel Build 14 (KERNEL)
Click to expand...
Click to collapse
HOW TO ROOT:
1st Step:
#Download 7zip
#Right click on the ftf file which you have just flashed.
#Choose 7zip > Open archive
#Select just the kernel.sin file
#Click extract and save the file anywhere in desktop.
#Unzip the kernel folder (xsspeed or advanced kernel) that you have downloaded. Copy the kernel.elf file.
#Unzip and open the FASTBOOT BINARY folder. Go to 'fastboot' folder and paste the kernel.elf file
#Turn of your phone.
#Press Power Button+Volume UP Key and connect your phone via usb to your pc. BLUE led will light up (fastboot mode)
#The fastboot folder opened. Click 'SHIFT+RIGHT MOUSE BUTTON'
#Choose 'OPEN COMMAND WINDOW HERE' and you will get windows command prompt.
#Type the following command to check if device is connected.
Code:
fastboot devices
#Now flash the kernel
Code:
fastboot flash boot kernel.elf
#Now reboot from fastboot mode
Code:
fastboot reboot
Click to expand...
Click to collapse
After the reboot, your phone will be rooted and will use custom kernel :highfive:
GETTING BACK TO STOCK KERNEL WITH ROOT ACCESS:
#Open Flashtool
#Turn off your phone and get into fastboot mode (Power+Volume UP then connect the phone via usb to pc. Blue led will turn on)
#Click the Thunder button and choose FASTBOOT
#Click 'Select Kernel To Flash'
#Choose the kernel.sin file that you have extracted earlier from the ftf file and saved earlier in your desktop.
#Reboot.
Click to expand...
Click to collapse
Now your phone is rooted yet back to stock kernel
have fun :highfive: :highfive:
thanks for the guide.
now i'm back to ics and running Xcream (cool), with cwm & root. But without an unlocked boot-loader no extra tweaks for me. damn you rogers for locking my boot-loader.
so maybe you can help with a question. i have made a few themes for my older phones xperia x10, xperia play, htc raider, htc evo 3d. and really want to do the same for my xperia s.
now i have been reading and have the latest apk tool with the updates of apk tool jar and the aapt.exe.
i still can't recompile systemui.apk. and from what i'm reading you can't touch the framework res. now i'm use to using adb to push all my files to my phone.
so as the thread title said i was trying to change the font. and this caused a bootloop.
do you know of a guide or list of things we can tweak?
thanks
Is it specific for each device? Or does it depend only on finding the correct partition/block to be extracted?
Could you point me to further readings about that?
Thanks.
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
DopeyTheOne said:
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
Click to expand...
Click to collapse
Well, that link is to proceed AFTER you have boot.img at hand. I want to find a way to extract it from my phone (assuming default.prop can be changed in there).
Thanks.
When you make a back up with CWM, you have a copy of your bootimage in the clockworkmod map, not?
That's the thing ... I am trying to figure out how to get that backup in hand at first.
Currently, following the method in http://droidcore.blogspot.com.br/2012/12/how-to-edit-initrc-in-android.html
It seems to use the same scripts as cited in your link.
Will post results afterwards.
Don't make things more complicated as they are. If you just install CMW recovery (or TWRP for that matter) for your device, you have your full backup in minutes, including one of your bootimage, then use the script from my first post.
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
MrCabana said:
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
Click to expand...
Click to collapse
I used a CWM image to root my device. Booted up with that image, and flashed SU....after that you can use su, and apparantly, with the changes you made with your bootimage...you'll be like God on your phone
Sent from my S500 using xda app-developers app
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Click to expand...
Click to collapse
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
bromeara said:
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
Click to expand...
Click to collapse
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Alright thank you. I'm fairly new to the android ecosystem and to boot I'm working on a Fire tablet so its running fireos and amazon doesn't really make it easy to touch their code
think he is facing the same situation as mine, for hk version of htc u12+, its hard to find the proper RUU or firmware from internet. Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Vita.T said:
Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
Click to expand...
Click to collapse
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
dano.556 said:
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
Click to expand...
Click to collapse
Ok....
I am assuming that the op has a samsung device....
Same Problem
Loku_kika said:
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Click to expand...
Click to collapse
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Lloydster said:
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Click to expand...
Click to collapse
just google "Latest Software Version for OPPO OPPO AX7" and go to the Software Updates page on oppo-uk.custhelp.com. Download 2.4GB ozip file (like CPH1903EX_11_OTA_0210_all_oStq7F7jxqfF.ozip) and unpackit with 7zip program. You'll find boot.img inside .ozip file.
I do not have root, there is no recovery or rom for my phone, Can I extract the boot.img from my phone storage, to patch it with Magisk?
Thanks to serajr here - https://forum.xda-developers.com/showpost.php?p=75505302&postcount=2973 Go directly to that post and give thanks.
You need:
Stock O ftf (best to use Flashtool/Xperifirm)
Modded boot img for 34.4.A.2.19 - https://mega.nz/#!AgtQ2Sob!JjLRcUVjuy6FNanjGY49g-YYmkcda04witfHp4hwvmo
Modded boot img for 34.4.A.2.32 - https://mega.nz/#!Z1tzEJbZ!e9ET_RtUpKjXRwnJa_TDsMrVwvT-hPxmk06KtryHOuc
Modded boot img for 34.4.A.2.85 - https://mega.nz/#!p5UwAabR!_ofmr_WdId9RdH48Xb3cZtSIzsQ6qcTJTAFYcKHFWJE
Kernel elf file to use with rootkernel [34.4.A.2.85] - https://mega.nz/#!M102lYTZ!9bj2KE-vbNWlej3Dw0NuiXJcfpgiy16svSHud73bLfw
Modded boot img for 34.4.A.2.107 - https://mega.nz/#!Nls0EQBR!Cc4lVcA85f8YeNTo8nMqsuwLzveW5duSbyeZDlI5kDE
Kernel elf file to use with rootkernel [34.4.A.2.107] - https://mega.nz/#!Zp10CASK!iGLE94Tj1SSk1U2p4KLpVrcGmD68C3YvqKMXD6VPFjI
Modded boot img for 34.4.A.2.118 - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA
Kernel elf file to use with rootkernel [34.3.A.2.118] - https://mega.nz/#!Ylcm1SwA!GuX9dfd2HAqLXy1jom-C6mgP0s4jYXl9qSySkvb_mtA
TWRP - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
1. Flash stock ftf from Xperifirm via Flashtool
2. After flash, connect in fastboot (before booting phone) and type in command line 'fastboot flash boot boot.img' (this assumes that your modified boot img is in the current directory,and is named 'boot.img'; otherwise, you need to edit the command accordingl)
3. Then type 'fastboot flash recovery twrp-3.2.1.img' (same note as above)
Done
Now, you can flash Magisk, (or whatever), and have root access.
If you want Drm fix, flash serajr's zip here - https://forum.xda-developers.com/attachment.php?attachmentid=4404527&d=1517335127
If you want to restore your own ta with munjeni tool, you will need to patch boot img yourself with rootkernel tool here - https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
How to get stock kernel elf and patch your boot img with rootkernel:
1. Download and build stock ftf from Xperifirm via Flashtool
2. Go to Flashtool > tools > sin editor, and navigate to stock kernel sin file, in the downloaded firmware folder. Click on sin file and choose 'exrract data', and it will create a kernel elf.
3. Follow the guide by serajr. You need only to put the kernel elf into rootkernel folder, then open a command prompt there and run 'rootkernel kernel.elf boot.img'. Answer all questions 'yes', unless you want to skip drm fix and restore your own ta, (if that's the case, you need your target file in that folder renamed to TA.img). After script runs, you will have a new boot img that you can use to follow the guide.
Done...
Magisk, MicroG, and Xposed tested... (update - I haven't tried yet, but I've read that Xposed not working on ...85; update 2 - confirmed, bootloop; update 3 - Xposed fix now available here - https://forum.xda-developers.com/x-compact/themes/xposed-fix-118-t3870673)
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Can confirm the above method worked for me. I used the TA.img instead of drm fix, and i get root and security test still have widefine and fidokeys enabled.
Just slight reminder for linux user, you need to add execute permission on both `rootkernel` and `bootimg`, otherwise rootkernel tool will fail with permission issue.
levone1 said:
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Click to expand...
Click to collapse
With which options is your modified boot image prepared?
maluus said:
With which options is your modified boot image prepared?
Click to expand...
Click to collapse
Dm-verity disable - yes
Force encrypt disable - yes
Drm fix - yes
For Drm fix you still have to flash serajr zip. If you want to restore ta with munjeni tool, you will need to patch boot yourself.
Op updated for 3-click root...
SuperSU,Xposed
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
...
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
I was able :laugh::good: Xposed release link
levone1 said:
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
Click to expand...
Click to collapse
Oh, well. Thank you! It's working now.
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Stephenhs said:
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Click to expand...
Click to collapse
Can you try running the tool and creating the boot.img yourself? I use the singapore ftf and doesn't have problem booting the system (with the boot img I created myself). I do not put twrp on boot img though. I boot twrp from fastboot when needed
I created boot.img and everything works Thanks a lot!
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Kianush said:
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Click to expand...
Click to collapse
Post linked in op has special instructions for us with Xc - skip that part.
https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
hello guys, i've created a boot.img whit the tool of rootkernel whit my ta.backup but it does not work. the boot it's ok but if i chek my drm keys they say not provisioned. my ta.backup load 2.097.152 byte like the post shows. can someone help me? thanks
update:
sorry guys, i've done again the kernel patch whit my ta backup and this time goes perfect. i don't know why the first time didn't work but now it's ok!
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Wxfdswxc said:
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Click to expand...
Click to collapse
Twrp - https://forum.xda-developers.com/x-compact/development/twrp-3-2-1-decryption-t3751998
As for rebooting to system, can't say for sure... Root method involves only changing boot img, so shouldn't affect system. Any errors in fastboot, etc?
Original flash should be clean flash official stock ftf from Xperifirm. First boot could be 10 minutes...
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
cubano2031 said:
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
Click to expand...
Click to collapse
Sent from my LGE LM-X410.FGN using XDA Labs
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Rebel_X said:
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Click to expand...
Click to collapse
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
Thanks a lot!! And it was as simple as that. It works fine. :good:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
MAREK10747 said:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
Click to expand...
Click to collapse
Hi,me devie is I4293
I have unrar the rom , so i get the boot_X-FLASH-ALL-8F02.sin
would you mind to make the kernel for me?
the file is here :
https://drive.google.com/file/d/1sywqfBtELSTgRXtTBEvlI454K_1ul-1h/view?usp=sharing
my gmail is [email protected]
you can send it to me.
thank you.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
yishisanren said:
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
Click to expand...
Click to collapse
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Zaben said:
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Click to expand...
Click to collapse
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
yishisanren said:
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
Click to expand...
Click to collapse
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
wang4632 said:
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
Click to expand...
Click to collapse
older version can not patch boot.img, because when you click "install the zip",it will let you update the new verison.
Any news on the boot loop situation? I also encounterd this problem and back to running original boot.img. having an unlocked bootloader is useless without root ?
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Did you lose any feature like super vivid mode and camera focusing after unlocking the bootloader?
can't find the driver, the model is l421dual sim, can't rooting, have i already patched the boot img?
My I4293 stuck in bootloop~~help ~!
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
This phone cannot be rooted at this time due to the lack of the img.patch and no driever.
Zack_U said:
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
Click to expand...
Click to collapse
Are you still stuck? For all of the latest Sony phones try NewFlasher instead.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Flashtool doesn't support our phones. Magisk 19.1+ currently doesn't work with our phones. Hopefully 19.4 will fix that.