Develop Bugs

/Possible brick?/ Problems Unbricking

What does a SE Xperia play brick look and feel like? I may have bricked... no fastboot, when i hold the power button, i get bursts of vibration (similar to the one when you DO actually turn it on) and it doesn't actually turn on.

http://androidflip.com/unbrick-xperia-play-flashtool-step-step-guide/
I Decided to use this to unbrick and everything downloaded fine. the PROBLEM is that when i get to the part where i flash the system, it gives me this:
Code:
27/018/2011 18:18:47 - INFO - <- This level is successfully initialized
27/019/2011 18:19:05 - INFO - Preparing files for flashing
27/019/2011 18:19:09 - INFO - Searching Xperia....
27/019/2011 18:19:09 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&2F64E158&0&4
27/019/2011 18:19:09 - INFO - Start Flashing
27/020/2011 18:20:15 - INFO -
27/020/2011 18:20:15 - INFO - Flashing loader
27/020/2011 18:20:15 - ERROR - Error flashing. Aborted
27/020/2011 18:20:15 - INFO - Now unplug the device and power it on
27/020/2011 18:20:15 - INFO - Then go to application settings
27/020/2011 18:20:15 - INFO - turn on Unknown Sources and Debugging
THIS is a problem, because my "device" is unable to turn on. Options?

Are you using flashtool beta version 0.2.9.1?
Have you installed ggsetuo.exe (drivers that came with flashtool)?
Are you using a compatible ftf file for your phone?
Regards Dousan...

Just following the tutorial. The FTF was said to be the generic one for the Xperia Play. For drivers, I don't remember if i installed them last time, but my SEXP was recognised so i would think that i did. I'll try to install them and see if that does anything. Flashtool version: unknown. I'll check.

Wich model do you have R800i/a/at/x.
Afaik the x and at models are not compatible with the UK generic FW. One dude got the UK generic to work on a x model by doing alot of tweaking, but otherwise non.
It could be that you connect your device to early and it times out before it starts flashing?
Maybe you can restore with SEUS?
Regards Dousan...

I have R800x. Where would I be able to find a compatable ftf file?

I may have found the stock R800x FTF http://forum.xda-developers.com/showthread.php?t=1201725

brainard52 said:
I may have found the stock R800x FTF http://forum.xda-developers.com/showthread.php?t=1201725
Click to expand...
Click to collapse
Yes thats the one, you'll need the 'full system' ftf. It states that your bootloader will relock when flashing this file, but you should restore 100%.
So you'll need to go through unlocking and rooting again if you want that.
If you want to go to 2.3.3 i think you have to opdate to 2.3.3 before unlocking your bootloader or else you end up with a brick. Then unlock and root or you might be able to unlock/root/relock/update OTA in that order? I don't know for sure how the R800x works as it's slightly different than my R800i.
As stated I'm not 100% sure on the procedure for updating and rooting when you've flashed the 'full system' file, so ask about it in the thread you linked to or there might be a thread about it in the dev section.
Regards Dousan...

Awesome. Now, the file I downloaded is 236498950 bytes, or 225.5 MB. aproximately how long will the flashing take, and what message will i receive after it IS finished?

brainard52 said:
Awesome. Now, the file I downloaded is 236498950 bytes, or 225.5 MB. aproximately how long will the flashing take, and what message will i receive after it IS finished?
Click to expand...
Click to collapse
I'm not sure haven't timed it, but would say around 3-5 min. and the flashing will end with the same thing as when you got an error (flashing system.sin takes the longest afaik, sometimes i've thought it's stalled lol) :
Code:
27/020/2011 18:20:15 - INFO - Now unplug the device and power it on
27/020/2011 18:20:15 - INFO - Then go to application settings
27/020/2011 18:20:15 - INFO - turn on Unknown Sources and Debugging
The file size sound about right since your FW is stripped from SE stuff
Regards Dousan...

I got it fixed. It took about two seconds to fix. Titanium backup helped me out a lot.
Sent from my R800x using XDA App

Error when rooting phone FTError

