Database Users

[fully functional] CyanogenModRecovery 5.0.2.6

Preambula:
When Grif_07 compiled his CM, as a result he got a new version of the CWM.
The CWM text color changed to blue.
After the flash you will get a cyclic reboot CWM, as is the case with the installation of CWM by means of Rom Manager.
Functions not tested. So it is not responsible for the performance. Solely for testing purposes.
How to install:
Flash in recovery.
Ambula:
thanks to Grif_07 and ketut.kemujaya we have fully working CWM 5.0.2.6.
Download here.
Proof

I'll try, maybe the boot cyclic to CWM problem comes from the kernel that I could fix or you can try to flash back the boot image (boot.img) after flashing the recovery image. I have an experience even using a fixed kernel I got boot cyclic and resolved by flash back the boot image.

ketut.kumajaya said:
...that I could fix.
Click to expand...
Click to collapse
It would be great!

If only I was good at this :/
Forever living in my Galaxy Ace using XDA App

ketut.kumajaya said:
you can try to flash back the boot image (boot.img) after flashing the recovery image.
Click to expand...
Click to collapse
It does not help with bootloop on this version CWM(
P.S. flash this CWM and try to make a backup - get error when backup boot.img(
Flash back to CWM 4... - bootloop, flash boot.img - normal boot.

Lovetz said:
It does not help with bootloop on this version CWM(
P.S. flash this CWM and try to make a backup - just error(
Flash back to CWM 4... - bootloop, flash boot.img - normal boot.
Click to expand...
Click to collapse
That means you got CWM v5 ?
Forever living in my Galaxy Ace using XDA App

EmoBoiix3 said:
That means you got CWM v5 ?
Click to expand...
Click to collapse
I flash it, but got a bootloop, and flashback to CWM 4.0.0.9.

EmoBoiix3 said:
That means you got CWM v5 ?
Click to expand...
Click to collapse
No, but he can back to CWM4 without bootloop

ketut.kumajaya said:
No, but he can back to CWM4 without bootloop
Click to expand...
Click to collapse
I am preparing to compile new CM build right now. What I need to change in sources for CWM5 bootloop fixing?

Grif_07 said:
I am preparing to compile new CM build right now. What I need to change in sources for CWM5 bootloop fixing?
Click to expand...
Click to collapse
I think the fix is in kernel. Give me time to fix above CWM5 shared by Lovetz.

ketut.kumajaya said:
I think the fix is in kernel. Give me time to fix above CWM5 shared by Lovetz.
Click to expand...
Click to collapse
Ok... Then I am starting to compile... Maybe a new version of CWM will built to.

Grif_07 said:
I am preparing to compile new CM build right now. What I need to change in sources for CWM5 bootloop fixing?
Click to expand...
Click to collapse
Apply this fix
https://github.com/PabloPL/android_...mmit/46e96915a7e0459dc6b3aec04aa47329371fff44
To return from recovery, our kernel need to call reboot with recovery_done option.
(you can test this - while in CWM5, try to run reboot recovery_done, you should back to Android).

Fixed using CF-Root's CWM4 kernel (a kernel with a patched pm2.c, thanks to ilarrain) and add 2 lines command to init.rc to load jbd2 and ext4 modules.
For CyanogenMod 7.1 and advance user only for now!
How to flash:
- Boot your device into CWM recovery
- Push recovery-clockwork-5.0.2.3-galaxyace.img to your device using "adb push recovery-clockwork-5.0.2.3-galaxyace.img /tmp/" command
- Login to your device over "adb shell"
- Mount /system using "mount /dev/block/stl12 /system" command
- Flash CWM recovery using "flash_image recoveryonly /tmp/recovery-clockwork-5.0.2.3-galaxyace.img" command
- Umount /system using "umount /system" command
- Reboot your device using "reboot recovery" command to test your new CWM recovery
- Reboot your device
Not fully tested and have no enough space to try the backup/restore function
EDIT:
Recovery flashable zip added.
EDIT2:
Please try the *-fix.zip version.
Changelog:
- mount, umount, and rm scripts taken from my CF-Root-S5830 CWM to fix mount error problem
- /etc/recovery.fstab changed to mount /sd-ext partition and to fix recovery backup problem
EmoBoiix3 and Lovetz, waiting for your report
EDIT3:
The fix version almost same as clockwork-5.0.2.6 I have modified before and shared here by Grif_05, except:
- remove a garbage file
- ext4 support compiled in kernel, not as a module
- using new Samsung proprietary modules taken from DXKPD

ketut.kumajaya said:
Fixed using CF-Root's CWM4 kernel (a kernel with a patched pm2.c, thanks to ilarrain) and add 2 lines command to init.rc to load jbd2 and ext4 modules.
For CyanogenMod 7.1 and advance user only for now!
How to flash:
- Boot your device into CWM recovery
- Push recovery-clockwork-5.0.2.3-galaxyace.img to your device using "adb push recovery-clockwork-5.0.2.3-galaxyace.img /tmp/" command
- Login to your device over "adb shell"
- Mount /system using "mount /dev/block/stl12 /system" command
- Flash CWM recovery using "flash_image recoveryonly /tmp/recovery-clockwork-5.0.2.3-galaxyace.img" command
- Umount /system using "umount /system" command
- Reboot your device using "reboot recovery" command to test your new CWM recovery
- Reboot your device
Not fully tested and have no enough space to try the backup/restore function
recovery-clockwork-5.0.2.3-galaxyace.img (4.89 MB)
Click to expand...
Click to collapse
I'll flash this image and see whether backups work . Will edit this post .
EDIT: Error while backing up recovery image . Backup stops .
Edit2: This CWM doesn't support mounting /sd-ext
Edit3: Restore works though .

ketut.kumajaya said:
EDIT:
Recovery flashable zip added.
Click to expand...
Click to collapse
1. When try to make backup:
Backing up boot image...
Backing up recovery image...
Error while backing up recovery image!
Click to expand...
Click to collapse
2. After boot in to CWM /cache and /sdcard are already mounted.
3. When try to wipe cache
wiping cache....
Formatting /cache...
Cache wipe complete.
Click to expand...
Click to collapse
4. But in log:
Formatting /cache...
I:Formatting unknown device.
mount: mounting /dev/block/stl14
on /cache failed: Invalid argument
W:failed to mount /dev/block/stl14 (File exists)
rm: can`t remove '.' or '..'
rm: can`t remove '.' or '..'
Cache wipe complete.
mount: mounting /dev/block/stl14
on /cache failed: Invalid argument
W:failed to mount /dev/block/stl14 (File exists)
Click to expand...
Click to collapse

Please try the (still not sure) fixed version: recovery-clockwork-5.0.2.3-galaxyace-fix.zip

ketut.kumajaya said:
Please try the (still not sure) fixed version: recovery-clockwork-5.0.2.3-galaxyace-fix.zip
Click to expand...
Click to collapse
Ketut, I have 5.0.2.6 version. Do you need it?

Grif_07 said:
I have 5.0.2.6 version.
Click to expand...
Click to collapse
Upload here, why not?

ketut.kumajaya said:
Please try the (still not sure) fixed version: recovery-clockwork-5.0.2.3-galaxyace-fix.zip
Click to expand...
Click to collapse
Backup works fine now . Thanks a lot ketut !
I even have the CF-Root indication :3

Lovetz said:
Upload here, why not?
Click to expand...
Click to collapse
because it has bootloop and not working backup.

Fota TWRP 2.8.6.0 with f2fs recovery for amami by @o-l-a-v

@o-l-a-v have made latest twrp 2.8.6.0 recovery with f2fs for flashing on fota partition. I publish it here bcs there is no development behind it. It works with latest cm12 nightlies
f2fs is untested report pls
All thanks to @o-l-a-v
Install through fastboot:
fastboot flash recovery
https://mega.co.nz/#!3gRwGZiK!sXMsMx1GGwUVkTCCsr8ntZekCE-o-hB4DDp6wlhVQqA
New version again
You don't need any app for flashing, use fastboot, see above
be careful if you write: fastboot flash boot you won't be able to boot

Cool, what ROMs did you test this on ?

OmarEinea said:
Cool, what ROMs did you test this on ?
Click to expand...
Click to collapse
i´m on liquid, but it works on every no stock rom,i used previous version on all your roms
i have made it bcs @championswimmer has not amami support for twrp in his recovery manager only for philz and i prefer twrp

funiewski said:
I have made latest twrp 2.8.0.1 recovery for flashing on fota partition. I publish it here bcs there is no development behind it.
Install through fastboot:
fastboot flash recovery fotaZ1cTWRP2.8.0.1.img
https://dl.dropboxusercontent.com/u/17658154/fotaZ1cTWRP2.8.0.1.img
Click to expand...
Click to collapse
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?

Rekoil said:
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?
Click to expand...
Click to collapse
That was TWRP developer @Dees_Troy who found the possibility of using fota partition on xperia devices for recovery flashing. Here: http://forum.xda-developers.com/showpost.php?p=38640389&postcount=2
You access it in usual way, Sony logo+led light press volume+. Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed. If you are flashoholic like me it is quite a pain. With recovery on fota partition it is no longer a problem. @championswimmer has made a small paid app for flashing recovery on fota, but as i wrote before it does not support twrp for amami only philz and you can flash it easily with fastboot. This works only on aosp and cm roms, if you want to overwrite recovery on fota you can either use flashtool and flash only fota, uncheck all other boxes or you can use recovery manager i mentioned earlier.

funiewski said:
Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed.
Click to expand...
Click to collapse
Nice, expirienced same problems.
Thanx @funiewski

Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?

CoolDevelopment said:
Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?
Click to expand...
Click to collapse
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon

funiewski said:
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon
Click to expand...
Click to collapse
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.

How does it work that the phone enters recovery from FOTA partition and not kernels internal recovery?

Rekoil said:
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.
Click to expand...
Click to collapse
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me

funiewski said:
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me
Click to expand...
Click to collapse
Yeah but it is still executing the kernel from the boot partition, so if you **** up boot partition you'll **** up recovery, so it's not much of a recovery. It just loads data from the FOTA partition. A true recovery has its own kernel.

On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?

paulle said:
On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?
Click to expand...
Click to collapse
Exactly in same way as this one.

@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well

russel5 said:
@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well
Click to expand...
Click to collapse
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here

funiewski said:
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here
Click to expand...
Click to collapse
Not stock, but for stock ROM with stock ramdisk (except RIC is disable)
This boot NOT have any recovery, only work with FOTA recovery
View attachment boot.zip

Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)

o-l-a-v said:
Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)
Click to expand...
Click to collapse
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp

funiewski said:
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp
Click to expand...
Click to collapse
Yes, stock CM kernel. Hm. I'll try again. Eventually try that custom kernel.

MultiBoot the OnePlus One with EFIDroid - Working on Nougat

So a while back I stumbled on EFIDroid and decided to give it a spin and was surprised how well it works on our device. Bellow I have a video tutorial showing how EFIDroid works. It even has support for a secondary firmware - which means that you could also have Hydrogen OS installed alongside Lineage 14 with no issues since each has its own firmware and recovery. Have fun multibooting everybody.
NOTE: For the OnePlus One when adding a ROM, the directory for the new ROM should be under /media and also you will have to use TWRP 3.0.0_0 (newer ones have bigger ramdisks that cause problems).

CedArctic said:
So a while back I stumbled on EFIDroid and decided to give it a spin and was surprised how well it works on our device. Bellow I have a video tutorial showing how EFIDroid works. It even has support for a secondary firmware - which means that you could also have Hydrogen OS installed alongside Lineage 14 with no issues since each has its own firmware and recovery. Have fun multibooting everybody.
NOTE: For the OnePlus One when adding a ROM, the directory for the new ROM should be under /media and also you will have to use TWRP 3.0.0_0 (newer ones have bigger ramdisks that cause problems).
Click to expand...
Click to collapse
I have f2fs partation, will it work on that. And i have selected data/media/0/multiboot/sultan
But i am getting can't locate boot kernel size problem

pankspoo said:
I have f2fs partation, will it work on that. And i have selected data/media/0/multiboot/sultan
But i am getting can't locate boot kernel size problem
Click to expand...
Click to collapse
I have f2fs as well and everything works fine as efidroid creates virtual ext4 partitions. Are you using TWRP 3.0.0? Also if you failed to boot a ROM once and then try to boot another it will fail, that's why you make a quick reboot and then boot directly the second ROM.

CedArctic said:
I have f2fs as well and everything works fine as efidroid creates virtual ext4 partitions. Are you using TWRP 3.0.0? Also if you failed to boot a ROM once and then try to boot another it will fail, that's why you make a quick reboot and then boot directly the second ROM.
Click to expand...
Click to collapse
Link TWRP 3.0?

pankspoo said:
Link TWRP 3.0?
Click to expand...
Click to collapse
Here you go: https://dl.twrp.me/bacon/twrp-3.0.0-0-bacon.img.html

Giving it a try just now.. Will let you know how to it goes.. Thanks

4yush said:
Giving it a try just now.. Will let you know how to it goes.. Thanks
Click to expand...
Click to collapse
Happy flashing

CedArctic said:
Happy flashing
Click to expand...
Click to collapse
I get into TWRP, but not able to find the ROM file, thought i have it in my internal memory?

4yush said:
I get into TWRP, but not able to find the ROM file, thought i have it in my internal memory?
Click to expand...
Click to collapse
The twrp you booted can only see a virtual internal storage partition. Just boot the secondary twrp, connect to your PC and copy the ROM again

4yush said:
I get into TWRP, but not able to find the ROM file, thought i have it in my internal memory?
Click to expand...
Click to collapse
use otg and connect pen drive keep that ROM in pen drive and flash

pankspoo said:
use otg and connect pen drive keep that ROM in pen drive and flash
Click to expand...
Click to collapse
I doesnt detect an OTG.

Just copy zip file AFTER you boot secondary recovery

4yush said:
I doesnt detect an OTG.
Click to expand...
Click to collapse
Go to settings- mount- select usb
Then while flashing there is tab near flash zip saying select storage go there and select usb
That's it

Can't get secondary ROMS to work on Bacon
I've got Lineage OS 14.1 + nethunter + gapps as my Primary ROM. EFIDroid to manage the multiboot. TWRP 3.0.0.0 as recovery. No problem in Primary OS.
I am able to create the secondary OS partitions. I am successfully able to flash the secondary OS. It boots successfully. However, whenever I try to flash open gapps (nano or pico) the system reboots and gives the message "Previous Boot Failed. Cant allocate child memory -9".
I've tried this with two roms now, [ROM][OFFICIAL][7.1.2_r29][BACON][OPTIMIZED]RESURRECTION REMIX [5.8.5][OMS] and [ROM][8.1.0_r7] AOSP Oreo for OnePlus One [Stable] and the error is the same. This tells me its not ROM related?
One more thing, I must mount the system partition before flashing gapps or I get "updater process ended with error: 139". I've also tried increasing the size of the system partition of secondary os from 1GB to 2GB but the result is the same.

Same Problem
I've tried with yet another OS as secondary. There is no problem in flashing and booting the OS but flashing gapps just fails. This definitely has everything to do with EFIDroid.
Further, I've tried flashing the same OS+gapps as primary and it works. Gapps flashing is not working only on secondary OS. Everytime the same error pops up after rebooting abruptly "Previous Boot Failed can't allocate child memory -9 0xffffff7"
Kindly help. Multiboot is of no use if I can't flash gapps on secondary OS.

aksrocks said:
I've tried with yet another OS as secondary. There is no problem in flashing and booting the OS but flashing gapps just fails. This definitely has everything to do with EFIDroid.
Further, I've tried flashing the same OS+gapps as primary and it works. Gapps flashing is not working only on secondary OS. Everytime the same error pops up after rebooting abruptly "Previous Boot Failed can't allocate child memory -9 0xffffff7"
Kindly help. Multiboot is of no use if I can't flash gapps on secondary OS.
Click to expand...
Click to collapse
It hasn't been updated specifically for the OnePlus One for long now, so too bad.

[Guide] How to decrypt data on Mate 9 (hi3660) [2018-11-01]

Hi .
I'm tired with Huawei's encryption. It's ok with Emui Rom but for AOSP (or other based on it) it's annoying :crying:
So use this guide for remove it definitively
WARNING !!
ALL YOUR DATA WILL BE DELETED ,SO BACKUP ALL YOUR PICTURES,VIDEO ETC ... TO YOUR PC OR IN EXT SDCARD
Download and copy in sdcard,not internal ,in attached files my :
- Huawei_remove_encyption_data
- Custom TWRP 3.2.3 recovery
rename my twrp_recovery.img.zip to twrp_recovery.img (remove .zip at the end, it's for upload this files into xda (size files))
or
in Android File Host
Download
HERE
PROGRESS :
Boot into fastboot, and Run
"fastboot -w", to wipe crypto
without rebooting flash included patched TWRP (fastboot flash recovery_ramdisk twrp_recovery.img)
Boot into TWRP, then Wipe internal storage, Wipe > Format Data then write "Yes"
Then flash my Huawei_remove_encyption_data script
reboot into TWRP recovery
Now you could continue to flash AOSP/LOS/CUSTOMS ROMs
And we're Done
Changelogs
2018-11-01
* Add new Android File Host Download link
* Add new MINADBD
* Fix selinux denial with stock kernel
Click to expand...
Click to collapse
Note:
If you want to come back to stock EMUI/Encryption data ,reboot into erecovery and use "download last firmware and recovery" and follow the steps
Enjoy :good:
Creadits:
@AL_IRAQI for the inspiration of this guide

Updated 2018-10-24
* Update script with busybox mount program , more stable as previous script
* Update TWRP with Static Busybox ,last teamwin stuff and some other fix

This is on a good path, thank you brother for your work ...:good:

I tried on my VTR-L29C432 (P10) and it worked!
Now I can flash files from my internal storage.
It works on EMUI and custom roms, even android 9. @micky387 Thank you so much for this tool bro

It just isnt working for me.
it installs twrp, but it fails with the wiping
when i try to format data it says cannot mount storage
acant install any rom either.
also refuses to download latest update in emui recovery
man, does huawei suck!

caniranges said:
It just isnt working for me.
it installs twrp, but it fails with the wiping
when i try to format data it says cannot mount storage
acant install any rom either.
also refuses to download latest update in emui recovery
man, does huawei suck!
Click to expand...
Click to collapse
Which device ,mate 9 ?
download again and try the new files. I have updated my twrp and script for more support

After flashing custom ROM, my data partition was encrypted.

Need some help here.
I have a mate 9 US variant. I was directed here from [Recovery][10-09-2018][3.2.3-0] TWRP for the Huawei Mate 9 (hi3660) (https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796).
1) Successfully installed TWRP 3.2.3.
2) Backed up my /system partiton using TWRP to my ext SD card.
3) Boot into fastboot and run "fastboot -w". It shows
"
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.078s]
finished. total time: 0.078s
"
Not sure it is successful or not.
4) No rebooting and flash TWRP 3.2.3 again.
5) reboot to TWRP successfully, but not able to format data. It shows "failed to mount '/data'"
---------------------------------------------------------------------------------------------------------------------------------------------
Just found these two post have different TWRP files. The version numbers are the same, but file sizes are not. Is successful with the TWRP posted in this page.

