Simply put, this is (as of now) the latest TWRP (with F2FS, without multirom - sorry).
https://www.mediafire.com/?mj5885q1x5lamzv
Either install it normally or by using fastboot:
Code:
fastboot flash recovery fota.img
If you head over to AndroPlus' thread and download his latest kernel (as of writing, that is Z3_AndroPlusKernel_F2FS_v26a.zip) you could format /system and /cache as F2FS and it will boot and run fine, /data will however, sadly, not format or work as F2FS. But so far, /system and /cache does.
* Goal: get /data to work with F2FS as well
Thanks for contributing ! Will Multirom ever get integrated by any chance ?
Sent from my Xperia Z3 using XDA Free mobile app
I didn't think anybody was interested.
But sure, I'll see what I can do!
You do need to wait a few days though.
Sure I think there would be a good amount of interest considering it would mean that no matter what happened to the Kernel/recovery we would still be able to fall back on Fota for Multirom.
Sure take your time, would be great if possible.
Sent from my Xperia Z3 using XDA Free mobile app
I don't suppose we are any closer to having MultiRom integrated into this ?
Thanks bud
Sent from my Xperia Z3 using XDA Free mobile app
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
kjames2001 said:
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
Click to expand...
Click to collapse
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
panzerscope said:
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
so you mean i can just flash this into fota and boot into it? Thanks.
kjames2001 said:
so you mean i can just flash this into fota and boot into it? Thanks.
Click to expand...
Click to collapse
Correct !
Sent from my Xperia Z3 using XDA Free mobile app
panzerscope said:
Correct !
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
I flashed it via fastboot, but i couldnt enter any recovery. no led indication or vibration. pressed vol up and down and not working. runing lollipop tho, maybe that's the problem?
kjames2001 said:
I flashed it via fastboot, but i couldnt enter any recovery. no led indication or vibration. pressed vol up and down and not working. runing lollipop tho, maybe that's the problem?
Click to expand...
Click to collapse
Lol, just Remembered, you need Cm to use it.
来自我的 D6603 上的 Tapatalk
kjames2001 said:
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
Click to expand...
Click to collapse
You need something that, in the init, at boot, waits to check and see if you hit a set key.
"If set key is pushed - load "kernel" (or really ramdisk) from FOTA-partition"
Or more correctly, as @AndroPlus has coded it:
Code:
if [ -n "$POWRKEYCHECK" ]
then
#load FOTA ramdisk
busybox mknod -m 600 ${BOOTREC_FOTA_NODE}
busybox mount -o remount,rw /
busybox ln -sf /sbin/busybox /sbin/sh
extract_elf_ramdisk -i ${BOOTREC_FOTA} -o /sbin/ramdisk-recovery-fota.cpio -t / -c
busybox rm /sbin/sh
load_image=/sbin/ramdisk-recovery-fota.cpio
busybox echo 'Selected FOTA recovery' >>boot.txt
fi
If you want to do that yourself I can attach the original Sony LP kernel, dt.img and ramdisk for you.
Stock ROM
Hi. Just flashed your TWRP on my Z3, but I can't boot into it. What could be a problem? I am using latest CM12. Everytime I press vol + button during boot and lila light I get into CM recovery.
da900 said:
Hi. Just flashed your TWRP on my Z3, but I can't boot into it. What could be a problem? I am using latest CM12. Everytime I press vol + button during boot and lila light I get into CM recovery.
Click to expand...
Click to collapse
Well, to put it easy:
On boot the phone has a script that tells it to look for certain keys to be pushed.
1. If volume up is pushed then go to CM Recovery
2. If volume down is pushed then go to TWRP Recovery
3. If camera button is pushed then go to...
And so on. If there is no script telling the phone to do so (original Sony kernel/ramdisk) then the phone will just simply boot in to android. Nothing tells it to do otherwise.
If there is a script that only tells the phone to boot in to CM recovery or what ever, then that's the only options the phone has.
The kernel (or rather, the ramdisk with the kernel) you use has to have support for booting from the FOTAKernel-partition. If there is no support for it in the kernel then the installed FOTAKernel will just exist there. Not hurting anything, but not doing any good either.
TL;DR - ask the creator/developer of your kernel to add booting from the FOTAKernel as a feature.
Is there any automated or hassle-free way of replacing the nightly CM12 installer script with the script required for this recovery? Or do I have to download the zip manually, unzip, replace the sript manually, rezip, transfer the zip to my Z3, and then flash - every day?
panzerscope said:
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
Wrong. On Sony devices, once the bootloader is locked, the device will NOT boot the contents of the FOTAKernel partition.
This is similar to older Samsung devices.
The problem with this, of course, is that you normally can't change recovery without changing the kernel.
The workaround developed (IIRC by Dees_Troy of TWRP) was to have the boot kernel extract its recovery ramdisk from the FOTAKernel partition if present, allowing a person to switch recoveries without switching kernels - but they still need a kernel that will read the ramdisk. Also, the recovery ramdisk present needs to "play nice" with the kernel itself, which can lead to problems when Qualcomm or Sony do things that break display compatibility. For example, I'm fairly certain most current Z3 FOTAKernel builds use RGBX_8888, which Qualcomm dropped support for in vanilla framebuffers (like what recovery uses) in newer kernels. So any FOTAKernel ramdisk that tries to use RGBX_8888 will fail, for example, with Sony AOSP (due to it using a newer 3.10 kernel)
Related
I bought the Xperia Mini Pro as second-hand device just days ago (almost new for just ~$40 ) and this small guy really impresses me with its MSM8255 CPU and the ability to run CM10.1 as smoothly as my other devices
However, as I checked in ROM threads, before I flash any ROM, I have to flash the boot.img included MANUALLY VIA FASTBOOT, which renders on-the-go ROM switching impossible (i.e. I'll have to reach for my laptop whenever I'm itching to flash ).
One extra thing I tried is that, for my other devices, this command:
Code:
flash_image boot boot.img
...flashes a boot.img kernel via Terminal Emulator on the phone, enabling me to switch kernel really fast. Plus, these devices can also flash zip packaged kernels via CWM.
But when I executed the same command on XMP, an error pops up that goes, "can't find boot partition, failed with error: -1"...
So here's my question: how to flash kernels (boot.img) on the phone itself? Both command line method and CWM flashing method are welcome.
Thanks for reading this far and thanks in advance for any assistance!
Sent from HTC Incredible S @ PACman v21
It's not possible at the moment and probably will never be. You need access to PC if you want to flash kernel.
Koloses said:
It's not possible at the moment and probably will never be. You need access to PC if you want to flash kernel.
Click to expand...
Click to collapse
Reason? I've had my hands on an Arc S before, same 2011 lineup device, and its CWM flashes the kernel that comes with the ROM package. Why not for similarly hardware designed XMP (and all MDPIs)? Is there any vital partition differences I missed?
Sent from HTC Incredible S @ PACman v21
AndyYan said:
Reason? I've had my hands on an Arc S before, same 2011 lineup device, and its CWM flashes the kernel that comes with the ROM package.
Click to expand...
Click to collapse
No it doesn't, just because it's in the zip doesn't mean it gets flashed.
AndyYan said:
Reason? I've had my hands on an Arc S before, same 2011 lineup device, and its CWM flashes the kernel that comes with the ROM package. Why not for similarly hardware designed XMP (and all MDPIs)? Is there any vital partition differences I missed?
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
No it won't work like that. One reason should be that kernel+recovery are on one partition. But you need a PC
And no, arc s can't do that, too!
Sent from my Nexus 7 running Android 4.2.2
XperienceD said:
No it doesn't, just because it's in the zip doesn't mean it gets flashed.
Click to expand...
Click to collapse
mihahn said:
No it won't work like that. One reason should be that kernel+recovery are on one partition. But you need a PC
And no, arc s can't do that, too!
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
Oh well... I must have forgotten about that Arc S, yeah I remembered I used fastboot to flash a FXP128 kernel to it back in the days... Thanks for helping guys! Too sad that I don't have easy access to my PC though...
Sent from HTC Incredible S @ PACman v21
mihahn said:
One reason should be that kernel+recovery are on one partition.
Click to expand...
Click to collapse
Wait a second! What's that partition's name, if it's not "boot" or "recovery"?? May not help with my problem, but if you know, please tell me!
Sent from HTC Incredible S @ PACman v21
AndyYan said:
Wait a second! What's that partition's name, if it's not "boot" or "recovery"?? May not help with my problem, but if you know, please tell me!
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
I don't know the name and you can flash a kernel/recovery on its own, but if you flash the recovery first and afterwards a kernel, it'll be overwritten. So I guess it's the same partition, but I don't know more, sorry!
Sent from my Nexus 7 running Android 4.2.2
mihahn said:
I don't know the name and you can flash a kernel/recovery on its own, but if you flash the recovery first and afterwards a kernel, it'll be overwritten. So I guess it's the same partition, but I don't know more, sorry!
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
Well then, thx
Sent from HTC Incredible S @ PACman v21
Its not that kernel and recovery are on the same partition, its that we doesnt even have dedicated recovery partition in the first place. In fact, we doesnt even have the so called stock recovery at all.
All the custom recovery like twrp or cwm we got by fusing it in kernel ramdisk, and for locked bootloader by adding it to system partition.
an0nym0us_ said:
Its not that kernel and recovery are on the same partition, its that we doesnt even have dedicated recovery partition in the first place. In fact, we doesnt even have the so called stock recovery at all.
All the custom recovery like twrp or cwm we got by fusing it in kernel ramdisk, and for locked bootloader by adding it to system partition.
Click to expand...
Click to collapse
But here I'm talking about boot, not recovery, and not having a dedicated recovery is no prob for me. (Sorry if this sounds rude)
Recovery is fused into kernel, then is there a dedicated BOOT/KERNEL partition?
Sent from HTC Incredible S @ PACman v21
Of course there is. Every phone got boot partition. If it doesnt have one then where would the kernel be stored.
Consider this
There's a boot and a system partion. But no recovery partition
So the recovery goes along with the kernel to the boot partition. Since changing the kernel would involve changing in boot partition, the recovery would be wiped along with it, so it can't be done from the phone itself.
(Correct me if iam wrong)
Don't forget to hit thanks
I recently purchased a Xperia S LT26i. It does not have a recovery partition and cwm is embedded in the kernel ramdisk. Still, it is possible to flash kernels from recovery. I have no idea how does it work but we can definitely flash kernels via CWM. Secondly, flashing kernels means flashing a new recovery but on XS we have a Fota partition which is being used for storing the recovery(even without using this partition kernels can be flashed via CWM)
So maybe something can be done for our phones too.
Sent from my LT26i using xda app-developers app
mnishamk said:
Consider this
There's a boot and a system partion. But no recovery partition
So the recovery goes along with the kernel to the boot partition. Since changing the kernel would involve changing in boot partition, the recovery would be wiped along with it, so it can't be done from the phone itself.
(Correct me if iam wrong)
Don't forget to hit thanks
Click to expand...
Click to collapse
AFAIK, once CWM recovery is displayed, it's loaded into memory and thus the recovery partition CAN be wiped with recovery itself. Plus with other devices, the command "flash_image recovery recovery.img" works while booted up and in Terminal Emulator.
And we seem to drift away from my original question: is flashing KERNEL from phone possible? Not related to recovery, though recovery is bundled with kernel, with the above theory a kernel still can be flashed. I just don't know what the corresponding partition NAME for XMP's kernel is...
Sent from HTC Incredible S @ PACman v21
AndyYan said:
AFAIK, once CWM recovery is displayed, it's loaded into memory and thus the recovery partition CAN be wiped with recovery itself. Plus with other devices, the command "flash_image recovery recovery.img" works while booted up and in Terminal Emulator.
And we seem to drift away from my original question: is flashing KERNEL from phone possible? Not related to recovery, though recovery is bundled with kernel, with the above theory a kernel still can be flashed. I just don't know what the corresponding partition NAME for XMP's kernel is...
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
Even I think that Cwm is loaded into the ram when it starts. Here is the proof - when I had cwm installed on /system partition, I formatted /system in cwm but cwm still functioned properly until I rebooted. This proves that Cwm is loaded into Ram memory which is volatile.
Sent from my LT26i using xda app-developers app
To the OP AndyYan,
You can flash your boot.img file to xmp from your arc s and to arc s from xmp. Just find and download fastboot binary for arm devices. I flashed a kernel to my friend's Neo V from my XMP by this method. You have to connect the devices via a usb otg cable.
RavinduSha said:
To the OP AndyYan,
You can flash your boot.img file to xmp from your arc s and to arc s from xmp. Just find and download fastboot binary for arm devices. I flashed a kernel to my friend's Neo V from my XMP by this method. You have to connect the devices via a usb otg cable.
Click to expand...
Click to collapse
You mean I can run fastboot on another phone and flash the kernel? Well, not exactly what I expected, but still, will you give a link? And will the fastboot binary work for 1) non-Sony device and 2) device that doesn't support OTG?
EDIT: I got the fastboot binaries, and I do have a non-Sony device (the Vido tablet in my sig) which supports OTG. See if this works and I'll report back later
Sent from HTC Incredible S @ PACman v21
AndyYan said:
You mean I can run fastboot on another phone and flash the kernel? Well, not exactly what I expected, but still, will you give a link? And will the fastboot binary work for 1) non-Sony device and 2) device that doesn't support OTG?
EDIT: I got the fastboot binaries, and I do have a non-Sony device (the Vido tablet in my sig) which supports OTG. See if this works and I'll report back later
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
fastboot works on other devices too. you can check whether it works or not by typing any fastboot command in the terminal.
RavinduSha said:
fastboot works on other devices too. you can check whether it works or not by typing any fastboot command in the terminal.
Click to expand...
Click to collapse
Thanks, will try tonight!
(However, having to flash kernel in this way really suppresses my enthusiasm of flashing ROMs on XMP... )
Sent from HTC Incredible S @ PACman v21
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Sony Xperia Z Ultra (togari)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Note: based on cm-11.0 kernel
Meant for advanced users / dev to be eventually repacked and provided for all ROMs
Feel free to repack and open your thread
Just post a link to your topi here
Sweet!
Yay! About time you got round to this device, great work man
Oh yeah! I gotta say, things are moving fast for the Ultra these days!
What's the best way to flash this IMG file ?
Sent from my C6806_GPe using XDA Premium HD app
golfinggino said:
What's the best way to flash this IMG file ?
Sent from my C6806_GPe using XDA Premium HD app
Click to expand...
Click to collapse
I just 'noobly' fastboot flash boot the image over GPe rom and the phone won't boot, just blank after the power pushed.
I had to fastboot flash boot this GPe kernel with recovery to get the phone booting normaly.. : )
OK I am currently running the gpe ROM what exactly do I need to do to replace my current cwm recovery ?
Sent from my C6806_GPe using XDA Premium HD app
Kernel won't boot. Looks like "dt.img" is missing from the kernel.
I tried "fastboot boot philz_touch_6.10.0-togari" and command prompt says "Failed: dtb not found".
Then I tried "fastboot flash boot philz_touch_6.10.0-togari" and the phone won't boot. The led blinks orange for a while and the phone turns off.
EDIT: Woops, my bad. OP says this is meant for devs to repack into their kernels and not for direct usage.
EDIT 2: I repacked GPE ROM kernel with Philz Touch from this thread and TWRP from [NUT]'s XZDualRecovery. Download it here: http://forum.xda-developers.com/showpost.php?p=49565501&postcount=337
In recovery, Philz Touch says version 6.0.4.6. Don't know if it's normal 'cause the download says 6.10.
ChillyChan said:
Kernel won't boot. Looks like "dt.img" is missing from the kernel.
I tried "fastboot boot philz_touch_6.10.0-togari" and command prompt says "Failed: dtb not found".
Then I tried "fastboot flash boot philz_touch_6.10.0-togari" and the phone won't boot. The led blinks orange for a while and the phone turns off.
EDIT: Woops, my bad. OP says this is meant for devs to repack into their kernels and not for direct usage.
EDIT 2: GPE ROM kernel with Philz Touch from this thread and TWRP from [NUT]'s XZDualRecovery: http://forum.xda-developers.com/showpost.php?p=49565501&postcount=337
In recovery, Philz Touch says version 6.0.4.6. Don't know if it's normal 'cause the download says 6.10.
Click to expand...
Click to collapse
It should have a dt.img. But like most sony devices, seems useless when rom doesn't match kernel
So, like i said, it is meant for a dev owning the device to repack it
Guys is this recovery gonna change my .139 kernel for a old one ?
Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This recovery is WIP and intended for a preview only. Touch is a total mess and devs are working on it. The boot image will boot to system as usual, only touch is buggy. While recovery image will only boot to recovery.
Download:
The complete boot image, thanx @Abhinav2: http://d-h.st/Jvs
How to (for boot image):
1. fastboot flash the boot image
2. Press Volume down repeatedly to enter TWRP
Only Recovery Image by me: Recovery.img
How to (for recovery image):
1. Download recovery image
2. Make NANDROID backup of current Rom, also have its boot.img ready
3. Enter fastboot mode and " fastboot flash boot recovery.img"
4. Start the phone, it will go directly into recovery
5. When finished, press Power + Volume up untill 3 vibrations
6. Enter fastboot mode and "fastboot flash boot boot.img"
7. Restart
CREDITS:
- munjeni
- Abhinav2
- wan5xp
it won't boot CM or stock ya? so we just test the recovery right?
itachilinux said:
it won't boot CM or stock ya? so we just test the recovery right?
Click to expand...
Click to collapse
there is no boot.img complete boot image is also WIP
Sent from my Nexus 7
XperiaMT27 said:
there is no boot.img complete boot image is also WIP
Sent from my Nexus 7
Click to expand...
Click to collapse
will test it tonight, also changing my rom from carbon to your AOKP
will report bugs also.
Here- http://d-h.st/eE0 This is my version. It SHOULD boot into twrp by pressing power button when phone vibrates. I've turned on LED. This SHOULD also boot normally into system. @XperiaMT27 I'll explain you how to do this later. If you want you can go through its ramdisk to see how it works. Basically a init script which separately controls ramdisk and recovery. Recovery related stuff is removed from main ramdisk as it is triggered separately. A bootrec-device defines all the partitions and FOTA partition is used with elf_extract method. Will let you know more later. BTW touch won't work and don't bother I'll work on it. I have enough logs now and can work. If any of you is willing to help, they are more than welcome. Help of any kind, big or small, is appreciated.
This version is untested but it should work as it works for Xperia P and Xperia U but flash at your own risk. If you don't know how to repair your device, I won't recommend you to flash.
Cheers,
AJ
Abhinav2 said:
Here- http://d-h.st/eE0 This is my version. It SHOULD boot into twrp by pressing power button when phone vibrates. I've turned on LED. This SHOULD also boot normally into system. @XperiaMT27 I'll explain you how to do this later. If you want you can go through its ramdisk to see how it works. Basically a init script which separately controls ramdisk and recovery. Recovery related stuff is removed from main ramdisk as it is triggered separately. A bootrec-device defines all the partitions and FOTA partition is used with elf_extract method. Will let you know more later. BTW touch won't work and don't bother I'll work on it. I have enough logs now and can work. If any of you is willing to help, they are more than welcome. Help of any kind, big or small, is appreciated.
This version is untested but it should work as it works for Xperia P and Xperia U but flash at your own risk. If you don't know how to repair your device, I won't recommend you to flash.
Cheers,
AJ
Click to expand...
Click to collapse
this does not stop at recovery, same thing happened to me before.
XperiaMT27 said:
this does not stop at recovery, same thing happened to me before.
Click to expand...
Click to collapse
You tried this one? And you mean it doesn't vibrates for recovery? Cause that's basically impossible as I've added the line for vibration in init.sh but I guess there must be something different with sola. I'll work on it
Cheers,
AJ
Abhinav2 said:
You tried this one? And you mean it doesn't vibrates for recovery? Cause that's basically impossible as I've added the line for vibration in init.sh but I guess there must be something different with sola. I'll work on it
Cheers,
AJ
Click to expand...
Click to collapse
vibration and led is there but i think there is ramdisk corruption.. see PM
XperiaMT27 said:
vibration and led is there but i think there is ramdisk corruption.. see PM
Click to expand...
Click to collapse
Nope. Ramdisk is alright. The problem is sola uses event1 while event2 is defined in bootrec. Connect your device to PC(usb debugging on). Open terminal and type the following exactly-
Code:
adb shell
su
cd /dev/input
ls -al event1
Let me know the output.
Cheers,
AJ
Abhinav2 said:
Nope. Ramdisk is alright. The problem is sola uses event1 while event2 is defined in bootrec. Connect your device to PC(usb debugging on). Open terminal and type the following exactly-
Code:
adb shell
su
cd /dev/input
ls -al event1
Let me know the output.
Cheers,
AJ
Click to expand...
Click to collapse
yes ramdisk is fine, was my fault.
here is the output
Code:
[email protected]:/dev/input # ls -al event1
crw-rw---- 1 root input 13, 65 Feb 26 14:49 event1
actually 10 events from 0 to 9 are defined
XperiaMT27 said:
yes ramdisk is fine, was my fault.
here is the output
Code:
[email protected]:/dev/input # ls -al event1
crw-rw---- 1 root input 13, 65 Feb 26 14:49 event1
actually 10 events from 0 to 9 are defined
Click to expand...
Click to collapse
No. I'm talking about bootrec-device, that's different.
-----
Anyways, test this guys- http://d-h.st/Jvs It should work
Cheers,
AJ
Abhinav2 said:
No. I'm talking about bootrec-device, that's different.
-----
Anyways, test this guys- http://d-h.st/Jvs It should work
Cheers,
AJ
Click to expand...
Click to collapse
not power button but good old Volume Down button
OP updated with Abhinav2's kernel.
how to adb-ing when i'm in recovery?
Sent from my Xperia Sola using XDA Premium 4 mobile app
itachilinux said:
how to adb-ing when i'm in recovery?
Sent from my Xperia Sola using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think it should work the usual way. Just try and report
Sent from my Xperia Sola
Abhinav2 said:
No. I'm talking about bootrec-device, that's different.
-----
Anyways, test this guys- http://d-h.st/Jvs It should work
Cheers,
AJ
Click to expand...
Click to collapse
Thanks a lot @XperiaMT27 and @Abhinav2 for your hard work!
Just want to ask whether in this version is the touch fixed?
Or just the boot.img is added now?
I think I read it in OP, but sorry to bother you again.
Sent from my Xperia Sola using XDA Premium 4 mobile app
XperiaMT27 said:
This recovery is WIP and intended for a preview only. Touch is a total mess and devs are working on it. The boot image will boot to system as usual, only touch is buggy. While recovery image will only boot to recovery.
Download:
The complete boot image, thanx @Abhinav2: http://d-h.st/Jvs
How to (for boot image):
1. fastboot flash the boot image
2. Press Volume down repeatedly to enter TWRP
Only Recovery Image by me: Recovery.img
How to (for recovery image):
1. Download recovery image
2. Make NANDROID backup of current Rom, also have its boot.img ready
3. Enter fastboot mode and " fastboot flash boot recovery.img"
4. Start the phone, it will go directly into recovery
5. When finished, press Power + Volume up untill 3 vibrations
6. Enter fastboot mode and "fastboot flash boot boot.img"
7. Restart
Click to expand...
Click to collapse
I can install without problems (i'm on cm11)? Does it work the touch? which of the two linked is better to install?
Sorry for my bad english and my STUPID QUESTIONS
Petru97 said:
I can install without problems (i'm on cm11)? Does it work the touch? which of the two linked is better to install?
Sorry for my bad english and my STUPID QUESTIONS
Click to expand...
Click to collapse
no, it doesn't even work well. touch screen is messy.
Device information:
Xperia Z Ultra
Cyanogenmod 11 M12 (togari from offical cm side)
Smartphone is encrypted
Bootloader unlocked
Nothing else changed (kernel etc.)
Hi,
since a few hours i try to get TWRP 2.8.5.0 to work.
After installing it according the offical description and rebooting into the recovery, my z ultra only shows the Sony logo and doesn´t do anything (it took me some time to figure out how to turn it off... Power + vol up).
To get the cm cwm back, i´ve used fastboot to flash boot.img.
The integrated cwm can´t mount the encrypted data partition and is useless for me. To avoid problems on my heavily used z ultra, i tried TWRP first on my old (encrypted) Nexus 7 (2012) tablet, works like a charm and most important, it doesn´t have any problems with encrypted devices.
The installation on the Nexus 7 was not really mentionable, fastboot flash recovery file.img, that´s it.
The Z Ultra is different, the teamwin page says :
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
It won´t work, the above mentioned problem is the result.
Maybe i need a custom kernel, any suggestions?
Thanks for your help.
CM kernel probably doesnt allow to flash other kernel than it has (cwm). Flash great devs kernel and than twrp. I have it (at least multi rom 2.8.4 one) and it works.
However after screen off it reboots and i dont know what cause it
Thanks for your answear, i try it next weekend.
Code:
Rom: Resurrection Remix® Lollipop v5.3.6 - Togari
Kernel: from rom
Recovery: Dunno where it came from? Perhaps when flashing Candy5 Beta.
Im kind off in the same position, recovery says
Code:
E: Cannot load volume /misc
Finding update package...
Opening update package...
Installing update package...
Package is for device: ...[B][I]bla bla bla you get the thing[/I][/B]
E: failed to install /sideload/package.zip
E: Please take note of ..[B][I]bla bla bla[/I][/B]
Installation aborted.
E: Cannot load volume /misc!
When trying to flash any zip file. When the flash starts I see something like "verification failed" flashing by really quick .....I guess the verify is active which is causing this issue?
BUT this damn recovery has no damn setting to change that! Probably possible to modify some config.txt manually.
Is it possible to change recovery somehow from CM recovery?
I tried by flashing great devs with fastboot. Then it says finished but the same recovery is still present...
Sorry for ranting a bit ..I'm in the middle of some other projects going on with BSD but this one is driving me nuts :silly: I just want to flash TWRP on my device It should not be this difficult
My advice for you is to flash boot.img from resurrection remix - its great devs kernel v2 with twrp - or zombie kernel for 5.0 which has built in twrp.
Both can be flashed using fastboot, so u dont need working recovery for it and they both should work with all 5.0 roms except gpe one.
Im not sure what versions of recovery they have built in, but after that u can flash multirom zip, which has 2.8.4.x one (with mutirom support ofc,but its just addition for "stock" functions it has). I dont think u can use official twrp 2.8.5.0 with nonstock kernel as i tried to flash it to recovery partition and fotakernel and always it doesnt boot (recovery, rom and kernel worked fine, just after pressing vol+, vol- or power when purple light comes up, it changes to yellow and stay like this till i forced reboot).
I tried it with Great Devs KK (v1 + AICP 7.0l) and LP (v2 + RR or AICP 8.0 unofficial build), built in kernel in AICP 8.0 unofficial and Validus.
MultiROM twrp works fine with GD v1 and v2
ch3mn3y said:
My advice for you is to flash boot.img from resurrection remix - its great devs kernel v2 with twrp - or zombie kernel for 5.0 which has built in twrp.
Both can be flashed using fastboot, so u dont need working recovery for it and they both should work with all 5.0 roms except gpe one.
Im not sure what versions of recovery they have built in, but after that u can flash multirom zip, which has 2.8.4.x one (with mutirom support ofc,but its just addition for "stock" functions it has). I dont think u can use official twrp 2.8.5.0 with nonstock kernel as i tried to flash it to recovery partition and fotakernel and always it doesnt boot (recovery, rom and kernel worked fine, just after pressing vol+, vol- or power when purple light comes up, it changes to yellow and stay like this till i forced reboot).
I tried it with Great Devs KK (v1 + AICP 7.0l) and LP (v2 + RR or AICP 8.0 unofficial build), built in kernel in AICP 8.0 unofficial and Validus.
MultiROM twrp works fine with GD v1 and v2
Click to expand...
Click to collapse
....well im stuck. I have tried everything. Even hotbooting. That damn CM recovery is there no matter what!
I'm gonna give it a try tomorrow and start on zero. Either flash a stock rom with flashtool or scrubber port which is not based on cm.
I'll report later with some results
Mybe try to:
- dl your rom and zombie or gd
- open ur roms zip with ie 7zip
- delete boot.img
- unpack kernels zip and move boot.img to roms zip
- copy new zip to device
- flash stock
- flash kernel (zombie or gd)
- using built in recovery (should be twrp( flash roms zip
As there will be built in kernel with twrp it should stay after reboot.
If not do it again but before reboot in the and flash multirom zip
Sent using C6833 - AICP/GreatDevs
Solved the issue.
First I Downloaded
STOCK ROM] [FTF] Xperia Z Ultra 6833 14.4.A.0.118 "SRF FR".
GoogleDrive: Download FTF
Thanks to @dandyqb
Click to expand...
Click to collapse
And Flashtool 9.18.5
But I got stuck with Flashtool prompting me to move content from C:\flashtool\firmwares C:\users\admin\.flashtool/firmwares (??)
Abandoned flashtool and downloaded Flashtool 9.16.1 instead. But this time I hit another issue.
Code:
Flashing system bla bla bla.
Abort..
Error..
Device connected in Flashmode.
Grrrrr..!!
Abandoned the FTF file and downloaded
STOCK ROM] [FTF] Xperia Z Ultra 6833 14.4.A.0.118 "VodaFone UK".
mediafire: Download FTF
Thanks to @Feodorus 4PDA
Click to expand...
Click to collapse
This time it worked out. Flashtool read the FTF and pushed it to the device as it should.
Booted device and transfered files to my device
Code:
cm-Resurrection_Remix_LP_v5.3.6-20150221-togari.zip
gapps-lp-20141109-signed.zip
MultiROM-v30x-180115-UNOFFICIAL-togari.zip
I did the rest manually. Downloaded and opened [email protected]_LRX21P.S3.4201_by_Scrubber.
Took out the file "For_ALL_ZU_5.0_Scrubb_GPE_kernel_initD.img"
Renamed file and flashed it with
Code:
Fastboot flash boot boot.img
Booted into recovery and flashed
Code:
cm-Resurrection_Remix_LP_v5.3.6-20150221-togari.zip
gapps-lp-20141109-signed.zip
MultiROM-v30x-180115-UNOFFICIAL-togari.zip
Turned off device. Booted into Fastboot mode
Renamed "TWRP_multirom-togari_20150201-00.img" to "recovery"
Flashed file with
Code:
Fastboot flash recovery recovery.img
Fastboot reboot
Wooh.. And I reached a very unfamiliar place named Multirom upon boot saying Auto-boot! :good::laugh:
Glad u made it. It strange that u need steps with gpe port, but maybe some devices are different
Multirom lets u boot more than one rom. Its like grub on pc, so its good thing, but take 5-6 secs of additional booting time
And flash older version of flashtool (eg. 0.9.18.2), if u want to keepfirmwares in flashtool/firmwares folder. Devs change somethin and people like me with small system partition or ssd drive, which has limited space will have problems if it keeps that way (or well need to stay with older verions)
Sent using C6833 - AICP/GreatDevs
ch3mn3y said:
Glad u made it. It strange that u need steps with gpe port, but maybe some devices are different
Multirom lets u boot more than one rom. Its like grub on pc, so its good thing, but take 5-6 secs of additional booting time
And flash older version of flashtool (eg. 0.9.18.2), if u want to keepfirmwares in flashtool/firmwares folder. Devs change somethin and people like me with small system partition or ssd drive, which has limited space will have problems if it keeps that way (or well need to stay with older verions)
Sent using C6833 - AICP/GreatDevs
Click to expand...
Click to collapse
I didn't really need scrubbers kernel. I just used it to flash a recovery on to my device as I came from stock rom after flashing the FTF.
Just kind of a "safety first" step instead of jumping right onto flashing the multirom .img file and not knowing if its gonna boot or not. :silly:
Scrubbers gpe port was just the first rom that popped up in my head so its why I used it.
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
What kernel are u using? Im on GreatDevs and after flashing 2.8.5.0 it doesnt boot. I mean its flashed, but after reboot when i press vol+/- like i do with twrp 2.8.4 (multirom one)or before did with cwm it freezes on kernel logo (led color changes from purple to yellow)
Sent using C6833 - AICP/GreatDevs
ch3mn3y said:
What kernel are u using?
Click to expand...
Click to collapse
If this question is for me, I use official CM12.
Its in my forum and tapatalk signatures - Great Devs, KK one.
So maybe its it and cm11 kernel (or only GD) doesnt support 2.8.5+ ??
I can live with 2.8.4 for now (till I move to LP)
B.Maximenko said:
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Click to expand...
Click to collapse
I have tried this app. And other similar apps I could find on play store. They did not work.
The output in this app showed that it successfully replaced recovery but on reboot CM recovery was still present.
B.Maximenko said:
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Click to expand...
Click to collapse
the app doesn't work for me either (i'm running slimkat build 9 stock)
i can't get 2.8.5.0 working permanently (at least not after a power down)... it'll work right after a fastboot flash
lame Sony putting kernel and recovery together.... wth... my Note 2 was so much simpler to work with...
anyone got a TWRP theme which is suitable with xperia ultra z?
http://forum.xda-developers.com/xpe.../recovery-twrp-3-0-0-touch-recovery-t3309938/
This is deprecated.
In this thread I'll share the .img files of the latest TWRP available for our device, so you can flash them with Rashr/PhilZ/Cyanogen recovery.
Disclaimer:
you are responsible for what you do. If your device stops working after you follow this guide, it's not my fault. However, as usual, if you do things in a correct way, you won't face any problems.
Requirements:
any ROM with any kernel
unlocked bootloader
Don't flash it if you have got a locked bootloader!
Features:
up-to-date source
flashable signed zip
f2fs support
Changelog:
TWRP 2.8.7.0_8
- other cleanups
- startup now is not slow! It just takes 3 - 4 seconds!
- Reboot bug is fixed - maybe
TWRP 2.8.7.0_7
- optimizations and cleanups
TWRP 2.8.7.0_6
- f2fs for /system is supported (this is for Temasek users)
TWRP 2.8.7.0_5
- f2fs support improved
- minor optimizations
- less overheating
TWRP 2.8.7.0_4
- attempt to fix issues with reboot option
TWRP 2.8.7.0_3
- signed flashable zip added
TWRP 2.8.7.0_2
- f2fs bugs fixed
- fixed overheating
How to install:
flash the zip through any recovery (even Cyanogen recovery!)
Download from Android File Host:
[url]https://www.androidfilehost.com/?fid=24052804347826443[/URL]
Stock FOTAKernel to remove any recovery (included this one): [url]http://forum.xda-developers.com/xperia-sp/general/stock-components-flashable-zips-t3184111[/URL]
Be sure to select the right variant of your device!
Thanks to:
@[NUT]
@antr34
@TechnoSparks
This work in miui v6
Thanks a lot for this quick update :thumbup:
Working fine on AICP's official nightlies with stock kernel.
The TITAN has landed. Hide your works from this critic! The official maintainer of the XSP Lollipop and M Hub.
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
pilger said:
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
Click to expand...
Click to collapse
I use it and i cant flash nothing
Guizão BR said:
I use it and i cant flash nothing
Click to expand...
Click to collapse
What is the output of the command? Does it throw you an error or anything?
@pilger i'm here, what to do next?
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
pilger said:
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
Click to expand...
Click to collapse
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
J73 said:
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
Click to expand...
Click to collapse
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
pilger said:
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
Click to expand...
Click to collapse
Thanks to you! All's well now, I'm so glad to have TWRP again thank you!
pilger said:
What is the output of the command? Does it throw you an error or anything?
Click to expand...
Click to collapse
Sorry i Forgot to edit the play, this have more time to flash
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Tomoms said:
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Click to expand...
Click to collapse
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
kunal9007 said:
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Tomoms said:
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Click to expand...
Click to collapse
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
kunal9007 said:
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Well, strange. f2fs volumes couldn't be mounted.
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Adrian DC said:
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Click to expand...
Click to collapse
just realized that I didn't had tangerine installed i was on first build of official cm and then before flashing radium i formated to f2fs
Sent from my XT1033 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
and i flashed tangerine after atleast 1 day use of stock kernel
Sent from my XT1033 using Tapatalk