Q and A for [KERNEL][SGP712/SGP771] AndroPlusKernel v13

[IlariJ]

Yes, that sounds like a plan to me ... that just confirmed me that it's probably re-locked.

Ok, so I tried to re-unlock. Here's the log:

10/050/2016 07:50:18 - INFO - Flashtool Version 0.9.19.10 built on 04-10-2015 21:00:00
10/050/2016 07:50:18 - INFO - Executing search strategies to find proxy selector
10/050/2016 07:50:18 - INFO - No proxy found for IE. Trying next one
10/050/2016 07:50:18 - INFO - Strategy firefox failed trying next one : No Firefox installation found
10/050/2016 07:50:18 - INFO - No proxy found for java. Trying next one
10/050/2016 07:50:18 - INFO - Syncing devices from github
10/050/2016 07:50:18 - INFO - Scanning devices folder for changes.
10/050/2016 07:50:22 - INFO - Pulling changes from github.
10/050/2016 07:50:23 - INFO - Devices sync finished.
10/050/2016 07:50:27 - INFO - Device disconnected
10/050/2016 07:50:44 - INFO - Device connected in fastboot mode
10/051/2016 07:51:07 - INFO - Please connect your device into flashmode.
10/051/2016 07:51:15 - INFO - Device disconnected
10/051/2016 07:51:22 - INFO - Device connected in flash mode
10/051/2016 07:51:23 - INFO - Opening device for R/W
10/051/2016 07:51:23 - INFO - Reading device information
10/051/2016 07:51:24 - INFO - Phone ready for flashmode operations.
10/051/2016 07:51:24 - INFO - Opening TA partition 2
10/051/2016 07:51:24 - INFO - Current device : SGP771 - CB5A26F9ZR - 1295-7869_R13A - 1292-0698_28.0.A.8.260 - GENERIC_28.0.A.8.260
10/051/2016 07:51:24 - INFO - Closing TA partition
10/051/2016 07:51:24 - INFO - Processing loader.sin
10/051/2016 07:51:24 - INFO - Checking header
10/051/2016 07:51:25 - INFO - Flashing data
10/051/2016 07:51:25 - INFO - Loader : S1_Root_f936 - Version : MSM8994_41 / Boot version : S1_Boot_MSM8994_LA1.2_110 / Bootloader status : NOT_ROOTABLE
10/051/2016 07:51:25 - INFO - Max packet size set to 4096K
10/051/2016 07:51:25 - INFO - Opening TA partition 2
10/051/2016 07:51:25 - INFO - Start Reading unit 000008B2
10/051/2016 07:51:25 - INFO - Reading TA finished.
10/051/2016 07:51:25 - INFO - Closing TA partition
10/051/2016 07:51:25 - INFO - Unlock code saved to C:\Users\Ilari\.flashTool\registeredDevices\CB5A26F9ZR\ulcode.txt
10/051/2016 07:51:33 - INFO - Ending flash session
10/051/2016 07:51:33 - INFO - You can now unplug and restart your device
10/051/2016 07:51:34 - INFO - Device connected in flash mode
10/051/2016 07:51:34 - INFO - Device disconnected
10/051/2016 07:51:42 - INFO - Device connected in flash mode
10/051/2016 07:51:50 - INFO - Device disconnected

However, after I rebooted, it hasn't even been reset and boots with everything just as before.
I also tried fastboot, getting the same "FAILED....."-error.

Plan B?

 

[[NUT]]

Ok, so I tried to re-unlock. Here's the log:


However, after I rebooted, it hasn't even been reset and boots with everything just as before.
I also tried fastboot, getting the same "FAILED....."-error.

Plan B?

uhm... what the heck was the firmware image you flashed meant for?

Loader : S1_Root_f936 - Version : MSM8994_41 / Boot version : S1_Boot_MSM8994_LA1.2_110 / Bootloader status : NOT_ROOTABLE

That by itself says your bootloader does not allow to be unlocked. Are you sure you had a succesful unlock before?

I'll be asking a moderator to move the related posts to this issue to a new thread in the Q&A section, we are starting to hijack this topic for this issue, which we shouldn't... So don't be alarmed if our posts are suddenly removed. :good:

---------- Post added at 09:57 AM ---------- Previous post was at 09:56 AM ----------

@[NUT]



try https://github.com/AndroPlus-org?tab=repositories

I have not figured out his TWRP modifications.
What I found in his repository looks to me like an older copy of a TWRP branch of the OmniROM repository.
I found scripts for the Z5...

Actually, I already gone through his repositories, but that what we need isn't there...

 

[IlariJ]

