[PoC][Work in progress] Trim Area Proof Of Concept

RaXelliX · May 11, 2017

S1gma said:
If you have bootloader unlocked, maybe flash recovery using fastboot and leave kernel without recovery integrated?

realtuxen said:
As said above why not just flash recovery to fotakernel (fastboot flash recovery twrp.img) and leave it out from kernel? To get into TWRP press power+vol untill phone turns on. That will work fine and you won't have to rely on kernel and recovery image is compatible every time there is an update to either one. Just exclude fotakernel in flashtool when updating and recovery won't be overwritten, or you will have to fastboot flash recovery again.

As another example you don't even need to flash recovery, it can also be booted with 'fastboot boot twrp.img' by now getting into recovery and get root should be the least of your problem.

Sorry for sidetracking the thread.

Nope no luck. I tried many combinations to get things working including all suggested. I even flashed both the working recovery and working (older kernel by androplus). Then went into recovery and flashed the PoC created stock kernel from there. Upon reboot recovery stopped working. No led during boot, no reaction to pressing vol key but phone itself booted to system.

So whatever makes this revovery work is some special sauce androplus has baked into his kernel and obviously the PoC version is missing this. Just dunno what that something is. Here's the thread: https://xdaforums.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685
And notes:

Advanced stock kernel
-For 34.1.A.1.198
-ric, dm-verity disabled
-DRM patch from tobias.waldvogel
-SELinux Permissive
-Load recovery from recovery (FOTAKernel) partition

So i assume PoC is doing almost the same exept DRM fix wich is unnessesary and SELinux Permissive wich would only work for Marshmallow if i read munjeni's answer correctly. I assume PoC also loads recovery from FOTAKernel if i choose to include it?

realtuxen · May 11, 2017

No poc does not load from fotakernel if you include it. I think you misunderstand. Fotakernel location and poc boot.img have nothing to do with each other. The point was to leave recovery out from poc and use fotakernel to load recovery instead. You do not wait for led to come to enter recovery in fotakernel.

fastboot flash boot pocboot.img
fastboot flash recovery androplustwrp.img

Again leave recovery out from pocboot.img and when you need to enter recovery hold volume down key and power button until recovery appears.

Is this what you did?

shoey63 · May 12, 2017

munjeni said:
Added support for latest devices e.g. XZS so Z5 will work too

Getting this on Z5 mm

Code:

-------------------------------------------------------
             Xperia Command Line Flasher               
                                                       
                 by Munjeni @ 2014-2017                     
-------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_adde#5&3879604a&0&5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: Universal Serial Bus controllers
Device Instance Id: USB\VID_0FCE&PID_ADDE\5&3879604A&0&5

Timeout happened!

Edit: Haven't tried on N, don't want N on this device. I have z, z3, z5 and X:silly:

RaXelliX · May 12, 2017

realtuxen said:
No poc does not load from fotakernel if you include it. I think you misunderstand. Fotakernel location and poc boot.img have nothing to do with each other. The point was to leave recovery out from poc and use fotakernel to load recovery instead. You do not wait for led to come to enter recovery in fotakernel.

fastboot flash boot pocboot.img
fastboot flash recovery androplustwrp.img

Again leave recovery out from pocboot.img and when you need to enter recovery hold volume down key and power button until recovery appears.

Is this what you did?

I held down vol down. I did'nt try vol down+power. Aside from that that was one of the ways i flashed yes.

realtuxen · May 12, 2017

RaXelliX said:
I held down vol down. I did'nt try vol down+power. Aside from that that was one of the ways i flashed yes.

Well that's it then. You need to turn on the phone by holding power and vol - untill recovery you flashed to fotakernel with 'fastboot flash recovery twrp.img' appears. You do not wait for any led to turn on in any color. That is for recovery in poc boot.img that you should just leave out because of compability.

munjeni · May 12, 2017

shoey63 said:

Getting this on Z5 mm

Code:

-------------------------------------------------------
             Xperia Command Line Flasher               
                                                       
                 by Munjeni @ 2014-2017                     
-------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_adde#5&3879604a&0&5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: Universal Serial Bus controllers
Device Instance Id: USB\VID_0FCE&PID_ADDE\5&3879604A&0&5

Timeout happened!

Edit: Haven't tried on N, don't want N on this device. I have z, z3, z5 and X:silly:

Thanks! Can we move to xflasher thread? Did your device loader.sin capable and which configuration you use, loader.sin or noloader? Can you post xflasher.bat which you used?

Andrzej_Andrzej · May 13, 2017

constant bootloop