I just flashed to LT15i_4.0.2.A.0.62_Generic Global World and when I use flashtools to uroot I get
05/007/2012 02:07:52 - INFO - <- This level is successfully initialized
05/007/2012 02:07:52 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
05/007/2012 02:07:52 - INFO - You can drag and drop ftf files here to start flashing them
05/007/2012 02:07:57 - INFO - Device connected with USB debugging on
05/008/2012 02:08:00 - INFO - Connected device : LT15
05/008/2012 02:08:00 - INFO - Installed version of busybox : N/A
05/008/2012 02:08:00 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
05/008/2012 02:08:01 - INFO - Pushing C:\Flashtool\.\devices\LT15\busybox\1.19.0\busybox to /data/local/tmp/busybox
05/008/2012 02:08:03 - INFO - Pushing C:\Flashtool\.\custom\root\zergrush.tar.uue to /data/local/tmp
05/008/2012 02:08:04 - INFO - Running part1 of Root Exploit, please wait
05/008/2012 02:08:26 - INFO - Waiting for device
05/009/2012 02:09:26 - INFO - Forced stop waiting.
05/009/2012 02:09:26 - INFO - Running part2 of Root Exploit
05/009/2012 02:09:26 - INFO - Running rootit2
05/009/2012 02:09:27 - ERROR - Cleaning rootit files
Mounting /system R/W
FTError

.62 can't be rooted by any method yet. Either flash a pre-rooted kernel if you have an unlocked bootloader, if not flash.42, root then ota update.

sinkster said:
.62 can't be rooted by any method yet. Either flash a pre-rooted kernel if you have an unlocked bootloader, if not flash.42, root then ota update.
Click to expand...
Click to collapse
I have a locked bootloader. I flashed .42, rooted it, but OTA still failed.

If you keep attempting the ota then it will eventually complete, apparently.

See my post here:
http://forum.xda-developers.com/showpost.php?p=23285407&postcount=15

sinkster said:
If you keep attempting the ota then it will eventually complete, apparently.
Click to expand...
Click to collapse
Yes it did.

hi mate, if you are on 0.62, then just flash an old kernel using flashtool and then you would be able to root 0.62 as well
or have a look at this
http://talk.sonymobile.com/message/142493#142493

OFFICIAL UPDATED Flashtool 0.9.13.0 for ALL XPERIA (Windows)

Latest Flashtool 0.9.13.0 for ALL XPERIA (Windows)
Windows Edition - v0.9.11.0 - MD5 : A0F880F3CF420A31D86026F49A2013D7
Updated on 12/06/2013 ©2011 by Androxyde
More information at http://androxyde.github.com/
Flashtool Release Notes:
* 0.9.13
This version is a big split with every previous ones.
And not fully featured as previous can be.
I changed the UI framework from Swing to SWT because of a better integration with Mac UI.
Here is what is missing from previous releases :
- No multilingual UI
- No recovery installer
- No kernel installer (for 2010 devices)
- No ROM cleaner.
- Cannot Add/Edit/Remove devices.
No TA hex editor (in pro mode)
Version fully compatible with all 2013 devices (Z1/Z Ultra/Tablet Z etc etc)
Unified Bootloader unlock feature with the new BLU icon. No more unlock plugin.
As for flashing, BLU is available even without any connected device, even with
unrecognized devices.
Updated SuperSU package. Added servicemnu root hack
(works with Z1/Z Ultra)
Known working for Xperia T/V too
Added TA partition backup/restore. Using this feature, you can backup TA before unlock.
Restore TA will relock the devicee and get DRM back as well as BE2
(full complete relock). You cannot count on this feature if ever your device is
already unlocked. Missuse of this feature can brick the device
Introduction to Flashtool:
Flashtool is a flashing software that can be used to :
1. Flash original Images (Android 1.6, 2.1, 2.3 Images)
2. Root your phone
3. Install Recovery, Busybox, custom kernels
4. Clean your Rom (remove /system/apps apps of your choice)
(Be careful, unless you really know what you do, do not modify the default list.
This can make your phone stuck at the SE Logo)
5. Clear dalvik cache
6. Optimize (install of JIT v2)
(Disabled in 0.4, will readd it as a plugin for 2.1 phones only)
7. Customize (installs apps found in the custom/apps folder of the flashtool)
8. Clean uninstalled (remove any references to system apps removed in the
Clean (root needed) step)
9. Edit any text file on the device
10. Rebrand your device
Download Link
https://mega.co.nz/#!d4lx1bZQ!Ltt8Bw...Rvh0Z2ZMl-kCn0
Thanks for mirror @marco.it
FAQ.
Q : Can Flashtool unlock bootloader for a first time unlock ?
A : Yes, it does it using official sony method (get key, then issue the right fastboot command)
Q : Can Flashtool relock bootloader ?
A : Yes
Q : Can Flashtool unlock bootloader after a relock ?
A : Yes.
With this release, before unlocking first time, root your device and you will be able to backup your TA partition (Raw ta backup). By doing this, you will be able to relock / restore your TA partition and have back BE2 and all DRM keys.
Happy flashing
HIT THANKS BUTTON IF IT HELPED