uhm... what the heck was the firmware image you flashed meant for?



That by itself says your bootloader does not allow to be unlocked. Are you sure you had a succesful unlock before?

I'll be asking a moderator to move the related posts to this issue to a new thread in the Q&A section, we are starting to hijack this topic for this issue, which we shouldn't... So don't be alarmed if our posts are suddenly removed. :good:

The firmware's the Nordic Combined 28.0.A.8.260 / R13A from XperiFirm. And like I said, I originally got the bootloader open using Sony's "official" instructions, then tried flashing TWRP with fastboot which went through fine the first time, but when I booted to recovery the tablet froze.
Then I re-flashed this same firmware with Flashtool, and this issue appeared when I tried fastboot again.

What I was then suggested was that I had activated MyXperia's some kind of defense system which broke the ability to unlock, use fastboot etc.
I can't say for certain that I didn't, since I just tried to get the tablet running asap so I could try TWRP-install again and so on.

I still find it hard to believe that there's a (bloat)software that can mess up the tablet so bad even a complete erase can't undo it, but still the tablet's otherwise completely usable.

 

[[NUT]]

The firmware's the Nordic Combined 28.0.A.8.260 / R13A from XperiFirm. And like I said, I originally got the bootloader open using Sony's "official" instructions, then tried flashing TWRP with fastboot which went through fine the first time, but when I booted to recovery the tablet froze.
Then I re-flashed this same firmware with Flashtool, and this issue appeared when I tried fastboot again.

What I was then suggested was that I had activated MyXperia's some kind of defense system which broke the ability to unlock, use fastboot etc.
I can't say for certain that I didn't, since I just tried to get the tablet running asap so I could try TWRP-install again and so on.

I still find it hard to believe that there's a (bloat)software that can mess up the tablet so bad even a complete erase can't undo it, but still the tablet's otherwise completely usable.

Well, MyXperia does something funky with your TA or a bootloader partition(s), which is NEVER replaced by a flash of the system. The bootloader lock-up is meant to protect your device from the fastboot side, if your device is ever stolen or missing. If you have a solid password/pin on the software side it should then protect your device's contents, with the only possibility for the 'thief' to wipe it completely (using flash mode): which makes sure he will never obtain your data.

It's actually very logical, but it's something you need to be 100% sure you don't use when unlocking or working on an unlocked device. The wipe of your device removed the key which was used to securely encrypt the setting on the TA/Bootloader, which can now never be changed again.

If you have a backup of your TA/bootloader partitions from BEFORE these issues started (and BEFORE you used MyXperia!) then you might have a chance... but I'd call it slim...

 

[IlariJ]

Well apparently I don't have, since I never got TWRP to work, so couldn't take a backup. Guess that's that, then.. :/

 

[IlariJ]

Well apparently I don't have, since I never got TWRP to work, so couldn't take a backup. Guess that's that, then.. :/

 

[killdozer56]

Hi. I also follow this topic and hope fixed twrp well be released soon. And of course I wish I could help to make it faster But I found something interesting, does anybody have two cores stopped in the cpu-z, maybe that's the reason of random reboots?

Hi
Thanks to @[NUT] for his Awesome works :good:
I have three cores "stopped" in Cpu-z (no random reboots)
In kernel aduitor i have three cores "offline" so i think this is normal and dependent to the Cpu load or the cpu governor.

 

[Destroyedbeauty]

@AndroPlus

Are you reading the topic?

 

[Destroyedbeauty]

Hi. I also follow this topic and hope fixed twrp well be released soon. And of course I wish I could help to make it faster But I found something interesting, does anybody have two cores stopped in the cpu-z, maybe that's the reason of random reboots?

Hi
Thanks to @[NUT] for his Awesome works :good:
I have three cores "stopped" in Cpu-z (no random reboots)
In kernel aduitor i have three cores "offline" so i think this is normal and dependent to the Cpu load or the cpu governor.

Have anyone of you two experienced random freezes, kernel panic(s) or system freezes because of this "behaviour"?

@[NUT] Maybe the freezing issue detailed above is related to the touch_fusion thing?

 

[Destroyedbeauty]

Hi. I also follow this topic and hope fixed twrp well be released soon. And of course I wish I could help to make it faster But I found something interesting, does anybody have two cores stopped in the cpu-z, maybe that's the reason of random reboots?

Hi
Thanks to @[NUT] for his Awesome works :good:
I have three cores "stopped" in Cpu-z (no random reboots)
In kernel aduitor i have three cores "offline" so i think this is normal and dependent to the Cpu load or the cpu governor.

