So I upgraded to android 10 open beta and now viper4android keeps asking to install the drivers and twrp isnt asking for my password so I cant access storage or anything from twrp
I am on twrp 3.3.1-4
Did you try removing the password from your current rom.
Robert235 said:
Did you try removing the password from your current rom.
Click to expand...
Click to collapse
Just tried and still nothing it comes up with swipe to allow modifications and I do that but internal storage is still 0
That's Strange, I remember both on the OnePlus 6 and OnePlus 7 Pro when switching from stock ROM to AOSP having a password used to cause issues with twrp. I wonder if the new version of twrp installer will work.
I wanna try a factory reset but it wont let me
D.Va said:
I am on twrp 3.3.1-4
Click to expand...
Click to collapse
Your on the wrong twrp version.
Flash the latest unofficial twrp.
twinnfamous said:
Your on the wrong twrp version.
Flash the latest unofficial twrp.
Click to expand...
Click to collapse
I would but I can't and I've never had issues with the official twrp builds I personally think it's just the beta causing some weird encryption bug
D.Va said:
I would but I can't and I've never had issues with the official twrp builds I personally think it's just the beta causing some weird encryption bug
Click to expand...
Click to collapse
Why can't you?
The unofficial is maintained by the same person as official.
Also it's not a bug. It's the change in encryption /decryption. So if you won't use unofficial then you can wait patiently for official to update there source and build.
twinnfamous said:
Why can't you?
The unofficial is maintained by the same person as official.
Also it's not a bug. It's the change in encryption /decryption. So if you won't use unofficial then you can wait patiently for official to update there source and build.
Click to expand...
Click to collapse
I can't cause my twrp is showing Internal Storage as 0 and won't mount stuff and I can't wipe
The unofficial twrp comes with a .img file and zip. Use a PC to boot into the .img with fastboot then use that booted image which should allow decryption and flash the zip.
D.Va said:
I can't cause my twrp is showing Internal Storage as 0 and won't mount stuff and I can't wipe
Click to expand...
Click to collapse
Do you have magisk installed?
Use the twrp installer zip.
twinnfamous said:
Your on the wrong twrp version.
Flash the latest unofficial twrp.
Click to expand...
Click to collapse
Solved. NVM, it just popped out as soon as I asked the stupid question.
Can you please tell me where can I find the unofficial twrp? It's like a freaking unicorn, evading my desperate searches.
stefanaroman88 said:
Solved. NVM, it just popped out as soon as I asked the stupid question.
Can you please tell me where can I find the unofficial twrp? It's like a freaking unicorn, evading my desperate searches.
Click to expand...
Click to collapse
Look here. https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Related
This is an unofficial port of TWRP Recovery for the Oppo F1F on Project Spectrum Bootloader. Much Thanks and credit goes to the TWRP team, Lineage team, and brinleyaus for making this possible. This will allow flashing of modification zips (eg. supersu, magisk, xposed, etc) over the top of Project Spectrum or flashing spectrum based ROMS.
Instructions:
Already running Project Spectrum
- If you haven't already unlocked you bootloader you will need to go into SETTINGS > ABOUT PHONE and tap BUILD NUMBER 7 times to unlock DEVELOPER OPTIONS, Then go into SETTINGS > DEVELOPER OPTIONS and enable them, also enable ADB DEBUGGING and OEM UNLOCK. Now reboot into fastboot (adb reboot bootloader) and run fastboot oem unlock.
- Install this image file through fastboot (If you are unsure of this step follow one of the many tutorials about installing TWRP through fastboot)
On ColourOs with TWRP
- Do a full wipe first or the install will fail. (In TWRP hit WIPE then swipe to factory reset.) Do a backup first as you will lose data.
- Flash this zip file through twrp and then hit "wipe dalvic and cache", then hit HOME then REBOOT then RECOVERY. (rebooting to the new recovery will ensure the recovery sticks) then Flash any Spectrum based rom or restore any Spectrum based backup. NOTE the ColorOs system and boot.img will still be there but wont boot so you MUST flash or restore a Spectrum based rom before you reboot to system.
Reserved.
MiniBlu said:
Reserved.
Click to expand...
Click to collapse
Battery can't charge full!! Help ?
Added file and instructions to OP to flash Spectum bootloader,firmware and twrp From ColorOs TWRP.
Thank.link from androidfilehost is slowly. I using wifi
Sent from my F1w using XDA-Developers Legacy app
MiniBlu said:
Added file and instructions to OP to flash Spectum bootloader,firmware and twrp From ColorOs TWRP.
Click to expand...
Click to collapse
The TWRP is not the 3.1.1
It is the 3.0.1
khannz7 said:
The TWRP is not the 3.1.1
It is the 3.0.1
Click to expand...
Click to collapse
Which file are you talking about, I just checked the links and the flashable zip was actually pointing to the full ROM which defiantly has the 3.1.1-0 version. (I just fixed the link to point at the bootloader, firmware and twrp zip.) Are you rebooting to recovery after flashing to make it stick?
MiniBlu said:
Which file are you talking about, I just checked the links and the flashable zip was actually pointing to the full ROM which defiantly has the 3.1.1-0 version. (I just fixed the link to point at the bootloader, firmware and twrp zip.) Are you rebooting to recovery after flashing to make it stick?
Click to expand...
Click to collapse
The PS 1
Yeah doing it right....But it is the same old twrp 3.0.1 mentioned somewhere in the G+ forums....
Never mind ....did you get the port to work
khannz7 said:
Yeah doing it right....But it is the same old twrp 3.0.1 mentioned somewhere in the G+ forums....
Never mind ....did you get the port to work
Click to expand...
Click to collapse
Which ps1 g or zip?
I have just checked. None of the files I have posted are the old version. They are all the newest 3.1.1-0 version.
No not yet.
MiniBlu said:
I have just checked. None of the files I have posted are the old version. They are all the newest 3.1.1-0 version.
No not yet.
Click to expand...
Click to collapse
I have installed the full ps rom with twrp but what I got is not 3.1.1 it is the 3.0.1
+
Maybe I could help you somewhere with the port
I have to remove the sd card and then re-insert it then it received. who can solve it? The battery will charge too long to fill up
khannz7 said:
I have installed the full ps rom with twrp but what I got is not 3.1.1 it is the 3.0.1
Click to expand...
Click to collapse
OK, I'll download it and check, maybe I uploaded from the old folder. Hope not 6.5 hours to upload it.
MiniBlu said:
OK, I'll download it and check, maybe I uploaded from the old folder. Hope not 6.5 hours to upload it.
Click to expand...
Click to collapse
I would love to help you with the port and maybe I could get something new to learn:fingers-crossed:
Phucan2017 said:
I have to remove the sd card and then re-insert it then it received. who can solve it? The battery will charge too long to fill up
Click to expand...
Click to collapse
No one. If you don't like it stick with ColorOs or Lineage.
khannz7 said:
I would love to help you with the port and maybe I could get something new to learn:fingers-crossed:
Click to expand...
Click to collapse
Not just yet, just got to work out the ramdisk changes needed to get ported roms to boot properly with spectrum kernel, then I'll share the info with you and then let the porting begin.
MiniBlu said:
No one. If you don't like it stick with ColorOs or Lineage.
Not just yet, just got to work out the ramdisk changes needed to get ported roms to boot properly with spectrum kernel, then I'll share the info with you and then let the porting begin.
Click to expand...
Click to collapse
Cool
I did that. But for oppo f1 this rom is not finished yet but there are still many bugs. I return coloros
Just used the spectrum zip and worked flawlessly.(from other thread oops) Thanks alot.
How to go back to coloros ? Do i need to flash stock recovery ?
Sent from my F1f using XDA Labs
the_reds2000 said:
How to go back to coloros ? Do i need to flash stock recovery ?
Sent from my F1f using XDA Labs
Click to expand...
Click to collapse
No, Read the OP of this thread. There is a zip (and instructions) to return to ColorOs Bootloader,firmware and TWRP. From there you can flash any TWRP flashable ColourOs based Rom (ColorOs or LineageOS) or restore backups from them.
Which root method will be used for this?
Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
System
1.Optimized network connection
2.Optimized stability for wi-fi connection
3.Fixed screen flickering issue in day light
4.General bug fixes and improvements
5.confirm pin without tapping
Camera
Improved HDR mode
Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.
I also get that update.
If i download it.. can i just not update right away?
because i want to manually update from twrp and re root with magisk.
Thanks in advance
Sent from my ONEPLUS A6000 using Tapatalk
ossy1337 said:
Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.
Click to expand...
Click to collapse
I have no photos with older firmware.i think now the photos taken are more brighter
Root users beware: issues with newer TWRP version!
This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
So since twrp latest works fine on my device with encryption included, I can just start the update?
Sent from my ONEPLUS A6003 using Tapatalk
Neurom67 said:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
Click to expand...
Click to collapse
Can you link 3.2.1-1 version? https://eu.dl.twrp.me/enchilada/ There is only 3.2.1-0 or 3.2.2-0
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
No problem with blue twrp.
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Fails for everyone atm. Was working fine for me until two days ago before Google updated the api
Sent from my ONEPLUS A6003 using Tapatalk
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Here is why; https://mobile.twitter.com/topjohnwu/status/1029239685338419200
3.2.1.0 installed 5.1.11 fine on my OP6.
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
SpectraFun said:
No problem with blue twrp.
Click to expand...
Click to collapse
Batfink33 said:
3.2.1.0 installed 5.1.11 fine on my OP6.
Click to expand...
Click to collapse
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?
Have TWRP 3.2.3 and installed 5.1.11 just fine.
SMS786 said:
Have TWRP 3.2.3 and installed 5.1.11 just fine.
Click to expand...
Click to collapse
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk
Vuska said:
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
Didn't disable my pattern lock..worked just fine.
I downloaded the zip online and installed through TWRP. Just make sure to reinstall your TWRP installer after installing the full rom OTA (wipe cache/dalvik first), then reboot back into TWRP and install Magisk..then boot into system.
The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade
Chinaroad said:
The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade
Click to expand...
Click to collapse
People seem to be saying this for every release
giebeka said:
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?
Click to expand...
Click to collapse
Used Oxygen updater to download zip. Rebooted to bootloader. Went Install and selected ZIP. then added TWRP zip as well. Installed both. Rebooted to bootloader again. Flashed elementalx kernel(you can skip it) and magisk. All works fine.
kakkooran said:
Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
...
5.confirm pin without tapping
Click to expand...
Click to collapse
I can't find where to enable this. Anyone found it?
Has anyone been successful in running the new Open Beta build unencrypted? It's driving me absolutely nuts! It's a matter of time until whatever OnePlus changed makes it into the stable builds, I very much prefer to keep my phone unencrypted.
H4X0R46 said:
Has anyone been successful in running the new Open Beta build unencrypted? It's driving me absolutely nuts! It's a matter of time until whatever OnePlus changed makes it into the stable builds, I very much prefer to keep my phone unencrypted.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-decrypt-oneplus-7-pro-t3951131
aaryan45 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-decrypt-oneplus-7-pro-t3951131
Click to expand...
Click to collapse
This zip no longer works. I've always used it, but OnePlus changed something in the beta builds where this zip no longer works. I've spoken with the dev and he's stumped too.
H4X0R46 said:
This zip no longer works. I've always used it, but OnePlus changed something in the beta builds where this zip no longer works. I've spoken with the dev and he's stumped too.
Click to expand...
Click to collapse
u tried the latest version of the zip right?
aaryan45 said:
u tried the latest version of the zip right?
Click to expand...
Click to collapse
Yeah, on the open beta builds, it leads to an endless boot animation, never boots.
yes, same here.. hate to run encrypted.. OB 16 was the last that could be decrypted with this zip
raikkoni27 said:
yes, same here.. hate to run encrypted.. OB 16 was the last that could be decrypted with this zip
Click to expand...
Click to collapse
Yeah I miss it too! Very much so. I like the freedom to go between customs roms and never have to format my userdata! Hopefully soon someone will come up with a solution..... @topjohnwu Comes to mind. Any idea or expertise on the newer OnePlus devices not being unencryptable?
H4X0R46 said:
Yeah I miss it too! Very much so. I like the freedom to go between customs roms and never have to format my userdata! Hopefully soon someone will come up with a solution..... @topjohnwu Comes to mind. Any idea or expertise on the newer OnePlus devices not being unencryptable?
Click to expand...
Click to collapse
What are the steps to switch between custom roms by staying unencrypted and not formatting our internal storage .
insaneparnoid said:
What are the steps to switch between custom roms by staying unencrypted and not formatting our internal storage .
Click to expand...
Click to collapse
You download zackptg5's unencrypt zip and flash that before booting a new rom. He has an XDA thread here if you Google "no forceencrypt" and his own website, zackptg5.com. what you're looking for is his dm verity zip. Flash before booting a new rom if you're already unencrypted and you'll be fine. IF you're encrypted (just never messed with it at all), you will need to flash his zip and FORMAT (not wipe) your data. Clean slate. Lose everything.
EDIT: This currently doesn't work on beta builds of OOS.
H4X0R46 said:
You download zackptg5's unencrypt zip and flash that before booting a new rom. He has an XDA thread here if you Google "no forceencrypt" and his own website, zackptg5.com. what you're looking for is his dm verity zip. Flash before booting a new rom if you're already unencrypted and you'll be fine. IF you're encrypted (just never messed with it at all), you will need to flash his zip and FORMAT (not wipe) your data. Clean slate. Lose everything.
EDIT: This currently doesn't work on beta builds of OOS.
Click to expand...
Click to collapse
Keep Decrypt between Roms:
-Wipe Data only in twrp!!! (NEVER WIPE SYSTEM OR - VENDOR ON OP7P)
-Flash Rom
-Flash TWRP
-Reboot Recovery
-Flash any other zips you want like Gapps-Kernels- ex.....
-Flash No Verity Mod
-Flash Magisk
-Reboot System
is this right?
aaryan45 said:
Keep Decrypt between Roms:
-Wipe Data only in twrp!!! (NEVER WIPE SYSTEM OR - VENDOR ON OP7P)
-Flash Rom
-Flash TWRP
-Reboot Recovery
-Flash any other zips you want like Gapps-Kernels- ex.....
-Flash No Verity Mod
-Flash Magisk
-Reboot System
is this right?
Click to expand...
Click to collapse
Mostly, I'd flash Magisk before the verity zip. The rest is correct!
@H4X0R46 till now did you get any success in decrypt latest Beta 19?
Zhuang zhuang said:
@H4X0R46 till now did you get any success in decrypt latest Beta 19?
Click to expand...
Click to collapse
No unfortunately. I had a talk with zackptg5 and he's stumped too. I tried to get him a logcat on boot so he could see what's wrong, but my phone bootloops on beta's with his zip and will not let me take a logcat. He's as stumped as I am [emoji21]
H4X0R46 said:
No unfortunately. I had a talk with zackptg5 and he's stumped too. I tried to get him a logcat on boot so he could see what's wrong, but my phone bootloops on beta's with his zip and will not let me take a logcat. He's as stumped as I am [emoji21]
Click to expand...
Click to collapse
Oh, quite sad I hope he can find out the solution soon
H4X0R46 said:
Has anyone been successful in running the new Open Beta build unencrypted? It's driving me absolutely nuts! It's a matter of time until whatever OnePlus changed makes it into the stable builds, I very much prefer to keep my phone unencrypted.
Click to expand...
Click to collapse
Damn
I have been decrypted on the stable builds since a long time now. Was planning to switch to beta once OOS11 drops. But now it seems like I shouldn't.
I'm using ArrowOS and after every OTA update, my phone gets unrooted (new boot.img). How do I avoid this?
There seems to be no method officially to address this issue. Follow this link and do as instructed.
You should be posting this in ArrowOS thread.
Anyway, are you using OTA decryption supported recovery?
Magisk require decryption to reinstall itself, if the recovery you are using doesn't prompt you password during OTA, then it isn't decrypting thus magisk will not reinstall itself.
Lu5ck said:
You should be posting this in ArrowOS thread.
Anyway, are you using OTA decryption supported recovery?
Magisk require decryption to reinstall itself, if the recovery you are using doesn't prompt you password during OTA, then it isn't decrypting thus magisk will not reinstall itself.
Click to expand...
Click to collapse
I'm using TWRP, not the one that ArrowOS has.
dantevn said:
I'm using TWRP, not the one that ArrowOS has.
Click to expand...
Click to collapse
Can you remind me, does twrp prompt you for password during ota? I don't really remember.
personally, I suggest you to use the official orangefox recovery, I'm using that and magisk reinstall itself though I'm using lineage
Lastly, I don't think arrowos has any recovery of their own
Lu5ck said:
Can you remind me, does twrp prompt you for password during ota? I don't really remember.
personally, I suggest you to use the official orangefox recovery, I'm using that and magisk reinstall itself though I'm using lineage
Lastly, I don't think arrowos has any recovery of their own
Click to expand...
Click to collapse
It doesn't. I'll try it, thanks.
I haven't actually tried it yet, but when flashing the No Gravity kernel it says something about Magisk was detected, and it says it's doing something so it won't need to be refreshed. Might be worth a try? https://forum.xda-developers.com/t/...9-02-protonclang.4328217/page-2#post-85600529
Hey Everyone,
I'm looking to try LOS 19.1 for the first time on my new OP8T.
I always see TWRP as a suggestion for the best custom recovery, but on the download page "twrp-installer-3.7.0_11-0-kebab.zip" is the file name. I'm confused, as the 11-0 means it's for Android 11, but I saw that TWRP 3.7.0 is supposed to support Android 12.
Can I use TWRP for installing LOS 19.1 on Android 12 or should I use the LOS-recovery?
And if I do, can I still use Magisk (on their page they say to use TWRP)?
Sorry for this newbie question. Thanks in advance!!
All the best
The official TWRP doesn't support A12.
Use the unofficial one from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
henschn3435 said:
Hey Everyone,
I'm looking to try LOS 19.1 for the first time on my new OP8T.
I always see TWRP as a suggestion for the best custom recovery, but on the download page "twrp-installer-3.7.0_11-0-kebab.zip" is the file name. I'm confused, as the 11-0 means it's for Android 11, but I saw that TWRP 3.7.0 is supposed to support Android 12.
Can I use TWRP for installing LOS 19.1 on Android 12 or should I use the LOS-recovery?
And if I do, can I still use Magisk (on their page they say to use TWRP)?
Sorry for this newbie question. Thanks in advance!!
All the best
Click to expand...
Click to collapse
3.7.0 is recovery release version and 11-0 means it's for Android 11.
BillGoss said:
The official TWRP doesn't support A12.
Use the unofficial one from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
Click to expand...
Click to collapse
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?
Dior DNA said:
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?
Click to expand...
Click to collapse
It works on both the 8T and the 9 9R. If you want to be sure try to boot into it before flashing.
Dior DNA said:
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?
Click to expand...
Click to collapse
TheNewHEROBRINE said:
It works on both the 8T and the 9. If you want to be sure try to boot into it before flashing.
Click to expand...
Click to collapse
If you look at the title of that thread you'll notice that it says "TeamWin Recovery Project (8T / 9R)".
So, yes, it's for both the 8T and 9R (lemonades) but not the 9 (lemonade).
BillGoss said:
If you look at the title of that thread you'll notice that it says "TeamWin Recovery Project (8T / 9R)".
So, yes, it's for both the 8T and 9R (lemonades) but not the 9 (lemonade).
Click to expand...
Click to collapse
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255
Dior DNA said:
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
Can you share the full log?
TheNewHEROBRINE said:
Can you share the full log?
Click to expand...
Click to collapse
sure, give me another day ...I just deleted the Orangefox and TWRP directories
Dior DNA said:
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.
BillGoss said:
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.
Click to expand...
Click to collapse
Thanks all! One should perhaps forbid files under /data/fonts/files/ ... After deleting those, I could finish both (unofficial) Orangefox and (unofficial) TWRP backup just fine. Agreed, this does not 100% prove ERROR root cause but sure does consistently correlate. So now maybe one should harden custom recovery images to avoid the trap, especially since the trap seems to be a known one by some people (like @BillGoss).
BillGoss said:
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.
Click to expand...
Click to collapse
BTW, do you know the reason why files inside fonts/files folder prevent backup process from going?
Rootk1t said:
BTW, do you know the reason why files inside fonts/files folder prevent backup process from going?
Click to expand...
Click to collapse
No, I never understood what the problem was with those files.
BillGoss said:
No, I never understood what the problem was with those files.
Click to expand...
Click to collapse
When installing ota zips from TWRP, оne should restore stock boot and recovery because checks are inside ota zips?
Rootk1t said:
When installing ota zips from TWRP, оne should restore stock boot and recovery because checks are inside ota zips?
Click to expand...
Click to collapse
Correct, but only in incremental updates.
But I don't think the current TWRP can process OOS incremental updates - the last time I tried I got an error.
BillGoss said:
Correct, but only in incremental updates.
But I don't think the current TWRP can process OOS incremental updates - the last time I tried I got an error.
Click to expand...
Click to collapse
BillGoss said:
Flashing OTA zips - both full and incremental. Note: incremental OTAs need stock boot and recovery installed so make sure you flash these before starting the install, otherwise it will fail.
Click to expand...
Click to collapse
Has something changed from your post?
Rootk1t said:
Has something changed from your post?
Click to expand...
Click to collapse
Lol! I think I'm going senile!
Given that I tend to test before making statements like the one you quoted, I'd say that that is correct for the 1-4 version of TWRP.
But it may not be true for 1-5 as I've found some issues with it (eg, fastbootd doesn't work) and I've not fully tested flashing otas with 1-5.
BillGoss said:
Lol! I think I'm going senile!
Given that I tend to test before making statements like the one you quoted, I'd say that that is correct for the 1-4 version of TWRP.
But it may not be true for 1-5 as I've found some issues with it (eg, fastbootd doesn't work) and I've not fully tested flashing otas with 1-5.
Click to expand...
Click to collapse
Thanks for letting us know
Rootk1t said:
Thanks for letting us know
Click to expand...
Click to collapse
I went hunting and I found the conversation where I flagged the problem with flashing OTAs on the latest TWRP (on the TWRP development site):
I wanted to test using TWRP to install an OTA zip on OOS 12. The first time I tried I got an error because it was expecting the current version to match those of C.33 but they didn't - even though I was on C.33. So I used `resetprop` to set the proper values and then it sort of worked, but still gave errors.
I was using the latest version (1.5 or 220827) of TWRP.
Click to expand...
Click to collapse
And now I'm wondering how correct my statement about flashing OTAs working on the previous version. I'll have to do some more digging to see if I can find solid proof of OTA working on TWRP 12 v1.4.
Update: I found where I tested flashing OTAs on TWRP 12. That was back on 220805. That was before 1.4 came out (220818). But I didn't expect that this function would get broken, so I never actually tested on 1.4.
BillGoss said:
I went hunting and I found the conversation where I flagged the problem with flashing OTAs on the latest TWRP (on the TWRP development site):
And now I'm wondering how correct my statement about flashing OTAs working on the previous version. I'll have to do some more digging to see if I can find solid proof of OTA working on TWRP 12 v1.4.
Update: I found where I tested flashing OTAs on TWRP 12. That was back on 220805. That was before 1.4 came out (220818). But I didn't expect that this function would get broken, so I never actually tested on 1.4.
Click to expand...
Click to collapse
So as i understood correctly flashing OTAs in TWRP is broken on v1.4 and works on prior versions?