Related
Hi guys, just sharing my experience with kernels which don't have CWM integrated as default recovery.
Latest versions of Voodoo - 5.x - converts /system to ext4.
The standalone version of ClockworkMod, the one flashed by RomManager, does not support ext4. However, as explained by supercurio himself, the kernel needs to have 3e recovery which allows you to execute the update.zip (standalone ClockworkMod recov.) with wrappers necessary to mount ext4 partitions as ext4. With 2e recovery, partitions are mounted as j4fs, hence bad and failed flashes.
If the kernel has CWM integrated, then all is fine, you can flash without worries.
If you already know this, good for you
While accurate, wrong forum.
MikeyMike01 said:
While accurate, wrong forum.
Click to expand...
Click to collapse
Not wrong at all You have to be into development and flashing to care about CWM and Voodoo
But lets let the mods decide
Hi !
With Vooodoo 5.x, ClockWorkMod support Ext4 both when run from Rom Manager and as the default recovery.
Working scenario :
- Starting a backup from Rom manager
- Restoring a backup from CWM recovery alone
- Installing a sdcard zip from Rom Manager
etc.. 100% compatibility.
Well, there is no non-working scenario, I cannot give you example of them
Notes:
- If you reboot in recovery (adb reboot recovery), you get the Voodoo Red CWM recovery. This one contains the "voodoo lagfix" menu, as a help to configure it.
- If you use CWM from Rom Manager, you get the Green CWM, compiled and updated by Koush.
As precised, both work the same way with Ext4 now. To get this result, I wrote wrappers allowing Ext4 support without the requirement of a modified CWM.
PS, to the OP: I suggest you specify the version for those who are not working.
Every current and final version of Voodoo is
supercurio said:
Hi !
With Vooodoo 5.x, ClockWorkMod support Ext4 both when run from Rom Manager and as the default recovery.
Working scenario :
- Starting a backup from Rom manager
- Restoring a backup from CWM recovery alone
- Installing a sdcard zip from Rom Manager
etc.. 100% compatibility.
Well, there is no non-working scenario, I cannot give you example of them
Notes:
- If you reboot in recovery (adb reboot recovery), you get the Voodoo Red CWM recovery. This one contains the "voodoo lagfix" menu, as a help to configure it.
- If you use CWM from Rom Manager, you get the Green CWM, compiled and updated by Koush.
As precised, both work the same way with Ext4 now. To get this result, I wrote wrappers allowing Ext4 support without the requirement of a modified CWM.
PS, to the OP: I suggest you specify the version for those who are not working.
Every current and final version of Voodoo is
Click to expand...
Click to collapse
OK, my non-working scenario is like this:
I installed Darky's JPU with Voodoo v5.0.2. Installed xcaliburinhand's kernel with Voodoo lagfix 5.0.1. Loaded CWM recovery and tried to install something - no go - and when it worked (i dont know how) my system did not boot.
This happened not once, not twice but 3 times trying to flash things which if flashed from the kernel integrated CWM did not give me any kind of errors or brake my system.
supercurio said:
Notes:
- If you reboot in recovery (adb reboot recovery), you get the Voodoo Red CWM recovery. This one contains the "voodoo lagfix" menu, as a help to configure it.
Click to expand...
Click to collapse
xcaliburhand's kernel has the completely useless 2e recovery.
MikeyMike01 said:
xcaliburhand's kernel has the completely useless 2e recovery.
Click to expand...
Click to collapse
indeed useless, but if supercurio is right, the ClockworkMod recovery that I have on the sdcard should handle the system without issues.
Note: I flashed the recovery few times just to be sure that is not corrupted or whatever.
This is a kernel issue but I get similar results with voodoo disabled. Test for yourself.
Stephenv1971 said:
This is a kernel issue but I get similar results with voodoo disabled. Test for yourself.
Click to expand...
Click to collapse
OK, will do.
That means the ROM dev now has to update to latest CWM in order to write to ext4? I think we are using 2.5.1.0....
I think this is also why some people say that theme mods doesn't stick.
killer23d said:
That means the ROM dev now has to update to latest CWM in order to write to ext4? I think we are using 2.5.1.0....
I think this is also why some people say that theme mods doesn't stick.
Click to expand...
Click to collapse
The situation is like this: xcaliburhand's 2.2.1 kernel might have problems and CWM will not work if the ROM is powered by this kernel. However, if you have a different kernel and you see the same problem, let us know. The thread will remain like it is until someone tries to load standalone CWM and flash something with it on a different kernel.
MikeyMike01 said:
xcaliburhand's kernel has the completely useless 2e recovery.
Click to expand...
Click to collapse
Yes, 2e recovery is a mistake, because it allows you to execute the CWM update.zip alone.
without wrappers, which means it will destroy your Ext4 partitions, mounting them as j4fs.
Voodoo for Froyo come with 3e recovery.
supercurio said:
Yes, 2e recovery is a mistake, because it allows you to execute the CWM update.zip alone.
without wrappers, which means it will destroy your Ext4 partitions, mounting them as j4fs.
Voodoo for Froyo come with 3e recovery.
Click to expand...
Click to collapse
This explains it Editing OP
killer23d said:
That means the ROM dev now has to update to latest CWM in order to write to ext4? I think we are using 2.5.1.0....
I think this is also why some people say that theme mods doesn't stick.
Click to expand...
Click to collapse
For the ROM dev, there is no need to do anything special about recoveries.
Keeping 3e is a better idea because 2e can cause troubles and thanks to default CWM recovery (powerful!) 2e is useless.
Anyway thanks for pointing out this potential issue with non-standard kernels!
I prepare a new Eclair release at the moment
Maybe I should add this kind of checks to prevent anyone executing an CWM update.zip directly, from the 2e recovery menu.
So, basically xcaliburhand has to fix this.
icezar1 said:
This explains it Editing OP
Click to expand...
Click to collapse
Yep For the OP:
only non working scenario is running CWM from a 2e recovery.
But if your Voodoo kernel has CWM built in, you cannot start 2e recovery manually.
MikeyMike01 said:
So, basically xcaliburhand has to fix this.
Click to expand...
Click to collapse
He has 2 options:
- restoring 3e instead of 2e
- insert a built-in CWM.
I'm reachable for help
icezar1 said:
Hi guys, just sharing my experience.
Latest versions of Voodoo converts /system to ext4.
The standalone version of ClockworkMod, the one flashed by RomManager, does not support ext4. However, as explained by supercurio himself, the kernel needs to have 3e recovery which allows you to execute the update.zip (standalone ClockworkMod recov.) with wrappers necessary to mount ext4 partitions as ext4. With 2e recovery, partitions are mounted as j4fs, hence bad and failed flashes.
Click to expand...
Click to collapse
Lol no it does not need 3e recovery.
the wrapper are installed by Voodoo code during the boot.
Only in case of if the kernel doesn't have built-in CWM, 3e is recommended, for Voodoo kernel builders because 2e can allow running direct CWM update.zip - without wrappers -
If the kernel has CWM built-in 2e or 3e don't matter.
for reference, how to use the injector:
https://github.com/project-voodoo/lagfix/tree/stable/voodoo_injector
supercurio said:
Lol no it does not need 3e recovery.
the wrapper are installed by Voodoo code during the boot.
Only in case of if the kernel doesn't have built-in CWM, 3e is recommended, for Voodoo kernel builders because 2e can allow running direct CWM update.zip - without wrappers -
Click to expand...
Click to collapse
Yeah yeah, figured that out still editing the post
Just got my GF a Glacier yesterday and I'm curious.. What filesystem does HTC use on /system /cache /data and /dbdata?
The stock ROM is Froyo (Android 2.2.x), I understand its filesystems are EXT2. Gingerbread (Android 2.3) uses EXT4.
Thanks. Nice to know HTC doesnt stick people with crappy filesystems like Samsung does.
Just a correction, and a clarification.
Correction: I mistyped. Froyo uses EXT3, the journalled version of EXT2. But EXT2/3 are the same when the filesystem is at rest.
Clarification: Should you elect to install a custom ROM, have a care to flash the right version of ClockworkMod Recovery to do your nandroid backups, restores, and ROM installs. CWMR version 2.x is for EXT3 filesystems, and CWMR version 3.x is for EXT4 filesystems, and they are not compatible.
There is an MT4G-unique version of CWM Recivert produces by Option94, our forum mod, which can deal with both EXT3 and EXT4 filesystems correctly. It goes by the name "Version 3.0.0.6" and there are a couple of threads about it in the development subforum. If you are switching back and forth between Froyo and Gingerbread, it is an easier way to go.
Nice. I won't be converting her filesystem because frankly she wont notice . Good bit of knowledge to have though, thanks!
regP said:
Nice. I won't be converting her filesystem because frankly she wont notice . Good bit of knowledge to have though, thanks!
Click to expand...
Click to collapse
The reason they mentioned the different Recovery image for file systems is this. FroYo which is Ext3 will only use the older 2.5.x.x recovery images. IF you want to move to Gingerbread you will have to load a recovery image that handles Ext4 systems, which is Recovery Image 3.0.0.5.
you cannot flash 2.3 ROMs with a 2.5.x.x recovery image, nor can you restore back to a 2.2 ROM using 3.0.0.5.... you end up with a bootloop problem.
Now if you want to do both and not have to worry about the recovery image use 3.0.0.6, which a link can be found in my signature.
neidlinger said:
The reason they mentioned the different Recovery image for file systems is this. FroYo which is Ext3 will only use the older 2.5.x.x recovery images. IF you want to move to Gingerbread you will have to load a recovery image that handles Ext4 systems, which is Recovery Image 3.0.0.5.
you cannot flash 2.3 ROMs with a 2.5.x.x recovery image, nor can you restore back to a 2.2 ROM using 3.0.0.5.... you end up with a bootloop problem.
Now if you want to do both and not have to worry about the recovery image use 3.0.0.6, which a link can be found in my signature.
Click to expand...
Click to collapse
I get you. Don't plan on doing any flashing on that phone. Was just curious as to what the default system was for the 4g. Thanks for all the info it def may come in handy some day.
i tried to flash this stock kernel from here.
whene i flash it via recovery, i get status 7.... i wiped all my partitions to EXT3 with this zip.
im using RCMix3D Runny 1.5, with 4EXT Recovery
thanks for help!
I think you can't use 4ext recovery with ext3 partitions. I might be wron... you should try using cwm recovery if you have already formatted your partitions into ext3.
thanks!
but i still get status 7....
maby zip broken? some one has anothe download?
desidunda said:
I think you can't use 4ext recovery with ext3 partitions. I might be wron... you should try using cwm recovery if you have already formatted your partitions into ext3.
Click to expand...
Click to collapse
You can...
I'm using 4ext recovery and GB Sense 3.0 that is ext3 partitioned.
Can't click your link but have you tried the stock kernel from GB Sense 3.0 thread? Or mayby that was what you linked to? But I'm pretty sure you have to change your partitions to ext3 then which you can do in 4ext recovery.
DubelBoom said:
thanks!
but i still get status 7....
maby zip broken? some one has anothe download?
Click to expand...
Click to collapse
I don't know where you downloaded it from but here is a link try it.
http://www.multiupload.com/W42VMZLFTO
desidunda said:
I don't know where you downloaded it from but here is a link try it.
http://www.multiupload.com/W42VMZLFTO
Click to expand...
Click to collapse
from there i downloaded....
it worked for someone??
i copid the files from this zip, to Unity V9 zip, and i got no erorres
but i get stuck on splash screen..
ClockworkMod Recovery 6.0.3.3with Touch Interface
Download:
https://code.google.com/p/forumber-projects-for-u8800/downloads/detail?name=recovery-clockwork-6.0.3.3-touch-u8800_installable.zip&can=2&q=
Bugs:
No offmode charging
Installation:
Install the zip via any recovery.
ClockworkMod Recovery 6.0.2.8
Download:
http://code.google.com/p/forumber-projects-for-u8800/downloads/detail?name=recovery-clockwork-6.0.2.8-2.6.35.7-u8800.img&can=2&q=
Bugs:
I have not encountered any problems.
ClockworkMod Recovery 5.0.2.8
Download:
http://code.google.com/p/forumber-projects-for-u8800/downloads/detail?name=recovery5.0.2.8-2.6.35.7-u8800.img&can=2&q=
Difference of 5.0.2.7 by genokolar:
-All of framebuffer (graphic) problems are fixed.
-Kernel updated so mount problems are fixed
-Softkey lights are open by default
-USB Mass Stroage faster than older
-ADB working
Bugs:
-It hasn't got any bug
Installation:
Root your phone.
Download the recovery.img down below.
Save it to wherever you want.
Make sure the image name is recovery.img, rename if needed.
Download any root file manager, which can mount and show hidden folders.
Mount /.cust_backup as rw.
Copy and replace recovery.img from SD card to /.cust_backup/image/recovery.img
Thanks to:
Blefish --for graphic.c ,his explanations and help about anything. You are the great man!
Dazzozo --for help about rmt_stroage,and random reboots
stockwell --for recovery.fstab,offmode charge modules etc.
wmi543 --for CyanogenMod vendor tree
Seems great! :good:
Good work.
btw are you going to update TWRP Recovery?
dark_vader said:
Good work.
btw are you going to update TWRP Recovery?
Click to expand...
Click to collapse
The new version is uploading...
Re: [RECOVERY] ClockworkMod Recovery 5.0.2.8
Good stuff, softkeys working (it didn't with 5.0.2.5)
Sent from my Huawei U8800
the sd card cannot be mount. iam the only one?
vlc_marcos said:
the sd card cannot be mount. iam the only one?
Click to expand...
Click to collapse
did you try advanced > reboot recovery ?
ok its working. thanks
Hello.
Just a question i used this recovery and now i want to get back to the old 4.0.0.5 because i have lots of backups that is not supported from 5.0.2.8.
I changed to the old 4.0.0.5 recovery.img but my phone doesnt load the recovery.It stucks at ideos logo.
But when i use the 5.0.2.8 the recovery works fine.
Why is this happening?
snaker12 said:
Hello.
Just a question i used this recovery and now i want to get back to the old 4.0.0.5 because i have lots of backups that is not supported from 5.0.2.8.
I changed to the old 4.0.0.5 recovery.img but my phone doesnt load the recovery.It stucks at ideos logo.
But when i use the 5.0.2.8 the recovery works fine.
Why is this happening?
Click to expand...
Click to collapse
hi there. i presume your problem is related to the recovery itself.
i can be wrong, but i guess that the old recovery 4.0.0.5 is based in the old .32kernel. that's because u cant load it.
If i'm wrong, pls let me know!
snaker12 said:
Hello.
Just a question i used this recovery and now i want to get back to the old 4.0.0.5 because i have lots of backups that is not supported from 5.0.2.8.
I changed to the old 4.0.0.5 recovery.img but my phone doesnt load the recovery.It stucks at ideos logo.
But when i use the 5.0.2.8 the recovery works fine.
Why is this happening?
Click to expand...
Click to collapse
Yes. 4.0.0.5 recovery it's based on 2.2 so if you want use this old recovery you must downgrade to froyo.
Mlopik said:
Yes. 4.0.0.5 recovery it's based on 2.2 so if you want use this old recovery you must downgrade to froyo.
Click to expand...
Click to collapse
Then i must be wrong at the clockwork recovery that i think it was 4.0.0.5.
My old recoverys from Oxygen rom which is 2.3.7 have this structure:
.android_secure.img
cache.img
cust.img
data.img
system.img
This recovery has this structure:
.android_secure.vfat.tar
boot.vfat.tar
cache.ext4.tar
data.ext4.tar
system.ext4.tar
So i assume this is the reason that when i try to recover to my old recoverys the rom reboots freezes and all the wierd stuff.
Can you please tell me which recovery has the old stucture of recovery that i mensioned before and that supports 2.3.7 which is my oxygen backups.
Thanks
snaker12 said:
Then i must be wrong at the clockwork recovery that i think it was 4.0.0.5.
My old recoverys from Oxygen rom which is 2.3.7 have this structure:
.android_secure.img
cache.img
cust.img
data.img
system.img
This recovery has this structure:
.android_secure.vfat.tar
boot.vfat.tar
cache.ext4.tar
data.ext4.tar
system.ext4.tar
So i assume this is the reason that when i try to recover to my old recoverys the rom reboots freezes and all the wierd stuff.
Can you please tell me which recovery has the old stucture of recovery that i mensioned before and that supports 2.3.7 which is my oxygen backups.
Thanks
Click to expand...
Click to collapse
5.0.2.7 ,5.0.2.8 and TWRP recoveries are based on 404020 baseband and 2.6.35.7 kernel. Older recoveries are based on 129005 baseband and 2.6.32.9 kernel.
Clockworkmod switched nandroid backup file type to .tar since CWM 5.x.x.x, CWM 4.0.0.5 uses .img file type for backups.
So which CWM was released after 4.0.0.5 and before 5.x.x.x ?
Because if Mlopik said 4.0.0.5 is for froyo 2.2 then which CWM is for 2.3.5 / 2.3.7 and supports .img files?
snaker12 said:
So which CWM was released after 4.0.0.5 and before 5.x.x.x ?
Because if Mlopik said 4.0.0.5 is for froyo 2.2 then which CWM is for 2.3.5 / 2.3.7 and supports .img files?
Click to expand...
Click to collapse
5.5.0.4 and 5.0.2.7 for GB?
snaker12 said:
So which CWM was released after 4.0.0.5 and before 5.x.x.x ?
Because if Mlopik said 4.0.0.5 is for froyo 2.2 then which CWM is for 2.3.5 / 2.3.7 and supports .img files?
Click to expand...
Click to collapse
All of CWM versions supports all of android versions. Mlopik want to say 5.0.2.6 and older CWM versions are supports only 129005 baseband and 2.6.32.9 kernel.
Which baseband or kernel version do you use?
ClockworkMod Recovery 6.0.2.8 added.
Enjoy
Gonna "flash" right now. What are differences?
Thanks dude :good:
Re: [RECOVERY] ClockworkMod Recovery | 5.0.2.8 & 6.0.2.8 |
No changelog?
★Sent From My U8800★
don't see any diference at all between 5.0.2.8 and 5.0.2.7....
Where are they exactly?
@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.