majeed619 said:
Latest Flashtool 0.9.11.0 for ALL XPERIA (Windows)
Windows Edition - v0.9.11.0 - MD5 : A0F880F3CF420A31D86026F49A2013D7
Updated on 12/06/2013 ©2011 by Androxyde
More information at http://androxyde.github.com/
Flashtool Release Notes:
* 0.9.11
This version is a big split with every previous ones.
And not fully featured as previous can be.
I changed the UI framework from Swing to SWT because of a better integration with Mac UI.
Here is what is missing from previous releases :
- No multilingual UI
- No recovery installer
- No kernel installer (for 2010 devices)
- No ROM cleaner.
- Cannot Add/Edit/Remove devices.
No TA hex editor (in pro mode)
Version fully compatible with all 2013 devices (Z/ZL/Tablet Z etc etc)
Unified Bootloader unlock feature with the new BLU icon. No more unlock plugin.
As for flashing, BLU is available even without any connected device, even with
unrecognized devices.
Updated SuperSU package. Added servicemnu root hack
(works with Z/ZL for all FW up to .434)
Known working for Xperia T/V too
Added TA partition backup/restore. Using this feature, you can backup TA before unlock.
Restore TA will relock the devicee and get DRM back as well as BE2
(full complete relock). You cannot count on this feature if ever your device is
already unlocked. Missuse of this feature can brick the device
Introduction to Flashtool:
Flashtool is a flashing software that can be used to :
1. Flash original Images (Android 1.6, 2.1, 2.3 Images)
2. Root your phone
3. Install Recovery, Busybox, custom kernels
4. Clean your Rom (remove /system/apps apps of your choice)
(Be careful, unless you really know what you do, do not modify the default list.
This can make your phone stuck at the SE Logo)
5. Clear dalvik cache
6. Optimize (install of JIT v2)
(Disabled in 0.4, will readd it as a plugin for 2.1 phones only)
7. Customize (installs apps found in the custom/apps folder of the flashtool)
8. Clean uninstalled (remove any references to system apps removed in the
Clean (root needed) step)
9. Edit any text file on the device
10. Rebrand your device
Download Link
http://sdrv.ms/ZJN81O
HIT THANKS BUTTON IF IT HELPED
Click to expand...
Click to collapse
THANK YOU! Every link I was finding was around a 45 min download!

thanks for the link.. i hope that i finally can unbrick my ZQ -.- he's stucked in Sony logo

http://postimg.org/image/jnx079uwd/
I have problem downloading flashtool driver of xperia arc s
As you can see I attached picture.

Bassheadzero said:
thanks for the link.. i hope that i finally can unbrick my ZQ -.- he's stucked in Sony logo
Click to expand...
Click to collapse
Just simply flash the compatible ftf file for your device using flashtool
Your phone will be fine I faced the same issue few weeks back

sanjulgupta said:
Just simply flash the compatible ftf file for your device using flashtool
Your phone will be fine I faced the same issue few weeks back
Click to expand...
Click to collapse
Oh many thanks mate, I already get solved this problem flashing a ftf fw!
Cherrs!

This may be a dumb question, but I'll ask it anyways.
I have an Xperia ZL that was purchased from bell. I know it has a locked bootloader that cannot be unlocked through the official Sony tool, so i'm wondering if it can be unlocked with this flashtool?
If so that would be awesome.
If not, I'll be supremely unimpressed with Sony.
Sent from my C6506 using xda premium

Folder is empty! Kindly re-upload.

I agree

Folder is empty

Hey guys, after some serious digging, I found it here. http://www.flashtool.net/download.html

-NM

