[MM / N] [LB] Dirtycow Temp Root Shell and Debloat Script (Freeze Unwanted Apps)

[p0kemon]

Bro... How did you manage to extract them? X Compact with locked BL, right?

trimarea.img is from Z3! I didn't found unit 1046b in trimarea.img, @DannyWilde did you restored locked trim area befere you unlocked bootloader using flash tool?

Edit:
On seccond file TA.img which is locked trim area dump I not found unit 1046b in backup partition, its not twice present like on z1 line so have no sense using flash tool unlocking method, so that confirm that we still need system user at least for dumping trim area unit 1046b trought libta.so which is realy worst case since if we get that system user at least we are so close to root user, I think wasting time with trim area hack have no sense, right?

Edit:
On @shoey63 the same thing, no backup of the unit 1046b

One more thing on z3 and on x compact found unit headers with:
1. C1 E9 F8 3B 32 32 32 34
2. C1 E9 F8 3B FF FF FF 34

and unused blocks is filled with 0x10 and some with 0x32, why that differs I realy have no idea I realy thinked it differs since some dumps is from 64 bit device, but no, it differs on z3 too which is 32 bit device. On trim area which I started working its diferent:
booth 1. & 2. is C1 E9 F8 3B FF FF FF FF and all unused blocks is filled with 0xFF. What can be happen if we reconstruct things on x comact and z3 like format which I'm working on I have no idea. I will wait somebody with broken z3 to test reconstructed trim area, until that happen I realy no want to risk somebody brick phone by this tool

Edit (sorry!):
Hey but I forgot @istux z3, on his phone we got success by reconstructing his trim area! It was in format like one which I am using and no brick happened!

 

[DannyWilde]

Sorry @serajr,
I didn't want to confuse you, TA image and backup are from z3 compact.

---------- Post added at 08:38 PM ---------- Previous post was at 08:30 PM ----------

@p0kemon,
Bootloader of z3c was never opened before. I did backup with back tool before I unlocked bootloader. I can restore and try once more. But it wouldn't change anything, right?

 

[p0kemon]

It wouldn't change anything since somehow seems its only double in my trim area, your and shoey63 's ta confirms that there is no backup of that units in locked trim area so expected is no backup in unlocked too. Thanks guys anyway! If somebody want to risk device and flash reconstructed trim area pm me please!

 

[yacloo]

i can confirm my former z3 compact's backup have double 1046b but i am not sure both keys were located separately on primary and secondary partitions
i don't have much time to confirm location of keys
it's was never unlocked and it's dead anyway

 

[DannyWilde]

Hmm, phone can be hard bricked eventually, is that right?

 

[p0kemon]

Yes! One byte is enought for hardbrick.

 

[rayman]

Full TA partition backup is now out (source will come later): http://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236

 

[sve1313]

The backup of TA is successfuly.

 

[serajr]

Full TA partition backup is now out (source will come later): http://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236

Just amazing! :good:

 

[DannyWilde]

I love to hear this!!!!! ?

 

[yacloo]

New kernel bug has been discovered maybe can be useful rooting on LB

http://seclists.org/oss-sec/2016/q4/607

Sent from my Xperia X using XDA Labs

 

[p0kemon]

I have done trimarea_tool (command line tool), and that tool nothing change in trim area dump other than unit headers (I have not implemented the rest of my tools since undocumented trim area is still undocumented and very risky is touching trim area, so I not included the rest, it will be public somedays when things gone fully tested), partition hashes and unused blocks, it cleans that 32323234 bytes and writes ffffffff instead and regenerates hashes, thats all by now. Unit data is the same. I have included ton of checks, for example if you try to modify your original ta dump, tool will not generate reconstructed trim area, if size is different, if trim area is not 0x200000 bytes long... and many more. Since we are at initial stage about trim area in general we can't know how safe is playing with trim area, @itsux is only one who flashed reconstructed trim area and reported no hard brick. I must notify you now with red words DO NOT FLASH IF YOU NO WANT TO RISK!!! THIS IS VERY DANGEROUS AND MAY HARD BRICK YOUR PHONE - MEANS KILL FOREVER!!! Use only if you have broken phone for example working phone with not working or broken screen and you no need that phone, don't flash on daily phone! Itsux is only one who tested on his Z3 phone which is with broken screen, I have modified his trim area the same way, he flashed back that trim area and reported here that his phone is not hard bricked. Again I don't know how safe things is so I am not responsible if tool kills your phone, use at your own risk!! But if you realy want to risk and probably kill your own phone please report what happened at least, it would help further development on this tool!

