Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOGS
Changelogs can be found from TeamWin site TeamWin - TWRP
BUGS:
- No off mode charging, boots straight in to recovery.
INFORMATION:
- Supports the f2fs file system.
2016-05-10
- TWRP version 3.0.2-0
2016-02-06
- TWRP version 3.0.0-1
2015-12-10
- TWRP version 2.8.7.0
2014-10-26
- TWRP version 2.8.1.0
2014-10-15
Today (2014-10-15) I announce a build with F2FS support, today's and upcoming build's will have support for F2FS file system. Read more about F2FS from post #18.
DOWNLOAD:
For u8800pro
Stable:
TWRP_2.8.1.0-20141026-u8800pro.zip
Unstable:
TWRP_3.0.2-0-u8800pro.zip
TWRP_3.0.0-1-u8800pro.zip
TWRP_2.8.7.0-20151210-u8800pro.zip
For u8860
TWRP_2.8.1.0-20141026-u8860.zip
Looking for the u8800 version?
It can be found here: [RECOVERY] TWRP 2.8.1.0 recovery for u8800.
Big thanks to @Dees_Troy, @bigbiff and @Captain_Throwback. Also I want to thank you @desalesouche from his help.
Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!
CrysisLTU said:
Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!
Click to expand...
Click to collapse
Thanks and thanks to you and other dev's who was part of this forum, you have made a job which can't be forgotten!
Great. This must be a record. Not so famous device, still getting superb support from devs. Lets see what happens to Android L.
It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work
Greekguy74 said:
It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work
Click to expand...
Click to collapse
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.
Lihis said:
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.
Click to expand...
Click to collapse
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.
Greekguy74 said:
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.
Click to expand...
Click to collapse
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.
Lihis said:
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.
Click to expand...
Click to collapse
I tried those instructions and they don't seem to work.
If I attempt it from the normal recovery screen I get a
Code:
update package;s ext name error
E:ota_pre_update error
Maybe will try to flash everything ie reinstall B928 as well and not just try to unlock the pink screen.
Will keep you posted.
Greekguy74 said:
I tried those instructions and they don't seem to work.
Click to expand...
Click to collapse
What is the error? No, you cannot flash the update.app via recovery.
Lihis said:
What is the error? No, you cannot flash the update.app via recovery.
Click to expand...
Click to collapse
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss
Greekguy74 said:
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss
Click to expand...
Click to collapse
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?
Lihis said:
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?
Click to expand...
Click to collapse
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.
Greekguy74 said:
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.
Click to expand...
Click to collapse
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image
Lihis said:
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image
Click to expand...
Click to collapse
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:
Greekguy74 said:
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:
Click to expand...
Click to collapse
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?
Lihis said:
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?
Click to expand...
Click to collapse
adb is not accessible but fastboot seems that it is. even though I cannot flash anything since they are locked.
Support for F2FS file system
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.
Lihis said:
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.
Click to expand...
Click to collapse
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.
mohammad.afaneh said:
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.
Click to expand...
Click to collapse
Thanks! Are you working a F2FS enabled rom?
Related
Hi
Here are flashable zip file wich installs latest Sony stock 6.0.1 Marshmallow ROM 23.5.A.1.291_R3D (VMo AU-NZ), SuperSu v2.76 and latest TWRP 3.0.20 with read and write acces to system. Because device is Wi-Fi only region doesn´t matter. Only difference is bloatware. Since Sony hasn´t push update to SGP511 I use SGP512 firmware which is working fine on my device. If you want you can edit build.prop file in /system -folder to correct model number as shown in screenshot.
Here is the link for new 6.0.1 firmware:
https://mega.nz/#!VcxGyRZK!U4NqLOSeg1X_3KNC1_xXm2WnH4_i2OoZ6NwuyaIR6Hw
MD5 is: D3B78445485765AB7BD3A163F2A6C4BD
Make nandroid backup before flashing.
Install it by flashing whole zip file via custom recovery. TWRP recommend. If coming from .570 or .575 firmware dirty flash with art/dalvik cache wipe is okay.
If coming from older firmware factory reset is most likely necessary with cache and dalvik/art cache wipes but anyhow recommend. If you want you can restore your data with TWRP after installation and reboot. This install compatible busybox. If you install incompatible busybox you may loose acces to TWRP.
After flashing .zip file if you are getting bootloop you have atleast two choises.
- With pc and Flashtool use your firmware original ftf -file and flash it by excluding "FOTAKernel", "Partition" and "System". In other words in "exclude section" tick these and don´t wipe anything. (Credits @AlanDS)
- Or download "bootloop fix" from here: https://mega.nz/#!BUxFxSAR!bPVEEDnsPz962JQ1uA2PKJv9tYLKA47N0fhA80ltEvw
(Credits @niaboc79 and @machao44) and flash it with TWRP
Here is the old 23.1.A.1.28 (Customized NCB) FTF -file link:
For SGP511: https://mega.nz/#!sVIn1IJI!Ywqoksuej83vNkc__nNrBy-im6tfLjWr_mbonMd6PPk
MD5 is: aab7e5728dccb59d44d5ebe38c34c8da
This version of firmware should be rootable. For instructions and download go here: http://forum.xda-developers.com/crossdevice-dev/sony/root-how-to-root-5-0-lollipop-t3212108
Credits: @Androxyde @Chainfire @[NUT] @IaguCool @zxz0O0 @Wolfbreak @shoey63 @serajr @championswimmer @russel5
Any news on sgp512? or I can use this one? thanks in advance
Cocolopes said:
Any news on sgp512? or I can use this one? thanks in advance
Click to expand...
Click to collapse
At the moment latest for SGP512 is .726 firmware but you can use this one.
kulvertti said:
At the moment latest for SGP512 is .726 firmware but you can use this one.
Click to expand...
Click to collapse
good...I miss something if I use this? I think the only difference its the internal memory...
Cocolopes said:
good...I miss something if I use this? I think the only difference its the internal memory...
Click to expand...
Click to collapse
Nope. Only difference between devices is memory size and your device regognize correct size even if you use this. Only thing is your device shows as SGP511 but you can chance that in build.prop file if you like.
Er... on my Z2 Tablet with .726 firmware there is no "Ultra Stamina" mode... or am I missing something?
Or is "Ultra Stamina" introduced only with this new firmware version??
Thanks, I just noticed this version was offered as a 21 MB system update on my current ROM (23.1.A.0.690 NCB). But this is much better :good:
hasenbein1966 said:
Er... on my Z2 Tablet with .726 firmware there is no "Ultra Stamina" mode... or am I missing something?
Or is "Ultra Stamina" introduced only with this new firmware version??
Click to expand...
Click to collapse
You are right. Chancelog is copy/pasted from universal source so there is device specific differencies and because this device is wifi only there is no ultra stamina mode.
kulvertti said:
You are right. Chancelog is copy/pasted from universal source so there is device specific differencies and because this device is wifi only there is no ultra stamina mode.
Click to expand...
Click to collapse
hey man...if I flash this I will losse all my internal sd data? or I only need to backup my apps and nothing more? (sorry if I ask to much things)
Cocolopes said:
hey man...if I flash this I will losse all my internal sd data? or I only need to backup my apps and nothing more? (sorry if I ask to much things)
Click to expand...
Click to collapse
For to be safe I recommend to make nandroid backup including kernel, system and data. However if something go wrong system backup with kernel might be enough to bring your device back.
This ain't wipe your internal sd on it's own so it is your choice.
Thanks man, you're always so fast! We should be getting 5.1 next month I read somewhere
Tap to awake isnt working, is ghis a known bug?
BLiapis said:
Tap to awake isnt working, is ghis a known bug?
Click to expand...
Click to collapse
Nope. Double tap to wake work fine here.
Factory reset coming from KK, everything working perfectly, including root/SU and double tap to wake.
In case anyone has similar issues, I couldn't download from Mega directly to device (it kept disconnecting at around 10%), had to download using PC and transfer using SD card.
Thanks Kulvertti for all the work you do for our device, it is much appreciated! :good:
Hello !
I am already on Lollipop & rooted, does updating thanks to the Sony update center will keep my root or does this flashable zip is mandatory to keep root ?
Thanks
Angeal Hewley said:
Hello !
I am already on Lollipop & rooted, does updating thanks to the Sony update center will keep my root or does this flashable zip is mandatory to keep root ?
Thanks
Click to expand...
Click to collapse
This will keep your root. About OTA, maybe with small updates but haven't tested it with latest update.
kulvertti said:
This will keep your root. About OTA, maybe with small updates but haven't tested it with latest update.
Click to expand...
Click to collapse
Thanks for the reply!
I flashed your zip to be 100% sure to keep root
issue
hey man,
I just spent like 2 hours trying to get CWM installed for castor windy. finally ended up using a combo of ADB "fastboot reboot-bootloader" reboot-boot <lightning-bolt-symbol/fastboot mode/select kernal to flash> and put in an extracted boot.img for CWM (nightly build). i then did "fastboot reboot" and rapidly pressed the volume up button. it worked and im now in CWM. I put your zip on my sd card before, and I navigated to that <apply update/choose from sdcard1/flashablesomeupdatedetailsidontwanttocopy.zip> (strangly I noticed that there were 2 identical "choose from sdcard1" options)
cwm paused for a second, then outputted
Install failedFinding update package...
Opening update package...
E:footer is wrong
E:signature verification failed
Installation aborted
sorry about my formatting of what I did, Im new to xda devs
thanks in advance for the help, and thank you for supporting a tablet that very few people seem to use
joeyishar said:
hey man,
I just spent like 2 hours trying to get CWM installed for castor windy. finally ended up using a combo of ADB "fastboot reboot-bootloader" reboot-boot <lightning-bolt-symbol/fastboot mode/select kernal to flash> and put in an extracted boot.img for CWM (nightly build). i then did "fastboot reboot" and rapidly pressed the volume up button. it worked and im now in CWM. I put your zip on my sd card before, and I navigated to that <apply update/choose from sdcard1/flashablesomeupdatedetailsidontwanttocopy.zip> (strangly I noticed that there were 2 identical "choose from sdcard1" options)
cwm paused for a second, then outputted
Install failedFinding update package...
Opening update package...
E:footer is wrong
E:signature verification failed
Installation aborted
sorry about my formatting of what I did, Im new to xda devs
thanks in advance for the help, and thank you for supporting a tablet that very few people seem to use
Click to expand...
Click to collapse
Install Dualrecovery from here: http://forum.xda-developers.com/showthread.php?p=53661356 and use TWRP to flash .zip file.
kulvertti said:
Install Dualrecovery from here: http://forum.xda-developers.com/showthread.php?p=53661356 and use TWRP to flash .zip file.
Click to expand...
Click to collapse
First: Thanks to Kulvertti for all his work.
I am still confused. Do I need to root my device on forehand?
What I have understood so far:
You don't have to have root to flash NUT's [TABZ2][TWRP][PhilZ Touch][CWM] XZDualRecovery (It won't bring you root either).
So you can flash this recovery as long as you are on unrooted but rootable stock firmware (e.g. 17.1.2.A.0.314).
Then can flash this pre-rooted stock Lollipop ROM 23.1.A.1.28 and you will have root.
So only 3 steps to go from unrooted stock Lollipop to to this pre-rooted Lollipop?
1) flash rootable firmware (from PC, using flashtool).
2) flash "NUT's" recovery (from PC, using NUT's installer).
3) flash this pre-rooted stock Lollipop ROM (from sdcard1, using TWRP recovery)
Is this correct??
UPDATE:
Moved my TWRP activities into this new thread !
http://forum.xda-developers.com/pixel-c/development/twrp-3-0-2-0v16-t3400503
As I still like to make the "perfect" TWRP for Pixel C .. here are the next versions ...
Update.ZIP_TWRP_dragon_3.0.2-0_v16.zip -> to be installed via TWRP
TWRP_dragon_3.0.2-0_v16.img -> to be installed via fastboot
Changes to previous (v15) version:
- ADB shell was not working in recovery - fixed now !
- chromeos-3.18 kernel -> v160617
Pls find the new version here: http://forum.xda-developers.com/pixel-c/development/twrp-3-0-2-0v16-t3400503
followmsi said:
As it looks like, I do have my prodcutive weekend ..
Today I have released a new TWRP version .. USB-OTG works now.
Update.ZIP_TWRP_dragon_3.0.2-0_v4.zip
Now I have made another version .. Update.ZIP_TWRP_dragon_3.0.2-0_v5.zip
For this version I have ported the Nexus 6 P decryption functionality to Pixel C.
As I don´t have an encrypted /data partition anymore I would like to ask for some testers.
This TWRP version should be able to access your encrypted data partition now - hopefully.
Please install both versions from your current TWRP.
Pls make a "reboot to recovery" once you have installed the .zip file.
Inside the download folder there also .img files for fastboot installation, or you unzip the .zip file.
Download frome here: https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks
Click to expand...
Click to collapse
Good stuff!
I'm decrypted so can't test that, but the USB-OTG is working AOK! :good:
Thanks for report ..
v5 will not make problems if you are already decrypted, like me too.
OTG is working fine in both versions.
I'm now decrypted, but thanks for the efforts for people coming from a clean encrypted state
My usb-c to micro usb is not working for me with my otg cable, so i will have to wait to test that functionaility too.
scoobydu said:
I'm now decrypted, but thanks for the efforts for people coming from a clean encrypted state
My usb-c to micro usb is not working for me with my otg cable, so i will have to wait to test that functionaility too.
Click to expand...
Click to collapse
Thanks for the info ..
I guess I will encrypt my data partition soon and test myself.
Now as I have a quick backup and restore possibility
When you release something you should be able to "fully" test it.
I have a small USB-C adapter which is working in normal system and now in recovery as well.
Luckily it's working .. there are many cables and adapters which are not working.
Cheers
I´m on a decripted device too but I have now a Nandroid on an USB stick! That´s really awesome! Thanks followmsi
My anker adapter doesn't work, but I have ordered another from amazon, due tomorrow, that is supposed to support org, so will hopefully be able to test the otg then.
v4 worked perfectly. It was exactly what i needed. Thank you.
followmsi said:
This TWRP version should be able to access your encrypted data partition now - hopefully.
Click to expand...
Click to collapse
Not sure it's working. From a fresh, locked Pixel C, I unlocked bootloader, flashed TWRP_dragon_3.0.2-0_v5.1.img via fastboot, rebooted into recovery and TWRP still cannot see/mount the data partition. Did I miss a step somewhere or do something wrong?
stevehanler said:
Not sure it's working. From a fresh, locked Pixel C, I unlocked bootloader, flashed TWRP_dragon_3.0.2-0_v5.1.img via fastboot, rebooted into recovery and TWRP still cannot see/mount the data partition. Did I miss a step somewhere or do something wrong?
Click to expand...
Click to collapse
Same for me
RolfFrie said:
Same for me
Click to expand...
Click to collapse
Thanks for the update .. it is not working yet.
It was a test .. I have implemented the "original" TWRP mechanism for decryption .. but Pixel C is using other libraries to decrypt .. "angler" and "bullhead" are using the same way.
But they are not "mixed" ChromeOS devices.
Will remove v5.1 soon from the website .. hopefully we will manage it later on.
Maybe I will add a short technical description .. what I did and maybe someone else is able to get the rest of the puzzle.
Thanks for your help and testing !
Cheers
stevehanler said:
Not sure it's working. From a fresh, locked Pixel C, I unlocked bootloader, flashed TWRP_dragon_3.0.2-0_v5.1.img via fastboot, rebooted into recovery and TWRP still cannot see/mount the data partition. Did I miss a step somewhere or do something wrong?
Click to expand...
Click to collapse
Are you still encrypted ?
Pls have another try .. v5.5 .. the last try
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks
followmsi said:
Are you still encrypted ?
Pls have another try .. v5.5 .. the last try
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks
Click to expand...
Click to collapse
I flashed the N preview 3 like stock but now I'm encrypted... How can uncrypt it ?
En Kee said:
I flashed the N preview 3 like stock but now I'm encrypted... How can uncrypt it ?
Click to expand...
Click to collapse
Encrypted would be good .. but I am not sure if the TWRP works the same on N.
To decrypt you need to format your data .. with encryptable flag, e.g. Install SuperSU 2.72 above.
Cheers
followmsi said:
Are you still encrypted ?
Pls have another try .. v5.5 .. the last try
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks
Click to expand...
Click to collapse
I'm not unfortunately.
I was stuck in a recovery bootloop whatever I do... But... In bootloader it worked with the command : fastboot reboot.... I don't know why but I don't care !
I'm now with the N Preview 3 and rooted
While testing new kernel I had the same issue today.
Recovery bootloop.
"fastboot reboot" sovled the problem ...
Cheers
followmsi said:
While testing new kernel I had the same issue today.
Recovery bootloop.
"fastboot reboot" sovled the problem ...
Cheers
Click to expand...
Click to collapse
any changelog?
worth to update if i'm on your v4.6?
Smaller recovery image due to new lzma compressed kernel .. and the decryption libs are included.
Nothing else has changed.
No real need to upgrade .. but with update.zip the update goes fast anyway.
Cheers
The Recovery bootloop is a little bit tricky sometimes. Because if you do not own a PC (like me for the moment) you couldn't work with the tablet for a while. I had one Loop after making a nandroid. So I fear to turn off the device.
Is it possible to jump back to stock recovery for example before I'm traveling and reflash TWRP back home to minimize the risk of a loop when there is no PC reachable?
Hello, guys. Today i'm compiling the latest twrp.img using official omnirom 8.0 & Lineage 14.1 source code.
Seems all works as it should. Enjoy.
Need:
* unlocked bootloader
* latest official firmware .291
How-to:
* download recovery.img
* turn off your phone and flash recovery
Code:
fastboot flash recovery name_of_recovery.img
* press vol-down + power, when phone vibrate, unpress only power button. See logo 'Sony' unpress vol-down button.
Thanks:
* @nailyk for decryption
UPDATE_09.03.2017:
* new version 3.1.0-0
UPDATE_13.05.2017
* new version 3.1.1-0
UPDATE_03.12.2017
* new version 3.2.0-0
UPDATE_09.12.2017
* new version 3.2.1-0
UPDATE_14.12.2017
* added omni's version
Download Lineage 14.1 recovery:
HERE
Download Omni 8.0 recovery
HERE
Well done... Did you test also *.img flash?
I had some issues with 3.0.2.1 for aries. This gave me error messages (sorry cannot remember which in particular)
But 3.0.2.0 works as usual.
EDIT
* press vol-down + power, when phone vibrate, unpress only power button. See logo 'Sony' unpress vol-down button.
For me its just enough to release them both quite quickly after it vibrates...
Is it work only for android n? Or including android M? And is it fota recovery?
fluffi444 said:
Well done... Did you test also *.img flash?
Click to expand...
Click to collapse
What img files are you mean?
Recovery can flash only boot and recovery imgs
dddestiny said:
Is it work only for android n? Or including android M? And is it fota recovery?
Click to expand...
Click to collapse
It's work on Android M and yes, this is fota recovery
russel5 said:
What img files are you mean?
Recovery can flash only boot and recovery imgs
Click to expand...
Click to collapse
boot.img made problems. But I am going to test it for myself. No problem.
fluffi444 said:
boot.img made problems. But I am going to test it for myself. No problem.
Click to expand...
Click to collapse
OK - Looks like that it works!
But still one question left: In Backup CACHE is showing only with (0MB)
I know that backing up cache seams to be useless but sometimes its still usefull. In old TWRP 3.0.2.0 is shows mostly (4MB).
If I backup CACHE with 3.0.3.0 its give me the output 0MB saved.
Has it some thing to do with the arguments of CACHE in recovery.fstab?
Code:
noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic wait,check,formattable
This is the old from 3.0.2.0 (not yet tried to change that in 3.0.3.0)
Code:
nosuid,nodev wait
EDIT
And finally USB-OTG is working! Cool!!!
@fluffi444 bro, twrp not using recovery.fstab, it's using twrp.fstab
and what size of your cache folder when your phone is booting up? my is only 40kb that's all.
russel5 said:
@fluffi444 bro, twrp not using recovery.fstab, it's using twrp.fstab
and what size of your cache folder when your phone is booting up? my is only 40kb that's all.
Click to expand...
Click to collapse
OK - feel a bit dumb now ...
I have 4,08 MB (an 192,53 MB free) - that is what Solid Explorer gives me...
EDIT
I put now an 4,5 MB file to CACHE folder - An now it shows me (5 MB) in recovery
EDIT2
I check again single folders and files in CACHE folder - They have only 22,47 KB in total...(without my manual copied file)
I guess we can close this discussion Thanks again for your work and your help!
I guess they changed the way of correct recognition of the free space.
I installed this recovery in my Z3C running the AOSP 7.1.1 ROM, but, as soon as I turned my phone on afterwards, my SD card was accused to be corrupted. As soon as I went back to TWRP v3.0.2-0, everything went back to normal. It's a 512 GB card, if it matters.
Sent from my Sony D5833 using XDA Labs
casouzaj said:
I installed this recovery
Click to expand...
Click to collapse
Can you post the recovery log to see what happend?
russel5 said:
Can you post the recovery log to see what happend?
Click to expand...
Click to collapse
Nevermind! I flashed it again in order to grab the log, but the issue simply didn't happen. Don't know what caused it the first time I flashed it. I'm keeping it this way. Thanks, anyway!
Sent from my Sony D5833 using XDA Labs
@russel5 Im guessing this is not official, but im a little bit confused? What is that build.prop you have attached in the OP?
EDIT: Btw great work man!
How to flash the recovery on concept 3657? when I flash the recovery, it hints "partition table doesn't exist"
panzerox123 said:
@russel5 Im guessing this is not official, but im a little bit confused? What is that build.prop you have attached in the OP?
EDIT: Btw great work man!
Click to expand...
Click to collapse
What do you mean, not official? Build.prop generated when you compiled something from sources.
Sent from my Sony D5803 using XDA Labs
russel5 said:
What do you mean, not official? Build.prop generated when you compiled something from sources.
Click to expand...
Click to collapse
By not official, I meant it's not on the twrp page yet ...
I was confused because build.prop says omni_aries
panzerox123 said:
By not official, I meant it's not on the twrp page yet ...
I was confused because build.prop says omni_aries
Click to expand...
Click to collapse
It's not on twrp page because i need to write email and send this to omniteam, don't want.
And aries mean z3c, like sirius z2 and other. Omni used aosp names in devices tree, like this https://github.com/sonyxperiadev/device-sony-aries
russel5 said:
It's not on twrp page because i need to write email and send this to omniteam, don't want.
And aries mean z3c, like sirius z2 and other. Omni used aosp names in devices tree, like this https://github.com/sonyxperiadev/device-sony-aries
Click to expand...
Click to collapse
I understand. So is this more stable than 3.0.2-1?
There are so many peoples on my home forum had problems with this version 2-1.
This thread created for you, guys. You can tell me - stable this new version or not
For me all works like it should. Tested on unlocked bootloader and locked.
russel5 said:
There are so many peoples on my home forum had problems with this version 2-1.
This thread created for you, guys. You can tell me - stable this new version or not
For me all works like it should. Tested on unlocked bootloader and locked.
Click to expand...
Click to collapse
Full stable for me. Thanks again for your work.
anyone tried flashing this on carbon rom?
Guys.
I made a bit modified version of @russel5 very nice work for our Z3C:
- A bit more colors, nice navbar buttons and new navbar background (fits to main screen background)
- More img flash options (be carefull with img flash because wrong flashes can brick you phone)
- More partition backup and restore options (boot is also included for sure - but not shown on the pic)
- New with 3.1.0-0: Additional partition for backup/restore: mmcblk1p2 ext4 mounted to /sd-ext - This is second partition on external SD Card, if available.
- New with 3.1.1-0: All above mentioned changes and official ones: https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
Too beauty to keep it only for me
Requirements
Only for Unlocked Bootloader (UB)
New Bootloader needed: LA3.0_M_3
Information
Maybe NOT working with 7.x.x ROMs like (LineageOS/Carbon) - Only tested with MM and stock-like ROM (like SLiMM 3.8).
Please visit corresponing threads for help with TWRP and any 7.x.x ROM.
Installation - 2 Options:
a) Flashable zip via TWRP to update existing.
b) Extract twrp-3.x.x-0-z3c_Vxx.img from zip-file and flash via fastboot: fastboot flash recovery twrp-3.x.x-0-z3c_Vxx.img
Start FOTA Recovery:
Shut down phone completely - wait 5-10 secs - Press Power and Vol Down until short vibration - release both keys and wait - done.
UPDATE 18.06.2017
New 3.1.1-0 from Russel5 - Modded by me. Thanks to Russel5 and TWRP-Team.
UPDATE 15.03.2017
New 3.1.0-0 from Russel5 - Big thx again to him! Say thanks to him - not me!
Thanks to @russel5 - This is his work:
https://forum.xda-developers.com/z3-compact/general/d5803-z3c-aries-twrp3-0-t3543113
@fluffi444 I flashed the recovery.img in fota with twrp and recovery is still 3.0.2. Any idea why?
doriandiaconu said:
@fluffi444 I flashed the recovery.img in fota with twrp and recovery is still 3.0.2. Any idea why?
Click to expand...
Click to collapse
Maybe i have an idea.... You know how to start FOTA Recovery correctly?
Shut down phone completely - wait 5 secs - Press Power and Vol Down until short vibration - release both keys and wait - done.
Looks like you still booting your system or kernel recovery....
Otherwise check your bootloader - must be LA3.0_M_3 (Service Menu - Service Info - Software Info - S1 Boot Version)
UPDATE 15.03.2017
New 3.1.0-0 from @russel5 - Big thx again to him! Say thanks to him - not me!
can someone please explain/summarize for me the differences of twrp recoveries that we have on the z3c. if i got it right, there is (1) old bl recovery = kernel 'attached', (2) new bl recovery = seperated img from kernel and (3) fota recovery wich uses an unused partition of unlocked bl.
is that correct?
whats the advantage of fota? can every custom rom use all the different recoveries? can (2) + (3) be flashed both on the same device?
i am really confused wich version i wanna install and keep on my phone...
thanks
filou76 said:
can someone please explain/summarize for me the differences of twrp recoveries that we have on the z3c. if i got it right, there is (1) old bl recovery = kernel 'attached', (2) new bl recovery = seperated img from kernel and (3) fota recovery wich uses an unused partition of unlocked bl.
is that correct?
whats the advantage of fota? can every custom rom use all the different recoveries? can (2) + (3) be flashed both on the same device?
i am really confused wich version i wanna install and keep on my phone...
thanks
Click to expand...
Click to collapse
Yes - this all can be confusing!
I'm trying to be complete as I can be - I will mention only the last dev of the tools - Actually many more are involved and often it's an growing work of many - Especially No 1.
1) For LB - We have recovery (and root) for LB - Here the last (and best) rooting and TWRP method is the one from russel5:
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This installs recovery files to SYSTEM partition folder /system/etc/mm_twrp_recovery
This is file: recovery.twrp.cpio.lzma
2) Only UB - Recovery integrated in Kernel a) and b)
a) Rootkernel (tobias.waldvogel) https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
afaik this was one of the first tools which can integrated automaticly very resource-conserving recovery to kernel - Disadvantage: Hard to change TWRP if new version is out.
b) PoC TA Tool (munjeni) https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
Great quite new tool which can also integrate TWRP (but here the complete fota recovery.img) to kernel: Advantage easy to change TWRP to new version, because full fota revovery.img is used
3) Only UB - Recovery to FOTA partition (now known as recovery partition) - newer bootloader needed
This is the recovery.img you can download from official TWRP page or from russel5 (img to be flashed via fastboot) or from this thread (flashable.zip).
Those recovery.img's are complete bootable images with zImage and ramdisk (TWRP is in ramdisk).
That all means that it's indeed possible to have THREE recvoerys running on one phone! But this is senseless of course !!!
Option 1 is only recomended if you are on LB! But works also for UB. But its away if you flash complete new ROM (as TWRP is on SYSTEM)
Option 2 is.... for what? Let me say: Only if you really need the function to reboot to recovery directly from system.
Option 3 is my favorite (but only for UB) - this is bootable no matter what you did to system or even with kernel!
It's on his own seperate partionen and save for unwanted modifications, wrong boot or system flashes, etc
Only (and actually not really an) disadvantage is that you have to start this from shutted down phone... Reboot to recovery is not working!
fluffi444 said:
Yes - this all can be confusing!
I'm trying to be complete as I can be - I will mention only the last dev of the tools - Actually many more are involved and often it's an growing work of many - Especially No 1.
1) For LB - We have recovery (and root) for LB - Here the last (and best) rooting and TWRP method is the one from russel5:
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This installs recovery files to SYSTEM partition folder /system/etc/mm_twrp_recovery
This is file: recovery.twrp.cpio.lzma
2) Only UB - Recovery integrated in Kernel a) and b)
a) Rootkernel (tobias.waldvogel) https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
afaik this was one of the first tools which can integrated automaticly very resource-conserving recovery to kernel - Disadvantage: Hard to change TWRP if new version is out.
b) PoC TA Tool (munjeni) https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
Great quite new tool which can also integrate TWRP (but here the complete fota recovery.img) to kernel: Advantage easy to change TWRP to new version, because full fota revovery.img is used
3) Only UB - Recovery to FOTA partition (now known as recovery partition) - newer bootloader needed
This is the recovery.img you can download from official TWRP page or from russel5 (img to be flashed via fastboot) or from this thread (flashable.zip).
Those recovery.img's are complete bootable images with zImage and ramdisk (TWRP is in ramdisk).
That all means that it's indeed possible to have THREE recvoerys running on one phone! But this is senseless of course !!!
Option 1 is only recomended if you are on LB! But works also for UB. But its away if you flash complete new ROM (as TWRP is on SYSTEM)
Option 2 is.... for what? Let me say: Only if you really need the function to reboot to recovery directly from system.
Option 3 is my favorite (but only for UB) - this is bootable no matter what you did to system or even with kernel!
It's on his own seperate partionen and save for unwanted modifications, wrong boot or system flashes, etc
Only (and actually not really an) disadvantage is that you have to start this from shutted down phone... Reboot to recovery is not working!
Click to expand...
Click to collapse
Wow, thanks a lot @fluffi444!! It's even more complicated than I thaught. WHAT A MESS! :silly:
Well I'am still on Concept Rom --> Bootloader LA3.0_L_Hero_16. I guess that one is close to LA3.0_M_3? Don't remember where I got my TWRP 3.0.0.0 version from, but i flashed it as recovery.img, so it should be fota-type, right? Actually I can reboot from system to recovery ...
I think I'll keep this one as is and see if I need a newer version one day, when i change system to any Nougat rom.
filou76 said:
Wow, thanks a lot @fluffi444!! It's even more complicated than I thaught. WHAT A MESS! :silly:
Well I'am still on Concept Rom --> Bootloader LA3.0_L_Hero_16. I guess that one is close to LA3.0_M_3? Don't remember where I got my TWRP 3.0.0.0 version from, but i flashed it as recovery.img, so it should be fota-type, right? Actually I can reboot from system to recovery ...
I think I'll keep this one as is and see if I need a newer version one day, when i change system to any Nougat rom.
Click to expand...
Click to collapse
Yes - flashing by fastboot goes to FOTA/Recovery partition... Yes - keep it - I don't even know how Concept N or M will react...
Did anyone tried to do backup/restore with this recovery?
I am using it since flashing to LineageOS 14.1 and did multiple backups. Tonight I broken my google account in the ROM, so I wanted to restore to last backup. I already tried four of my backups and all of them are bootlooping, so I am starting to suspect the recovery, as all of those backups were done from perfectly working system.
johny.mnemonic said:
Did anyone tried to do backup/restore with this recovery?
I am using it since flashing to LineageOS 14.1 and did multiple backups. Tonight I broken my google account in the ROM, so I wanted to restore to last backup. I already tried four of my backups and all of them are bootlooping, so I am starting to suspect the recovery, as all of those backups were done from perfectly working system.
Click to expand...
Click to collapse
Yes - fully working here. Even Restore. But I still use 6.0.1.
But sometimes (not recovery version related) its not enough to restore only DATA or only SYSTEM.
It happens to me that only an complete restore of all saved partition did the trick...
But as I said that happens also with older recoverys or/and not modded.
fluffi444 said:
Yes - fully working here. Even Restore. But I still use 6.0.1.
But sometimes (not recovery version related) its not enough to restore only DATA or only SYSTEM.
It happens to me that only an complete restore of all saved partition did the trick...
But as I said that happens also with older recoverys or/and not modded.
Click to expand...
Click to collapse
Then it must be something either with my setup, or with 7.1.1 itself.
I tried everything: partial restore, full restore, new flash with recovering of data partition only... Everything was bootlooping.
I am not sure what finally worked, as I was trying it desperately for hours, but most probably the last mentioned thing without flashing Magisk.
johny.mnemonic said:
Then it must be something either with my setup, or with 7.1.1 itself.
I tried everything: partial restore, full restore, new flash with recovering of data partition only... Everything was bootlooping.
I am not sure what finally worked, as I was trying it desperately for hours, but most probably the last mentioned thing without flashing Magisk.
Click to expand...
Click to collapse
Try twrp 3.0.2.0 or 3.0.3.0. Some said they have problems with 3.1.0.0 an LOS.
UPDATE 18.06.2017
New 3.1.1-0 from Russel5 - Modded by me. Thanks to Russel5 and TWRP-Team.
Hi,
This recovery its amazing because i am trying to have a 6.0.1 With TWRP 3.x.x with Magisk, root and Xposed. At the moment when i ve Magisk and root, i miss Recovery by Magisk mod boot image.
Any idea why screen appear as out resolution or refresh. At least ... it seen enter on Recovery, BUT I CANT reset With Vol+, Vol-, Cam , Power...
at least i can connect by adb and restart.
¿Any idea?
Thanks
zeryors said:
Hi,
This recovery its amazing because i am trying to have a 6.0.1 With TWRP 3.x.x with Magisk, root and Xposed. At the moment when i ve Magisk and root, i miss Recovery by Magisk mod boot image.
Any idea why screen appear as out resolution or refresh. At least ... it seen enter on Recovery, BUT I CANT reset With Vol+, Vol-, Cam , Power...
at least i can connect by adb and restart.
¿Any idea?
Thanks
Click to expand...
Click to collapse
Hi, i know the sad answer... the problem its the screen, Original Screen (broken touch panel) show perfect Recovery but the "new" screen its the problem... its compatible but not 100% :_(
It´s curious a normal Recovery show OK but not FOTA
Hi there,
booting this current version of TWRP from `recovery/fota` is not working for me. The device just reboots but should load TWRP. I flashed it via `fastboot flash recovery [twrp.img]` without any errors.
TWRP is booting if I flash it to `boot` instead of `recovery`. I flashed CarbonROM this way but lost TWRP after that of course. I also tried [russel5's TWRP 3.1.1-0] which is not booting from `recovery/fota` either. However, an older TWRP version by Tomascus I found -> here <- is booting fine from `recovery/fota`.
Maybe this is bootloader related but I am not entirely sure. If so, how can I update the bootloader?
Sony Xperia Z3 Compact D5803
- Bootloader: 1286-7314_S1_Boot_MSM8974AC_LA3.0_52-2
- ROM: CARBON-CR-5.1-MOO-RELEASE-z3c-20170918-1012
TWRP's tried:
- Russel5's TWRP 3.1.1-0 FOTA Recovery MOD by fluffi444
- [D5803,z3c,aries]Twrp_3.1.1-0_img_for_unlocked_bootloader by russel5
- Tomascus TWRP 3.1.0-0
Andi- said:
Hi there,
booting this current version of TWRP from `recovery/fota` is not working for me. The device just reboots but should load TWRP. I flashed it via `fastboot flash recovery [twrp.img]` without any errors.
Click to expand...
Click to collapse
My MOD is technically the same as original one from Russel. So please ask in his thread (you did this already... btw: please do not post the same question in several threads)
I never tried 7.x.x-based ROMs. So I cannot say anything reladed to the compatibility I'm afraid. MM with stock-like ROM is working with 3.1.1.0 (from Russel).
I will make an note in OP...
And note this: https://forum.xda-developers.com/showpost.php?p=71882082&postcount=12
I am trying to install a newer TWRP for Carbon Mod custom rom. I tried:
- install .img with TWRP in TWRP
- flashify
- official app TWRP from google play
- fastboot commands with "platform-tools"
Everywhere I get a message that everything went fine but in TWRP I still have the old version - 3.0.0.2 :/
I am asking for help because I have been fighting this from two days :/
I have Xperia Z3C with unlocked bootloader, stock prerooted firmware .291 + EliteKernel v3.
Piospi said:
I am trying to install a newer TWRP for Carbon Mod custom rom. I tried:
- install .img with TWRP in TWRP
- flashify
- official app TWRP from google play
- fastboot commands with "platform-tools"
Everywhere I get a message that everything went fine but in TWRP I still have the old version - 3.0.0.2 :/
I am asking for help because I have been fighting this from two days :/
I have Xperia Z3C with unlocked bootloader, stock prerooted firmware .291 + EliteKernel v3.
Click to expand...
Click to collapse
To which partition have you installed the TWRP image file? Starting with your phone turned off, f it's been sent to the FOTAKernel partition, hold both the power and the volume down buttons until your phone vibrates (as if it was booting up normally), when you should release the power button. When the screen lights up, release the volume down button.
Otherwise, if you installed TWRP in the recovery partition, boot your phone up as usual. When you see the led lit up, press the volume button.
casouzaj said:
To which partition have you installed the TWRP image file? Starting with your phone turned off, f it's been sent to the FOTAKernel partition, hold both the power and the volume down buttons until your phone vibrates (as if it was booting up normally), when you should release the power button. When the screen lights up, release the volume down button.
Otherwise, if you installed TWRP in the recovery partition, boot your phone up as usual. When you see the led lit up, press the volume button.
Click to expand...
Click to collapse
Thank you very much for the answer. Starting the phone with Power + VolUp does not do anything. The phone shows the Sony logo and the system starts.
I installed the IMG file in recovery / fota and the ZIP version doesn't ask for locations.
Today I updated my Asus Zenfone max Pro M2 to pie via fota update.
After successful installation the phone rebooted,
And then the thing happened, screen keeps blinking.
Any suggestions? I have 6gb varient
Fix for screen blinking after pie stable fota update
Vikassir33 said:
Today I updated my Asus Zenfone max Pro M2 to pie via fota update.
After successful installation the phone rebooted,
And then the thing happened, screen keeps blinking.
Any suggestions? I have 6gb varient
Click to expand...
Click to collapse
1.First unlock the bootloader of your phone.
2.Download Oreo fastboot rom raw zip file.
3.Install the necessary drivers and platform tools in your laptop.
4. Extract the rom zip file.
5. Copy all contained files in the rom file and paste in the platform tools folder.
6.Now enable usb debugging and connect phone to the laptop.
7.Enter the platform tools folder and open cmd and write "adb reboot bootloader"
8. Now once you are in fastboot mode double click on Flash_All.cmd in platform tools.
9.After that you will boot your system in oero build .
10.Now final stem check for system updates and you will get a fota update arround 800mb
11.After the update done you are good to go.
12. For further any quarry you can contact me(Whatsapp+call) : 8670647386 Gmail: [email protected]
WARNING!! : 1. DO NOT UPDATE IN PIE AFTER 800mb UPDATE UNTILTHE NEXT PIE UPDATE IS COMMING.
2. ANY MISTAKE CAN BRICK YOUR DEVICE I WILL NOT BE RESPONSIBLE FOR THIS.
All the links and screenshots will be given tomorrow.
subhojit2016 said:
1.First unlock the bootloader of your phone.
2.Download Oreo fastboot rom raw zip file.
3.Install the necessary drivers and platform tools in your laptop.
4. Extract the rom zip file.
5. Copy all contained files in the rom file and paste in the platform tools folder.
6.Now enable usb debugging and connect phone to the laptop.
7.Enter the platform tools folder and open cmd and write "adb reboot bootloader"
8. Now once you are in fastboot mode double click on Flash_All.cmd in platform tools.
9.After that you will boot your system in oero build .
10.Now final stem check for system updates and you will get a fota update arround 800mb
11.After the update done you are good to go.
12. For further any quarry you can contact me(Whatsapp+call) : 8670647386 Gmail: [email protected]
WARNING!! : 1. DO NOT UPDATE IN PIE AFTER 800mb UPDATE UNTILTHE NEXT PIE UPDATE IS COMMING.
2. ANY MISTAKE CAN BRICK YOUR DEVICE I WILL NOT BE RESPONSIBLE FOR THIS.
All the links and screenshots will be given tomorrow.
Click to expand...
Click to collapse
Fastboot ROM?????? Where can we get fastboot ROM from? I am searching from last few days, but I didn't get the fastboot ROM.
nice_guy75 said:
Fastboot ROM?????? Where can we get fastboot ROM from? I am searching from last few days, but I didn't get the fastboot ROM.
Click to expand...
Click to collapse
Download This Version WW-15.2016.1812.179 OR WW-15.2016.1901.186 (revert back to oreo from android p)
RedRobbin said:
Download This Version WW-15.2016.1812.179 OR WW-15.2016.1901.186 (revert back to oreo from android p)
Click to expand...
Click to collapse
@RedRobbin
There are no active links,
The blinking problem solved by itself, I don't know what changed, but now no blinking any more
Vikassir33 said:
The blinking problem solved by itself, I don't know what changed, but now no blinking any more
Click to expand...
Click to collapse
Sadly my phone is still giving me this screen blinking issue.
Anything you remember particularly doing before your phone was fixed?
nice_guy75 said:
@RedRobbin
There are no active links,
Click to expand...
Click to collapse
You can download from official website its size around 1.7 gb
RedRobbin said:
You can download from official website its size around 1.7 gb
Click to expand...
Click to collapse
Official site does not have fastboot ROM, those zips are meant to be flashed via stock recovery.
Sent from my ASUS_X01BDA using Tapatalk
Is there a technical reason why you can rollback to the last month's ROM from the Asus website with the stock recovery? Has the filesystem changed or something?
nice_guy75 said:
Official site does not have fastboot ROM, those zips are meant to be flashed via stock recovery.
-- Flash stock recovery
-- Put downloaded zip file into external SD
-- Boot into stock recovery
-- Apply update from external storage and locate file
-- done
Click to expand...
Click to collapse
RedRobbin said:
nice_guy75 said:
Official site does not have fastboot ROM, those zips are meant to be flashed via stock recovery.
-- Flash stock recovery
-- Put downloaded zip file into external SD
-- Boot into stock recovery
-- Apply update from external storage and locate file
-- done
Click to expand...
Click to collapse
That I know, I wanted to have Fastboot ROM, which can be flashed via PC.
Click to expand...
Click to collapse
I tried to install the laat Oreo ROM from the Asus website using stock recovery but it failed with a message something like, you can't flash an older version than the one installed.
damole said:
Is there a technical reason why you can rollback to the last month's ROM from the Asus website with the stock recovery? Has the filesystem changed or something?
Click to expand...
Click to collapse
Dear simply visit any Asus service center they will downgrade it to Oreo, I visited today, and one interesting thing is they don't have any stable update for now . Soon a newer fota update will release.
damole said:
I tried to install the laat Oreo ROM from the Asus website using stock recovery but it failed with a message something like, you can't flash an older version than the one installed.
Click to expand...
Click to collapse
First flash twrp then wipe everything except sd card and then flash stock recovery and try again
I posted here about the issues I had. I know that at first the problem is the old firmware can't be installed over newer firmware, when I fix that problem the zip package is no longer signed correctly.
Please could you explain why the method you suggest will work.
Yes it's work i done with 2 max pro m2
damole said:
I posted here about the issues I had. I know that at first the problem is the old firmware can't be installed over newer firmware, when I fix that problem the zip package is no longer signed correctly.
Please could you explain why the method you suggest will work.
Click to expand...
Click to collapse
In case of system update failure the zip file you are trying to flash will be corrupted. (Happened with me many times as i renamed the oreo stock rom to above the build number of the pie update so my phone would treat the downloaded oreo rom to be new .but during the system update after reaching aroung 25 % it displayed an error and the next thing i remember is the zip file getting corrupted) so always keep a backup!
On 25th of april new pie update was released which fixed screen blinking issue.