stevessvt said:
Hey guys, after some serious digging, I found it here. http://www.flashtool.net/download.html
Click to expand...
Click to collapse
not a valid windows 32 application.

alex4659 said:
not a valid windows 32 application.
Click to expand...
Click to collapse
Really? Did you try this version of it?
Windows Edition : v0.9.11.0 – MD5 : A0F880F3CF420A31D86026F49A2013D7
It worked just fine for me and several others.

Folder is empty , Kindly reupload and update the links

stevessvt said:
Really? Did you try this version of it?
Windows Edition : v0.9.11.0 – MD5 : A0F880F3CF420A31D86026F49A2013D7
It worked just fine for me and several others.
Click to expand...
Click to collapse
yes i did.
im using parallels desk top for mac so im downloading it for my macbook pro as well.
you dont by chance have a direct link to a ftf to a pre rooted firmware (i think gingerbread) for the xperia x10s do you?
thanks again,
Alex
---------- Post added at 08:47 PM ---------- Previous post was at 08:39 PM ----------
this is what i get when i try to flash the kernel-4.3-v21.ftf:
Note, my phone is stuck at the sony ericsson screen
27/044/2013 20:44:23 - INFO - <- This level is successfully initialized
27/044/2013 20:44:23 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
27/044/2013 20:44:23 - INFO - libusb version 1.0.15
27/044/2013 20:44:27 - INFO - Device disconnected
27/044/2013 20:44:39 - INFO - Selected es209ra / 21 / 4.3.X
27/044/2013 20:44:39 - INFO - Preparing files for flashing
27/044/2013 20:44:39 - INFO - Please connect your device into flashmode.
27/044/2013 20:44:49 - INFO - Device connected in flash mode
27/044/2013 20:44:50 - INFO - Opening device for R/W
27/044/2013 20:44:50 - INFO - Device connected in flash mode
27/044/2013 20:44:50 - INFO - Device ready for R/W.
27/044/2013 20:44:50 - INFO - Reading device information
27/044/2013 20:44:50 - INFO - Phone ready for flashmode operations.
27/044/2013 20:44:51 - INFO - Current device : X10i - CB511PDEG8 - 1241-1846_R1C - 1227-4612_3.0.1.G.0.75 - WORLD-1-4-8_3.0.1.G.0.75
27/044/2013 20:44:51 - INFO - Start Flashing
27/044/2013 20:44:51 - INFO - Processing loader
27/044/2013 20:44:51 - INFO - Checking header
27/044/2013 20:44:51 - INFO - Ending flash session
27/044/2013 20:44:51 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
27/044/2013 20:44:51 - ERROR - Error flashing. Aborted
27/044/2013 20:44:51 - INFO - Device connected in flash mode
27/044/2013 20:44:53 - INFO - Device disconnected
27/044/2013 20:44:55 - INFO - Device connected in flash mode
27/044/2013 20:44:59 - INFO - Device disconnected
---------- Post added at 08:47 PM ---------- Previous post was at 08:47 PM ----------
SnakeEyesNinja said:
Folder is empty , Kindly reupload and update the links
Click to expand...
Click to collapse
dito

Mega.co.nz mirror:
https://mega.co.nz/#!d4lx1bZQ!Ltt8BwMnkRTWPUNzZDwZ7AzIDaEGLRvh0Z2ZMl-kCn0

with this version of Flash tool i'm not seeing a xperia ion option. Is there another phone that is identical to mine within those options?

montrese04 said:
with this version of Flash tool i'm not seeing a xperia ion option. Is there another phone that is identical to mine within those options?
Click to expand...
Click to collapse
HOPE IT WORKS :good:
http://forum.xda-developers.com/showthread.php?t=1812168

ERROR SIN verification failed
I have a question about flashtool 0.9.13.0:
What does mean 'SIN verification failed'? Is there a problem in the ftf file itself, in the configuration of flashtool or between ftf file and phone (baseband, bootloader, etc)?
Thanks for any hints,
Alexej

[Q] Flashtool stuck at "Reading device information"