Download -> http://forum.xda-developers.com/crossdevice-dev/sony/dangerous-tool-trim-tool-t3516007/post70009868

 

[istux]

I have done trimarea_tool (command line tool), and that tool nothing change in trim area dump other than unit headers (I have not implemented the rest of my tools since undocumented trim area is still undocumented and very risky is touching trim area, so I not included the rest, it will be public somedays when things gone fully tested), partition hashes and unused blocks, it cleans that 32323234 bytes and writes ffffffff instead and regenerates hashes, thats all by now. Unit data is the same. I have included ton of checks, for example if you try to modify your original ta dump, tool will not generate reconstructed trim area, if size is different, if trim area is not 0x200000 bytes long... and many more. Since we are at initial stage about trim area in general we can't know how safe is playing with trim area, @itsux is only one who flashed reconstructed trim area and reported no hard brick. I must notify you now with red words DO NOT FLASH IF YOU NO WANT TO RISK!!! THIS IS VERY DANGEROUS AND MAY HARD BRICK YOUR PHONE - MEANS KILL FOREVER!!! Use only if you have broken phone for example working phone with not working or broken screen and you no need that phone, don't flash on daily phone! Itsux is only one who tested on his Z3 phone which is with broken screen, I have modified his trim area the same way, he flashed back that trim area and reported here that his phone is not hard bricked. Again I don't know how safe things is so I am not responsible if tool kills your phone, use at your own risk!! But if you realy want to risk and probably kill your own phone please report what happened at least, it would help further development on this tool!

Actually I have a faulty motherboard, that's why I took the risk
And I confirm it worked.
Dude, I think it's time you start your own thread in Sony Cross-Device General forum.
The project is good.
So, if you open a specific thread in a more general section, you have more chance to find some testers (with a Sony in the closet ready to be tortured ) and maybe more developers who can help you.
Just a suggestion...

 

[p0kemon]

You are right! I have created a new thread http://forum.xda-developers.com/crossdevice-dev/sony/dangerous-tool-trim-tool-t3516007

 

[serajr]

You are right! I have created a new thread http://forum.xda-developers.com/crossdevice-dev/sony/dangerous-tool-trim-tool-t3516007

Yeah... Sony's guys must be proud of you.

You've been doing a such incredible work around here, no doubt about it, but as istux suggested, and I can see now you just did it, more and more devs can see it over there, and probably more brave people will appear too!
Keep up the great job my friend!!

 

[serajr]

Now that we have proper tool to perform backup of TA partition, "safe" root came true (unlocking device's bootloader), and original OP's dirtycow Debloat script became deprecated (IMO)!
I'm about to release a new Debloat script (as a new thread) which will remove unwanted system apps (will backup them firstly), which can free up by at least 2.4gb internal storage!
It will require recovery, or at least root! Stay tuned!!

 

[KWOKSFUNG]

Now that we have proper tool to perform backup of TA partition, "safe" root came true (unlocking device's bootloader), and original OP's dirtycow Debloat script became deprecated (IMO)!
I'm about to release a new Debloat script (as a new thread) which will remove unwanted system apps (will backup them firstly), which can free up by at least 2.4gb internal storage!
It will require recovery, or at least root! Stay tuned!!

Can't wait for nougat Xperia Xposed from u!!

 

[serajr]

Can't wait for nougat Xperia Xposed from u!!

Nor the Xposed Framework for the nougat has been developed yet! Anyway, time will tell us!

 

[DannyWilde]

@p0kemon
I unlocked bootloader of my X compact via flashtool as you described in this tread.
I wanted to backup TA as I did with the z3 compact.
But i am not able to boot my x compact after unlocking. I am asked to enter password to start android. So i'm also not able to boot in to bootloader to flash recovery.
You got any idea what to do?

 

[DannyWilde]

Solved. Need factory reset after unlock.