Related
Could It Be Possible To Dual Boot GPE Rom and Stock Meaning have a dual boot capable recovery and kernel?
Ver3go said:
Could It Be Possible To Dual Boot GPE Rom and Stock Meaning have a dual boot capable recovery and kernel?
Click to expand...
Click to collapse
I think that would depend on the Madoco switcher, if it was made compatible.
I think that if someone could port philz touch recovery to lg pad then we could have dual boot
katsika said:
I think that if someone could port philz touch recovery to lg pad then we could have dual boot
Click to expand...
Click to collapse
i already asked and gave phil all he needed its up to him
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
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.
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
I have TWRP installed as my permanent recovery on my device. My question is what would happen if I flash (for example) system-arm64-aonly-gapps-su.img using TWRP on my device? Will it bricked? Can I restore it by flashing stock using ODIN?
I posted on a wrong thread. Kindly move it to https://forum.xda-developers.com/project-treble/trebleenabled-device-questions-and-answers since this is a question.
ECOTV said:
I have TWRP installed as my permanent recovery on my device. My question is what would happen if I flash (for example) system-arm64-aonly-gapps-su.img using TWRP on my device? Will it bricked? Can I restore it by flashing stock using ODIN?
I posted on a wrong thread. Kindly move it to https://forum.xda-developers.com/project-treble/trebleenabled-device-questions-and-answers since this is a question.
Click to expand...
Click to collapse
It won't brick, it just won't boot. The system image is designed to look for boot vendor etc in different partitions, not in the system as it previously was
miffymiffy said:
It won't brick, it just won't boot. The system image is designed to look for boot vendor etc in different partitions, not in the system as it previously was
Click to expand...
Click to collapse
So if I flash it and if it won't boot, can I return to stock using ODIN?
ECOTV said:
So if I flash it and if it won't boot, can I return to stock using ODIN?
Click to expand...
Click to collapse
No idea how you'd go back. The moral is don't flash it. It won't work
miffymiffy said:
It won't brick, it just won't boot. The system image is designed to look for boot vendor etc in different partitions, not in the system as it previously was
Click to expand...
Click to collapse
I have a Samsung Galaxy J4 Plus and it has treble support (A ONLY) but when i flash GSI it wont boot. it end up in a bootloop and i cant get it to boot. What should i do ??
dewin_prins said:
I have a Samsung Galaxy J4 Plus and it has treble support (A ONLY) but when i flash GSI it wont boot. it end up in a bootloop and i cant get it to boot. What should i do ??
Click to expand...
Click to collapse
Just wipe system and data and flash an specific rom for your device.
Schnedi said:
Just wipe system and data and flash an specific rom for your device.
Click to expand...
Click to collapse
i am at the boot screen of pixel experience gsi rom but it wont boot to system.. or it just takes a long time its been on the google logo for about an hour now and its not in the os yet should i wait or do something else i dont know what to do to make it go to the system..
Precautions for a gsi rom flash
If your device is supported then you must boot up with gsi
Do you wiped dalvik /cache / data partitions before booting with gsi or i say before flashing gsi rom