Have anyone of you two experienced random freezes, kernel panic(s) or system freezes because of this "behaviour"?

@[NUT] Maybe the freezing issue detailed above is related to the touch_fusion thing?

 

[jelbo]

Have anyone of you two experienced random freezes, kernel panic(s) or system freezes because of this "behaviour"?

@[NUT] Maybe the freezing issue detailed above is related to the touch_fusion thing?

AFAIK the random reboots are mainly, or mostly, in conjunction with running Xposed. If so, please continue this discussion in Crashes (red LED, black screen, reboot) with running Xposed. I can't think of any reason touch_fusion would be involved, if so, everyone, or everyone rooted, would suffer random reboots.

 

[jelbo]

Have anyone of you two experienced random freezes, kernel panic(s) or system freezes because of this "behaviour"?

@[NUT] Maybe the freezing issue detailed above is related to the touch_fusion thing?

AFAIK the random reboots are mainly, or mostly, in conjunction with running Xposed. If so, please continue this discussion in Crashes (red LED, black screen, reboot) with running Xposed. I can't think of any reason touch_fusion would be involved, if so, everyone, or everyone rooted, would suffer random reboots.

 

[[NUT]]

[snip] @[NUT] Maybe the freezing issue detailed above is related to the touch_fusion thing?

AFAIK the random reboots are mainly, or mostly, in conjunction with running Xposed. If so, please continue this discussion in Crashes (red LED, black screen, reboot) with running Xposed. I can't think of any reason touch_fusion would be involved, if so, everyone, or everyone rooted, would suffer random reboots.

I have to agree with @jelbo here, if touch_fusion would be to blame the tablet would have these crashes/freezes without having root too. My guess it is caused by something in the kernel or a driver.

Time and time again @DooMLoRD has had these kinds of issues due to governors not working properly or WiFi drivers acting up. Sony does not always release the latest sources to their WiFi drivers, so (as an example) there could still be a bug in the driver which the stock ROM+kernel does not have anymore.

 

[[NUT]]

[snip] @[NUT] Maybe the freezing issue detailed above is related to the touch_fusion thing?

AFAIK the random reboots are mainly, or mostly, in conjunction with running Xposed. If so, please continue this discussion in Crashes (red LED, black screen, reboot) with running Xposed. I can't think of any reason touch_fusion would be involved, if so, everyone, or everyone rooted, would suffer random reboots.

I have to agree with @jelbo here, if touch_fusion would be to blame the tablet would have these crashes/freezes without having root too. My guess it is caused by something in the kernel or a driver.

Time and time again @DooMLoRD has had these kinds of issues due to governors not working properly or WiFi drivers acting up. Sony does not always release the latest sources to their WiFi drivers, so (as an example) there could still be a bug in the driver which the stock ROM+kernel does not have anymore.

 

[Destroyedbeauty]

I have to agree with @jelbo here, if touch_fusion would be to blame the tablet would have these crashes/freezes without having root too. My guess it is caused by something in the kernel or a driver.

Time and time again @DooMLoRD has had these kinds of issues due to governors not working properly or WiFi drivers acting up. Sony does not always release the latest sources to their WiFi drivers, so (as an example) there could still be a bug in the driver which the stock ROM+kernel does not have anymore.

So old Wifi driver sources can cause the device to freeze and being unresponsive?

 

[Destroyedbeauty]

I have to agree with @jelbo here, if touch_fusion would be to blame the tablet would have these crashes/freezes without having root too. My guess it is caused by something in the kernel or a driver.

Time and time again @DooMLoRD has had these kinds of issues due to governors not working properly or WiFi drivers acting up. Sony does not always release the latest sources to their WiFi drivers, so (as an example) there could still be a bug in the driver which the stock ROM+kernel does not have anymore.

So old Wifi driver sources can cause the device to freeze and being unresponsive?

 

[killdozer56]

Hi,
I also got a reboot on v13 (after several startup without problem)

 

[killdozer56]

Hi,
I also got a reboot on v13 (after several startup)

 

[killdozer56]

Have anyone of you two experienced random freezes, kernel panic(s) or system freezes because of this "behaviour"?

@[NUT] Maybe the freezing issue detailed above is related to the touch_fusion thing?

Hi,
I had 2 freeze after two weeks in v12 (without Xposed installed) related to I don't know what.

 

[killdozer56]

Have anyone of you two experienced random freezes, kernel panic(s) or system freezes because of this "behaviour"?

@[NUT] Maybe the freezing issue detailed above is related to the touch_fusion thing?

Hi,
I had 2 freeze after two weeks in v12 (without Xposed installed) related to I don't know what.