@micky387 Hi!
One Question, the fstab file was taken from Honor View 10 forum or you modded that? Because I the one that I'm using was taken from there.
First I did the wipes on Twrp but my internal storage wasn't recognized when the phone booted, so I had to wipe using stock recovery and it worked, now I can use my internal memory on Twrp.

Hi guys.
OP updated
* Update script with busybox mount program , more stable as previous script
* Update TWRP with Static Busybox ,last teamwin stuff and some other fix
Click to expand...
Click to collapse

soft-touch said:
After flashing custom ROM, my data partition was encrypted.
Click to expand...
Click to collapse
Try with new stuff.
swith to busybox for more device variant support
huhtan said:
Need some help here.
I have a mate 9 US variant. I was directed here from [Recovery][10-09-2018][3.2.3-0] TWRP for the Huawei Mate 9 (hi3660) (https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796).
1) Successfully installed TWRP 3.2.3.
2) Backed up my /system partiton using TWRP to my ext SD card.
3) Boot into fastboot and run "fastboot -w". It shows
"
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.078s]
finished. total time: 0.078s
"
Not sure it is successful or not.
4) No rebooting and flash TWRP 3.2.3 again.
5) reboot to TWRP successfully, but not able to format data. It shows "failed to mount '/data'"
---------------------------------------------------------------------------------------------------------------------------------------------
Just found these two post have different TWRP files. The version numbers are the same, but file sizes are not. Is successful with the TWRP posted in this page.
Click to expand...
Click to collapse
Same, use new script and twrp in OP and report
sfoot13 said:
@micky387 Hi!
One Question, the fstab file was taken from Honor View 10 forum or you modded that? Because I the one that I'm using was taken from there.
First I did the wipes on Twrp but my internal storage wasn't recognized when the phone booted, so I had to wipe using stock recovery and it worked, now I can use my internal memory on Twrp.
Click to expand...
Click to collapse
Hi,
first, fstab is from Mate 9. The only diff with View 10 is this line.
Code:
/devices/platform/e7f00000.hifi_usb/* auto auto defaults voldmanaged=usbotg:auto
you can add it in my fstab if you want for your device
for the second question ,I have already noted that for me, just restart in recovery mode to fix this
With TWRP do you use ?

micky387 said:
Hi,
first, fstab is from Mate 9. The only diff with View 10 is this line.
you can add it in my fstab if you want for your device
for the second question ,I have already noted that for me, just restart in recovery mode to fix this
With TWRP do you use ?
Click to expand...
Click to collapse
Thanks for the answer
On my last testing, I flashed your fstab without problems and wiped using stock.
To flash your zip, first I need to use this twrp https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 it boots even if the phone is encrypted but you need a sdcard, after the decrypt is done, I replace it with this twrp https://marijuana.ddo.jp/cm/recovery

sfoot13 said:
Thanks for the answer
On my last testing, I flashed your fstab without problems and wiped using stock.
To flash your zip, first I need to use this twrp https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 it boots even if the phone is encrypted but you need a sdcard, after the decrypt is done, I replace it with this twrp https://marijuana.ddo.jp/cm/recovery
Click to expand...
Click to collapse
Thanks do you have a xda link of the second TWRP ?
It's just to see if it use too a symlinks script for our partitions

micky387 said:
Thanks do you have a xda link of the second TWRP ?
It's just to see if it use too a symlinks script for our partitions
Click to expand...
Click to collapse
No, I saw the link on this post https://forum.xda-developers.com/showpost.php?p=77262856&postcount=166 but I think @love_marijuana is the dev, because of the splash screen of the twrp :silly: talk to him bro.

OP Updated
2018-11-01
* Add new Android File Host Download link
* Add new MINADBD
* Fix selinux denial with stock kernel
Click to expand...
Click to collapse
We can use all TWRP feature now in Stock kernel.
Because Huawei has removed setenforce permission into kernel , the recovery script (setenforce 0) dont work , so "use" adb and other stuff was blocked by selinux
Fix all selinux denial by this commits

Return to stock emui/encryption
Hello!
I have a mate 9 c432 b370 with LineageOS 16 by micky (but due to stopped development i want to go back, the other treble roms just aren't working that well as rhis one, and I'm having a bit of bad battery life right now)
My question is:
"If you want to come back to stock EMUI/Encryption data ,reboot into erecovery and use "download last firmware and recovery" and follow the steps"
Is this the only way to go back to stock/encryption?
A wipe data or factory reset on emui stock recovery wouldn't work?
I'm asking because i have decrypted a while ago.
The last time i tried to use erecovery it said "no packages available" with an exclamation mark.
I have flashed stock system, kernel, ramdisk and recovery to boot back several times, but this time i have decrypted the internal storage...
Just need confirmation and/or possible solution to this. @micky387
Thanks in advance

hello @micky387
noob question. is it possible to work on a mate 8 debrand(AL10C00) atm im running openkirin omnirom 5.2,
would like to try other gsi roms. to check the most compatible rom..
your reply is very much appriciated
thank you

P10 Lite / WAS-LX1
Works on P10 Lite (WAS-LX1) with a fitting TWRP (I used Darkjokers 3.3.1). Used the zip over ADB sideload, so no external SD needed. Thanks for showing us da wae pal :good:

Hey dudes will this work on mate 8 Oreo ? If soon could you mod it for it ? Thanks

c|nder said:
Hey dudes will this work on mate 8 Oreo ? If soon could you mod it for it ? Thanks
Click to expand...
Click to collapse
If you check by the dates, it was all discussed at the time of EMUI 8/Oreo.
Earlier with Nougat, there was no such problem (TWRP was able to access internal storage).
To the other side, with current EMUI 9.1, Vendor is read-only and proposed modifications will not work

[HELP OXYGEN OS] Can´t install 5.1.5 update or flash in original recovery!!

Hello, I have an OP 5 with unlocked bootloader and i was rooted. So, I'm in 4.5.13, and i'm trying to install 5.1.5 but i need to be unrooted for this.
Somehow when i removed root (magisk) my phone entered in bootloop mode (i think that magisk lost the original boot img). I flashed the stock boot img and the phone booted normally and without root. However i think that some "crumbs" of the magisk or adway stayed in my system or phone partitions and my phone continues to say that he can´t install the OTA. I've already wiped cache and data in the recovery and tried to install with adb sideload but it fails.
I still have my OOS and is working fine, but I can't update... Any ideas?
Do you think that if I do the normal settings > restore factory settings will it work? Or that option will be also damaged?
Should i boot TWRP in fastboot, and try to do a factory reset and then flash 5.1.5?
For your information, i've never flashed anything besides magisk and the attempts to update. The rom is the original as also the recovery. To flash the magisk i always booted twrp connected by usb to my PC.
I apreciate all the help!!

pdalvares said:
I apreciate all the help!!
Click to expand...
Click to collapse
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.

Dirk said:
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.
Click to expand...
Click to collapse
Yo, i already tried it different ways, but thank you :/

pdalvares said:
Yo, i already tried it different ways, but thank you :/
Click to expand...
Click to collapse
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/

Dirk said:
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/
Click to expand...
Click to collapse
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:

pdalvares said:
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:
Click to expand...
Click to collapse
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.

Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
I've made what you said but it gives me the error "Updater process ended with error: 7"

pdalvares said:
I've made what you said but it gives me the error "Updater process ended with error: 7"
Click to expand...
Click to collapse
Which TWRP are you using? It should be the latest Official version, or you could try the latest codeworkx from here:
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Error 7 is a generic error code. The useful information about the error is usually in the body of text.
If you can't get TWRP to play nicely you can use it to format partitions as mentioned before, and then use it to install the stock OOS recovery from the bottom of this page:
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
The stock recovery is an .img, so in the TWRP 'Install' menu you need to select Image instead of Zip at the bottom of the screen. Move the stock recovery .img to Internal Storage and flash it. Reboot into Stock Recovery and flash full OOS zip.

Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!

pdalvares said:
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!
Click to expand...
Click to collapse
Let me know how you get on. :good:

Dirk said:
Let me know how you get on. :good:
Click to expand...
Click to collapse
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
EDIT:
Could it be because the bootloader is unlocked?? Is it safe to lock it like i unlocked it? No problem?

pdalvares said:
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
Click to expand...
Click to collapse
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877

Dirk said:
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Click to expand...
Click to collapse
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "

pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
Are you trying to OTA or full ROM? OTA is not going to work. Only full ROM .zip will get the job done.
Have you considered giving up on OOS for now and just try flashing a Custom ROM from TWRP? I'd recommend Dirty Unicorns Oreo for now until Pie ROMs mature. You can get their ROM from their website.. Should be no issue at all flashing it. Opengapps ARM64, 8.1 Nano is the Gapps i'd recommend.
Wipe in TWRP, Flash Firmware/ROM/Gapps/Magisk. Job done.

pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/

pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
Initial boot can take some time.
I'm at a loss why your phone hates OOS, but it might love Custom ROMs. Give it some thought.

pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes

pdalvares said:
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes
Click to expand...
Click to collapse
Good news! :good:
You can see how resilient OP phones are. You can pretty much always get them back to a working condition. I can only guess but it sounds like you were right. Something was wrong with your Bootloader after the initial problems. Glad you got it sorted.