Flash TWRP to FOTA Partition(SONY XPERIA S).(Terminal Command Method)I will not responsible if you do something wrong to yor device
You can flash TWRP into fota partition if your kernel supports to flash it.(Ask the developer if support is available or not,To know more about Fota Partition Read here.).if yes then follow procedure.
1. You must have to root your ROM first.
2. Download TWRP.img (is the recovery file) from TWRP website.Place the downloaded twrp.img in sdcard. (Don’t place it under any folder.just copy to sdcard.if the downloaded file name is something else then rename it to twrp.img).
3. Now goto playstore and install terminal emulator app to your phone.
4. Now open terminal emulator app and type
su (and press enter key.it will ask for root permission.GRANT it) then type
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11
(and press enter keyr.be careful while you writing the above commands.)
Finished.Now you have successfully flashed twrp recovery into fotapartition.Reboot your phone and when you see pink led just tap Volume UP key to enter to recovery.
Rom Flash Procedure
METHOD 2:
First extract boot.img and recovery.img from rom.zip and copy both to SD card root folder
1. Flash twrp recovery image like you flash kernel/boot.img(by flash tool or by fastboot method).
2. Enter to recovery.
Then follow the image by the numbers written in the image.Swipe to flash.
Then do the same for boot.img but choose boot. Img from SD card and boot(partition) in image 4. Swipe to flash and done.
Sir, Could you please help me.
I have CWM recovery installed on Xperia SL and is running Layers ROM Cm11 based.
But I am thinking of switching to a new rom as the earlier one was very laggy. ([ROM][XS][5.1.1][LMY48P] OneOfaKind 22/09/2015 | UberTC 4.9 | Layers | Aroma Addon)
Could you tell me what shall I do with regards to:
1. Making the build.script change to make it compatible with Xperia SL
2. Do I need a TWRP recovery ? How will it go alongwith the CWM recovery which I already have installed and running pretty well ?
Thanks !
C0D3FR34K said:
Sir, Could you please help me.
I have CWM recovery installed on Xperia SL and is running Layers ROM Cm11 based.
But I am thinking of switching to a new rom as the earlier one was very laggy. ([ROM][XS][5.1.1][LMY48P] OneOfaKind 22/09/2015 | UberTC 4.9 | Layers | Aroma Addon)
Could you tell me what shall I do with regards to:
1. Making the build.script change to make it compatible with Xperia SL
2. Do I need a TWRP recovery ? How will it go alongwith the CWM recovery which I already have installed and running pretty well ?
Thanks !
Click to expand...
Click to collapse
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.
nageswarswain said:
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.
Click to expand...
Click to collapse
Problem is I am not able to find support for Xperia SL
The difference between Xperia S and SL is just 1.5GHz and 1.7GHz CPU respectively.. but support for the latter is sh!t
C0D3FR34K said:
Problem is I am not able to find support for Xperia SL
The difference between Xperia S and SL is just 1.5GHz and 1.7GHz CPU respectively.. but support for the latter is sh!t
Click to expand...
Click to collapse
As said by You, the difference is just in frequency, and none in hardware. So what ever applies to XS will apply to XSL.
Mirhawk said:
As said by You, the difference is just in frequency, and none in hardware. So what ever applies to XS will apply to XSL.
Click to expand...
Click to collapse
Thanks ! I have installed TWRP latest build using fastboot !
nageswarswain said:
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.
Click to expand...
Click to collapse
This is tantamount to spam but plz plz help me !!!
I was resizing the my 2GB partition but I am stuck now in the middle !!
I got stuck in step 10
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
/sdcard #
Click to expand...
Click to collapse
Followed the instructions on this thread :
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058
C0D3FR34K said:
This is tantamount to spam but plz plz help me !!!
I was resizing the my 2GB partition but I am stuck now in the middle !!
I got stuck in step 10
Followed the instructions on this thread :
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058
Click to expand...
Click to collapse
I saw now that you have solved your problem. And this time also @mirhl is present there to help..good guy mirhl.
Hello, i am using DooMKernel which comes with a preinstalled TWRP v2.5.0.0 now i am trying to update it to the latest version via Terminal or Fastboot but it doesn't work version stays the same. Does anyone know what could be the problem?
Torroan said:
Hello, i am using DooMKernel which comes with a preinstalled TWRP v2.5.0.0 now i am trying to update it to the latest version via Terminal or Fastboot but it doesn't work version stays the same. Does anyone know what could be the problem?
Click to expand...
Click to collapse
Here is a link which will give you mickybart's recovery and kernel of nAOSO b26.but before flashing this first copy the rom to your phone because u can't boot the device after flashing it.so flash this and reboot to recovery and flash the rom you want.
Link.
https://mega.nz/#!SZ9DXZgZ!tzugmlsOMum3cZYXyTh69lDDlhGfGjV-Fw2VKvaYdK8
Thanks, in case i want to keep my current stock ROM there is no problem whatsoever is there? I mean i can just install the Kernel and i'll be good to go?
Torroan said:
Thanks, in case i want to keep my current stock ROM there is no problem whatsoever is there? I mean i can just install the Kernel and i'll be good to go?
Click to expand...
Click to collapse
Take backup of the current rom before flashing the other file.then do as I said
TWRP... thanks!
Thanks
Thanks for the guide really appreciate !!
BTW - only mine recovery dont show temperature? my soft is oneofakind and newest twrp recovery in FOTA via dd command.
I installed twrp 2.8.7 using this and my phone got stuck in a boot loop
I am on uCyan b04.
guruAhtasham said:
I installed twrp 2.8.7 using this and my phone got stuck in a boot loop
I am on uCyan b04.
Click to expand...
Click to collapse
Flash ucyan b04 kernel only on fastboot and try to reboot...
nageswarswain said:
Flash ucyan b04 kernel only on fastboot and try to reboot...
Click to expand...
Click to collapse
Thanks for the reply but it didn't work
have to do a clean flash again to make it boot.
Related
Now we have official TWRP support, so this thread will not be updated anymore. For more info about official TWRP visit this thread.
Tired waiting for someone to repack kernel with your favorite version of recovery? Or tired to run recovery script every time you update your ROM or kernel? Now you don't need any repacked kernels or recovery-scripts. Use your FOTAKernel as recovery partition!
It works on any kernel with extract_elf_ramdisk utility (it's built in mostly all kernels for custom ROMs, but I am not sure) by @Dees_Troy. And don't forget, that you are doing on your own risk, I am not responsible for bricked devices, acid rains or thermonuclear war.
Installation:
Download zip and flash it via your current recovery. If your current recovery is unusable, you can flash it via terminal emulator:
- Extract FOTAKernel.img and place it to the root of your external SD-card
- Type su and grant root access
- Type
Code:
dd if=/ext_card/FOTAKernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
- Reboot to recovery to test if it works (if not, try again and check if you are doing it correctly).
Download:
TWRP 2.8.7.0
TWRP 2.8.6.0 (this and next versions are compiled for Xperia M by me)
Older versions and CWM:
TWRP 2.8.5.0 (port from Xperia L)
TWRP 2.8.4.0 (thanks to @Rohan purohit for bringimg it for Xperia L, I just ported and modded it)
TWRP 2.8.0.0/CWM (or scroll down, it's right below this post)
You can restore original FOTAKernel image by following instructions in this post (or just scroll down, it is 3rd post, lol).
Some info:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader this partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer @Dees_Troy (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery! Here is some info from Dees_Troy.
Download
TWRP 2.8.6.0>>>
TWRP 2.8.5.0>>>
TWRP 2.8.4.0>>>
Restoring original image
- You can restore original FOTAKernel flashing it via Flashtool by flashing any firmware (just uncheck everything in "wipe" section and uncheck everything in "exclude" section excluding "FOTA" like in attached screenshot).
- Or install attached zip via recovery or flash FOTAKernel.img from archive as it is written in OP.
cucumber09 said:
TWRP version is 2.8.0.0, because I could not boot 2.8.3.0 this way (maybe due to ramdisk size limitations), I'll look for this later and will try to fix it
Click to expand...
Click to collapse
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea
kh34d said:
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea
Click to expand...
Click to collapse
I don't know for sure. Download both recoveries, try to flash one that differs from yours and reboot recovery. If it changes, that means it works on CM11 kernel. BTW, even if it doesn't work on CM11, it will work when you will flash CM12 kernel. So you can flash it to be prepared.
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Okay, I will upload original FOTAKernel.
itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Everything about restoring is in 3rd post.
cucumber09 said:
Everything about restoring is in 3rd post.
Click to expand...
Click to collapse
Thangs, now all problem will be fixed ..
@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?
KHM90 said:
@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?
Click to expand...
Click to collapse
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.
cucumber09 said:
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.
Click to expand...
Click to collapse
Ok thx, Not needed just wanna know whether it will work or not
btw, FOTA kernel awesome idea:good:
I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...
ndrancs said:
I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...
Click to expand...
Click to collapse
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.
I'm confused, does it work for locked bootloader?
pincheraro said:
I'm confused, does it work for locked bootloader?
Click to expand...
Click to collapse
No way. It even won't work on stock kernel with unlocked BL.
@cucumber09 Which build is the attached FOTA restore zip from? .9?
elmkzgirxp said:
@cucumber09 Which build is the attached FOTA restore zip from? .9?
Click to expand...
Click to collapse
No, it is from earlier build, but also from 4.3. From first 4.3 build, as I remember.
cucumber09 said:
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.
Click to expand...
Click to collapse
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?
ndrancs said:
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?
Click to expand...
Click to collapse
I read these sources. And 49th line defines size of uncompressed ramdisk. But now I am not sure, which one is used in our kernel. I suppose, that newer one.
Hi,
So first I tried to install a new ROM over my Android Revolution ROM, flashing boot.img via Flashify.
Now the wifi, service and bluetooth dont work anymore.
So I tried to install the new layout many times via TWRP install through Flashify but every time I try a NL ROM (like FlexOs or any NL Rom) via recovery, i get : "your recovery is using the new storage layout but the rom you're trying to install is not" even after wiping /data and /sdcard0
I dont have any computer so I have to flash boot.img via Flashify.
Thanks in advance for helping me.
kinder771 said:
Hi,
So first I tried to install a new ROM over my Android Revolution ROM, flashing boot.img via Flashify.
Now the wifi, service and bluetooth dont work anymore.
So I tried to install the new layout many times via TWRP install through Flashify but every time I try a NL ROM (like FlexOs or any NL Rom) via recovery, i get : "your recovery is using the new storage layout but the rom you're trying to install is not" even after wiping /data and /sdcard0
I dont have any computer so I have to flash boot.img via Flashify.
Thanks in advance for helping me.
Click to expand...
Click to collapse
U dont have to flash the boot.img with flashify ...i had tried before to flash a recovery via flashify but it was not successful ...so you will have to try aroma kernel flasher to flash kernel/boot.img without the pc ...hers the link to it
http://forum.xda-developers.com/showthread.php?t=2413561
Great im gonna try this and ill telly ou
Thanks for your answer
Ok so I tried the kernel app and Aroma but I got stuck on a bootloop and ended reinstalling the old ROM using OTG.
So tell me everything i have to do, i have the ROM and the boot.img, what do install/do and how ?
Thanks a lot.
kinder771 said:
Ok so I tried the kernel app and Aroma but I got stuck on a bootloop and ended reinstalling the old ROM using OTG.
So tell me everything i have to do, i have the ROM and the boot.img, what do install/do and how ?
Thanks a lot.
Click to expand...
Click to collapse
1. go ahead and download the kexec kernel v10(old layout) if you are on old layout or the new layout one if you are on new layout
2. Download this Recovery App: AromaFM-KL Flasher(4.6)(ZeusKL v10+ only)
3.download arhd rom
4. go into fastboot anf flash the kexec kernel you download in step 1 via Fastboot flash boot Zeus.img(or the name of the kernel.img )
5.Boot into recovery (TWRP).
6. Now you install Aroma-KL.zip. When you do this aroma file manager opens in recovery.
7. In aroma file manager select the zip of your rom i.e arhd
8. Now after you select your zip in the previous step, aroma gives you a list of options. In this select install the zip.(let all the option which are selected as it is ...dont deselect any option)
9.exit aroma
10.reboot
Sorry but i'm stuck at step 4 asking to flash zeus.img via fastboot because i have no computer.
Is there a way to flash it through recovery or through the app ?
Thx
kinder771 said:
Sorry but i'm stuck at step 4 asking to flash zeus.img via fastboot because i have no computer.
Is there a way to flash it through recovery or through the app ?
Thx
Click to expand...
Click to collapse
No . I dont think so..(dont even try ...as ur hox may get hard bricked)
arrange for a computer for only this time ..and once you have flashed that kernel...you wont need a computer henceforth both for flashing a rom or a kernel you can do it via the aromma kernel
Ok then Ill try to get one.
Still thanks for all your help.
kinder771 said:
Ok then Ill try to get one.
Still thanks for all your help.
Click to expand...
Click to collapse
Dont say "thanks" hit the thanks button
You didn't tell me that : forum.xda-developers.com/showthread.php?t=2586472
I used my android tablet and it worked great !!
Thanks though for your help
kinder771 said:
You didn't tell me that : forum.xda-developers.com/showthread.php?t=2586472
I used my android tablet and it worked great !!
Thanks though for your help
Click to expand...
Click to collapse
Even i didnt knew that...thnx for your help
Did u succeed in flashing the aroma kernel flasher??
Yeah the boot gets flashed but for the rom i get : archive does not contain android-info/product.txt
Any idea on that?
Is it possible to flash Aroma zip via fastboot ? Whats the command to use ?
Thanks
Done I finally succeeded in transferring files to the HOX.
I am using twrp new layout (twrp big) so I booted in recovery, went to Mount and selected only Data then I transferred files from my tablet using "adb push (local) (remote)" !
Introduction
Disclaimer: While this TWRP has been tested by myself on my own device to flash, wipe and backup, I make no warranties as to it's performance. Use at your own risk.
WARNING: flashable version contains a kernel boot image which will be flashed to your device along with the recovery image.
Click to expand...
Click to collapse
Installation instructions
This recovery image is for the E6553 single SIM Z3+. Do not use it on another model.
This recovery image requires an unlocked bootloader. You will lose some functionality on your phone if you unlock your bootloader
Do your research and make sure you're using the latest version of the relevant tools if you do decide to unlock.
DO NOT enable MyXperia functionality if you've unlocked your bootloader. You will brick your device.
This first download of this recovery image CANNOT be flashed to your phone and must be used in fastboot mode only
The second download is a flashable recovery
Use the first version to flash the second dual-boot.zip version
Unzip the recovery.zip file to extract the recovery.img file to use in fastboot mode
Code:
C:\>adb reboot bootloader
C:\>fastboot boot recovery.img
C:\>adb push dual-boot.zip /sdcard/dual-boot.zip
C:\>adb push dual-boot.zip.md5 /sdcard/dual-boot.zip.md5
Click to expand...
Click to collapse
Now use the TWRP install feature to install dual-boot.zip. Follow the prompts of the Aroma graphical installer.
CAVEAT: this extends the boot time by about 5 - 10 seconds as ramdisk images need to be unpacked and there's a wait on a keypress to determine whether to enter recovery mode. In order to boot into recovery, press power on. When you see the yellow LED come on then press the down volume button once or twice. You will then boot into TWRP.
NOTE: the dual-boot.zip installs a new 28.0.A.8.251 kernel. If you're using the autoroot kernel from Devries you will need to flash SuperSU to re-root your device
This dual boot/recovery works by flashing the recovery image to the FOTAkernel partition. A custom ramdisk image contains the normal boot image. If the down volume keypress is detected, then the recovery ramdisk is automatically extracted from the FOTAKernel partition and flow of control switches to recovery. If no keypress is detected then the normal ramdisk is extracted and normal android boot ensues.
Those of you who installed version 1.0 please download and install this version 1.1 to fix the error with the startup of the trim area daemon
Download
Binary
Fastboot TWRP Recovery Image v2.8.7.0-e6553-1.0 for Z3+ E6553
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 (MD5: 52d4b7d406308dbd457e8b94210b7c87)
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 - MD5
Sources @ github
device_sony_kitakami
device_sony_ivy
Click to expand...
Click to collapse
Changelog
Code:
Current changelog: -- 29 September 2015
[new] v1.1 fix up problem in combined ramdisk preventing trim area daemon from starting correctly
[new] Flashable recovery - 28 September 2015
[new] Fixed various sys/class issues so that CPU temperature and LED / backlight control work correctly
[new] Updated to use 28.0.A.8.251 kernel (as opposed to the AOSP kernel)
[old] Initial release - 10 September 2015
Click to expand...
Click to collapse
Thanks To
The regular contributors to the Z3+ forum, among others @[NUT], @ChrisJ951, @DHGE, @Devries, @zxz0O0, @Venkat Kamesh, @AndroPlus, @Sacktreter who pass on knowledge and who make the forum a lively and cooperative place
Click to expand...
Click to collapse
People who installed version 1.0 of the Flashable TWRP must please update to version 1.1 to correct a bug.
Awesome work.
Glad you were able to get the screen working for it! Boots up fine w/o issue for me
This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+
AMoosa said:
This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+
Click to expand...
Click to collapse
I'd venture to suggest that it's highly unlikely that locked bootloader recovery could work. The DM_VERITY is almost a guarantor of that. Just search for CONFIG_DM_VERITY or Verity in the Z3+ forums for more info.
Even if an exploit works, the second it modifies the system partition, the kernel panics and refuses to boot. The only way of preventing that is to flash a new kernel or edit the ramdisk to remove the verity key. And the only way to flash a new kernel / edit the ramdisk is to unlock the bootloader.
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
This is correct behaviour. You're not actually flashing the recovery image, just temporarily booting a recovery kernel and associated ramdisk. Sony Xperia devices don't have a recovery partition, or more accurately, they don't have a bootloader than can check and load a boot image from a recovery partition.
Technically it's possible to make the boot image check for a ramdisk on another partition and use this instead of the normal ramdisk, but this is step two. Sony should be releasing an open recovery bootloader fairly soon for the Z3+ which will allow this recovery image to be flashed. It's already been released for other devices.
Until Sony releases open recovery for Z3+ or I spend the time trying to implement a feature that probably only has days or weeks of utility (until Sony releases the open recovery for Z3+) , you're stuck with a TWRP that you need to launch every time in fastboot mode.
On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot
elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
New version now flashable so that you can boot into recovery...read top post carefully before using.
serrin85 said:
On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot
Click to expand...
Click to collapse
Fixed in latest version
http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..
deecept said:
http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..
Click to expand...
Click to collapse
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.
dl12345 said:
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.
Click to expand...
Click to collapse
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!
deecept said:
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!
Click to expand...
Click to collapse
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks
dl12345 said:
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks
Click to expand...
Click to collapse
HI dl12345,
this recovery support Dual model? E6533
hi.question...i get remote: dtb not found error when trying to boot the recovery..any ideas?
didnt get a thing... how do i install?
please, release TWRP for 6533 too
we need custom recovery so bad
Dathrex said:
please, release TWRP for 6533 too
we need custom recovery so bad
Click to expand...
Click to collapse
Pleaseee ????
Brother, please, help us with twrp to E6533, please.
Enviado de meu E6533 usando Tapatalk
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:
Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!
youngcube said:
Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!
Click to expand...
Click to collapse
no need to flash superSU i think, it's already included in the kernel.
zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.
bruno$0 said:
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.
Click to expand...
Click to collapse
Working wonderful with SuperSU 2.68 I have a doubt do you have a DRM Restore that works with this Android Version?
Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks
[/COLOR]
creepyvillager said:
Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks
Click to expand...
Click to collapse
No flashing a kernel doesn't wipe anything, if you're having a dilemma then take a backup of everything like apps, contacts etc using titanium backup, copy the backup folder to your external memory or computer then flash.
Hope it helps.
P. S ONLY INSTALLING A RECOVERY WIPES EVERYTHING.
---------- Post added at 09:41 AM ---------- Previous post was at 09:25 AM ----------
bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:
Click to expand...
Click to collapse
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?
njaya95 said:
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?
Click to expand...
Click to collapse
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.
creepyvillager said:
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.
Click to expand...
Click to collapse
I just found out to use this kernel i should have .244 firmware i bet you're at .185 so update it to .244 then try this kernel. I'm just downloading the firmware now using Xperifirm(https://www.google.com/url?sa=t&rct...9Q4Ht-00R24lisYcw&sig2=ac8ImW1ZY7AvFSZpG9I9mA) and i'll post what i did to the phone after the update.
zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
It's not, need to flash SuperSU I flashed 2.66 Beta
bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:
Click to expand...
Click to collapse
Hey can you help me, how to make this kernel SELinux status permissive.
njaya95 said:
Hey can you help me, how to make this kernel SELinux status permissive.
Click to expand...
Click to collapse
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.
bruno$0 said:
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.
Click to expand...
Click to collapse
Okay ?
Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?
SugnaB said:
Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?
Click to expand...
Click to collapse
It's for 6.0.1 so don't flash it for 5.0.1, update the firmware then flash it cause Sony would have updated somethings in the kernel which won't work with old firmwares. The reason for boot working is maybe because of the phone rebooting from fastboot mode.
Hope it helped. [emoji4]
Sent from my E6533 using XDA-Developers mobile app
Did it need a Unlocked Boot-loader device?
sani007 said:
Did it need a Unlocked Boot-loader device?
Click to expand...
Click to collapse
offcourse.
Sorry for the noob question but I need to know the prerequisites,
Can I flash the Kernel right after flashing stock file OR....
Do I need to first unlock my bootloader
Do I need to have backed up my TA partition
hi there, i wanna update form .185 to .224. is it possible to update without wipe the data? and if it can, if i wanna root it, i just flash this kernel after fw upgrade, then flash supersu via twrp, am i right? thanks
If Xperia Z3+ Dual can't be bootloader unlocked, what's the point in this kernel?!
Team Win Recovery Project for Xperia M5
NOTE : This recovery for only bootloader unlocked M5s! Doesn't work with locked bootloader.
Installation :
for Lollipop users :
1- Root your device with this https://goo.gl/F512NR or this https://goo.gl/NADp3S)
for Marshmallow users :
1- Install this kernel (optional) (https://goo.gl/nBWatu)
After the first step, continuous steps same for all users.
2- Go to the /system and delete recovery-from-boot.p with any file manager that has a root privilege.
3- Enable USB debugging and connect the phone to PC.
4- Open cmd and enter these codes:
Hollyss(SingleSim)
Code:
adb reboot bootloader
fastboot flash fotakernel twrp-3.1.1-0-hollyss.img
fastboot reboot
Hollyds(DualSim)
Code:
adb reboot bootloader
fastboot flash fotakernel twrp-3.1.1-0-hollyds.img
fastboot reboot
Bugs :
- USB-OTG not working
- Cache partition has some troubles, it is not wipeable
Workaround for cache:
-In TWRP click settings and enable "Use rm -rf instead of formatting"
Download :
Hollyss-20170910-SingleSim
https://www.androidfilehost.com/?fid=673368273298984560
Hollyds-20170910-DualSim
https://www.androidfilehost.com/?fid=889764386195928556
TRXteam Members :
- @ByBlaCk
- @krkshalill
- @TheShadow35
Changelog :
Code:
2016-12-9 :
-Fix the device name and codename
-Fix Otg(Needs test)
2016-09-22:
- Added M5 Dual support.
2016-09-15:
- MTP issues fixed
- Minor bug fixes
2016-09-14:
- Updated to TWRP 3.0.2-2
- SD Card now working
2016-09-13:
- Initial release
I can't flash it, 30.1.A.1.55 is not supported.
Although i have it rooted & unlocked the bootloader.
Nvm foundnew firmware; flashing now.
Limi96 said:
I can't flash it, 30.1.A.1.55 is not supported.
Although i have it rooted & unlocked the bootloader.
Nvm foundnew firmware; flashing now.
Click to expand...
Click to collapse
@Limi96
Sorry bro, I forgot adding installation for Lollipop Now I'm adding :good:
TRXteam said:
you must flash marsmallow rom and try again
Click to expand...
Click to collapse
Will post results when i come back home, i just flashed 30.2.A.0.100 going out now.
Added installation for Lollipop users.
http:\\i.imgur . com\8x0L2Zd.png
I now have a working TWRP thx!
Downloaded new firmware using xPirifirm flashtool 30.2.A.0.100 single sim, cda was 1300-3365.
Flashed new firmware using flashtool; E5603_30.2.A.0.100_1300-3365_R2B.
Booted up device, hard reset it because it looped then it loaded apps and i did the tutorial.
Flashed kernel using flashtool; boot_m5_ss_30.2.A.0.100_nodmv_su_drmfix.
Flashed twrp-3.0.2-2-holly using flashtool.
So far no complaints if i find any bugs i will inform!
i was looking for otg-usb issue for M5 and i stumble upon this page...big thanks to TRXteam for providing the recovery!!
By the way why is the otg not working...?
Limi96 said:
http:\\i.imgur . com\8x0L2Zd.png
I now have a working TWRP thx!
Downloaded new firmware using xPirifirm flashtool 30.2.A.0.100 single sim, cda was 1300-3365.
Flashed new firmware using flashtool; E5603_30.2.A.0.100_1300-3365_R2B.
Booted up device, hard reset it because it looped then it loaded apps and i did the tutorial.
Flashed kernel using flashtool; boot_m5_ss_30.2.A.0.100_nodmv_su_drmfix.
Flashed twrp-3.0.2-2-holly using flashtool.
So far no complaints if i find any bugs i will inform!
Click to expand...
Click to collapse
Thanks you reply:good:
ataraxist said:
i was looking for otg-usb issue for M5 and i stumble upon this page...big thanks to TRXteam for providing the recovery!!
By the way why is the otg not working...?
Click to expand...
Click to collapse
My Team look it and cant fix otg,but work ıt.Thanks you reply:good:
When I write the commands do I need to put my M5 in fastboot mode? Or plug the device in normal mode?
Thanks.
ginowoo said:
When I write the commands do I need to put my M5 in fastboot mode? Or plug the device in normal mode?
Thanks.
Click to expand...
Click to collapse
ıf your M5 in normal mode write this command
adb devices
adb reboot bootloader
fastboot flash fotakernel twrp-3.0.2-2-holly-20160915.img
fastboot reboot
ıf your M5 in fastboot mode write this command
fastboot flash fotakernel twrp-3.0.2-2-holly-20160915.img
fastboot reboot
how to boot into recovery after that?
warboss said:
how to boot into recovery after that?
Click to expand...
Click to collapse
Hold volume down when powering device up.
i realised that after using this recovery, the phone was recognised as Redmi_Note_2 in TWRP and windows pc? the recovery was modified from Redmi?
ataraxist said:
i realised that after using this recovery, the phone was recognised as Redmi_Note_2 in TWRP and windows pc? the recovery was modified from Redmi?
Click to expand...
Click to collapse
Yes,same sources from redmi
TRXteam said:
Yes,same sources from redmi
Click to expand...
Click to collapse
your english is ok!
So it cannot be modified to "Xperia_T2Ultra"?
I am on MM stock rom. If i do not need root, do it need to flash the kernel? Can i straight away flash this fotakernel for recovery?
"for Marshmallow users :
1- You're install this kernel first for root. (https://goo.gl/nBWatu)
After the first step, continuous steps same for all users."
ataraxist said:
I am on MM stock rom. If i do not need root, do it need to flash the kernel? Can i straight away flash this fotakernel for recovery?
"for Marshmallow users :
1- You're install this kernel first for root.
After the first step, continuous steps same for all users."
Click to expand...
Click to collapse
You need to unlock your bootloader
Yup.. Already unlocked bl.
Sent from my E5653 using XDA-Developers mobile app