Hi munjeni,
Ja have learnt a bit about android and adb. I have done ta_poc with a few kernels, boot.img(s).
So far no success. New_boot.img creation always went properly. When I flash it with fastboot I always got a bootloop. This is constant bootloop on sony logo. I assume that in order to take proper last_kmsg I need to connect to pc with adb, but when phone is in bootloop the only mode available is fastboot mode. So I tried (I don't know if it is correct) reboot to recovery and take this last_kmsg from recovery. But when I did that I received an error: fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.502s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 0.515s

I read a guide about bootloop in here: https://xdaforums.com/showthread.php?t=2426426 and it says: " Using ADB BY Samantha
DB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the manufacturer logo. (In new CWM versions it’s possible to use adb)
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is different from every device, but normally it’s after the manufacturer logo that the partitions get mounted. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
I use this script for example, called ondemand.bat (requires adb.exe and the 2 dlls)"

But this script is helpful when CWM is installed, but I have TWRP.

So I do not give up trying and learning but if you could advise me what to do and how to take that last_kmsg in spite of these obstacles described above.

regards,

levone1 · May 13, 2017

Andrzej_Andrzej said:
Hi munjeni,
Ja have learnt a bit about android and adb. I have done ta_poc with a few kernels, boot.img(s).
So far no success. New_boot.img creation always went properly. When I flash it with fastboot I always got a bootloop. This is constant bootloop on sony logo. I assume that in order to take proper last_kmsg I need to connect to pc with adb, but when phone is in bootloop the only mode available is fastboot mode. So I tried (I don't know if it is correct) reboot to recovery and take this last_kmsg from recovery. But when I did that I received an error: fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.502s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 0.515s

I read a guide about bootloop in here: https://xdaforums.com/showthread.php?t=2426426 and it says: " Using ADB BY Samantha
DB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the manufacturer logo. (In new CWM versions it’s possible to use adb)
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is different from every device, but normally it’s after the manufacturer logo that the partitions get mounted. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
I use this script for example, called ondemand.bat (requires adb.exe and the 2 dlls)"

But this script is helpful when CWM is installed, but I have TWRP.

So I do not give up trying and learning but if you could advise me what to do and how to take that last_kmsg in spite of these obstacles described above.

regards,

Unlock bootloader

Andrzej_Andrzej · May 13, 2017

levone1 said:
Unlock bootloader

My bootloader is unlocked.

levone1 · May 13, 2017

Andrzej_Andrzej said:
My bootloader is unlocked.

Ok... Just checking.

oSandmaNo · May 13, 2017

Hello, how does this work exactly? I created new boot image with my TA backup. Flashed it after flashing Stock 291 Mm on my z3. Camera is still showing lot of noise. But x reality and clear audio is present.

I have attached screenshot of the security test menu. Do I have to lock the bootloader?

x_one · May 13, 2017

oSandmaNo said:
Hello, how does this work exactly? I created new boot image with my TA backup. Flashed it after flashing Stock 291 Mm on my z3. Camera is still showing lot of noise. But x reality and clear audio is present.

I have attached screenshot of the security test menu. Do I have to lock the bootloader?

Flash kernel without tapoc and you will see the difference.
With tapoc you have drm key as with locked broader.

oSandmaNo · May 13, 2017

x_one said:
Flash kernel without tapoc and you will see the difference.
With tapoc you have drm key as with locked broader.

Yes, I was on unlocked bootloader, but camera is same after tapoc. That's what I'm asking. Is there anything left for me to do?

fluffi444 · May 13, 2017

oSandmaNo said:
Hello, how does this work exactly? I created new boot image with my TA backup. Flashed it after flashing Stock 291 Mm on my z3. Camera is still showing lot of noise. But x reality and clear audio is present.

I have attached screenshot of the security test menu. Do I have to lock the bootloader?

fluffi444 said:
Delete
/data/credmgr
/data/DRM
/data/mediadrm
And reboot

EDIT
And don't be afraid to do so.
Those data will be re-created after reboot but now with new DRM data from your original TA.img.

Try this.

Otherwise your TA.img is not ok or already not original anymore.

x_one · May 13, 2017

oSandmaNo said:
Yes, I was on unlocked bootloader, but camera is same after tapoc. That's what I'm asking. Is there anything left for me to do?

I see coupe errors on your screenshot. I think you need clear drm cert db and reboot. You should have all keys ok.

Delete
/data/credmgr
/data/DRM
/data/mediadrm
And reboot

EDIT
And don't be afraid to do so.
Those data will be re-created after reboot but now with new DRM data from your original TA.img.

fluffi444 · May 13, 2017

LOL. That was in the same second.

x_one · May 13, 2017

fluffi444 said:
LOL. That was in the same second.

Yeah.. But using phone is hard to find earlier posts and quote them

fluffi444 · May 13, 2017

x_one said:
Yeah.. But using phone is hard to find earlier posts and quote them

WTF! I did exactly the same! Again LOL!

oSandmaNo · May 13, 2017

Thanks both of you. Unfortunately I'm already in bed now . Have two exams tomorrow

I will give this a try tomorrow

Cheers

EDIT: woke up early to try this out. Seems as though it's working as ISO goes up to 12800 now. But the security test still shows as unknown error like in my previous screenshot. :/

EDIT2: ISO does reach 12800 but noise reduction is terrible. It doesn't exist even. I think my TA backup is screwed

munjeni · May 14, 2017

oSandmaNo said:
Thanks both of you. Unfortunately I'm already in bed now . Have two exams tomorrow
I will give this a try tomorrow

Cheers

EDIT: woke up early to try this out. Seems as though it's working as ISO goes up to 12800 now. But the security test still shows as unknown error like in my previous screenshot. :/

EDIT2: ISO does reach 12800 but noise reduction is terrible. It doesn't exist even. I think my TA backup is screwed

Your picture confirms that poc sucesfully mounted ta but your ta is definitelly from unlocked bootloader, you can also see that in poc log.

[PoC][Work in progress] Trim Area Proof Of Concept

Senior Member

Senior Member

Recognized Contributor

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts