Related
{
"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"
}
All credit for this software goes to the dev (Koushik Dutta and anyone else on his team).
** Nandroid backups made on previous versions of CWM cannot be restored in CWM 5.0.x.x. So if you have backups made in versions 2.5.x.x or 3.0.x.x, you will not be able to restore them once you've upgraded. **
HOMEPAGE
ClockworkMod.com
DOWNLOAD
Standard recovery
Link: recovery-clockwork-5.0.2.0-glacier.img - Rename to "recovery.img" for easier CLI entry
MD5: a5aea82ec2ad7b836c9c179fce0d520d - To verify, use ManD5 or the below ADB commands:
Touch recovery
Link: recovery-clockwork-touch-5.8.1.0-glacier.img - Rename to "recovery.img" for easier CLI entry
MD5: 687998d5093878147256c10ae9e98e5a - To verify, use ManD5 or these ADB commands:
Code:
adb push recovery.img /sdcard/recovery.img
adb shell md5sum /sdcard/recovery.img
INSTALLATION
- Via the ROM Manager app (version 4.4.0.3 or newer required)
- Via terminal emulator:
Code:
Move recovery.img to the root of your sdcard
Start the terminal app
su (press enter)
flash_image recovery /sdcard/recovery.img (press enter)
reboot recovery (press enter)
- Via fastboot (ADB installation and engineering bootloader version 0.85.2007 required):
Code:
Move recovery.img to a location where fastboot can find it.
Boot your phone into fastboot mode
Connect your phone via USB to your computer
fastboot devices
fastboot flash recovery recovery.img
CHANGE-LOG
5.0.0.1 through 5.0.1.0
Backups now use tar over yaffs for everything except mtd partitions. Backup speed improved.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type.
New color scheme
Status bar when backing up working again
Backing up of .android_secure working again
5.0.2.0
Bug-fix: root no longer lost on rom restore
5.8.0.9
Touch version - initial release (beta stage)
5.8.1.0
Major bug fixed (recovery.fstab malformed)
I'm not in any way responsible if something happens to your device. I'm simply posting this as a courtesy to the community.
I still don't know how this flew over our heads.
Either way, glad you provided every possible method to upgrade.
mackster248 said:
I still don't know how this flew over our heads.
Either way, glad you provided every possible method to upgrade.
Click to expand...
Click to collapse
Was there a 4.0? I was still on 3.0.24 still, and now I find out about this version. does anyone know its new features?
Ace42 said:
Was there a 4.0? I was still on 3.0.24 still, and now I find out about this version. does anyone know its new features?
Click to expand...
Click to collapse
As far as I know, the jump was made straight from 3.0.2.4 to 5.0.0.1. I have yet to see a changelog, but if anyone finds one, I'll add it to the OP. After poking through the menus, nothing obvious stood out, so it seems to be a bug fix and "behind the scenes" release.
-From Mr.Dutta via G+
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
Thanks for the heads up. Just flashed via rom manager without any issues.
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
epolaris said:
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
Click to expand...
Click to collapse
I'm not quite sure if that's a bug. Since there's a lot of internal changes, I'm assuming the path it takes from Android to CWM has changed. So maybe that's why we're stuck at the splash screen.
But that's not too big of a problem. So far it's much faster than the previous versions.
WOW! I just did a backup of my current Rom and it literally took like 1 minute! It's WAY faster now.
epolaris said:
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
Click to expand...
Click to collapse
I'm not having that issue at all. I can reboot into recovery using the power menu within Faux's 1.3.1 rom and it works perfectly. I can't speak about other roms, but just letting you all know that Faux's latest works fine.
<EDIT EDIT>
lol wrong forum.
updated to 5.0.0.1. seems pretty neat.
This new recovery backs up roms really fast. With the old version it used to take my phone 2 to 3 minutes to back up. Now about a minute. Its actually kind of scaring me. I don't know if its backing it up correctly. I'm affraid to restore lol.
Sent from my HTC Glacier using xda premium
coupetastic-droid said:
This new recovery backs up roms really fast. With the old version it used to take my phone 2 to 3 minutes to back up. Now about a minute. Its actually kind of scaring me. I don't know if its backing it up correctly. I'm affraid to restore lol.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I posted the changelog on the 1st page.
"I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!"
I also added the info from his Google+ page to the OP.
Any information on whether other built in tools such as sdparted were updated too? I have been having a lot of trouble with my SD card (I couldn't get it to format through sdparted because of some error I can't remember) and the option to partition your SD card through ClockWorkMod Recovery 3.x didn't allow to set EXT to a size of 0. I was able to partition my card the way I wanted through sdparted after flashing the new 5.0.0.1 recovery, but was curious as to whether there was a change within the recovery img that allowed me to finally partition the way I wanted or if the change was something else that caused my SD card to start functioning correctly.
bstapley said:
I'm not having that issue at all. I can reboot into recovery using the power menu within Faux's 1.3.1 rom and it works perfectly. I can't speak about other roms, but just letting you all know that Faux's latest works fine.
Click to expand...
Click to collapse
+1 Same here
Sent from my HTC Glacier using XDA Premium App
Ace42 said:
I posted the changelog on the 1st page.
"I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!"
Click to expand...
Click to collapse
just did a restore and everything went perfectly fine. thanx.
I was just wondering that when I flash a rom and it calls for 3.0.2.4 recovery do I still use that or can I use the new recovery..I know it's a dumb question but just want to make sure
Sent from my virtuous doubleshot glacier using XDA App
darksoul0013 said:
I was just wondering that when I flash a rom and it calls for 3.0.2.4 recovery do I still use that or can I use the new recovery..I know it's a dumb question but just want to make sure
Click to expand...
Click to collapse
Shouldn't be a problem. Nothing was changed that would make affect how a ROM is flashed.
I've modified Robin's boot.img to disable forced encryption.
With encryption gone, you'll be able to use TWRP to flash mods etc, without having to wipe your data every single time.
Other benefits include faster performance and better battery life.
Unfortunately, to actually remove the encryption - you will need to format one last time.
But once done and set up, you'll see that your phone is no longer encrypted.
{
"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"
}
Requirements:
- Unlocked bootloader
- PC / Mac
- fastboot (+ USB drivers if needed) -or- existing TWRP install
Instructions:
If you're using TWRP:
1. Perform a factory reset from within TWRP and reboot back into it (Note: This isn't required if your upgrading from an existing unencrypted stock install).
2. Flash the included zip file
3. Reboot
Manual flash using fastboot:
1. Download the zip and extract the boot.img file
2. Reboot your Robin into fastboot mode
3. Flash using the command:
Code:
fastboot -i 0x2c3f flash boot boot.img
4. Factory reset. (This isn't required if your Robin is already unecrypted and you simply want to update your /boot)
Note: If you skip this step, your phone will remain encrypted.
5. Reboot
Rollback:
1. Re-Enable encryption from Settings -> Security -> Encrypt Phone
2. Flash the stock boot.img
Credits:
@reddv1 for the original modification instructions (adapted from Nexus 5X) and @osm0sis for AIK
----
Disclaimer: Disabling encryption on your phone *will* reduce it's security. These files / instructions are provided only for those who understand and accept the risks of using an un-encrypted device, and are comfortable with modifying the internals of their phone. I will not be held responsible for any loss or damages occurred as a result of following the instructions and/or downloading the files listed on this page.
Thanks, worked well!
Thank tested, will se if it gets any faster. Have been having some problem with lag that comes from time to time that I haven't seen on other devices.
Otherwise, great to see support for such a small phone!
The Robin devs are trying to be Community friendly as much as possible its good to see.
can it still be updated using this mod boot ?
kanded said:
can it still be updated using this mod boot ?
Click to expand...
Click to collapse
Unfortunately no, because the OTA includes an updated delta for the kernel as well (which means the /boot needs to be 100% stock).
If you want to install via the OTA, you need to restore the stock boot.img (and the system partition - if you're rooted or modified it in any way, and the recovery too, if you have TWRP installed).
Alternatively, you may simply flash the updated stock ROM zip on top of your existing install - just be sure to flash the new boot.img zip immediately after (as well as SuperSU and any other mods you may have, if you want to preserve your current setup).
Thank you for this [deXter] it works great.
However does anyone have a solution for how to get rid of the 5 sec nag screen popping up at reboot?
Thanks in advance/arc.
For June update 350 please.
I need help!
When I boot up and finish setup ,my battery percentage said : 3.0858 % and Wi-Fi wasn't turning on did I do something wrong?
Angeldgaf said:
When I boot up and finish setup ,my battery percentage said : 3.0858 % and Wi-Fi wasn't turning on did I do something wrong?
Click to expand...
Click to collapse
This mod only allows you to use your phone unencrypted - it shouldn't affect your battery or WiFi. Are you sure you flashed the correct version?
Goto Settings - About. If you're on the June 1 ROM (Build 00WW_1_350) then your kernel version should say 3.10.84 Wed Jun 1. If these numbers do not match then restore to the latest factory image/ROM and start over. Also, have you tried a factory reset yet?
For 450 Please
Updated for build 450.
Hi everybody! Just receveid the OTA notification
I'm currentyl on 6.0.1 1450 rooted with twrp, do you have the modified boot.img for the Nougat beta as well? Thanks
Many thanks for this work. Getting the Robin rooted and usable was a struggle compared to the Nexus4. This mod helped greatly.
Boot image for N88 please. Thanks in advance.
So did I understand right, I only can use this mod for stock ROM (not for LineageOS 14.1)?
Steffen1st said:
So did I understand right, I only can use this mod for stock ROM (not for LineageOS 14.1)?
Click to expand...
Click to collapse
Yes. Lineage does not have forced encryption.
[deXter] said:
I've modified Robin's boot.img to disable forced encryption.
With encryption gone, you'll be able to use TWRP to flash mods etc, without having to wipe your data every single time.
Other benefits include faster performance and better battery life.
Unfortunately, to actually remove the encryption - you will need to format one last time.
But once done and set up, you'll see that your phone is no longer encrypted.
Requirements:
- Unlocked bootloader
- PC / Mac
- fastboot (+ USB drivers if needed) -or- existing TWRP install
Instructions:
If you're using TWRP:
1. Perform a factory reset from within TWRP and reboot back into it (Note: This isn't required if your upgrading from an existing unencrypted stock install).
2. Flash the included zip file
3. Reboot
Manual flash using fastboot:
1. Download the zip and extract the boot.img file
2. Reboot your Robin into fastboot mode
3. Flash using the command:
Code:
fastboot -i 0x2c3f flash boot boot.img
4. Factory reset. (This isn't required if your Robin is already unecrypted and you simply want to update your /boot)
Note: If you skip this step, your phone will remain encrypted.
5. Reboot
Rollback:
1. Re-Enable encryption from Settings -> Security -> Encrypt Phone
2. Flash the stock boot.img
Credits:
@reddv1 for the original modification instructions (adapted from Nexus 5X) and @osm0sis for AIK
----
Disclaimer: Disabling encryption on your phone *will* reduce it's security. These files / instructions are provided only for those who understand and accept the risks of using an un-encrypted device, and are comfortable with modifying the internals of their phone. I will not be held responsible for any loss or damages occurred as a result of following the instructions and/or downloading the files listed on this page.
Click to expand...
Click to collapse
Boot.img for N108?
Use the modified FED Patcher for the Robin from this thread:
https://forum.xda-developers.com/ne...d-patcher-robin-forceencrypt-disable-t3352006
It worked fine for me on 108. After flashing the latest 108 7.1.1 file from the Razer forums, I flashed TWRP 3.1.0-0, then the FED Patcher, and finally Super SU 2.82.
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..
Hello, the error described in the title appeared when i tried to dirty flash the Miui 13 update european version for the Poco F3 on top of Miui 12.5.7. Before flashing the rom i forgot to mount some partitions, including the cited ones, giving me the error. Now i can't mount the required partitions, can't flash the old system nor the newer and TWRP says there isn't an OS installed, as such it goes into a bootloop.
Does someone know what to do?
I tried using the MiFlash tool 2020.3.14.0 to flash the fastboot rom versionof Miui 12.5.7 but it outputs to "The name of the directory is not valid"
Pillow fan said:
Hello, the error described in the title appeared when i tried to dirty flash the Miui 13 update european version for the Poco F3 on top of Miui 12.5.7. Before flashing the rom i forgot to mount some partitions, including the cited ones, giving me the error. Now i can't mount the required partitions, can't flash the old system nor the newer and TWRP says there isn't an OS installed, as such it goes into a bootloop.
Does someone know what to do?
I tried using the MiFlash tool 2020.3.14.0 to flash the fastboot rom versionof Miui 12.5.7 but it outputs to "The name of the directory is not valid"
Click to expand...
Click to collapse
No doubt you have, but just to check... you have extracted to .tgz file to reveal a .tar, which also needs extracting (i use 7zip) until you have a folder that contains the images folder etc etc.
Also, it could help having Mi Flash and the above folder containing the images in the root of C drive, rather than deep in the drive with a long title - eg D:\ANDROID\Xiaomi\alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global
EDIT: oh and be sure to uncheck the flash all and lock option in MiFlash (bottom right corner), or your bootloader will be locked after flashing...
reg66 said:
No doubt you have, but just to check... you have extracted to .tgz file to reveal a .tar, which also needs extracting (i use 7zip) until you have a folder that contains the images folder etc etc.
Also, it could help having Mi Flash and the above folder containing the images in the root of C drive, rather than deep in the drive with a long title - eg D:\ANDROID\Xiaomi\alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global
EDIT: oh and be sure to uncheck the flash all and lock option in MiFlash (bottom right corner), or your bootloader will be locked after flashing...
Click to expand...
Click to collapse
I just controlled and it seems what i did while trying to flash the fastboot rom is completely wrong since i tried to flash the recovery version. I have downloaded the fastboot rom now but i will have to try to install it tomorrow
The rom was flashed succesfully this time but it still goes into the mi recovery when trying to boot. i flashed twrp to see if i could flash the rom from there and now all partitions can be mounted except for /data. When trying to decrypt it using the pin passcode it says Password Failed. is it because i also had the fingerprint and face unlock? When i still couldn't mount the other partitions I always used the pin passcode to decrypt storage. Has the passcode been changed when flashing with the mi flash tool? I don't have a recent system and data backup nor a backup of the internal storage so this issue is devastating to me, i want to save my data at all costs
EDIT: I tried reflashing twrp from fastboot and now I also can't mount the /cust partition with error "Structure needs Cleaning"
Perhaps someone else may offer some better advice, but as far as I can tell your original system is gone. Once you accept this sad fact, you need to flash fastboot rom using miflash choosing the option 'clean all' (NOT CLEAN ALL AND LOCK) to flash the system clean again, after flashing you can expect an error that miflash couldn't lock the device, this is usual. then your device will restart and take quite a few minutes to boot again. don't bother to flash twrp again yet, just the system running first
reg66 said:
Perhaps someone else may offer some better advice, but as far as I can tell your original system is gone. Once you accept this sad fact, you need to flash fastboot rom using miflash choosing the option 'clean all' (NOT CLEAN ALL AND LOCK) to flash the system clean again, after flashing you can expect an error that miflash couldn't lock the device, this is usual. then your device will restart and take quite a few minutes to boot again. don't bother to flash twrp again yet, just the system running first
Click to expand...
Click to collapse
So i have to accept that all my data is gone? No chances of decrypting the data partition? I'll wait and see if someone has something that could work, if nothing else does i guess i'll have to accept the reality. Thank you anyway
I experienced pretty much the same thing as you in the past (i.e. 'failed to mount' and 'no OS installed' errors); unfortunately, the internal storage is most likely wiped. Happy to be corrected for your sake, but I am in agreeance with @reg66.
EDIT: formatting
Sauceunny said:
I experienced pretty much the same thing as you in the past (i.e. 'failed to mount' and 'no OS installed' errors); unfortunately, the internal storage is most likely wiped. Happy to be corrected for your sake, but I am in agreeance with @reg66.
EDIT: formatting
Click to expand...
Click to collapse
TWRP doesn't display the "OS not installed error" and before flashing the fastboot rom version the data partition could be decrypted normally with the lockscreen passcode. Does this mean that Mi Flash encrypted the data partition with a different key?
Thank you to @reg66 and @Sauceunny , I have decide to wipe the memory of the phone as i have deemed it to be too much work to save some chats and images while the most important files are stored as a backup. I will have to plan the next update or changing rom more thorougly next time.
I have the same problem with my S21 ultra
Error on product, vendor and ODM
So i can't install stock ROM because of this error.
Doesnl anyone have an idea?
{
"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"
}
i cant mount system
i use poco f3
cant someone help me for fixed
how tp fixed..
please help
I'm facing the same errors except "Odm" I don't know what to do I tried to flash pixel experience rom in my mom's redmi note 10 using "twrp" it's just just in it. Please help me out
Download fastboot rom, use miflash to flash it (select clean all without lock) and dont play with mom's phone again. Watch a miflash tutorial on youtube if you're new to this.
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