Hi folks,
I'm trying to flash the latest firmware using flashtool, but it doesn't get any further than "Reading device information".
I've disabled driver signing checking and installed the flashtool, fastboot, z1 compact and common drivers for Rhine board devices. (I couldn't find anything else relevant)
I ran check drivers in flashtool and that seems ok. I'm using flashtool 0.9.16.1
Here's the log:
28/005/2014 00:05:23 - INFO - Flashtool Version 0.9.16.1 built on 06-16-2014 23:00:00
28/005/2014 00:05:23 - INFO - Executing search strategies to find proxy selector
28/005/2014 00:05:24 - INFO - No proxy found for IE. Trying next one
28/005/2014 00:05:24 - ERROR - Error parsing settingsprefs.js (The system cannot find the file specified)
28/005/2014 00:05:24 - INFO - Strategy firefox failed trying next one : java.io.FileNotFoundException: prefs.js (The system cannot find the file specified)
28/005/2014 00:05:24 - INFO - No proxy found for java. Trying next one
28/005/2014 00:05:24 - INFO - Syncing devices from github
28/005/2014 00:05:24 - INFO - Pulling changes
28/005/2014 00:05:24 - INFO - Devices sync finished.
28/005/2014 00:05:29 - INFO - Device connected in flash mode
28/005/2014 00:05:33 - INFO - List of connected devices (Device Id) :
28/005/2014 00:05:33 - INFO - - USB\VID_0FCE&PID_ADDE\7&FBF12B9&0&4 Driver installed : true
28/005/2014 00:05:33 - INFO - List of ADB devices :
28/005/2014 00:05:34 - INFO - - none
28/005/2014 00:05:34 - INFO - List of fastboot devices :
28/005/2014 00:05:34 - INFO - - none
28/006/2014 00:06:02 - INFO - Selected Bundle for Sony Xperia Z1 Compact (D5503). FW release : 14.4.A.0.108. Customization : DE
28/006/2014 00:06:02 - INFO - Preparing files for flashing
28/006/2014 00:06:13 - INFO - Please connect your device into flashmode.
28/006/2014 00:06:14 - INFO - Opening device for R/W
28/006/2014 00:06:14 - INFO - Reading device information
Anyone have an idea how to coerce this to work?

Are you on factory firmware now? If so try the Sony PC companion software.

mr mystery said:
Are you on factory firmware now? If so try the Sony PC companion software.
Click to expand...
Click to collapse
I'm on official Sony firmware. I'll give Sony PC companion a go now.
I thought I was not supposed to use it anymore since the phone's been rooted, at least none of the guides mention using the Sony tool.
But heck, if flashtool doesn't work I don't see what option I have really.
What I was trying to flash with flashtool was the firmware that Sony PC companion downloaded, then I decrypted it and created an ftf file from it.

For what it's worth - flashing with Sony PC Companion works fine, no need for flashtool.
Easy Root Toolkit v7 has restored root, and lockeddualrecovery beta installer 128 works fine.
129 reboots into a stuck Sony logo, so there's obviously an issue there, it seems that PhilZ recovery in that zip is buggy.
Now I'm back to normal. Still have no idea how to make flashtool work, and I would like to find out for when the next release is out.
Any help would be appreciated!

I had the same problem that you did. When you install the flashtool drivers make sure you install the flashmode, adb and z1 compact drivers. If your on windows 8 there's a process you need to do before you install the unsigned drivers.
In the flashtool FTF folder ensure your FTF is in there and if there are any other folders in there delete them as they are from the failed flash and flash tool will automatically refer to that folder every time you try and use flashtool.
Turn off your phone.
Run flashtool. I used the normal one not the x64 one.
Click Lightning icon.
Select firmware.
Flash and follow instructions.
I also forgot, make sure your computer doesnt go to sleep or turn its screen off while flashing as it will most likely fail again.
Sent from my D5503 using XDA Free mobile app

That's exactly what I've done, but it's not working. I'm on Server 2012, but for all intents and purposes it's same as Windows 8.
I went to disable driver signature checking and installed the following drivers from the pack:
flashtool
fastboot
z1 compact
common drivers for Rhine board devices
Are there any other drivers required for this?
Adb works fine, I believe those drivers came with Sony PC companion and I can use Easy Root Toolkit and stuff like that.
Also, assuming I can't get this to work - is it possible to get a flashable zip file from the ftf file - one that I could flash using PhilZ recovery?

The above mentioned advice does not work...stuck at reading information still...

