I'm running official LOS 17.1 with the latest firmware. Everything working fine, however whenever I restore the /data partition in both, TWRP and OrangeFox, I end up in a bootloop. This is very bad, I tried to create backups with decrypted data but still not working. I wonder if I'm the only one with this issue, or if it's already known, or if it's a bug, idk.
I never needed to restore partitions, tried after (unsuccessfuly) flashing the latest official MIUI ROM with TWRP. Idk if maybe that could be the cause.
Thanks in advanced.
David Masa said:
I'm running official LOS 17.1 with the latest firmware. Everything working fine, however whenever I restore the /data partition in both, TWRP and OrangeFox, I end up in a bootloop. This is very bad, I tried to create backups with decrypted data but still not working. I wonder if I'm the only one with this issue, or if it's already known, or if it's a bug, idk.
I never needed to restore partitions, tried after (unsuccessfuly) flashing the latest official MIUI ROM with TWRP. Idk if maybe that could be the cause.
Thanks in advanced.
Click to expand...
Click to collapse
when you flash a rom and want to restore it's data you have to recreate the same conditions
if the data is created when you rooed = flash magisk and restore data
if the data is created while you were decrypted = flash dfe + format then restore data
if still have boot loop then it may have a wrong value in setting data
after restore data , delete the folder /data/user_de/0/com.android.settings using the recovery file manager
loopypalm said:
when you flash a rom and want to restore it's data you have to recreate the same conditions
if the data is created when you rooed = flash magisk and restore data
if the data is created while you were decrypted = flash dfe + format then restore data
if still have boot loop then it may have a wrong value in setting data
after restore data , delete the folder /data/user_de/0/com.android.settings using the recovery file manager
Click to expand...
Click to collapse
Does restoring /system, /boot, dtbo and vendor partitions count as "recreate the same conditions"? magisk is stored in /boot afaik, so I assume yes. However, only /data is giving me a headache, restoring the rest of partitions doesn't cause any issues...
I'll try deleting the folder you say from the recovery.
David Masa said:
Does restoring /system, /boot, dtbo and vendor partitions count as "recreate the same conditions"?
Click to expand...
Click to collapse
only boot/dtbo but flashing magisk is enough ,so no need
magisk does not change system/vendor (except for the survival kit ...)
loopypalm said:
only boot/dtbo but flashing magisk is enough ,so no need
magisk does not change system/vendor (except for the survival kit ...)
Click to expand...
Click to collapse
I suppose that magisk isn't the problem then, because I tried to restore backups with the mentioned partitions and still getting bootloop. After restoring partitions one by one, I discovered /data was the problem.
David Masa said:
I suppose that magisk isn't the problem then, because I tried to restore backups with the mentioned partitions and still getting bootloop. After restoring partitions one by one, I discovered /data was the problem.
Click to expand...
Click to collapse
did you try deleteing the folder i said ?
if it still not work then the bkp maybe corrupted (happen to me 2 times with twrp and 1 with ofox ...)
i always backup the partions using “original” method not image backup，for the backup size of “original” method was smaller than the image backup。
but after recoverying these partions， it will cause “the system wasdestroyed”，so i have to using “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img”in fastboot mode
so i ask for help how to “patch” some zip in twrp to avoid the "destroyed" without using pc? @loopypalm @geoanto555
wsdyleon said:
i always backup the partions using “original” method not image backup，for the backup size of “original” method was smaller than the image backup。
but after recoverying these partions， it will cause “the system wasdestroyed”，so i have to using “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img”in fastboot mode
so i ask for help how to “patch” some zip in twrp to avoid the "destroyed" without using pc? @loopypalm @geoanto555
Click to expand...
Click to collapse
what do you mean by “original” method ???
also i don't understand your question
can you explain ?
loopypalm said:
what do you mean by “original” method ???
also i don't understand your question
can you explain ?
Click to expand...
Click to collapse
twrp:"" you will see an option on the backup page for System Image. A system image backup takes up more space than a regular system backup, but the system image backup is a bit-perfect backup that, when restored, will not break dm-verity (assuming that you don't break dm-verity before making the backup)."" original method was backuping the partion without using the option of "system image"
wsdyleon said:
twrp:"" you will see an option on the backup page for System Image. A system image backup takes up more space than a regular system backup, but the system image backup is a bit-perfect backup that, when restored, will not break dm-verity (assuming that you don't break dm-verity before making the backup)."" original method was backuping the partion without using the option of "system image"
Click to expand...
Click to collapse
i get it , but i don't think it's possible on RN8
are you sure that is available on ginkgo ?
can you send screenshot ?
loopypalm said:
i get it , but i don't think it's possible on RN8
are you sure that is available on ginkgo ?
can you send screenshot ?
Click to expand...
Click to collapse
most version of twrp only have the option “image backup”，
i can restore the backups，but after being recovery i have to using “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img”to avoid “system has been destroyed”
so i just want a zip for patching that in twrp on my cellphone ,without computer.
=====================================================================
so sorry，i succeed in restoring the backups with twrp from @geoanto555 weirdly。however，before this i came across lots of the error of “system has been destroyed”
wsdyleon said:
most version of twrp only have the option “image backup”，
i can restore the backups，but after being recovery i have to using “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img”to avoid “system has been destroyed”
so i just want a zip for patching that in twrp on my cellphone ,without computer.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
btw, @loopypalm, how do I flash DFE for the RN8? I think I've never do it
David Masa said:
btw, @loopypalm, how do I flash DFE for the RN8? I think I've never do it
Click to expand...
Click to collapse
If you want to read about it : here
download : here
you flash it like any zip in recovery
if it's the 1st time you have to format data (this will erase also internal storage)
So I could partially solve this issue, because the solution led me to another problem (read below). DFE was my savior. Here's what I learned from this adventure. Please correct me if there's something wrong on what I say. FYI, I used OF in all these cases.
When you're encrypted, format data and flash DFE (afaik the order does not matter, format data and then flash DFE should have the same effect as doing it vice versa).
When decrypted but will change your ROM, wipe data, flash the custom ROM and right after flash DFE. Otherwise data will get encrypted (afaik that depends on the ROM, not all of them may have forceencryption enabled, but if you're not sure you should do this step), at least in official LOS and crDroid.
Regarding backups: if the data partition was backed up encrypted, there's nothing to do. At least in my case it seems to be the cause of bootloop.
When flashing a custom ROM and then restoring its respective data partition (e.g. let's say I use LOS, I only back up data and then move another custom ROM, then I flash the LOS zip again and restore data), the screen lock is likely to fail, if there is one. In my case, I had a pattern which was not recognized, so I had to remove password using the OF addon. This doesn't happen when restoring system, which may be a common partition to backup, but I thought that this little comment was worth
However, now I'm facing another issue, at least with LOS: if I upgrade the ROM (manually or through the updater) I get bootloop again
The reason is unknown to me. If I upgrade, wipe data, flash DFE, magisk and then restore data, it doesn't work neither. I tried without flashing magisk or without wiping data too, but the result is the same. However, after some testing, I discovered that if I upgrade the ROM, flash DFE and restore system it works. The bad thing is that the end result is an upgrade for the ROM's partitions (boot, vbmeta, vendor, dtbo, system) except for system. So my conclusion is that there's a problem with the system partition which doesn't want to work with unencrypted data even if I flash DFE, because before I used DFE I could upgrade without issues.
This is very weird. But at least I can normally restore backups with data partition without bootloop. Which is your setup for the RN8 @loopypalm ? just for curiosity.
TL;DR: with DFE I can restore data backups without issues, however I cannot upgrade Lineage because the system partition causes a bootloop, even if flashing DFE after install.
OK, so finally I figured it out and Magisk was the problem when upgrading ROM with decrypted data. To upgrade LOS I did the following:
Boot OF
Remove Magisk
Wipe cache and dalvik
Flash the LOS zip
Flash DFE
Flash Magisk
Then I had to restore the modules. I assume this might be a bug or an issue with the magisk survival script?
I'll mark this thread as solved.
David Masa said:
... Which is your setup for the RN8 @loopypalm ? just for curiosity.
Click to expand...
Click to collapse
I use RRos (Resurrection Remix) it's also based on LOS but better (IMO)
i use now 8.7.2 A10 with latest A10 stable FW and no gapps
David Masa said:
OK, so finally I figured it out and Magisk was the problem when upgrading ROM with decrypted data.
Click to expand...
Click to collapse
If anybody is interested in following the issue: https://github.com/topjohnwu/Magisk/issues/4614
Related
This tool was created for the nexus 9 by @gladiac to get rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
This is a better implementation then having to manually patch every boot.img especially once custom aosp roms come along because cyanogenmod will have force encrypt enabled just like the nexus's. It also makes it easy to patch ota boot.img's by yourself.
Background
The Android CDD (Compatibility Definition Document) suggests that all devices SHOULD enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. FDE comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in the case of the nexus 9 (aka flounder) it's the CPU's task. Even though the nexus 9's CPU has 2 pretty fast cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any measurements)
There is an old discussion about this topic in cyanogenmod's gerrit. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome.
Because performance is important to me and my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher)
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
What do I need to make this work?
A supported device (Your Robin)
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like stock or cyanogenmod)
A recovery that includes busybox (TWRP)
How do I use it?
Make a through, conservative backup of your data if there is any on your device.
Go into your recovery (TWRP)
Flash fed_patcher_robin.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on the first ota for example and you used the patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Download:
https://www.androidfilehost.com/?fid=24459283995312942
Credits
* @gladiac he did all of the work for this i just edited a few things for it to work on the robin Link to his original thread
Mine just in case
Hi @deadman96385,
I could have added "ether" support to the generic version of FED-Patcher which is available at [http://forum.xda-developers.com/android/software-hacking/fix-fed-patcher-v8-forceencrypt-disable-t3234422]. However, I don't mind you having your own version here in the Robin-forum . I was planning to put FED-Patcher up on github to give it a more "open" touch and enable others to do modifications to it anyway. Anyhow, do you mind if I merge your changes in the generic version?
cheers glad
gladiac said:
Hi @deadman96385,
I could have added "ether" support to the generic version of FED-Patcher which is available at [http://forum.xda-developers.com/android/software-hacking/fix-fed-patcher-v8-forceencrypt-disable-t3234422]. However, I don't mind you having your own version here in the Robin-forum . I was planning to put FED-Patcher up on github to give it a more "open" touch and enable others to do modifications to it anyway. Anyhow, do you mind if I merge your changes in the generic version?
cheers glad
Click to expand...
Click to collapse
Sure go for it
Works great, thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Robin using XDA-Developers mobile app
So I have twrp and I have to wipe internal storage as its prompting for a password.
Do I wipe internal storage, boot into the phone. Download this. Flash, wipe phone again?
For some reason adb in twrp isn't working for me to push files
Is this working with 7.0? Thank you.
hololodilolo said:
Is this working with 7.0? Thank you.
Click to expand...
Click to collapse
No it is not. The only way to disable forced encryption on official Nougat for the Robin currently is with SuperSu and Magisk.
Saythis said:
No it is not. The only way to disable forced encryption on official Nougat for the Robin currently is with SuperSu and Magisk.
Click to expand...
Click to collapse
Not true. I've used this FED Patcher with stock 7.0 and 7.1.1 and it works fine. I've never had to use Magisk.
Phone won't boot past Robin logo once i flash this
I can't figure out why this isn't working for me since no one else seems to be reporting my problem..
I'm running Nougat 7.1.1 (Build N108).. When i flash this mod, it seems to flash correctly, but the phone never goes past the nextbit logo.. And yes, of course i've tried wiping, both before and after.. I've tried after a fresh install without booting at least once. I've tried after a fresh install after its booted at least once, then wiped, then flashed, but no go.. I've tried everything i could think of, but it just won't boot..
I bought a new phone, booted once and it asked to download updates (which let me know it didn't come with N108)..
So i rebooted into fastboot, unlocked it, and flashed the factory N108 build.. Everything worked fine and my phone booted into Nougat
So i rebooted into recovery (which was factory), wiped the phone, rebooted into fastboot and flashed twrp 3.1.1, and allowed it to replace the recovery img on the system partition so it wouldn't be replaced upon future reboots. i rebooted the phone and it worked fine..
So yes, everything, fastboot, twrp, and a functioning up to date Nougat works fine, but flashing this before or after a wipe, or even a "wipe>flash>wipe>reboot" just hangs at the robin logo forever (well, at least an hour.. i tried letting it sit thinking i wasnt waiting long enough)..
Am i mistaken in thinking that ONLY data, and the "sd-card" are encrypted? Should i wipe everything except the boot partition after i flash this, and then reflash every partition except boot?
Also, possibly related, is when i preform a factory reset WITH the newest twrp, it also hangs at the robin logo.. But a wipe with the factory recovery image works fine.. So, with all the flashing ive been doing between trying to get this to work, and then recovering the phone from a semi-bricked state, ive modified the "flash-all.bat" so that when i recover my phone, im only reflashing boot/system/recovery.. and different combinations of those images as ive been trying to pinpoint the problem.. but obviously, im out of ideas..
help?
EDIT: I also just installed linux and setup adb/fastboot, so i could start pulling apart boot images and manually modifying the changes, reflashing just the image, etc (since all my dev knowledge is on a linux system), but im having some issues with working wifi drivers on this machine.. so i havent tried to dissect the boot image manually yet.. just to eliminate potential issues, simply because im desperate).. I just want to get this mf unencrypted :'(
NEVERMIND!!
I'm really not sure why it didn't work, at all, following the description and 100 other variations of it.. Maybe there's a glitch in twrp 3.1.1-0? But this is what worked for me when all else failed.. And a description of my setup.. JIC anyone else has this problem one day..
Unlocked Bootloader
-Flashed the factory stock image N108 to bring everything "back to 0"
-Booted 1 time, jic boot.img was setting up any mount points or modifying itself after 1st boot..
( I did that because if you install twrp 3.1.1-0 right after flashing the factory 7.1.1 (N108) images, and boot into recovery without booting at least 1 time into the rom, it errors when trying to do a factory reset because it claims it cant find any of the mount points.. it also prevented me from pushing fed-patcher to the phone
-After its fully booted, i reset into recovery (factory recovery still) and wiped it
-I then rebooted into fastboot from recovery and flashed twrp 3.1.1-0
-i kept system read only for now since the next step would undo any changes, and then flashed fed-patcher
-i rebooted from recovery back to fastboot and reflashed the system image with the wipe flag "fastboot -i 0x2c3f -w system system.img"
-reboot.. success!! (keep in mind that you havent reinstalled twrp yet)
Basically, all i did different here when compared to the original instructions, and the other several hundred things i tried, was the "fastboot -i 0x2c3f -w system system.img" command after patching the boot image.. Which wiped system, and also wiped "everything else" with fastboot instead of twrp..
So again, i'm not sure if i was messing up by not wiping the system partition, or if it was a bug in twrp 3.1.1-0.. but im gonna play around some more..
soulife said:
NEVERMIND!!
..
So again, i'm not sure if i was messing up by not wiping the system partition, or if it was a bug in twrp 3.1.1-0.. but im gonna play around some more..
Click to expand...
Click to collapse
First - For TWRP to work correctly you need a pin setup for unlock. That way fastboot boot twrp.img will boot fine and allow you to decrypt with the pin you just set. If you want to force it anyway. You can format data (wipe everything) followed by push TWRP and magisk and flash the force-encrypt disabled boot image.
Second. After decryption you can push anything fed-patcher included.
Third - there was however another option. You could very well have flashed the dm-noverity and force encrypt disabled ROM also in this same section
Lastly I'd exercise caution on this device with the -w command. Some of the partitions are not clearly visible and many a user has had to replace their robin.
valhallen.282 said:
First - For TWRP to work correctly you need a...
Click to expand...
Click to collapse
Thanks man, i'll keep that in mind for if i ever decide to turn encryption on again and want recovery to play nice with the rom..
The problem i was having pretty much had everything to do with the fact that this is the first device i've owned with encryption enabled, and so i didn't have a clear (enough) understanding for how it worked.. and i still don't completely. But this particular problem was because i thought that the encryption was file based, which as you already know, it is not. It's closer to a filesystem based encryption, which is why i needed to reformat for it to work instead of just factory resetting or basic wiping..
I suppose i could have let it boot completely and setup a pin, and then formatted and removed encryption, but it seemed redundant.. I mentioned how reflashing the system image with the wipe flag fixed my problem, which i now know is because it reformatted the data partition as well, which i could do from within twrp (i think).. If not, the -w fastboot flag should be fine. I appreciate your word of caution though, but when you use the batch script provided by Nextbit to flash your device, it uses the -w flag after it flashes everything else. So it should be fine to use if twrp cant reformat an encrypted userdata (which i have no idea why it wouldnt work, but i feel like i tried that already)..
ill know more, and update my post for other new users once i start using other roms.. Which might be sooner than later since substratum wont change my notification shade on stock, and its too damn bright. Which is bugging the crap outta me. I'm using a systemless substratum legacy magisk module atm, maybe thats my problem, or maybe i need oms support, i donno yet.. Nougat is new to me, im learning its new features as i go..
Note:
Please take full twrp backup of your phone before you proceed with the below steps
Steps to Flash GSI:
You can follow one of the two methods to flash GSI in Realme 3
Fastboot Method:
1. Install TWRP:
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
2a. Commands to execute in fastboot mode:
fastboot erase system
fastboot flash system name_of_system.img
fastboot -w
fastboot reboot
TWRP Method:
1. Install TWRP:
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
2. Copy system.img file to your sdcard.
3. Boot your phone to TWRP.
4. Press Install - > Install Image button -> Select the System.img file -> Select System Image-> Swipe to Flash
5. Format Data and then Wipe Cache, Dalvik Cache
6. Reboot, Done.
I used gsi from here (use aosp_arm64, download aosp_arm64-img.zip from artifacts tab and extract and flash system.img only):
https://ci.android.com/builds/branches/aosp-pie-gsi/grid
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Incase you want to go back to stock follow the same process and flash stock system.img instead of gsi system.img
stock system image: https://www.androidfilehost.com/?fid=1395089523397966778
GSI List(use ARM64 AB or A/B images):
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
ADB Installer tool: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
what Custom rom did you user sir ?
jeffalaiza said:
what Custom rom did you user sir ?
Click to expand...
Click to collapse
AOSP
fawazahmed0 said:
AOSP
Click to expand...
Click to collapse
can i flash the gsi rom in gsi list of a-only partition ?
jeffalaiza said:
can i flash the gsi rom in gsi list of a-only partition ?
Click to expand...
Click to collapse
You have to use ab gsi for realme 3 phone, but if you are downloading from ci.android.com, use aosp_arm64
fawazahmed0 said:
AOSP
Click to expand...
Click to collapse
can i use this rom for daily driver that less of bugs ?
myeganz said:
can i use this rom for daily driver that less of bugs ?
Click to expand...
Click to collapse
I have not used that aosp gsi for much time, so not sure whether it is good for daily usage or not.
You can give it a try and see
What the meaning of veritydecrypt?
jeffalaiza said:
What the meaning of veritydecrypt?
Click to expand...
Click to collapse
Its a file ,link is there in the OP,
https://www.androidfilehost.com/?fid=6006931924117905745
How can i know my device use A,B, or AB ?
Link A.14 .ozip
@fawazahmed0 please link a.14 ozip file? thanks
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
---------- Post added at 02:45 AM ---------- Previous post was at 02:37 AM ----------
krimstix01 said:
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
Click to expand...
Click to collapse
Fixed it lol. Just run
Code:
fastboot erase nvram
fastboot erase nvdata
After flashing any rom i lost my cellular network did not showed sim card, i tried to flash stock back, but it was same,
I tried doing fastboot erase nvdata and nvram, now it recognises sim but no network coverage. Is there something I'm missing?
krimstix01 said:
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
---------- Post added at 02:45 AM ---------- Previous post was at 02:37 AM ----------
Fixed it lol. Just run
Code:
fastboot erase nvram
fastboot erase nvdata
Click to expand...
Click to collapse
android Q ba yung GSI na to bro?
(This problem is solved now, it's just for future reference)
Hi, I just came to know that Disable_Dm-Verity_ForceEncrypt.zip by @Zackptg5, was causing null imei or no network issue (I have raised an issue at github for this), if you have backup of nvdata, then go to fastboot mode and do:
fastboot flash nvdata nvdata.img
I know most of the guys will not have that backup.
I tested the Disable_Dm-Verity_ForceEncrypt.zip, when my phone didn't have sim cards in it. So I never came to know about the sim problem. I am really sorry for you guys.
And one more thing, some people are suggesting to do:
fastboot erase nvram
fastboot erase nvdata
NEVER DO THAT, I REPEAT NEVER DO THAT
you are erasing the partitions, then the phone will never recover.
Thats why it is very important to take complete twrp backup of all partitions. (currently there is no twrp for realme3 which allows backup for all partitions)
So I request twrp, pbrp etc developers to modify their device tree fstab to include all the partitions in this phone and also add backup flag for all partitions (also include preloader partitions)
Here is the list of all partitions in realme 3
https://www.androidfilehost.com/?fid=6006931924117922953
For those guys who have erased their nvram and nvdata partitions, please go to service center, nothing much can be done from my side , maybe someone else can help you out.
So, guys who are having network issue after flashing Disable_Dm-Verity_ForceEncrypt.zip and have not erase their nvram and nvdata, please do the following:
1. boot to custom recovery (twrp, pbrp etc)
2. connect your phone to pc/laptop
3. execute these commands:
adb shell mkdir test
adb shell mount /dev/block/by-name/nvdata test
adb shell chcon ubject_r:nvdata_file:s0 /test/fstab.mt6771
adb shell reboot
fawazahmed0 said:
Hi, I just came to know that Disable_Dm-Verity_ForceEncrypt.zip by @Zackptg5, was causing null imei or no network issue (I have raised an issue at github for this), if you have backup of nvdata, then go to fastboot mode and do:
fastboot flash nvdata nvdata.img
I know most of the guys will not have that backup.
I tested the Disable_Dm-Verity_ForceEncrypt.zip, when my phone didn't have sim cards in it. So I never came to know about the sim problem. I am really sorry for you guys.
And one more thing, some people are suggesting to do:
fastboot erase nvram
fastboot erase nvdata
NEVER DO THAT, I REPEAT NEVER DO THAT
you are erasing the partitions, then the phone will never recover.
Thats why it is very important to take complete twrp backup of all partitions. (currently there is no twrp for realme3 which allows backup for all partitions)
So I request twrp, pbrp etc developers to modify their device tree fstab to include all the partitions in this phone and also add backup flag for all partitions (also include preloader partitions)
Here is the list of all partitions in realme 3
https://www.androidfilehost.com/?fid=6006931924117922953
For those guys who have erased their nvram and nvdata partitions, please go to service center, nothing much can be done from my side , maybe someone else can help you out.
So, guys who are having network issue after flashing Disable_Dm-Verity_ForceEncrypt.zip and have not erase their nvram and nvdata, please do the following:
1. boot to custom recovery (twrp, pbrp etc)
2. connect your phone to pc/laptop
3. execute these commands:
adb shell mkdir test
adb shell mount /dev/block/by-name/nvdata test
adb shell chcon ubject_r:nvdata_file:s0 /test/fstab.mt6771
adb shell reboot
Click to expand...
Click to collapse
Is magisk root now stable?
yametekudasai said:
Is magisk root now stable?
Click to expand...
Click to collapse
yeah
Does anyone try to flash Havoc Os? It's stable or not ? And does Bluetooth,Fingerprint,... work well? Or you have tried to flash another gsi rom is stable, please share.
my realme 3 1821 is only black screen .. can you tell me why?
Tấn Ho said:
Does anyone try to flash Havoc Os? It's stable or not ? And does Bluetooth,Fingerprint,... work well? Or you have tried to flash another gsi rom is stable, please share.
Click to expand...
Click to collapse
I tried many GSI ROMs, but VoLTE and Fingerprint works in none of them, execept for these two, everything else seems to work, in Havoc OS atleast
Bien...
I was trying to flash the EU rom on my Redmi Note 8, but I did wype to all the partitions, until that moment I had informed myself about how to flash, how to root and use twrp, but the issue of the partitions still did not know, I selected all the partitions except data and sd and I did wype, in the end my cell phone was completely bricked, I try to turn it on and for a period of less than half a second, I get the Redmi logo, below it says Powred by Android and above I get a padlock open indicating that the bootloader is unlocked, then I get a screen with the message "System has been destroyed" and then it turns off, unless I put it to load, in that case it enters the bootloop state, I cannot enter the recovery but yes I can enter fastboot, I tried to flash it through My Flash Tool and ADB, the problem is that the computer recognizes that the bootloader is unlocked, but when flashing it, a message appears that the bootloader It is locked, so flashing it is not an option, for that reason, I assume that the testpoint method for flashing by EDL would not work either.
That happened three weeks ago, at first I did not know the reason for the problem, later I learned more, I will not make that mistake again, but I am interested in knowing if there is a software solution; I would be interested in being able to download all the partitions and install them on my cell phone using the computer, I don't know if any of those who read this have the opportunity to find the partitions and share them here, I don't know if it is a realistic option, but I have hope, I saw that That solution worked with a OnePlus 3 and that's why I'm looking for information about my cell phone. The only other option I can think of is to change the motherboard, but it's very expensive and with that money, I'd better buy another cell phone.
By the way, my cell phone was in very good condition despite having used it for a year, it was very well cared for and I had no problems with both software and hardware, the reason why I was trying to change to the EU rom is because the Global version was to be a decaf version of the update.
I hope that someone can help to find a solution. Thanks for your understanding.
Diego_Arturo said:
Bien...
I was trying to flash the EU ...
Click to expand...
Click to collapse
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended
loopypalm said:
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended
Click to expand...
Click to collapse
I understand what you are saying, the problem is that I deleted all the partitions (/ boot, / system, / misk, and several others that I do not remember), the only ones that I did not delete were sd and data. I read that if you delete the boot partition, you should not restart the cell phone, you must flash a rom with the boot partition, if you don't, the cell phone will not start the operating system
Another thing: I didn't flash any ROMs, twrp didn't read my storage well and couldn't find the .zip file of the EU rom, I just wipe and reboot without flashing anything. I do not know why the cell phone still detects the system for a very brief moment before showing that the system has been destroyed, the problem is that it does not start. And when I try to flash the original ROM, the computer detects that the bootloader is unlocked, but when flashing I get an error saying that it is locked, it occurs to me that possibly the bootloader was one of the first things to be erased, but it was not completely erased Maybe the kernel or ramdisk was deleted and after that everything stopped and the cell phone just bricked, I don't know if I'm correct.
Diego_Arturo said:
I understand what you say, the problem is that I did wipe to all partitions, (/ boot, / system, / recovery, / cache, / misc and several others that I do not remember), I just did not wipe to SD and data partitions. I understand that if you delete the boot partition you must have a ROM ready that comes with a boot partition, or else you would be left with a hardbrick. What I don't know is if I can force the installation of all partitions.
Click to expand...
Click to collapse
-how did you wipe recovery ? did you use flashtool or something ?
-all roms now comes with boot img (boot partition is where the kernel files are stored) , so no problem wiping it (same for dalvik/cache/system/vendor/data)
yes, you can flash img files of partitions using fastboot (if that what you mean with force install a partition)
-what you should try now is reinstalling twrp 1st
nteresting ... It reassures me to know that I don't need to search for the partitions separately and only need to flash the ROM, although I am concerned about the same problem when flashing. I tried to flash using Mi Flash Tool, ADB and XiaoMi Tool V2, but it is always the same problem, it detects the unlocked bootloader, but when flashing it gives me an error.
I deleted all the partitions from TWRP, it was weird, because the videos didn't show many of the partitions that came out for me, that's why I don't remember them. Before doing wipe I made a copy of everything in case something went wrong, but in the end everything went wrong ...
Now that I remember, I deleted the partitions because when I tried to do anything, I got red letters and TWRP wouldn't let me do anything, when I deleted them the letters turned blue.
It seems to me that I tried to install TWRP from XiaoMi Tool v2 although I don't remember correctly, I will try and write again.
I HAVE ADVANCES!
I flashed the partitions one by one because Flash Tool still does not let me flash the ROM, on one occasion I flashed the system, but in the end it did not finish flashing, I still got the error "System has ben destroyed", I kept flashing partitions but there was no Result, in the end I flashed the system again and when it finished flashing, the error system has ben destroyed no longer appeared, now my cell phone is in a permanent bootloop state with the redmi logo, but it already lets me enter TWRP, I can't flash it from the computer, I'm going to try to get an SD card and flash it from recovery, I'm going to try to flash the EU ROM, but it's already a breakthrough, I don't have a hard brick anymore.
Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
I thank you very much for helping me find a solution, I hope this helps someone else and this serves me as my experience, I managed to solve a serious problem that I made and you helped me ... Thank you very much.
Diego_Arturo said:
Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
Click to expand...
Click to collapse
Glad it work for you ^........^ !
all sensors are working fine ?
Diego_Arturo said:
Thank you very much.
Click to expand...
Click to collapse
you know what to do
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.
Diego_Arturo said:
For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.
Click to expand...
Click to collapse
Miui roms are resource hungry and lag is not their only problem , battery and performance are also affected ...
i think you should try custom roms
First, I didn't want to, I preferred to wait, but seeing how slow the cell phone was and how fast the battery was draining, I felt that the best in the long run would be to install a ROM that did not consume so many resources, so I installed the latest version of Pixel Experience. I have to say that I did not expect anything from this ROM, I just expected fluidity and more battery, but in the end I liked it. I personally like MIUI, but I think that Pixel Experience could extend the life of my cell phone. I will continue using it and possibly in the future I will return to MIUI to see how it goes.
decryptionData
Spoiler: Old version
1. After flashing the ROM, you must make sure to inject TWRP, or install twrp ramdisk, or fastboot boot twrp.img, the bottom line is that you need to reboot into the reboot and not start the system
2. Before flashing DFE.zip, you need to check if the system is RW, if you are sure that it is RW, you can skip this step 3-6
3. We go into TWRP in it we mount the vendor section
4. Next, go to the terminal and write, "mount -o rw, remount /vendor", press enter
5. If nothing is written after execution, then the section in RW skips the next step
Or you can flash the zip file, go to the backupFSTAB folder and compare the "original" and move_to_move, if the second one weighs less and it exists at all, then the patch worked (it is advisable to manually remove it, before flashing the DFE, for the sake of convenience for verification)
6. If the terminal issued an error "/ dev / block / dm-3 'is read-only" or something similar, original and move to move are the same, then proceed to instructions 6.1-.6.3
6.1. Download the systemrw archive
6.2. flash in twrp, wait for the end of the process (you need about 10-12 free GB in memory)
6.3. restart TWRP
6.4 in the /data/
local/tmp/
systemrw_version/files/img section there will be a file after weighing about 8 gigs, you can delete it, or write a review, I will write automatic deletion in the DFE script
7. You can flash DFE.zip, if you removed the encryption for the first time, then you need to do "format data", if you update the ROM, you need to repeat steps 1-7, when changing the ROM, it is advisable to do "wipe date"
p.s Works on official miui, xiaomi.eu, and custom, not all tested, I do not know about hentai, since TWRP is not put on it
Tested on DerpFest (30.07), Xiaomi.eu (21.7.28), SyberiaOS (30.07), Official MIUI EEA 12.5.3
An example of how to flash
I have simplified patching for the end user as much as possible at the moment.
Instructions for ROMs based on MIUI (TWRP)
1. Flash ROM_MIUI.zip
2. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
3. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
Instructions for "sideload" type ROM (TWRP / Recovery adb - PC sideload - "adb sideload ROM.zip) Has a payload.bin file inside the .zip archive
1. Flash Custom_ROM.zip (with the "Inject recovery" checkbox, or after installation, do "install recovery ramdisk"
2. Reboot TWRP (in case of flashing through a PC, flash a temporary TWRP (Fastboot boot twrp.img)
3. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
4. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
Instructions for "Fastboot" type ROM
1. Open update.bat in a text editor or equivalent for your Operating System. Or Flash_all_exept_storage in case of miui, delete the last line like "fastboot reboot"
2. Run update.bat or use the mi flash tool in the case of miui, after selecting it to flash everything except the storage. At the end of the process, it will also boot into the temporary TWRP
3. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
4. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
thanks for the Super RW patch https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
Telegram support group Disable force encryption(DFE) for Poco F3 (alioth)
MFP, DFЕ, RO2RW, for Android 10+
Update channel @mfpupdate
t.me
Download https://drive.google.com/folderview?id=18NrZhttbyF-dHjM3VdfZdcPVrkmTeT_l
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sorry bro , the procedure is confusing , i ended up with stuck in splash screen , can you describe it properly?
lawong said:
sorry bro , the procedure is confusing , i ended up with stuck in splash screen , can you describe it properly?
Click to expand...
Click to collapse
I'll record a video later for clarity
LeeGarChat said:
I'll record a video later for clarity
Click to expand...
Click to collapse
thanks you sir!
lawong said:
thanks you sir!
Click to expand...
Click to collapse
Sorry for my bad english, using a translator
I updated the patch, now everything is convenient and simple
It doesnt work with oneos (miui) and ends up bootlooping to fastboot mode?
i23u8 said:
It doesnt work with oneos (miui) and ends up bootlooping to fastboot mode?
Click to expand...
Click to collapse
maybe i fixed it. try 2.4 version
LeeGarChat said:
maybe i fixed it. try 2.4 version
Click to expand...
Click to collapse
It worked! Im on the latest oneos with tertis kernel v2 and it works!
Hi @LeeGarChat I'm happy that you like my script. Please keep in mind that
NO UNAUTHORIZED , UNOFFICIAL REUPLOADS OF MY SYSTEMRW / SUPERRW FEAT. MAKERW FILES ARE ALLOWED!
Instead, you can simply put a link to the official SystemRW / SuperRW feat. MakeRW by lebigmac project page to both your video description as well as to first comment of this and your other 2 threads. Thank you.
Your installation error in your video can be avoided if /data is decrypted and mounted properly. Apparently some recoveries still have trouble doing that... This error doesn't happen if script is launched from within Android because /data partition is decrypted/mounted properly in Android.
Before running my SystemRW script you can check free space in /data partition using this command in terminal:
df -h
You need at least 10+ GB to run the script properly.
lebigmac said:
Hi. Please feel free to add a link to official SystemRW script's project page to both your video description as well as to first comment of this thread. Thank you.
Also that installation error can be avoided if /data is decrypted and mounted properly. Some recoveries still have trouble doing that.
This error doesn't happen if script is launched from within Android because /data partition is decrypted/mounted properly in Android.
Maybe in next version of script I should use this path as project path:
/data/systemrw_1.32b
What do you think?
You can check free space in /data partition using this command in terminal:
df -h
Click to expand...
Click to collapse
good idea. I'm just learning "bash" for now
LeeGarChat said:
decryptionData
Spoiler: Old version
1. After flashing the ROM, you must make sure to inject TWRP, or install twrp ramdisk, or fastboot boot twrp.img, the bottom line is that you need to reboot into the reboot and not start the system
2. Before flashing DFE.zip, you need to check if the system is RW, if you are sure that it is RW, you can skip this step 3-6
3. We go into TWRP in it we mount the vendor section
4. Next, go to the terminal and write, "mount -o rw, remount /vendor", press enter
5. If nothing is written after execution, then the section in RW skips the next step
Or you can flash the zip file, go to the backupFSTAB folder and compare the "original" and move_to_move, if the second one weighs less and it exists at all, then the patch worked (it is advisable to manually remove it, before flashing the DFE, for the sake of convenience for verification)
6. If the terminal issued an error "/ dev / block / dm-3 'is read-only" or something similar, original and move to move are the same, then proceed to instructions 6.1-.6.3
6.1. Download the systemrw archive
6.2. flash in twrp, wait for the end of the process (you need about 10-12 free GB in memory)
6.3. restart TWRP
6.4 in the /data/
local/tmp/
systemrw_version/files/img section there will be a file after weighing about 8 gigs, you can delete it, or write a review, I will write automatic deletion in the DFE script
7. You can flash DFE.zip, if you removed the encryption for the first time, then you need to do "format data", if you update the ROM, you need to repeat steps 1-7, when changing the ROM, it is advisable to do "wipe date"
p.s Works on official miui, xiaomi.eu, and custom, not all tested, I do not know about hentai, since TWRP is not put on it
Tested on DerpFest (30.07), Xiaomi.eu (21.7.28), SyberiaOS (30.07), Official MIUI EEA 12.5.3
An example of how to flash
I have simplified patching for the end user as much as possible at the moment.
Instructions for ROMs based on MIUI (TWRP)
1. Flash ROM_MIUI.zip
2. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
3. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
Instructions for "sideload" type ROM (TWRP / Recovery adb - PC sideload - "adb sideload ROM.zip) Has a payload.bin file inside the .zip archive
1. Flash Custom_ROM.zip (with the "Inject recovery" checkbox, or after installation, do "install recovery ramdisk"
2. Reboot TWRP (in case of flashing through a PC, flash a temporary TWRP (Fastboot boot twrp.img)
3. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
4. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
Instructions for "Fastboot" type ROM
1. Open update.bat in a text editor or equivalent for your Operating System. Or Flash_all_exept_storage in case of miui, delete the last line like "fastboot reboot"
2. Run update.bat or use the mi flash tool in the case of miui, after selecting it to flash everything except the storage. At the end of the process, it will also boot into the temporary TWRP
3. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
4. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
thanks for the Super RW patch https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
Download https://drive.google.com/folderview?id=18NrZhttbyF-dHjM3VdfZdcPVrkmTeT_l
View attachment 5381831
Click to expand...
Click to collapse
The new guide still need to flash RW Patch for first time ?
Jadugd said:
The new guide still need to flash RW Patch for first time ?
Click to expand...
Click to collapse
my DFE patch will tell you if you need to flash a separate SystemRW patch. in my patch there are commands to try to transfer memory to RW, but it does not always work. on the official miui does not work. need to flash systemRW, on xiaomi.eu my patch translates the system to RW
So far it works successfully in: oneos (with tertis v2 kernel), derpfest, syberia, spark, evo x, miui vn, miui vna.
It doesnt work with: arrow os
I am using twrp vishash (wont switch slots or boot using nebrassy)
i23u8 said:
It doesnt work with: arrow os
Click to expand...
Click to collapse
Copy error in TWRP, I will try to fix it
LeeGarChat said:
Copy error in TWRP, I will try to fix it
Click to expand...
Click to collapse
It actually flashes successfully in twrp and then just bootloops.
Btw, additional, works with mi-globe with stock kernel.
i23u8 said:
It actually flashes successfully in twrp and then just bootloops.
Btw, additional, works with mi-globe with stock kernel.
Click to expand...
Click to collapse
As for the Arrow ROM, it's strange that the file becomes zero size when copied. and I have not yet understood what it is connected with. conducted tests yesterday. in some conditions it is zero size, in some it normally copies. no idea at all yet what this is connected with. in the latest version 2.4b there is still no check for zero size files. I will rewrite it on the weekend, I hope I will fix the installation in the ROM arrow
Additional: works with mimix
new version 2.5
fixed work on ArrowOS
completely changed the logic of the script
now the script checks if fstab has gone to zero size
i23u8 said:
So far it works successfully in: oneos (with tertis v2 kernel), derpfest, syberia, spark, evo x, miui vn, miui vna.
It doesnt work with: arrow os
I am using twrp vishash (wont switch slots or boot using nebrassy)
Click to expand...
Click to collapse
LeeGarChat said:
new version 2.5
fixed work on ArrowOS
completely changed the logic of the script
now the script checks if fstab has gone to zero size
Click to expand...
Click to collapse
Omg awesome! Let me test it in 30 minutes
Hey folks OrangeFox Recovery is finally here for OnePlus Nord (avicii)...
THIS RECOVERY WILL SUPPORT STOCK ROMS, FBEv1 CUSTOM ROMS, FBEv2 CUSTOM ROMS.
DISCLAMER
Your warranty is now void.
I am not responsible for any damage that is made due to this action.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"If the device is encrypted, then you must format the data partition (NOTE: format - not just wipe). If the device is not encrypted, then you can just wipe the data partition (ie, no need to format)"
-source wiki.orangefox.tech
KNOWN ISSUE FOR FBEv1 Recovey : DATA BACKUP AND RESTORE NOT WORKING
DATA DECRYPTION NOT WORKING FOR SOME ROMS
KNOWN BUG FOR 00S12 Recovery (0.1%) : DATA BACKUP AND RESTORE WORKS, BUT HAVEN'T FOUND A PERFECT WAY TO RESTORE AND MAKE THE PHONE FULLY WORKING. IF YOU ARE FREE PLEASE CONSIDER TO FIND A WAY TO PERFECTLY BACKUP AND RESTORE OOS12 ROM DATA PARTITION
Note: Only boot and work with OOS12, never try to flash with FBEv1 or FBEv2 roms, if you do so, your device will face a softbrick. Similarly donot try FBEv1 or FBEv2 recoveries with OOS12. This is due to the mismatch in firmwares of OOS12 and other roms
If flashing rom from OOS12 variant, after installing custom rom, flash FBEv1, FBEv2 recovery accordingly. And vice versa
To flash OOS12 OTA (Only available from R11.1_3 onwards)
I added 2 scripts inside the recovery.
Before flashing OOS12 OTA
Go to terminal
Type and press enter
sh /system/bin/pre_oos_flash.sh
You will see an error "kPostinstallError" : just ignore it.
After flashing OOS12 OTA
Go to terminal
Type and press enter
sh /system/bin/post_oos_flash.sh
Then switch slot to updated slot
Downloads :
For FBEv1 Custom Roms :
OrangeFox Recovery R11.1_2 (Image File)
OrangeFox Recovery R11.1_2 (Flashable Zip Installer)
For OOS12 Rom:
OrangeFox Recovery R11.1_3 (Image File)
OrangeFox Recovery R11.1_3 (Flashable Zip Installer)
For FBEv2 Custom Roms :
OrangeFox Recovery R11.1_2 (Image File)
OrangeFox Recovery R11.1_2 (Flashable Zip Installer)
Guide to flash recovery :
• Reboot to FASTBOOT
• Connect your phone via USB to PC
• Open Command Prompt (You must install ADB and fastboot platform files) and type
• Only to boot the recovery
fastboot devices
fastboot boot <path to recovery image file>
• To flash recovery
fastboot devices
fastboot flash recovery <path to recovery image file>
Special Thanks to
OrangeFox Recovery Project
@DarthJabba9
@Wishmasterflo
@lordfinix
For People residing inside India
UPI :- [email protected]
For People residing outside India
Paypal
CHANGELOG (16/11/2022) - R11.1_3_OOS12
1) Initial Build
2) Support OOS12
3) 99.9% Features work
CHANGELOG (16/11/2022) - R11.1_2_FBEv1
1) Initial Build
2) Toggle Flashlight FIxed
3) Screen Ratio Fixed
4) Notch Positioning Fixed
5) Added CPU Temperature Monitor
6) Slot Switching Fixed
CHANGELOG (16/11/2022) - R11.1_2_FBEv2
1) Fixed Data Partition Backup & Restore
2) Fixed Data Partition Wipe
CHANGELOG (13/11/2022) - R11.1_1_FBEv2
1) Initial Build
2) Data Decryption Fixed
3) Toggle Flashlight FIxed
4) Screen Ratio Fixed
5) Notch Positioning Fixed
6) Added CPU Temperature Monitor
7) Slot Switching Fixed
Can you do one for a12 coloros?
skia16 said:
Can you do one for a12 coloros?
Click to expand...
Click to collapse
Ys. But require few edits. I need to build another separate version for Oxygen OS, Color OS and some other custom roms since they use FBEv1 file encryption.
Works super good! one of GOAT recoveries
@Sreeshankar K
Thanks for this great recovery! It´s working like a charm on my device.
One question: is it able to decrypt data/internal storage? I have a pattern, but there is no option in decryption to use this or am I wrong? I´m on Lineage OS 19.1.
gllark said:
@Sreeshankar K
Thanks for this great recovery! It´s working like a charm on my device.
One question: is it able to decrypt data/internal storage? I have a pattern, but there is no option in decryption to use this or am I wrong? I´m on Lineage OS 19.1.
Click to expand...
Click to collapse
Probably Lineage OS 19.1 is FBEv1 ROM. This recovery only support FBEv2 ROMs. I had mentioned it in the post. Currently no support for FBEv1 ROMs. If u want fully functioning recovery please go to the telegram group mentioned in the XDA post.
And also thanks for ur positive comment
Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data
Doc Sniper said:
Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data
Click to expand...
Click to collapse
Lemme check with lineage os 19.1. both 18.1 and 19.1 are FBEv1
Doc Sniper said:
Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data
Click to expand...
Click to collapse
I checked it on superior os which is FBEv1. And data partition was successfully decrypted
Sreeshankar K said:
I checked it on superior os which is FBEv1. And data partition was successfully decrypted
Click to expand...
Click to collapse
Strange, because here the decryption doesn't work.
The partition was once encrypted by LOS 18.1, hence probably FBEv1.
Also tried the FBEv2 recovery, but as expected no decryption dialog appears.
Thanks for testing and also creating the recovery.
Do we have any other options to test or fix this?
Doc Sniper said:
Strange, because here the decryption doesn't work.
The partition was once encrypted by LOS 18.1, hence probably FBEv1.
Also tried the FBEv2 recovery, but as expected no decryption dialog appears.
Thanks for testing and also creating the recovery.
Do we have any other options to test or fix this?
Click to expand...
Click to collapse
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.
Sreeshankar K said:
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.
Click to expand...
Click to collapse
This could possibly cause the Bluetooth problem, because the SELinux permissions don't seem to match after trying to decrypt data.
In any case, it's great that you're taking the time to look for the problem and fix it. Thanks.
Doc Sniper said:
This could possibly cause the Bluetooth problem, because the SELinux permissions don't seem to match after trying to decrypt data.
In any case, it's great that you're taking the time to look for the problem and fix it. Thanks.
Click to expand...
Click to collapse
Recovery settings and rom settings have no connections. Recovery only look for the fstab of rom to do the operations like wipe, install, backup and restore etc. Idk why that prob is appeared
Sreeshankar K said:
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.
Click to expand...
Click to collapse
Any news ?
Tried booting then flashing the R11.1_2_FBEv1 build using the fastboot manual flash, with OOS F17 EU (the latest for my device at the time of writing), it doesn't boot and just show the "boot/recovery destroyed" screen, any idea why?
Phone was also not booting after the flash, stuck on the "destroyed" screen, and I had to reflash the boot.img (no, I did not flash over boot, I double checked that I did specify recovery_a/_b when flashing)
WORMSTweaker said:
Tried booting then flashing the R11.1_2_FBEv1 build using the fastboot manual flash, with OOS F17 EU (the latest for my device at the time of writing), it doesn't boot and just show the "boot/recovery destroyed" screen, any idea why?
Phone was also not booting after the flash, stuck on the "destroyed" screen, and I had to reflash the boot.img (no, I did not flash over boot, I double checked that I did specify recovery_a/_b when flashing)
Click to expand...
Click to collapse
It is bcoz, OOS12 firmware doesn't support other custom kernels, firmwares etc
Sreeshankar K said:
It is bcoz, OOS12 firmware doesn't support other custom kernels, firmwares etc
Click to expand...
Click to collapse
Isn't "For Stock Roms (Oxygen OS and Color OS) & FBEv1 Custom Roms" a bit misleading then? Since it mention OOS and it being "For Stock Roms"
Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!
WORMSTweaker said:
Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!
Click to expand...
Click to collapse
Data backup and restore is buggy, means not saying that it is not working, haven't found a correct way to restore the backup of data partition, so if you have time please found a correct way to restore data partition, and post it here. Data decryption and all other features work.
[RECOVERY] [13] [UNOFFICIAL] TeamWin Recovery Project (8T / 9R) (2022-07-27)
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Like this we also need correct way to backup and restore data partition, so, if your are free do it.
WORMSTweaker said:
Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!
Click to expand...
Click to collapse
"I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything "
This is bcoz your data partition is not decrypted. Decrypt it using your rom password then everything will be normal. That's not a bug... Bug is in the restoration of backuped data. Actually not a bug. Didn't found a fully working way.
Need to find a perfect way to restore. OOS12 data restore is bit painful.
Take a look on data backup and restore
if you are free
Thank you