I have a Zenfone 2 (ZE551ML) with the latest WW firmware (2.20.40.97) which is obviously causing trouble with my phone. I want to revert back to the older firmware version (2.20.40.90 or even 2.20.40.63).
Is something like that possible on my phone? I've tried every resource that I could find online and nothing seems to work. It's not rooted - it's as is from the shop just with the latest update. I've tried sideloading but that obviously works only when updating firmware not downgrading. I've tried downloading recovery images and using fastboot to flash them but nothing happens.
So I ask again is it possible to downgrade stock firmware and if yes are there reliable tested instructions on how to do it?
Refer to http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 and follow the steps of root method 1 (pre-rooted image) to flash boot, droidboot and recovery images for the firmware version you want to revert to. However, DON'T download and flash the pre-rooted system image. Instead download the full firmware zip from ASUS, rename it as MOFD_SDUPDATE and place it on your external SD card. Erase your data and then boot back into the bootloader and then recovery mode. It should then install the firmware from your SD card.
kanagawaben said:
Refer to http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 and follow the steps of root method 1 (pre-rooted image) to flash boot, droidboot and recovery images for the firmware version you want to revert to. However, DON'T download and flash the pre-rooted system image. Instead download the full firmware zip from ASUS, rename it as MOFD_SDUPDATE and place it on your external SD card. Erase your data and then boot back into the bootloader and then recovery mode. It should then install the firmware from your SD card.
Click to expand...
Click to collapse
Thanks for the info! However I need help with the last part. I have no problem following up to the part about sending fastboot flash commands but what exactly does "Erase your data" mean? After I send the fastboot commands I am still in the bootloader screen. Do I proceed perhaps to the recovery mode to wipe/erase the cache? I am also wondering is it enough to just put the MOFD_SDUPDATE file in the root of the SD card? And do I need an unlocked bootloader to perform all these actions?
I understand that these questions might seem a bit noobish to experienced Android hackers but my experience on that field is limited to just doing one "unofficial" upgrade of my Nexus 4 to Lollipop so I would be grateful for any help.
EDIT: It seems I managed to figure out the correct order of things however when I reboot to bootloader I get the following error.
Code:
E:file path:/sdcard/MOFD_SDUPDATE.zip
E:failed to map file
SD installation aborted.
EDIT 2: It was actually an error on my end. I had my Windows set in a way to display file extensions so I accidentally named the file MOFD_SDUPDATE instead of MOFD_SDUPDATE.zip. Renaming the file did the trick.
I had to make a separate post just to thank you kanagawaben. Thanks! You are a life saver :victory: I've managed to successfully revert my phone to stock 2.20.40.90.
The best part is it resolves an issue with the proximity sensor which was obviously introduced with 2.20.40.97 (http://forum.xda-developers.com/zenfone2/help/proximity-sensor-inconsistently-t3224700/)
Related
Hello XDA, hello M9 users!
So, i rooted my phone back in September just to use some simple apps like Greenify, AdAway, etc. Yesterday the official Android 6.0 update arrived and I wanted to update. So I flashed the stock recovery and relocked my bootloader aaaand that was it. Everything was going ok untill the phone got in to the recovery. When it started to update the loading bar filled like 1/4. After that the red sign appeared on my screen. After that i just hard reseted my phone and everything was working ok and tried again but the same problem persisted. I started looking here on forums but i didn't find exact answeres except one. The guy sad: "The problem was solved. It took me 6 hours to manage this. All you need to do is re flash the stock backup with TWRP. ". Sadly I don't have the stock backup from my phone. And I'm thinking to reinstall TWRP recovery and flash version 1.32.401.8* from the thread called "HTC ONE M9 Stock File Collection (RUUs, Backups, etc.) - with linked Instructions" because I think that's the most stock version of this phone. So i have this question: should I do this or not? I am kinda noob, I am definetly not a pro with these things. I only know the basics and I am kindly asking for help. I will attach photos with phone info and everything that I mentioned here in the text. (sorry for my english, I'm trying my best)
If you guys find any solution I will be pleased to hear them!
Phone status:
-Rooted
-Bootloader: Relocked
-S ON
-Stock recovery (recovery version 2.10.401.1)
-SD Card capacity: 8GB only (i don't know if this helps)
-Stock 5.1 HTC Sense 7.0 (Software nr. 2.10.401.1)
-CID number: HTC__102
Thank you in advance!
Remember any changes with system such as root will cause OTA not work well.All you need to do is flash a RUU with right version.Or you can restore from TWRP with stock backup and flash stock recovery then you can get OTA.
If you want to install that update you either need the 2.10.401.1 backup or the corresponding RUU. As soon as you flash anything via TWRP your system gets mount as read/write. OTAs check the status of your system and fail if it's modified (=uninstalled system apps, root, etc.) and/or not mounted as read-only. Unrooting is not enough. You need to reflash an untouched system image (either via RUU or TWRP). Instructions can be found in my google sheet which is linked in post #5 of the thread where you found the 1.32.401.8 backup or in my signature.
Edit: Looks like I didn't type my answer fast enough.
Flippy498 said:
If you want to install that update you either need the 2.10.401.1 backup or the corresponding RUU. As soon as you flash anything via TWRP your system gets mount as read/write. OTAs check the status of your system and fail if it's modified (=uninstalled system apps, root, etc.) and/or not mounted as read-only. Unrooting is not enough. You need to reflash an untouched system image (either via RUU or TWRP). Instructions can be found in my google sheet which is linked in post #5 of the thread where you found the 1.32.401.8 backup or in my signature.
Edit: Looks like I didn't type my answer fast enough.
Click to expand...
Click to collapse
So the only thing i need to do is download "2.10.401.1.zip" RUU from your google sheet, copy it to my SD Card and enter in download mode and just wait untill it's done? Is this working with S-On?
It needs to be renamed correctly and the SD card needs to be formatted to fat32 (as stated in the instructions above the download links ). With S-ON you can use RUUs that have the same or a higher version than your phone. You only need S-OFF if you want to flash RUUs with a lower version (=downgrade) or one with a different SKU (the three numbers behind the second dot of the firmware version) than the one your phone got shipped with.
Flippy498 said:
It needs to be renamed correctly and the SD card needs to be formatted to fat32 (as stated in the instructions above the download links ). With S-ON you can use RUUs that have the same or a higher version than your phone. You only need S-OFF if you want to flash RUUs with a lower version (=downgrade) or one with a different SKU (the three numbers behind the second dot of the firmware version) than the one your phone got shipped with.
Click to expand...
Click to collapse
I am S-On and i don't want to S-Off. I don't want a lower version of RUU and i just want to simply upgrade to Android 6.0. So am I doing the right thing?
strikercs said:
I am S-On and i don't want to S-Off. I don't want a lower version of RUU and i just want to simply upgrade to Android 6.0. So am I doing the right thing?
Click to expand...
Click to collapse
Flippy498 said:
With S-ON you can use RUUs that have the same or a higher version than your phone.
Click to expand...
Click to collapse
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.
Flippy498 said:
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.
Click to expand...
Click to collapse
I have downloaded and copied the file on my SD Card using an SD Card reader because it wouldn't let me copy it using USB. The SD Card is FAT32 and i renamed the file to "0PJAIMG.zip". When i boot into the download mode it just enters download mode. It doesn't ask me if i want to flash the file. Any ideas what could be wrong?
Flippy498 said:
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.
Click to expand...
Click to collapse
I have downloaded and copied the file on my SD Card using an SD Card reader because it wouldn't let me copy it using USB. The SD Card is FAT32 and i renamed the file to "0PJAIMG.zip". When i boot into the download mode it just enters download mode. It doesn't ask me if i want to flash the file. Any ideas what could be wrong? I attached a screesnshot.
Are you sure you didn't rename it to "0PJAIMG.zip.zip". Looking at the "nmdsdcid" file I assume that file extensions aren't visible on your pc which could be the reason for your mistake.
Flippy498 said:
Are you sure you didn't rename it to "0PJAIMG.zip.zip". Looking at the "nmdsdcid" file I assume that file extensions aren't visible on your pc which could be the reason for your mistake.
Click to expand...
Click to collapse
I told you that I'm a noob. That's exactly what happened..
strikercs said:
I told you that I'm a noob. That's exactly what happened..
Click to expand...
Click to collapse
Thank you @Flippy498! Succesfully updated to Android 6.0!
So @Flippy498 saved my day with #3.
After getting to his really nice collection which can be found here and here I downloaded a TWRP Backup for my CID.
Remember fastboot getvar cid ?
Then I followed his nice tutorial until Step 5, but skipped 1 - 3.
Flippy498 said:
01. Format your SD card with a PC to exfat and put it back into your phone.
02. Boot to TWRP.
03. Create a backup on your external SD card. (Backing up "Boot" is more than enough. We only want TWRP to create the needed directories on your SD card.)
04. Download the correct backup for your firmware version. (It is stated in the line with "OS" at the beginning when you boot to download mode. The "firmware version" in "settings>about>software information>more" is only the base of the rom you are running.)
05. Unzip the downloaded backup.
06. Copy the unzipped backup folder to "TWRP/BACKUPS/<YourSerialnumber>/"on your SD card. Sometimes this is only possible if the SD card is directly connected to your PC and not put into your phone. I don't know why some M9s refuse the copy process.
Click to expand...
Click to collapse
So here was my problem, I have no external sd-card in my phone and trying to copy the 4.2 GB File via "Android Transfer" brought up the error, that files largen then 4GB are not supported to copy.
So I first made sure I prepared the following steps:
Flippy498 said:
07. I recommend wiping everything except "Micro SDcard", "USB-OTG" and "SD-Ext".
08. Check the "Mount system as read-only" box in the Mount menu.
Click to expand...
Click to collapse
Now make a folder structure like in Step 6 (if you are still in TWRP, no problem use the "mkdir <foldername>" command via the advanced tools tab. (read on, I tell you where it is)
So then, instead I copied the 2GB zip file in that folder and went to advanced tools in TWRP. There I chose the "execute command" tool, went inside the folder with the serialnumber and clicked select.
Now a command line appears and I entered "unzip" and the name of the zipfile ... well that took some time ... dont tend to klick kill ... you can make 3 coffees in that time (I advise you to drink only two :silly: otherwise you get overexcited)
After that another folder with the name of the zipfile shows up. Go back and click restore - then check that folder and three X Marks will appear, showing you that these mounts will be overwritten.
Now swipe to restore and go on:
Flippy498 said:
09. Restore the backup.
10. Boot to system (ignore the warning that no OS is installed). This process may actually take a while!
11. Congrats! Your system is now stock and able to receive and install official OTAs, again.
Click to expand...
Click to collapse
and thats's it. Worked like a charm. Thanks again @Flippy498 :highfive: !!
After spending hours upon hours reading through this forum I still haven't found a proper answer, so I am sorry if I start a thread that has been already answered somewhere else.
My phone apparently got a virus and it acts crazy: blocks on the start screen (the one that says HTC) and when I finally get it to start (through resetting to factory setting)s it starts to give me the message "People has stopped unexpectedly" over and over and over again.
It is locked
Has S-ON
CiD htc_Y13
So far I downloaded the fastboot
The RUU
The recovery image from here http://forum.xda-developers.com/htc-one-m8/general/guide-restore-european-htc-one-m8-to-t3072235
But I run into problems when I try to extract the rom.exe
And reading through the comments some people say that that method might end up bricking the device.
Can anyone give me a straight forward solution?
All I need to do is Return my phone to stock so that I can finally use it again
Thanks!
Flashing an RUU will format and restore all your phone's partitions to stock HTC condition - you'll lose all data, except your sd card.
1. Download the latest RUU file (in zip format) (6.12.401.4) from the link below:
https://www.androidfilehost.com/?fid=24369303960687057
2. Rename the file to:
0P6BIMG.zip
Note: The first character is zero, and make sure you don't rename it to 0P6BIMG.zip.zip
3. Put the file in the root directory of your sd card.
4. Boot into bootloader and follow the instructions to flash the ruu.
5. Enjoy
Thanks for the reply
shirreer said:
Flashing an RUU will format and restore all your phone's partitions to stock HTC condition - you'll lose all data, except your sd card.
1. Download the latest RUU file (in zip format) (6.12.401.4) from the link below:
2. Rename the file to:
0P6BIMG.zip
Note: The first character is zero, and make sure you don't rename it to 0P6BIMG.zip.zip
3. Put the file in the root directory of your sd card.
4. Boot into bootloader and follow the instructions to flash the ruu.
5. Enjoy
Click to expand...
Click to collapse
I get the following message when I tried this option :
Cancel Update!
Device halted due to large image update fail
Press Power to reboot
I also get wrong zipped image circa half way in the procedure
I guess you either have a corrupt download, file-system errors on your sd card or PC's hard disk, or you tried to flash the zip file from ADB.
Also, you can simply hard-reset your phone and start fresh. Then you can OTA up to 6.12.
Otherwise, if you want to flash the RUU, do this first:
1. Check your SD for errors and fix them.
2. Check your PC's hard disk for errors and fix them.
3. Download the file again and start over.
4. Follow my instructions to the letter.
5. Give us feedback
Thanks a million!!!!
shirreer said:
I guess you either have a corrupt download, file-system errors on your sd card or PC's hard disk, or you tried to flash the zip file from ADB.
Also, you can simply hard-reset your phone and start fresh. Then you can OTA up to 6.12.
Otherwise, if you want to flash the RUU, do this first:
1. Check your SD for errors and fix them.
2. Check your PC's hard disk for errors and fix them.
3. Download the file again and start over.
4. Follow my instructions to the letter.
5. Give us feedback
Click to expand...
Click to collapse
Thanks a million
All I had to do is FORMAT the SD and go through the process again. It worked like a charm- Thanks again Shirreer
You're very welcome. Glad I could help.
Cheers
SuperSU told me that my SU binary was out of date and so i tried to update it through TWRP like it recommended. Well that ended up failing in the middle of it (I don't have logs) and it seems like the backup I had is missing from my SD card. Whenever I load android it goes black screen, it'll show the back button and the status bar but none of that will be interactive. I can power it down but if i wait too long the buttons won't work. Anyways I was hoping someone had a backup for the a5_chl phone.
end360 said:
SuperSU told me that my SU binary was out of date and so i tried to update it through TWRP like it recommended. Well that ended up failing in the middle of it (I don't have logs) and it seems like the backup I had is missing from my SD card. Whenever I load android it goes black screen, it'll show the back button and the status bar but none of that will be interactive. I can power it down but if i wait too long the buttons won't work. Anyways I was hoping someone had a backup for the a5_chl phone.
Click to expand...
Click to collapse
Sorry your having problems. Why not just get the stock RUU file directly from HTC/downloads and flash back your stock recovery by running the RUU on your computer and before hitting start type %temp% into the search box and go to the RUU's running files and in one of the numbered files will be the rom.zip and within that file will be the recovery image. Copy that to your ADB/fastboot folder then flash it over your TWRP recovery but first I'd wipe the system and data in advanced wipe in TWRP to get your system partition clean( THIS WIPES THE WHOLE PHONE SO BE AWARE OF THAT AND MOVE FILES TO YOUR COMPUTER ACCORDINGLY OR BACK UP USING GOOGLE STOCK BACKUP IN SETTINGS IF YOU'RE NOT ALREADY FOR CONTACTS AND NUMBERS ETC). Then relock your bootloader with the stock recovery flashed back and run the RUU or put it in your ext SD and rename the file to OP9CIMG and reboot into your bootloader and it should automatically pick up the file and start flashing it. I have this same model phone and I keep my stock RUU that I got from HTC on my computer for just such a problem. I got a stock recovery zip from somewhere else but i can't remember where but it's also within the RUU itself. Try to find the link for you in a bit.
EDIT: here's a link to someone I know who had a whole tutorial for the a5_ul version of our phone on how to flash back a stock RUU from your computer or from within your ext SD card. Obviously the links with the files aren't valid for our phone but the steps are . Also has instructions for restoring using a TWRP backup but I wouldn't use someone else's TWRP backup if my hair was on fire. Especially since we have access to the pure stock RUU with our version why not take advantage of it. That's all I'm saying.
http://forum.xda-developers.com/desire-816/help/guide-how-to-flash-stock-recovery-ruu-t3308502
And here's the HTC RUU downloads link below
http://www.htc.com/us/support/rom-downloads.html
And lastly a link to a tutorial on extracting the stock recovery from the RUU .
http://androidforums.com/threads/guide-re-flash-stock-rom-ruu-after-bricking-a-rooted-device.565203/
Well not lastly I guess because here is a link to the stock recovery provided by FoxyDrew. Don't use the RUU link it's to kitkat but the recovery link below it is the same for lollipop as it's for the a5_chl
http://forum.xda-developers.com/desire-816/general/ruu-t2952058/post57019175#post57019175
thoctor said:
Sorry your having problems. Why not just get the stock RUU file directly from HTC/downloads and flash back your stock recovery by running the RUU on your computer and before hitting start type %temp% into the search box and go to the RUU's running files and in one of the numbered files will be the rom.zip and within that file will be the recovery image. Copy that to your ADB/fastboot folder then flash it over your TWRP recovery but first I'd wipe the system and data in advanced wipe in TWRP to get your system partition clean( THIS WIPES THE WHOLE PHONE SO BE AWARE OF THAT AND MOVE FILES TO YOUR COMPUTER ACCORDINGLY OR BACK UP USING GOOGLE STOCK BACKUP IN SETTINGS IF YOU'RE NOT ALREADY FOR CONTACTS AND NUMBERS ETC). Then relock your bootloader with the stock recovery flashed back and run the RUU or put it in your ext SD and rename the file to OP9CIMG and reboot into your bootloader and it should automatically pick up the file and start flashing it. I have this same model phone and I keep my stock RUU that I got from HTC on my computer for just such a problem. I got a stock recovery zip from somewhere else but i can't remember where but it's also within the RUU itself. Try to find the link for you in a bit.
EDIT: here's a link to someone I know who had a whole tutorial for the a5_ul version of our phone on how to flash back a stock RUU from your computer or from within your ext SD card. Obviously the links with the files aren't valid for our phone but the steps are . Also has instructions for restoring using a TWRP backup but I wouldn't use someone else's TWRP backup if my hair was on fire. Especially since we have access to the pure stock RUU with our version why not take advantage of it. That's all I'm saying.
http://forum.xda-developers.com/desire-816/help/guide-how-to-flash-stock-recovery-ruu-t3308502
And here's the HTC RUU downloads link below
http://www.htc.com/us/support/rom-downloads.html
And lastly a link to a tutorial on extracting the stock recovery from the RUU .
http://androidforums.com/threads/guide-re-flash-stock-rom-ruu-after-bricking-a-rooted-device.565203/
Well not lastly I guess because here is a link to the stock recovery provided by FoxyDrew. Don't use the RUU link it's to kitkat but the recovery link below it is the same for lollipop as it's for the a5_chl
http://forum.xda-developers.com/desire-816/general/ruu-t2952058/post57019175#post57019175
Click to expand...
Click to collapse
My thread has the KitKat and Lollipop RUU, which is the latest one from HTC, and should work fine for his issue
FoxyDrew said:
My thread has the KitKat and Lollipop RUU, which is the latest one from HTC, and should work fine for his issue
Click to expand...
Click to collapse
Cool. You're the man.
I want to flash a different rom on my htc m9 than already was installed. I changed the CID to HTC__001 (I am S-OFF) and downloaded RUU 3.35.401.12.zip. When I'm in download mode I type: fastboot flash zip Firmware3.35.401.12.zip in adb. I get an error: cannot load 'Firmware 3.35.401.12.zip'. Why is this? The zip is in the same directory with fastboot.exe and htc_fastboot.exe.
The situation has changed a bit. I decided to try to install from sd card and it worked perfectly. Now I was on 3.35.401.12. But I wanted to install android N. I read that you can't install from firmware 3 to 4 unless you want to install a full wipe zip. So I did. I installed M9_4.14.401.7_FullStock_wipe.zip from Sneakyghost. Now it is stuck on the white HTC screen. I can boot into bootloader, recovery etc. I even flashed twrp, installed SuperSU and wiped dalvid/cache but still stuck. I did see that I'm on 4.14.401.7. What can I do now?
I just read "Be sure to put a ROM onto your EXTERNAL SD before proceeding with a Full WIPE ZIP! Else you can also ADB push a ROM in recovery mode after fastboot reflashing a recovery. The newer TWRP variants also support a normal MTP connection and might support USB mass storage at a later stage. Phone will NOT boot without ROM reflash after using this!" in the thread from Sneakyghost. So, I understand why I'm not booting, but can I now flash stock 4.14.401.7? And how do I do that? Also with SD-method?
I believe you flash the ota once you've flashed the zip and that completes the process.
There is a dedicated nougat thread in the general section. The reply to one of my noobish questions answers this exact situation.
Beamed in by telepathy.
Hi,
Everytime I try to OTA update de weekly rom, I get the message that says that my memory is encrypted and directs me to recovery.
In recovery when I select the ROM, it returns ERROR 7, I know that it is related with 2 command lines in the updater script.
My question is, how can I fix this problems so I can normally OTA update?
Xiaomi MI 9 SE
TWRP 3.5.0_9-0
xiaomi.eu weekly (it happens in all versions)
Thanks
Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info
flairepathos.info said:
Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info
Click to expand...
Click to collapse
You're right, I think this is a generic problem, that's why I've not specified the model.
vmlc said:
You're right, I think this is a generic problem, that's why I've not specified the model.
Click to expand...
Click to collapse
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery
flairepathos.info said:
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery
Click to expand...
Click to collapse
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards
vmlc said:
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards
Click to expand...
Click to collapse
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible
flairepathos.info said:
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible
Click to expand...
Click to collapse
So this is not fixable, keep TWRP and have OTA update?
vmlc said:
So this is not fixable, keep TWRP and have OTA update?
Click to expand...
Click to collapse
Yes but now that you mention if you could edit the twrp recovery_id to match that of the stock recovery ,it might work because the system/ ota file calls for a specific recovery_id