TheNakedMam said:
The above mentioned advice does not work...stuck at reading information still...
Click to expand...
Click to collapse
Any luck with this? I'm having the same issue with my E2306. I have TWRP but i formated System, Cache, Data, Internal and ART partitions. I installed a beta 7.1.1 ROM which is missing features like Camera and Audio. Trying to restore Pexo ROM but the phone wont stay in fastboot mode nor is it recognized by fastboot devices.

Possible marshmallow root with locked boot-loader?

(not sure what thread to put it in)
I doubt this will work but i was using sony mobile flasher by androxyde and so my phone came up with root denied so I clicked on the root section and tried them all didn't work until i clicked on service menu and I got this
03/047/2016 19:47:53 - INFO - Pushing C:\Users\Myname\.flashTool\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\su to /data/local/tmp/su
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\Superuser.apk to /data/local/tmp/Superuser.apk
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\install-recovery.sh to /data/local/tmp/install-recovery.sh
03/047/2016 19:47:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\99SuperSUDaemon to /data/local/tmp/99SuperSUDaemon
03/047/2016 19:47:55 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\onload.sh to /data/local/tmp/
03/047/2016 19:47:55 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\getroot.sh to /data/local/tmp/
03/047/2016 19:47:55 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\install-recovery.sh to /data/local/tmp/
03/048/2016 19:48:13 - INFO - Look at your phone. Choose Service Test, then Display.
03/048/2016 19:48:13 - INFO - Waiting for uevent_helper rw
03/048/2016 19:48:15 - INFO - Device connected with USB debugging on
03/048/2016 19:48:16 - INFO - Connected device : Sony Xperia M5
03/048/2016 19:48:16 - INFO - Installed version of busybox : N/A
03/048/2016 19:48:16 - INFO - Android version : 6.0 / kernel version : 3.10.72+ / Build number : 30.2.A.1.21
03/048/2016 19:48:16 - INFO - Root access denied
03/048/2016 19:48:19 - INFO - Waiting for rooted shell
03/048/2016 19:48:20 - INFO - Root achieved. Installing root files. Device will reboot. Please wait.
03/048/2016 19:48:20 - INFO - Pushing C:\Flashtool\custom\root\ServiceMenu\installsu.sh to /data/local/tmp/
but I just hard bricked my phone and just got it back so I don't want to try it but if anyone is willing to try that would be great

It's simple: starting with Marshmallow update, Xperia M5 now have verified boot (dm-verity) enabled, just like all other Xperia devices from 2015 and onwards (some older Xperia devices also got dm-verity through a firmware update). That means it doesn't matter if you find a working exploit or not, modifying a single byte of the system partition will simply fail dm-verity checks and as result your phone won't boot (that's apparently what happened to your phone, you managed to modify the system partition and as result it refused to boot). No write access to system partition means no way to install su binary and other required files.
In other words, the ages of root with a locked bootloader are gone, unlocking the bootloader (so you can flash a modified kernel with dm-verity disabled or a systemless root solution) is the only way to get root now.

mbc07 said:
It's simple: starting with Marshmallow update, Xperia M5 now have verified boot (dm-verity) enabled, just like all other Xperia devices from 2015 and onwards (some older Xperia devices also got dm-verity through a firmware update). That means it doesn't matter if you find a working exploit or not, modifying a single byte of the system partition will simply fail dm-verity checks and as result your phone won't boot (that's apparently what happened to your phone, you managed to modify the system partition and as result it refused to boot). No write access to system partition means no way to install su binary and other required files.
In other words, the ages of root with a locked bootloader are gone, unlocking the bootloader (so you can flash a modified kernel with dm-verity disabled or a systemless root solution) is the only way to get root now.
Click to expand...
Click to collapse
I bricked my phone because I'm an idiot not because of that and I was on lollipop when I did it

"Hard bricked and got it back" - HOW?????
ih8redsn0w said:
(not sure what thread to put it in)
... but I just hard bricked my phone and just got it back ...
Click to expand...
Click to collapse
Hi there, this quote is extremely interesting!
What do you mean with "just got it back"? Got it back to booting...? Or got it back from a warranty repair?
Please let us know what we have to do to get our's back too... I hard bricked mine and don't seem to find a way to unbrick it. And more of us with the same problem are out there... THANKS indeed!