Related
Q&A for [Recovery][FOTA]CWM and TWRP recoveries for custom ROMs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Recovery][FOTA]CWM and TWRP recoveries for custom ROMs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
cucumber09 said:
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/mmcblk0p23
- Reboot to recovery to test if it works (if not, try again and check if you are doing it correctly).
Download:
TWRP 2.8.4.0 (thanks to @Rohan purohit for compiling 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 it 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.
BTW, I don't own any of this work, I just adapted recovery images for using them from FOTA partition. And recoveries are not compiled by me.
Click to expand...
Click to collapse
Hey, i use your recovery but when i write reboot recovery in terminal, my phone boots normally. But i can acess it by volume up button. How can i fix it?
Vp10 said:
Hey, i use your recovery but when i write reboot recovery in terminal, my phone boots normally. But i can acess it by volume up button. How can i fix it?
Click to expand...
Click to collapse
It is CM bug, it will be fixed in next nightlies.
Hi bro, i see new twrp update in xperia l thread ..
I hope you to update them ..
Thangs
cucumber09 said:
It is CM bug, it will be fixed in next nightlies.
Click to expand...
Click to collapse
And how we can flash new nightlies without recovery?
Hi, can I install twrp 2.8.4.0 from my FOTA recovery 2.4.0.0?
digt said:
Hi, can I install twrp 2.8.4.0 from my FOTA recovery 2.4.0.0?
Click to expand...
Click to collapse
[emoji782]
AggelosGR said:
And how we can flash new nightlies without recovery?
Click to expand...
Click to collapse
Recovery is accessible, just press many times vol rocker 'till you will enter the recovery.
---------- Post added at 20:59 ---------- Previous post was at 20:55 ----------
2ALL
I'm reading Q&A section not often, better write to main thread or tag me (if you are not quoting me), so I will see the notification.
How to solve image unstability in FOTA TWRP?
Hello @cucumber09. I've been trying your FOTA recovery, which I consider a great solution for our device, but I'm facing image unstability while in recovery: the screen flips and flicks horizontally making it very hard to tap correctly any option, and could lead to fatal errors. Could you please tell me a solution? I've tried flashing several kernels/traditional recoveries, but when I make it work satable in recovery, then the OS does'nt boot (bootloop). I'm using stock 4.3 15.4.A.1.9 ROM, unlocked bootloader, rooted, with Xposed Framework and Gravitybox module.
Also I've tried many KK and LP ROMs but I always return to stock 'cause I can't stand glitches and gaps while listening to my favourite tunes.
Thanks in advance,
e-bert.
e-bert said:
Hello @cucumber09. I've been trying your FOTA recovery, which I consider a great solution for our device, but I'm facing image unstability while in recovery: the screen flips and flicks horizontally making it very hard to tap correctly any option, and could lead to fatal errors. Could you please tell me a solution? I've tried flashing several kernels/traditional recoveries, but when I make it work satable in recovery, then the OS does'nt boot (bootloop). I'm using stock 4.3 15.4.A.1.9 ROM, unlocked bootloader, rooted, with Xposed Framework and Gravitybox module.
Also I've tried many KK and LP ROMs but I always return to stock 'cause I can't stand glitches and gaps while listening to my favourite tunes.
Thanks in advance,
e-bert.
Click to expand...
Click to collapse
Your problem is using the stock sony rom, it doesn't support FOTA recoveries properly, as soon as you switch to any other rom the FOTA recovery will work.
Thanks & new question.
Remorcer said:
Your problem is using the stock sony rom, it doesn't support FOTA recoveries properly, as soon as you switch to any other rom the FOTA recovery will work.
Click to expand...
Click to collapse
OK. Thank you for your quick response. Now, could you suggest to me any custom ROM that has no glitches or gaps in music playing? In yor opinion, which is the best ROM you've tried for our device (Xperia M SS c1904)?
Thanks again.
e-bert said:
OK. Thank you for your quick response. Now, could you suggest to me any custom ROM that has no glitches or gaps in music playing? In yor opinion, which is the best ROM you've tried for our device (Xperia M SS c1904).
Thanks again.
Click to expand...
Click to collapse
Everyone has its own taste in roms, I like stable and clean roms and would suggest cm11 or PA, try some of the roms and I'm sure you'll find your favourite.
Bliss pop is good.try it ,the battery is good.smooth performance and id say not much sound glitch .
Sent from my nicki using XDA Premium 4 mobile app
All hail to all cucumber..
its so frustrated to install kernel only for recovery..
and its more frustrating when your phone not responsive because incompatible kernel.
i recommended to install this trough recovery..
more reliable and low risk..
if you cant install from recovery (signature verification failed), first install another kernel to get unsigned recovery (niu kernel example)..
its a long way, but i'm prefer this than risking my phone because wrong command..
tested in resurrection remix rom 5.1..
Installed fota twrp with terminal, it freezes
So I did just as it was written. Installed it with command thru terminal on a CM 12 rom on Xperia z2.
It did work, for approx 10 seconds. I reboot in recovery, got first the screen for
CM recovery, before it changed to twrp. When I got there, I couldn't press anything
And suddenly it reboot into normal again. Dunno what it can be?!
Stuck on cyanogenmod boot
Flashed it and now i'm stuck on the cyanogenmod boot screen
is TWRP better or CWM...?
i flashed the twrp version 2.8.3.0 stuck on boot animation and when flashed 2.8.5.0 loop of recovery...m on xenon hd 5.1.1 rom...can anyone help???/ i want to flash twrp recovery
Neemac said:
So I did just as it was written. Installed it with command thru terminal on a CM 12 rom on Xperia z2.
It did work, for approx 10 seconds. I reboot in recovery, got first the screen for
CM recovery, before it changed to twrp. When I got there, I couldn't press anything
And suddenly it reboot into normal again. Dunno what it can be?!
Click to expand...
Click to collapse
It is for Xperia M, not Z2. So it won't work on it.
@Neemac i think z2 have official fota twrp, so why you not use them?
Sent from my C1905 using Tapatalk
Current firmware: Android 5.0.2, Build LRX22G, Cyanogen OS version 12.0-YNG1TAS0W0
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Use OTA for manually update from any official KitKat build; don't use fastboot flashable images on existing devices with KitKat bootloader - it will brick the device!
How to unbrick: http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040 (Credit goes to @tirta.agung)
OTA downloaded.... Now going with flashboot...
Need Some Help
Deleted
anyone flashed it yet???
Sent from my AO5510 using Tapatalk
Flashed it..initial boot will take a long time
blackyz said:
OTA downloaded.... Now going with flashboot...
Click to expand...
Click to collapse
I tried fastboot method now my phone is not booting
anyone done it successfully? my DL is halfway so I need procedural help.
Phone not booting
sharan.nyn said:
I tried fastboot method now my phone is not booting
Click to expand...
Click to collapse
I flashed with fastboot process successful but my phone not booting, nothing happening. i don't know what to do now no logo just dead.
I flashed it with TWRP.
Awsm CM12S.
Super smooth !
mralam92 said:
I flashed with fastboot process successful but my phone not booting, nothing happening. i don't know what to do now no logo just dead.
Click to expand...
Click to collapse
Same here bro!
now following this
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
sharan.nyn said:
Same here bro!
now following this
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
Click to expand...
Click to collapse
service centre help or not?
Posted cm12
Just installed the zip version of cm12 on yu. Could not wait for the official ota update. Updated zip using cwm recovery which I had installed while the phone was running on the cm11 kitkat 4.4.4 version.
I understand that since this is just a system update there is no need to change or revert back to the original recovery.
(just a doubt- is it necessary to revert back to original 4.4.4 system stock recovery in case we get the OTA or the OTA will take care of any Custom recovery and will install iteslf?)
Initial boot will take a long time due to the Android Runtime (ART) virtual machine which is the improvisation over the Dalvik Cache. So please be patient for all the 122 apps to get registered in by ART. I had tried the ART while on cm11 4.4.4 (despite of system warning that it might lead to crashes etc... ), even then it took a very long time......
Working absolutely fine. Initial experience is awesome. Will be observing it now for some time. Most other features are similar to the cm11. no more 3g detection errors. Got to explore more....
My first posting in XDA.
I owe a lot to this community from which I have taken a lot. I hope I will be able to give back even little that I have got to help others. :good::good:
By zip version i mean the version that can be installed using the phone recovery with out the need of a computer to push the system (i.e. the flashable version). I am not aware what the debuggable version means.
mralam92 said:
service centre help or not?
Click to expand...
Click to collapse
Service center said they will pickup the device in 7-8 days
please tell me difference between OTA,Fastboot flashable image and Boot Debuggable image.And which one should I download to install.?
Titokhan said:
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Click to expand...
Click to collapse
Is the Android version 5.0.x or 5.1?
Has anyone encountered any bugs at all?
To flash through recovery, do I need the OTA version?
CM 12 update
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..
dont flash thru fastboot all who flashed it thru are having hard bricked devices
weshall said:
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..
Click to expand...
Click to collapse
YES YOU CAN JUST FOLLOW THIS STEPS
1. Download official CM12s Ota(1st zip in the link).
2. Place the downloaded zip file in the ‘download’ folder on phone’s internal storage.
3. Boot Yureka into Stock Cyanogen recovery - To do so, power off the phone. Then press Volume Up + Volume Down and Power button simultaneously,Onec you boot into recovery do data/ factory reset.
4. Select ‘Apply Update’ > ‘choose from internal storage’ > /0 > Download > and select “cm-12.0-YNG1TAS0W0-tomato-signed.zip” file. The ROM will be flashed and you should be seeing the Android Bot
5. Once installation is over, go to main page and ‘wipe cache partition’
6. Then select Reboot system now
That’s it! Wait for a while as the device boots for the first time with all new and fresh Cyanogen OS 12.
IF you dont get anyhting just revert me back ,or pm will help you.:laugh:
Titokhan said:
Current firmware: Android 5.0.2, Build LRX22G, Cyanogen OS version 12.0-YNG1TAS0W0
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Use OTA for manually update from any KitKat build; don't use fastboot flashable images on existing devices with KitKat bootloader - it'll brick the device!
Click to expand...
Click to collapse
It just got updated if you flash it on kitkat bootloader, the device will get bricked
Many users have got their device bricked, the warning was too late I flashed it today at 1:50 AM
weshall said:
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..
Click to expand...
Click to collapse
Hi, You can very well install the .....signed.zip using the CWM recovery as I did.
1. Install the .....signed.zip file and not the ....flashable.zip or the ....bootable.zip files. Only the .....SIGNED.ZIP file either on your phone memory or sdcard
2. Reboot into the recovery mode either by using the advanced reboot option or by pressing the volumeup+down button and power buttons simultaneously and releasing them once you see the Yu logo and phone vibrates.
2. Use the Factory reset command first and then wipe the Cache
3. Navigate to the Install zip and chose the .....SIGNED.zip from either your phone memory or the SD Card as CWM has the option to chose the zip file. and swipe to install it.
4. After successful installation navigate to reboot and swipe to allow the system to restart.
5. Intial boot takes a very long time saying Android is updating. This is because Lollipop uses Android Runtime (ART) by default and not Dalvik Cache as a virtual machine for all apps. So please be patient till all the 122 or so apks are updated by ART. Takes around 10-15minutes.
6. The usual fist time boot stuff.... and then...
7. Enjoy. CM12 it is sweet.
---------- Post added at 09:58 AM ---------- Previous post was at 09:43 AM ----------
id74em8 said:
Is the Android version 5.0.x or 5.1?
Has anyone encountered any bugs at all?
To flash through recovery, do I need the OTA version?
Click to expand...
Click to collapse
It is android version 5.0.2
To flash through recovery (either CWM or TWRP) use the .....SIGNED.ZIP i.e. the first file in the list and NOT the .flashable.zip or the last one. Only the first one.
I installed the zip through CWM
The only bug I noticed was when you add the Powersaver option tile in the Notification drawer, when in the power saving mode, a notification showing the power save mode got invoked. When I used the same option after rebooting I am not getting it now..
Also all of a sudden a red boundary started to appear at the edges of the screen. So I though I had opted for the screen refresh notification in the Developer options but I had not. Still i could see the red rectangle when the screen refreshed. I had to reboot the system. Now fine.
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
hey guys,
i have a big problem.
i unlocked my one+ 3 2 weeks ago and installed twrp and cm13. all worked fine.
yesterday i read the news from cm the first devices will get offical cm14.
so i donwloaded the first rom and updated my phone (without a wipe!).
the cm14 starts good and all worked fine.
But, i find out, i can´t hear a phone call.
so, i want to go back to the twrp to restore my backup of cm13.
the problems begins....
i can´t boot twrp. i see the bootloader screen and after switching the screen to recovery (normaly) i got a black screen (seems like to shut off the screen).
then i tried to reinstall it, nothing.
after a full evening of trying i wiped it (factory reset) from android 7.
after the reboot i got the same problem. -> black screen after bootscreen Android won´t start, recovery won´t start.
then i downloaded a toolbox and installed the stock recovery -> no change -> black screen.
then i tried to find a stock image als *.img format to flash it with all (kernel and recovery, etc) with fastboot, but i didn´t find an image.
my last try was to make a full wipe with "fastboot -w". but this won´t work too.
so, now my phone will only boot into fastboot and thats it.
i need urgend help.
can anyone tell me what i can do? how can i install any os and wipe via fastboot and with no recovery?
thx a lot for your help.
ravn
ravn83 said:
hey guys,
i have a big problem.
i unlocked my one+ 3 2 weeks ago and installed twrp and cm13. all worked fine.
yesterday i read the news from cm the first devices will get offical cm14.
so i donwloaded the first rom and updated my phone (without a wipe!).
the cm14 starts good and all worked fine.
But, i find out, i can´t hear a phone call.
so, i want to go back to the twrp to restore my backup of cm13.
the problems begins....
i can´t boot twrp. i see the bootloader screen and after switching the screen to recovery (normaly) i got a black screen (seems like to shut off the screen).
then i tried to reinstall it, nothing.
after a full evening of trying i wiped it (factory reset) from android 7.
after the reboot i got the same problem. -> black screen after bootscreen Android won´t start, recovery won´t start.
then i downloaded a toolbox and installed the stock recovery -> no change -> black screen.
then i tried to find a stock image als *.img format to flash it with all (kernel and recovery, etc) with fastboot, but i didn´t find an image.
my last try was to make a full wipe with "fastboot -w". but this won´t work too.
so, now my phone will only boot into fastboot and thats it.
i need urgend help.
can anyone tell me what i can do? how can i install any os and wipe via fastboot and with no recovery?
thx a lot for your help.
ravn
Click to expand...
Click to collapse
Lots off people are getting this problem and trust me for some reason people post steps to fix this that are complicated for people who are just getting to playing around with TWRP.
Look, download the original TWRP recovery from here, https://dl.twrp.me/oneplus3/ the one you need is the 3.0.2-1 . I used it and I got back to MC13 From MC14.1 which by the way is now working pretty good. Once you fastboot flash recovery .this 3.0.2-1 recovery you can actually use it with MC14.1 as am doing right now. In any case. flash recovery >factory reset > adb your MC13 Zip to the phone > reboot...
Remember All Of This Steps Are Always Taken At Your Own Risk !!
Best of luck!!! [emoji6]
Sent from my ONEPLUS A3000 using Tapatalk
DiMatador said:
Lots off people are getting this problem and trust me for some reason people post steps to fix this that are complicated for people who are just getting to playing around with TWRP.
Look, download the original TWRP recovery from here, https://dl.twrp.me/oneplus3/ the one you need is the 3.0.2-1 . I used it and I got back to MC13 From MC14.1 which by the way is now working pretty good. Once you fastboot flash recovery .this 3.0.2-1 recovery you can actually use it with MC14.1 as am doing right now. In any case. flash recovery >factory reset > adb your MC13 Zip to the phone > reboot...
Remember All Of This Steps Are Always Taken At Your Own Risk !!
Best of luck!!! [emoji6]
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
to flash only the new recovery will not help.
tomorrow i will try to flash, wipe (with "fastboot -w" and copy the zip file.
Will the copy install the cm13 version? or do u mean sideload to have the cm13 zip for the twrp to flash?
Try to flash the modified twrp. Check the official topic for cm 14, it is linked over there
Edit: this one http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
superiscch said:
Try to flash the modified twrp. Check the official topic for cm 14, it is linked over there
Edit: this one http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
@superiscch just provided you with the TWRP that works. This is what i did !
Flash the recovery provided on the link >boot to the new recovery, you well see the version at the top left corner as 3.0.2-1 > factory reset > adb sideload the MC 13 ....... Reboot system > than add your choice of google apps to the sdcard root > reboot to recovery > flash google apps from with recovery than reboot, you would be golden. After, if your interested just flash the TWRP from the original twrp team. Cuss the one you just installed is modified, it be your choice !!
Sent from my ONEPLUS A3000 using Tapatalk
Hey guys,
thx for your replay. i will try it after work.
but i have one question ... what do u mean exactly with " adb your MC13 Zip"?
do u mean to transfer the zip to install with twrp or is there a command to install the zip to the systempartition?
ravn83 said:
Hey guys,
thx for your replay. i will try it after work.
but i have one question ... what do u mean exactly with " adb your MC13 Zip"?
do u mean to transfer the zip to install with twrp or is there a command to install the zip to the systempartition?
Click to expand...
Click to collapse
Okay... Look, once you have flash the modified recovery and you reboot. You be able to boot to your OS. Than you have to simple options 1. Load the CM13 ZIP file to your sdcard which you can use for installing with recovery
2. Boot into recovery and side load the MC 13 ZIP file into your phone using adb...sideload would be using adb
ADB... adb sideload <name of file> without the brackets...
Good luck man
Sent from my ONEPLUS A3000 using Tapatalk
Thx a lot guys, now it works and in installed my phone successfully.
it was the wrong twrp version.
now, the weekend is save :silly:
ravn83 said:
Thx a lot guys, now it works and in installed my phone successfully.
it was the wrong twrp version.
now, the weekend is save :silly:
Click to expand...
Click to collapse
Alriiiight !!
Sent from my ONEPLUS A3000 using Tapatalk
Unofficial TWRP 3.2.0-0 Mi Note 2 (scorpio)
Unofficial TWRP build for the Mi Note 2.
TWRP 3.1.1-0 Changelog https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
Compatible with TWRP Backup and Recuse Tool for PC
Download Link
twrp-3.2.0-0-scorpio.img
Update 14/07/17
Update TWRP to 3.2.0.0
Update 14/07/17
Update TWRP to 3.1.1-0
New streamlined kernel
Add F2FS support
Improved Android 7.0 Miui compatibility - If issues persist please let me know
Update 30/05/17
All features working as expected
Screenbrightness adjustment is now responding accurately with a suitable default brightness
Updated kernel.
Much quicker booting.
Installation Guide
Once you've got you're bootloader unlocked with MiFlash and run through all the Xiaomi hoops to unlock your bootloader and have a fastboot installed on your PC:
Simply place the download where you like and then open a command prompt and type
fastboot flash recovery /path/to/twrp-3.1.1-0-scorpio.img
BONUS THEMES & File Manager
Plus as a special treat I'm including a full guide below to use Materialised Theme and Aroma File Manager both working within TWRP 3.1.1-0
Themes available from here
1. Install the latest TWRP linked above.
2. Download one of the themes above (see screenshots below for recommendations)
3. Download Aroma File Manager for TWRP from here
4. Once booted into TWRP select Install and choose the theme.zip you've downloaded.
5. You will instantly see the theme applied
6. Click Install again and this time select "materialised_aromafm_200-b7.zip"
7. Once that zip has completed installing open the Materialised Options (the art palette icon on the top right)
8. Tick the box that says "Use Aroma File Manager"
9. Press back and select "File Manager" from the list.
10. Swipe to start Aroma File Manager
11. Enjoy!!
See attached thumbnails for themes in action.
Source:
https://github.com/stonetrapping/twrp_android_device_scorpio
Special thanks to:
z31s1g for the wonderful themes and the Aroma File Manager
Thanks, dude !
Working OK for both MIUI and AOSP based ROMs?
Working with ASAP and MIUI and encryption all round.
That's great! Thanks for sharing
After flashing this recovery, it boots right back into stock recovery. Any idea what i'm doing wrong? Do I have to disable dm-verity or something?
stephendt0 said:
After flashing this recovery, it boots right back into stock recovery. Any idea what i'm doing wrong? Do I have to disable dm-verity or something?
Click to expand...
Click to collapse
You can keep dm-verity. After flashing I'd suggest leaving fastboot and booting straight into recovery via fingerpress.
Flashing SuperSU or Magisk or similar should ensure survival of TWRP if it's being overwritten.
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Kris Chen said:
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Click to expand...
Click to collapse
1. I've noticed the slow speed too, I'm 100% sure why it's happening but I have some ideas.
2. The same ideas will hopefully address this issue.
It was a quick and dirty port since there was no native TWRP, I haven't had the time yet to improve it but I'll build an updated release based on 8.2.5.0 sometime soon and look to making it official.
Kris Chen said:
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Click to expand...
Click to collapse
Lastest TWRP build
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
Boots quicker. Screen brightness is fully adjustable. Reboot to recovery from TWRP is working
Has been submitted to TeamWin for official status but for now remains unofficial.
Please let me know your thoughts.
Thanks, StoneTrapper !!
I will check later after flashing new version !
StoneTrapper said:
Lastest TWRP build
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
Boots quicker. Screen brightness is fully adjustable. Reboot to recovery from TWRP is working
Has been submitted to TeamWin for official status but for now remains unofficial.
Please let me know your thoughts.
Click to expand...
Click to collapse
Really fast at boot, maybe because is a release from the future (30052017 )
great job, thanks man!
Can not use usb otg function ...
Can not use usb otg function ...
Otg function, no work
[email protected] said:
Can not use usb otg function ...
Otg function, no work
Click to expand...
Click to collapse
I've had no issues with USB-OTB, with any standard formatted flash drive (FAT32, NTFS, EXT4).
This is also the first I've heard of anyone having such an issue.
Does the OTG drive mount successfully in whatever ROM you're using? Is it attached prior to booting to TWRP? Can you provide additional information.
TWRP doesn't like remounting the same USB multiple times - i.e if you unplug the USB while in TWRP, and then reattach the same drive it won't remount it.
Sorry to feedback lately because I was too busy in past 2-week.
Well, new TWRP is working well.
The only one problem: If I want to upgrade firmware, TWRP will be replaced by MIUI stock recovery after flashing new version of MIUI ROM.
It's pretty annoying because I need to get into fastboot mode then flash TWRP. After that, entering TWRP and flash lineage OS ...
Is it possible to be fixed in next coming version ?
Kris
May I know how to flash the TWRP rom?
I'm on MIUI.eu ROM, can I flash full global MIUI original ROM with TWRP without bricking the phone ??
Before on Redmi note 3 u can't flash original ROM without bricking the phone, u needed special TWRP (zxc version) or modify the ROM
Can you explain me ?
Envoyé de mon Mi Note 2 en utilisant Tapatalk
Link down.
chemha said:
Link down.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=673368273298968884
Will op fixed shortly.
StoneTrapper said:
https://www.androidfilehost.com/?fid=673368273298968884
Will op fixed shortly.
Click to expand...
Click to collapse
It does not work. No download link found