As the title states here are the 4.4.4 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system
MD5HASH: 49aa7777a1c60fc6742f12c2a31f1cdf
Size: 481 MB
Type: disk dump (compressed 7z)
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it... It was the other guy... I swear.... Flash at your own risk
DooMLoRD said:
As the title states here are the 4.4.4 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system [UPLOADING]
MD5HASH: 49aa7777a1c60fc6742f12c2a31f1cdf
Size: 481 MB
Type: disk dump (compressed 7z)
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it... It was the other guy... I swear.... Flash at your own risk
Click to expand...
Click to collapse
Hi DOOMLORD!
All users are waiting UPLOADING dump GPE 4.4.4 System!
P.S. Kernel now ported
scrubber said:
Hi DOOMLORD!
All users are waiting UPLOADING dump GPE 4.4.4 System!
P.S. Kernel now ported
Click to expand...
Click to collapse
stupid asymmetric ADSL speeds... get 4 MBPS download and only 256KBPS upload :crying::crying:
restarted uploaded twice yesterday...
will try again today
DooMLoRD said:
stupid asymmetric ADSL speeds... get 4 MBPS download and only 256KBPS upload :crying::crying:
restarted uploaded twice yesterday...
will try again today
Click to expand...
Click to collapse
Ok. Will arrange topic
scrubber said:
Ok. Will arrange topic
Click to expand...
Click to collapse
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
DooMLoRD said:
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
Click to expand...
Click to collapse
No problem, any source and can parts
DooMLoRD said:
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
Click to expand...
Click to collapse
We can wait
joluke said:
We can wait
Click to expand...
Click to collapse
scrubber said:
No problem, any source and can parts
Click to expand...
Click to collapse
done
https://mega.co.nz/#!4RNx0Jaa!trTgJIXt8bB9R8LW6z3IVejSRV0MfqNvviD769UUsDo
@DooMLoRD
Have you seen a XZU GPe get stuck and be unable to flash the boot partition? I get this every time I attempt to flash it.
Code:
[[email protected] 4.4.4 Stock Rooted]# fastboot flash boot boot_4.4.4.img
sending 'boot' (20480 KB)...
OKAY [ 2.462s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 2.466s
Now before we all start screaming bad download, here's the list of things that I've tried...
I've tried multiple boot images from various sources, validating md5 sums accordingly. I even tried the restoration procedure from your thread about restoring to stock.
I've tried to erase the partition using fastboot (which doesn't return an error) but I still can't flash after that.
I've tried using a different OS with fresh drivers. I normally run on a Fedora 20 box but I've tried on Windows 7 using Flashtool as well.
I've tried to wipe & clear cache. (Didn't think this would help, but what the hell?)
Anyway, I'm out of ideas. Any thoughts would be greatly appreciated.
And thank you for all of your hard work on the Xperia line. I've appreciated all of the posts in this forum, the system images and tutorials, as well as the custom recoveries!
Update : flashing boot.img from CM11 works fine. Clearly I'm missing something about how to flash the boot partition on this device. Apparently not all boot.img files are created equal...
Update 2 : I can flash the Advanced Stock Kernel with Dual Recovery without issue, so I'm going to flash my way back to 4.4.3 and go from there.
Fixed! : In the end, it was because I was using an ELF image and fastboot didn't like flashing it for some reason. I reverted my phone back to 4.4.3 using the stock system.img and FOTAKernel.img, then used the Advanced Stock Kernel with Dual Recovery, since they were all flashable via fastboot. Once the system was up, I used adb to push the 4.4.3 stock boot.img to the device and the did an adb shell, su'ed to root, and dd'it onto the boot device. Rebooted, OTA'ed it to 4.4.4. Done.
What a night. This is what I get for starting this project late...
Has anyone with a broken camera tried flashing this image?
Does the camera work in 4.4.4 after the flash?
Sorry for the newbie question, but what is the proper way to flash these files?
This is what I tried:
fastboot flash system <system.img>
fastboot flash boot <boot.img>
fastboot flash FOTAKernel <FOTAKernel.img>
I got an error for the boot.img (same error as ekrunch), but system and FOTAKernel successfully flash.
This is my first Sony device, so not too familiar with flashing this type of phone.
Thanks,
Matt
pudgewack said:
Sorry for the newbie question, but what is the proper way to flash these files?
This is what I tried:
fastboot flash system <system.img>
fastboot flash boot <boot.img>
fastboot flash FOTAKernel <FOTAKernel.img>
I got an error for the boot.img (same error as ekrunch), but system and FOTAKernel successfully flash.
This is my first Sony device, so not too familiar with flashing this type of phone.
Thanks,
Matt
Click to expand...
Click to collapse
Forgive the long post, I'm sure some of this is repetitive, just trying to be complete for those who don't.
Sounds like you have the same exact problem as mine. Something about restoring an ELF image to the boot partition via Fastboot isn't working. Weird.
Alright, get ready to have some fun!
Get your device working again. I recommend using the 4.4.3 system.img/FOTAKernel.img and DooMLord's Advanced Stock Kernel with Dual Recovery. Worked like a charm for me. Get the 4.4.3 images from here and the kernel from here. Use "fastboot flash" accordingly for these 3 images. Note: The reason I use the custom kernel is b/c the 4.4.3 boot.img didn't flash correctly either.
Now you're running on 4.4.3 again, rooted. If you wiped data, don't bother signing in to your Google account, we're going to wipe again.
Now on to 4.4.4...
Okay so what we're going to do now is flash the boot.img for 4.4.4 on your running 4.4.3. Once you do this, the device probably won't boot Android again without some flashing in the boot loader, so brace yourself. :laugh:
First up, push the boot image to your device. You can do that with an ADB push, or ES File Explorer's handy FTP server, or just download the image with the phone. I used the 4.4.4 images from here. Get the boot-4.4.4.img on your device somehow and leave the system-4.4.4.img and FOTAKernel-4.4.4.img on your PC.
Code:
## [I](Not sure if you need the full path, I didn't push it this way)[/I]
adb push boot-4.4.4.img /storage/sdcard0/Download
Get a shell going
Code:
adb shell
Now that you're in the shell on your device, change to the right directory on the device, and copy the ELF image to the raw device using DD. (Everybody get your UNIX party hat out, we're going old school...)
Code:
su -
cd /storage/sdcard0/Download
dd if=boot4.4.4.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Alright, you have a 4.4.4 boot image. Now get back to the boot loader.
Code:
adb reboot-bootloader
And now it's time to get those 4.4.4 images onto the system. I'd highly recommend a good wipe of data/cache while you're at it. ("fastboot -w" will do this for you.)
Code:
fastboot flash FOTAKernel FOTAKernel-4.4.4.img
fastboot flash system system-4.4.4.img
That should do it. Reboot, lock on to your Google account, then fire up the developer's menu and crank up ART, then enjoy your device on 4.4.4. (BTW, this still didn't fix my camera. :crying: )
Good luck everyone! Hope this helps someone out. And would somebody please chime in with the simple command that I'm missing that fixes this problem and avoids all of this foolery?
ekrunch said:
Forgive the long post
Click to expand...
Click to collapse
Nice, well explained post.
ekrunch said:
@DooMLoRD
Have you seen a XZU GPe get stuck and be unable to flash the boot partition? I get this every time I attempt to flash it.
Code:
[[email protected] 4.4.4 Stock Rooted]# fastboot flash boot boot_4.4.4.img
sending 'boot' (20480 KB)...
OKAY [ 2.462s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 2.466s
Now before we all start screaming bad download, here's the list of things that I've tried...
I've tried multiple boot images from various sources, validating md5 sums accordingly. I even tried the restoration procedure from your thread about restoring to stock.
I've tried to erase the partition using fastboot (which doesn't return an error) but I still can't flash after that.
I've tried using a different OS with fresh drivers. I normally run on a Fedora 20 box but I've tried on Windows 7 using Flashtool as well.
I've tried to wipe & clear cache. (Didn't think this would help, but what the hell?)
Anyway, I'm out of ideas. Any thoughts would be greatly appreciated.
And thank you for all of your hard work on the Xperia line. I've appreciated all of the posts in this forum, the system images and tutorials, as well as the custom recoveries!
Update : flashing boot.img from CM11 works fine. Clearly I'm missing something about how to flash the boot partition on this device. Apparently not all boot.img files are created equal...
Update 2 : I can flash the Advanced Stock Kernel with Dual Recovery without issue, so I'm going to flash my way back to 4.4.3 and go from there.
Fixed! : In the end, it was because I was using an ELF image and fastboot didn't like flashing it for some reason. I reverted my phone back to 4.4.3 using the stock system.img and FOTAKernel.img, then used the Advanced Stock Kernel with Dual Recovery, since they were all flashable via fastboot. Once the system was up, I used adb to push the 4.4.3 stock boot.img to the device and the did an adb shell, su'ed to root, and dd'it onto the boot device. Rebooted, OTA'ed it to 4.4.4. Done.
What a night. This is what I get for starting this project late...
Click to expand...
Click to collapse
you should read the "TYPE" mentioned in the OP
you cant flash ELF images using fastboot on newer s1 bootloaders
ddslee said:
Has anyone with a broken camera tried flashing this image?
Does the camera work in 4.4.4 after the flash?
Click to expand...
Click to collapse
my camera was working fine (could take pics in 4.4.3)...
after flashing to 4.4.4 i can no longer "take pics" using the camera app... though the camera preview is coming...
ekrunch said:
Forgive the long post, I'm sure some of this is repetitive, just trying to be complete for those who don't.
Sounds like you have the same exact problem as mine. Something about restoring an ELF image to the boot partition via Fastboot isn't working. Weird.
Alright, get ready to have some fun!
Get your device working again. I recommend using the 4.4.3 system.img/FOTAKernel.img and DooMLord's Advanced Stock Kernel with Dual Recovery. Worked like a charm for me. Get the 4.4.3 images from here and the kernel from here. Use "fastboot flash" accordingly for these 3 images. Note: The reason I use the custom kernel is b/c the 4.4.3 boot.img didn't flash correctly either.
Now you're running on 4.4.3 again, rooted. If you wiped data, don't bother signing in to your Google account, we're going to wipe again.
Now on to 4.4.4...
Okay so what we're going to do now is flash the boot.img for 4.4.4 on your running 4.4.3. Once you do this, the device probably won't boot Android again without some flashing in the boot loader, so brace yourself. :laugh:
First up, push the boot image to your device. You can do that with an ADB push, or ES File Explorer's handy FTP server, or just download the image with the phone. I used the 4.4.4 images from here. Get the boot-4.4.4.img on your device somehow and leave the system-4.4.4.img and FOTAKernel-4.4.4.img on your PC.
Code:
## [I](Not sure if you need the full path, I didn't push it this way)[/I]
adb push boot-4.4.4.img /storage/sdcard0/Download
Get a shell going
Code:
adb shell
Now that you're in the shell on your device, change to the right directory on the device, and copy the ELF image to the raw device using DD. (Everybody get your UNIX party hat out, we're going old school...)
Code:
su -
cd /storage/sdcard0/Download
dd if=boot4.4.4.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Alright, you have a 4.4.4 boot image. Now get back to the boot loader.
Code:
adb reboot-bootloader
And now it's time to get those 4.4.4 images onto the system. I'd highly recommend a good wipe of data/cache while you're at it. ("fastboot -w" will do this for you.)
Code:
fastboot flash FOTAKernel FOTAKernel-4.4.4.img
fastboot flash system system-4.4.4.img
That should do it. Reboot, lock on to your Google account, then fire up the developer's menu and crank up ART, then enjoy your device on 4.4.4. (BTW, this still didn't fix my camera. :crying: )
Good luck everyone! Hope this helps someone out. And would somebody please chime in with the simple command that I'm missing that fixes this problem and avoids all of this foolery?
Click to expand...
Click to collapse
thanks for creating it i was lazy to write all this
DooMLoRD said:
....
my camera was working fine (could take pics in 4.4.3)...
after flashing to 4.4.4 i can no longer "take pics" using the camera app... though the camera preview is coming...
...
Click to expand...
Click to collapse
Preview comes out ok as the hardware does initialize. The issue is, from what I have seen and other who may have corroborated this, is the AF on the camera. You see, photosphere actually works well, just not the regular camera. Someone else mentioned that apps using infinity focus work as well.
My guess is that something in 4.4.3 and 4.4.4 (maybe in the kernel?) is looking for the missing DRM keys from devices with unlocked BL. Several people have already stated that they have no issues with their cameras, with the only difference being the locked bootloader in their devices. Considering that Sony had done something similar with the Z1 last year, I would not be surprised if it was the case here as well. Not sure why this would be the case for a GPE unit as it has no proprietary software (other than X-Reality)...
As I said, nothing but a guess albeit it does make sense (to me anyways).
Finally!!
Finally got my GPE to update using ekrunches excellent post..it took a little fiddling, (WIPE!! REALLY!!) but everything else went quite smoothly. I did find that fastboot -w didn't format partitions on cache and data and ended up in stock recovery to do a full wipe, after which things worked perfectly. Before that it was bootlooping on me. Didn't fix the camera though. I may leave this sucker mostly stock until someone fixes the camera...and on that note-I unlocked my bootloader immediately on getting the phone, before any updates ran. I've been considering the idea that if you unlocked before 4.4.2, that might be what's messing the camera up. I don't have any evidence for this though, it's just a guess.
DooMLoRD said:
you should read the "TYPE" mentioned in the OP
you cant flash ELF images using fastboot on newer s1 bootloaders
Click to expand...
Click to collapse
hahahaha I did. But it's the same for the boot and FOTAKernel images. What kept throwing me was one working while the other didn't but they were both the same type of file. How nice of Sony to do this... *cough cough*
DooMLoRD said:
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Click to expand...
Click to collapse
So is there a better way to flash that boot image or is this it?
DooMLoRD said:
thanks for creating it i was lazy to write all this
Click to expand...
Click to collapse
You're quite welcome. Thank you for all of the dumps, kernels, write ups, etc. It is much appreciated. I've been leeching information from this forum for years with no contribution other than some donations so I'm glad to help out. I was beating my head up against the wall when I wrote that first post as it was driving me crazy that I couldn't flash that boot image. I've been spoiled by Nexus devices.
Do i need to flash BootKernel and FOTAKernel as well or will simply flashing the system image work ?
Pallavgarg10 said:
Do i need to flash BootKernel and FOTAKernel as well or will simply flashing the system image work ?
Click to expand...
Click to collapse
Depends what you are trying to achieve?
Fully update your new GPe ZU?
From 4.4.2 to 4.4.4?
Already rooted or not, if not I would just flash the OTAs
I just want to update to 4.4.4 with as little modification as possible
Related
Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Marcusprit said:
Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Click to expand...
Click to collapse
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
es0tericcha0s said:
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
Click to expand...
Click to collapse
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Marcusprit said:
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Click to expand...
Click to collapse
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
es0tericcha0s said:
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
Click to expand...
Click to collapse
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Marcusprit said:
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Click to expand...
Click to collapse
Your device boots and is already rooted, right? If so, try to flash the updated img files with : https://play.google.com/store/apps/details?id=com.cgollner.flashify
recovery
Thank you I now have recovery
Marcusprit said:
Thank you I now have recovery
Click to expand...
Click to collapse
As the title states here are the 4.4.3 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system: http://www.androidfilehost.com/?fid=23501681358543103
boot: http://www.androidfilehost.com/?fid=23501681358543092
FOTAKernel: http://www.androidfilehost.com/?fid=23501681358543090
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it, or it kills your neighbor's dog.. It was the other guy... I swear.... Flash at your own risk
Thanks!
Sent from my C6806_GPe using Tapatalk
I'm going to sound astonishingly ignorant, but I came here from owning a samsung, so bear with me...I know how to use flashtool to flash the system and kernel, but how do I flash the bootloader? It doesn't seem to show up in flashtool (I have everything in that folder) and I'd really, really hate to brick my toy..can someone explain it like I'm five?
NM-I just had to do some digging..<sigh> I should have known...
wyvernwaddell said:
I'm going to sound astonishingly ignorant, but I came here from owning a samsung, so bear with me...I know how to use flashtool to flash the system and kernel, but how do I flash the bootloader? It doesn't seem to show up in flashtool (I have everything in that folder) and I'd really, really hate to brick my toy..can someone explain it like I'm five?
NM-I just had to do some digging..<sigh> I should have known...
Click to expand...
Click to collapse
That is boot.img,connect your phone in fastboot mode,open flashtool and choose fastboot then select kernel to flash,then choose the boot.img.
Loading system is terminated at 15%, add a mirror.
graffixnyc said:
As the title states here are the 4.4.3 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system: http://www.androidfilehost.com/?fid=23501681358543103
boot: http://www.androidfilehost.com/?fid=23501681358543092
FOTAKernel: http://www.androidfilehost.com/?fid=23501681358543090
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it, or it kills your neighbor's dog.. It was the other guy... I swear.... Flash at your own risk
Click to expand...
Click to collapse
Mega mirror.
EDIT: Got what I wanted, thanks.
graffixnyc said:
As the title states here are the 4.4.3 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system: http://www.androidfilehost.com/?fid=23501681358543103
boot: http://www.androidfilehost.com/?fid=23501681358543092
FOTAKernel: http://www.androidfilehost.com/?fid=23501681358543090
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it, or it kills your neighbor's dog.. It was the other guy... I swear.... Flash at your own risk
Click to expand...
Click to collapse
just thought that i would let u guys know that there is an easy way to flash this...
after download just reboot into fastboot mode:
Code:
adb reboot bootloader
and flash the system.img directly on the system partition
Code:
fastboot flash system system.img
this will take a while
after flashing just reboot from bootloader!
Code:
fastboot reboot
thats it!
BTW after flashing this and rebooting into CWM recovery and wiping the /cache & dalvik-cache now Wifi & camera are working fine!!!
@OP
its always a good idea to provide the MD5HASH of the files you uploaded!
Tried it on my phone-didn't hurt anything, but no fix on the camera, either.
Sent from my C6806_GPe using Tapatalk
DooMLoRD said:
just thought that i would let u guys know that there is an easy way to flash this...
after download just reboot into fastboot mode:
Code:
adb reboot bootloader
and flash the system.img directly on the system partition
Code:
fastboot flash system system.img
this will take a while
after flashing just reboot from bootloader!
Code:
fastboot reboot
thats it!
BTW after flashing this and rebooting into CWM recovery and wiping the /cache & dalvik-cache now Wifi & camera are working fine!!!
@OP
its always a good idea to provide the MD5HASH of the files you uploaded!
Click to expand...
Click to collapse
The md5 is shown on the Android file host download page. I always make sure I check what my local file md5 is compared to what the server says it is to make sure they match before I post anything. but yeah, the md5 is there. It's not my fault if people don't read the download page
Sent from my HTC One_M8 using Tapatalk
graffixnyc said:
As the title states here are the 4.4.3 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system: http://www.androidfilehost.com/?fid=23501681358543103
boot: http://www.androidfilehost.com/?fid=23501681358543092
FOTAKernel: http://www.androidfilehost.com/?fid=23501681358543090
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it, or it kills your neighbor's dog.. It was the other guy... I swear.... Flash at your own risk
Click to expand...
Click to collapse
Hi my friend! We look forward to hearing from you new firmware dump GPE 4.4.4!!! Link to the OTA update: http://www.randomphantasmagoria.com/firmware/z-ultra/c6806_gpe/ download: https://drive.google.com/uc?export=download&confirm=no_antivirus&id=0B_zuNWpIf1ujbFp0eVozVHdDaVE
PLEASE HELP ,i have a sony xperia z ultra g.p.e with 4.4.4 rooted and a locked bootloader which i managed to delete a system file and immediately started boot looping the boot animation.
I can still get into the stock recovery.
I've searched everywhere and all i see is instruction for unlocked bootloader .
I've read that i can't flash an ftf with a locked boot loader,please help
i have a macbook but also have access to a windows comp
please if anyone can help me with step by step instruction to bring the phone back to a working state i would forever be thankful.
icotulookn said:
PLEASE HELP ,i have a sony xperia z ultra g.p.e with 4.4.4 rooted and a locked bootloader which i managed to delete a system file and immediately started boot looping the boot animation.
I can still get into the stock recovery.
I've searched everywhere and all i see is instruction for unlocked bootloader .
I've read that i can't flash an ftf with a locked boot loader,please help
i have a macbook but also have access to a windows comp
please if anyone can help me with step by step instruction to bring the phone back to a working state i would forever be thankful.
Click to expand...
Click to collapse
If you do have a GPe DO NOT FLASH AN FTF it will result in a permanent hard brick. Look for DooMLoRD's return to stock thread in GPe development section, it will return you to stock 4.4.2 and then you can let it update from there.
Thank you I will give that a try and post back results
icotulookn said:
Thank you I will give that a try and post back results
Click to expand...
Click to collapse
I must apologize for giving out bad advice. Stock recovery will not allow flashing older firmware.
I think what may be possible is flashing the 4.4.4 system IMG with fastboot. Maybe @egzthunder1 or @blueether will be nice enough to offer some better advice.
adfurgerson said:
I must apologize for giving out bad advice. Stock recovery will not allow flashing older firmware.
I think what may be possible is flashing the 4.4.4 system IMG with fastboot. Maybe @egzthunder1 or @blueether will be nice enough to offer some better advice.
Click to expand...
Click to collapse
OK thanks yea I'm really lost, I've been searching and I can't find any instruction on this.
Is this even possible with a locked boot loader?
icotulookn said:
OK thanks yea I'm really lost, I've been searching and I can't find any instruction on this.
Is this even possible with a locked boot loader?
Click to expand...
Click to collapse
Is it bootlooping or just stuck?
You should be able to flash a 4.4.4 system image
Instructions would be:
Download system_4.4.4.7z from http://forum.xda-developers.com/showthread.php?t=2799423
Extract the system_4.4.4.img
Code:
fastboot flash system <path_to_system_4.4.4.img>
blueether said:
Is it bootlooping or just stuck?
You should be able to flash a 4.4.4 system image
Instructions would be:
Download system_4.4.4.7z from http://forum.xda-developers.com/showthread.php?t=2799423
Extract the system_4.4.4.img
Code:
fastboot flash system <path_to_system_4.4.4.img>
Click to expand...
Click to collapse
Its boot looping the boot animation over and over .
OK this is my first Sony phone, I'm sorta familiar with fast boot from my HTC days but its been along time
If I remember correctly I had to install android SDK and fast boot, do I need all the same in this case?
Like i said its been along time and i would be thankfull for any and all instruction given ...
icotulookn said:
OK thanks yea I'm really lost, I've been searching and I can't find any instruction on this.
Is this even possible with a locked boot loader?
Click to expand...
Click to collapse
Again I apologize for posting without refreshing my memory by looking up the older threads. There was two issues with my first post.
1. Stock recovery will not allow flashing older firmware as I mentioned.
2. There is an edited ota zip but it needs to be flashed with custom recovery, which I believe can only be used with an unlocked bootloader.
Hopefully fastboot flashing the system img does the trick.
---------- Post added at 12:22 AM ---------- Previous post was at 12:20 AM ----------
icotulookn said:
Its boot looping the boot animation over and over .
OK this is my first Sony phone, I'm sorta familiar with fast boot from my HTC days but its been along time
If I remember correctly I had to install android SDK and fast boot, do I need all the same in this case?
Like i said its been along time and i would be thankfull for any and all instruction given ...
Click to expand...
Click to collapse
This should do what you need.
http://forum.xda-developers.com/showthread.php?t=2317790
Thank you so much for the fast replies and the assistance, I think I just need the Sony drivers which I can do a search for.
Its getting late so I will give it a go tomorrow and report back.
Fingers Crossed !!
icotulookn said:
Thank you so much for the fast replies and the assistance, I think I just need the Sony drivers which I can do a search for.
Its getting late so I will give it a go tomorrow and report back.
Fingers Crossed !!
Click to expand...
Click to collapse
Easiest way to get the drivers may to download flashtool and grab them from the drivers folder.
ok I'm on a windows 8 comp and I've downloaded and installed adb and fast boot along with the sony drivers ..i have the phone in fast boot mode and usb connected and no matter what i do i can't get the comp to connect with the phone, am i missing something with windows 8 ?
am i doing something wrong with driver installation?
What am i doing wrong? i will gladly and thankfully accept any advice..
icotulookn said:
ok I'm on a windows 8 comp and I've downloaded and installed adb and fast boot along with the sony drivers ..i have the phone in fast boot mode and usb connected and no matter what i do i can't get the comp to connect with the phone, am i missing something with windows 8 ?
am i doing something wrong with driver installation?
What am i doing wrong? i will gladly and thankfully accept any advice..
Click to expand...
Click to collapse
Yes Windows 8 is a pain, Google for "disable driver signature verification in Windows 8" and see if that helps.
blueether said:
Is it bootlooping or just stuck?
You should be able to flash a 4.4.4 system image
Instructions would be:
Download system_4.4.4.7z from http://forum.xda-developers.com/showthread.php?t=2799423
Extract the system_4.4.4.img
Code:
fastboot flash system <path_to_system_4.4.4.img>
Click to expand...
Click to collapse
please help me , i put the system_4.4.4.img in drive C:\ and I'm having a problem remembering how to do the flash boot commands ,,what i have done is "fastboot flash system system_4.4.4.img" but without the quotes and its not working, can u tell me how to direct it to the path of C:\ because I'm pulling my hair out..can u help?
adfurgerson said:
Yes Windows 8 is a pain, Google for "disable driver signature verification in Windows 8" and see if that helps.
Click to expand...
Click to collapse
i think i got it but i can't remember the how to do the fastboot to where the system file is.
the file name is (system_4.4.4.img) and i have it on the C:\ drive
can u tell me the exact command for fast boot to that file?
many many thanks
icotulookn said:
please help me , i put the system_4.4.4.img in drive C:\ and I'm having a problem remembering how to do the flash boot commands ,,what i have done is "fastboot flash system system_4.4.4.img" but without the quotes and its not working, can u tell me how to direct it to the path of C:\ because I'm pulling my hair out..can u help?
Click to expand...
Click to collapse
You need the whole path ex. C:\user\icotulookn\downloads\4.4.4 system img.
I am positive I found the file and was able to copy and paste the path into adb, not sure if that works for fastboot.
adfurgerson said:
You need the whole path ex. C:\user\icotulookn\downloads\4.4.4 system img.
I am positive I found the file and was able to copy and paste the path into adb, not sure if that works for fastboot.
Click to expand...
Click to collapse
i have it directly on C:\ so would i go
fastboot flash system system_4.4.4.img C:\
when i go( fastboot flash system system_4.4.4.img ) it starts but then says<remote:command not allowed
icotulookn said:
i have it directly on C:\ so would i go
fastboot flash system system_4.4.4.img C:\
when i go( fastboot flash system system_4.4.4.img ) it starts but then says<remote:command not allowed
Click to expand...
Click to collapse
I havent used windows (if I can help it) for near 15 years but something like
fastboot flash system C:\system_4.4.4.img
"remote:command not allowed" is probably because of the locked BootLoader, I thought that may happen
Do you know what the fole you deleted was? you may be able to adb push it back onto the system if the GPe boots far enough.
The only other options I can think of are:
Ask Sony for a singed update.zip of the full 4.4.4 (no patch files) so it can be flashed by the stock recovery
Or use adb to do an oem unlock* - but this will wipe DRM keys and render the camera without auto focus
* You could try and run TA backup, but I think it will fail to gain root to do the back up... can you get shell access to the device? "adb shell"
Gonna suggest something off the left field, but if you have access to stock recovery... Have you tried doing a full wipe? I mean, unless ypu royally messed something up elsewhere, flashing system would give you the same end result as a full wipe.
Hopefully this helps.
blueether said:
I havent used windows (if I can help it) for near 15 years but something like
fastboot flash system C:\system_4.4.4.img
"remote:command not allowed" is probably because of the locked BootLoader, I thought that may happen
Do you know what the fole you deleted was? you may be able to adb push it back onto the system if the GPe boots far enough.
The only other options I can think of are:
Ask Sony for a singed update.zip of the full 4.4.4 (no patch files) so it can be flashed by the stock recovery
Or use adb to do an oem unlock* - but this will wipe DRM keys and render the camera without auto focus
* You could try and run TA backup, but I think it will fail to gain root to do the back up... can you get shell access to the device? "adb shell"
Click to expand...
Click to collapse
Some things I am wondering.
1. Can 5.0 update be flashed in stock recovery or would.it fail due to missing files?
2. Can a kernel with recovery be hotbooted to flash the edited 4.4.2 ota?
3. Can the 4.4.4 system img be flashed with flashtool?
4. Is there a fastboot command similar to "adb devices" that will confirm it is connected properly?
I swear that I had the same error trying to return GPe to stock using WIN 8.1 laptop, on WIN 7 desktop it worked fine.
adfurgerson said:
Some things I am wondering.
1. Can 5.0 update be flashed in stock recovery or would.it fail due to missing files?
2. Can a kernel with recovery be hotbooted to flash the edited 4.4.2 ota?
3. Can the 4.4.4 system img be flashed with flashtool?
4. Is there a fastboot command similar to "adb devices" that will confirm it is connected properly?
I swear that I had the same error trying to return GPe to stock using WIN 8.1 laptop, on WIN 7 desktop it worked fine.
Click to expand...
Click to collapse
1. Yes it can but you need to place the zip file in a folder that recovery will recognize (/cache or /sd)
2. Technically yes. However, you still need to be unlocked for that AFAIK.
3. I don't see why not
4. Flashtool will confirm if you have a properly connected devices
There are two rules in life for being successful:
1. Never reveal everything you know;
2.
EDIT: I encountered numerous problems in installing CM13 on Z5C, but a solution is already written here, and it's better than what I could write (because me no good english
Also the problem as explained below is determined only by a wrong environment, in which I blindly flashed uncompatible SW.
Hello, as in title I cannot get "fastboot flash recovery recovery.img" command to work.
This is what terminal gives me:
C:\adb>fastboot flash recovery TWRP-3.0.0.0-suzuran-v2.img
sending 'recovery' (21760 KB)...
OKAY [ 0.756s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.943s
Click to expand...
Click to collapse
Despite the lack of errors the phone is completely unaffected, there's no way I can enter recovery but flashing with "fastboot flash boot", which is improper and so OS loading is broken (it boots only the recovery).
EDIT: I then discovered that's normal behaviour, and that I wasn't able to boot in recovery normally because I flashed Marshmallow SW on Lollipop
I wasn't able to find a solution on the internet, I hope someone can help me.
Z5C E5823, Win7, adb and fastboot are OK
davidbevi said:
Hello, as in title I cannot get "fastboot flash recovery recovery.img" command to work.
This is what terminal gives me:
I wasn't able to find a solution on the internet, I hope someone can help me.
Z5C E5823, Win7, adb and fastboot are OK
Click to expand...
Click to collapse
There's nothing wrong here? Looks successful to me.
civicsr2cool said:
There's nothing wrong here? Looks successful to me.
Click to expand...
Click to collapse
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
davidbevi said:
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
Click to expand...
Click to collapse
You might want to re-download the TWRP and flash it again. You might be that one in a million person who have a corrupted downloaded file.
davidbevi said:
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
Click to expand...
Click to collapse
Download twrp 3.0.2, you're using the wrong one. Also if you use flash tool you can hotboot the recovery to get into it if you don't have a custom kernel that will allow you to get into recovery.
firdyRAY said:
[...] corrupted downloaded file.
Click to expand...
Click to collapse
I doubt because I tried 3 different packages, and every single one works, just I have to flash it unproperly. I would follow your advice anyway if it wasn't for:
civicsr2cool said:
Download twrp 3.0.2 [...]
Click to expand...
Click to collapse
This is the only thing I found googling, can you please give me a link or more info?
I managed to get TWRP v2.8.7.0 on my phone.
I'd like to write a solution on the original post, so those who have my problem also have my solution, but I have to know better:
1) the TWRP I installed comes from a zip containing boot.img and recovery.img
2) flashing both ("fastboot flash boot boot.img" & "fastboot flash recovery recovery.img") did the job
My guess is that you need a piece of code that IS the recovery and a piece of code that MAKES the recovery ACCESSIBLE. If this is the case I don't get how I was able to boot into recovery when flashed on boot. I am confused!
davidbevi said:
I managed to get TWRP v2.8.7.0 on my phone.
I'd like to write a solution on the original post, so those who have my problem also have my solution, but I have to know better:
1) the TWRP I installed comes from a zip containing boot.img and recovery.img
2) flashing both ("fastboot flash boot boot.img" & "fastboot flash recovery recovery.img") did the job
My guess is that you need a piece of code that IS the recovery and a piece of code that MAKES the recovery ACCESSIBLE. If this is the case I don't get how I was able to boot into recovery when flashed on boot. I am confused!
Click to expand...
Click to collapse
twrp 3.0.2
https://www.androidfilehost.com/?fid=24499762636001943
twrp 3.0 and up is for marshmallow, anything below is lollipop. the boot.img is your kernel, like i said before you need to have a custom kernel to access twrp or hotboot it every time you need it. if you're running marshmallow with a lollipop kernel idk how well that will work out for you in the long run. to understand why you need the boot.img kernel i suggest looking up sony ric.
civicsr2cool said:
twrp 3.0.2
https://www.androidfilehost.com/?fid=24499762636001943
twrp 3.0 and up is for marshmallow, anything below is lollipop. the boot.img is your kernel, like i said before you need to have a custom kernel to access twrp or hotboot it every time you need it. if you're running marshmallow with a lollipop kernel idk how well that will work out for you in the long run. to understand why you need the boot.img kernel i suggest looking up sony ric.
Click to expand...
Click to collapse
Thanks a lot, I was able to determine that my problem was caused by a ROM that is too old for what I was trying.
I was trying to install CM13 following CTXz's guide, but I had no idea I had to start from Marshmallow (and it's not written).
davidbevi said:
Thanks a lot, I was able to determine that my problem was caused by a ROM that is too old for what I was trying.
I was trying to install CM13 following CTXz's guide, but I had no idea I had to start from Marshmallow (and it's not written).
Click to expand...
Click to collapse
its in the thread somewhere towards the middle because i tested lollipop to cm13 and got nowhere fast as well.
edit:it says in op that required firmware is 6.0 fwiw
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
orthen2112 said:
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
Click to expand...
Click to collapse
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
trax7 said:
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
Click to expand...
Click to collapse
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
orthen2112 said:
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
Click to expand...
Click to collapse
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
trax7 said:
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
Click to expand...
Click to collapse
I have to admit I didn't understand very much in those to sentences.
trax7 said:
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Click to expand...
Click to collapse
Any ideas where else I can look
trax7 said:
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
Click to expand...
Click to collapse
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
orthen2112 said:
I have to admit I didn't understand very much in those to sentences.
Any ideas where else I can look
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
Click to expand...
Click to collapse
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
trax7 said:
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
Click to expand...
Click to collapse
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
orthen2112 said:
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
Click to expand...
Click to collapse
Glad I helped! The mods can close the thread now, I guess.
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
fetchaspade said:
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
Click to expand...
Click to collapse
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
trax7 said:
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
Click to expand...
Click to collapse
Thank you for your answer, sorry I did not notice.
My bootloader was indeed unlocked and I had adb + fastboot (on a linux distribution, never had to fetch specific drivers). In the end I tried to use flashtool to flash the stock Android L rom I had used for the downgrade (to backup the TA with the DRM keys before unlocking bootloader) which worked (I could not flash only the kernel image on boot). Then I tried again to boot on TWRP directly from fastboot mode without flashing anything: same error. I then downloaded a few recent stock Android N roms from xperifirm which flashtool could not unzip for some reason, then I found an Australian image elsewhere, and this time flashtool would accept it. So, back to Android N, I tried to flash TWRP again and it worked at last. I'm now running on the Lineage14.1+microG rom (so much better than stock roms I still can't believe it).
I guess TWRP, including old versions I tried, would not boot along the stock Android L rom that was currently flashed so I had to upgrade beforehand. I hope this will help people in the future.
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
elfae said:
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
Click to expand...
Click to collapse
Ofc that the latest recovery wont work for an Android version it wasn't made for (it would probably work on Marshmallow but Lollipop is too old). A different recovery would work there, the old zxz recovery if i remember correctly.
Also you can fastboot boot the recovery image directly.
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
elfae said:
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
Click to expand...
Click to collapse
You dont *have to* backup TA... It's only to preserve your original keys if you want. All of the custom kernels here emulate them anyway if you dont have the backup and LOS doesn't benefit from them at all.