[solved] Cant update to new CM rom? - Samsung Galaxy Nexus

Hi, I got a notice on CM updater that there was an 10.2 update so I dloaded it and let CM do its thing. Upon reboot everything seemed a little squirrley so I decided I was just going to do a clean flash.
Booted into recovery, wiped everything, but now every rom I try to flash gives me "set metadata recursive: some changes failed. Error executing updater binary n zip [path]" no matter what I try?
Any clue as to what is going on here?
edit: I can get in and out of recovery. I can push via adb. Also wiped via fastboot -w.
thx
EDIT: ended up getting everything back to stock and starting over. Thanks for looking.

Try updating your recovery (CWM/TWRP) to the latest.
Sent from Samsung Galaxy S Relay 4G @ CM11

updated to latest TWRP.
I'm getting errors about it being unable to mount /sdcard when I attempt to flash...

Ok it turned out I installed an older version of TWRP.
Flashed 2.6.3.2
When I attempt to flash a new rom I get this:
updating partition details.......
Full SELinux support is present
E: Failed to decrypt data
Formatting Cache using make_ext4fs fucntion.
Updating partition details...
E: Failed to wipe dalvik
Updating partition details...
Error flashing zip /sdcard/cm-11 nighty blah blah
Updating partition details...
FAILED
Click to expand...
Click to collapse
Am I screwed at this point? Do I need to revert everything back to original somehow? Kind of lost here at the moment.
thx

Related

xperia S cache format failed on block 13

Hello all,
First some background
as you can tell i have an xperia s. I had initially rooted it in .45, installed CWM, installed .55 system and CWM again, and had a perfectly healthy tool on my hands. A week ago i realized it had suddenly started to eat up the battery in half a day. I uninstalled everything i could think of, and nothing happened. So i though of going back to a previous CWM backup.
That proved impossible since the backup sequence always stopped at a formatting error. After a dozen attempts i lost my patience and used flashtool to install and root .45. Then CWM, then OTA to .55, and then CWM again (it was lost after OTA update to .55).
Took me about a day to put everything back.
That was yesterday.
Today i tried to install the camera mod from xperia V (had it before and truly the focusing is faster, cannot vouch for anything else though)
And there it was:
Instructions for installing the zip require to wipe cache first.
Through CWM when i tried to wipe cache, both ways available, i always get the same error
make_extf4fs failed on /dev/block/mmcblk0p13
I have seen that before on my phone but everything works OK in normal mode. Only time problems arise is when i need CWM...
I have also seen it reported in xda but nobody posted a solution.
Any thoughts?
I cannot take it back as defective either, because it works ok:silly:
I decided to take it a step further.
Went into CWM and chose wipe data/factory reset.
Here is the log
CWM recovery for 2012 Xperia V2
by kenjidct
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
--Wiping data...
Formatting /data...
e: format_volume: make_extf4fs failed on /dev/block/mmcblk0p14
formatting /cache
formatting /sd-ext
formatting /sdcard/.android_secure
data wipe complete
I tried it again right after that and it completed with no errors.
THen tried to format cache and -surprise- no errors...
So i went on to restore my previous backup.
checking MD5 sums
Restoring system
restoring data
e: format_volume make_extf4fs failed on /dev/block/mmcblk0p14
Error while formatting data
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
Tried to format data after that and again error at block 14
WTF??????????????????
AGAIN???????????
What do you make of this?
Guys. nobody knows, or nobody has the same errors?
I have exactly same issues.. i am running .45 rooted firmware o my SXS.. help us guys
sagardrokr said:
I have exactly same issues.. i am running .45 rooted firmware o my SXS.. help us guys
Click to expand...
Click to collapse
can u connect it to fastboot?
if u yes, from fastboot: fastboot erase cache. fastboot format cache. i think that flashing ftf full wipe can fix that too.
I am having this issue even after multiple(2-3) full wipes.
Let me be clear about that.
First time i encountered the situation i though it was just a glitch. So i went all out and erased everything. Reinstalled .45 , rooted, then OTA-ed to .55, then installed CWM (i actually installed it first at .45 but during the update to .55 it was lost, so i installed it again.) Problem insisted , so i re-did it all a couple of times until i run out of time to keep installing everything!!!
Now, as for the "manual" format you are referring to. How do we do that?
Can we do that through flash tool?
I was thinking of connecting the phone to the flashtool in flashmode and choosing only wipe cache.
But in order to do that i first have to choose an ftf and i was worried that i might erase everything again. I absolutely have no time to be installing everything again...!!!
m1st3r1 said:
can u connect it to fastboot?
if u yes, from fastboot: fastboot erase cache. fastboot format cache. i think that flashing ftf full wipe can fix that too.
Click to expand...
Click to collapse
I never tried but i think i can connect it to fastboot. But i am not much aware of fastboot process. SO i am hesitating to flash it..Though i'll give a try n will let you know the results.
sagardrokr said:
I never tried but i think i can connect it to fastboot. But i am not much aware of fastboot process. SO i am hesitating to flash it..Though i'll give a try n will let you know the results.
Click to expand...
Click to collapse
Don't worry my friend. The phone does everything it is supposed to do.
I have tested it as hard as i can but no error pops up during any operations.
Just when you format cache through CWM
schumifer1 said:
Don't worry my friend. The phone does everything it is supposed to do.
I have tested it as hard as i can but no error pops up during any operations.
Just when you format cache through CWM
Click to expand...
Click to collapse
DId you try the fastboot method?? Any success to pass through the errors?? We cant even install .55 firmware because of those errors..
schumifer1 said:
I decided to take it a step further.
Went into CWM and chose wipe data/factory reset.
Here is the log
CWM recovery for 2012 Xperia V2
by kenjidct
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
--Wiping data...
Formatting /data...
e: format_volume: make_extf4fs failed on /dev/block/mmcblk0p14
formatting /cache
formatting /sd-ext
formatting /sdcard/.android_secure
data wipe complete
I tried it again right after that and it completed with no errors.
THen tried to format cache and -surprise- no errors...
So i went on to restore my previous backup.
checking MD5 sums
Restoring system
restoring data
e: format_volume make_extf4fs failed on /dev/block/mmcblk0p14
Error while formatting data
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
Tried to format data after that and again error at block 14
WTF??????????????????
AGAIN???????????
What do you make of this?
Click to expand...
Click to collapse
Same problems here. error at block 13. Is there any fix yet? TIA
edit: So block 12 is for /system and block 13 for /cache I think and block 14 is for /data or sdcard. errors on all of that.
edit again today: Found the fix HERE. by just installing via fastboot ics17.elf (Advance Stock ICS Kernel)
I have the same errors again and again. Now each time i want to change the rom I have to flash Sony .45 rom, upgrade to .55 then root and flash CWM. It's either that or get stuck in à bootloop.
I've sent full error log on another thread.
Sent from my LT26i using xda app-developers app
silvershiver0323 said:
edit again today: Found the fix HERE. by just installing via fastboot ics17.elf (Advance Stock ICS Kernel)
Click to expand...
Click to collapse
Would be great but kernel flashing is for unlocked bootloader only. Mine is locked.
Sent from my LT26i using xda app-developers app
Lodotux said:
Would be great but kernel flashing is for unlocked bootloader only. Mine is locked.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
That's true. My bootloader is locked as well
isn't there way to track the problem and see what causes theses errors. apprently there aret terribly specific to some phones or some roms, stock or custom.
there should be a way to make a log of what's going on and have a dev help us with this.
here's the link i posted my error log with cwm :
http://forum.xda-developers.com/showpost.php?p=40564226&postcount=1445
Lodotux said:
isn't there way to track the problem and see what causes theses errors. apprently there aret terribly specific to some phones or some roms, stock or custom.
there should be a way to make a log of what's going on and have a dev help us with this.
here's the link i posted my error log with cwm :
http://forum.xda-developers.com/showpost.php?p=40564226&postcount=1445
Click to expand...
Click to collapse
According to Arakmar, the CWM formatting issue was fixed by updating the MMC storage driver in the kernel. As far as I know, drivers are a part of the kernel source which is then compiled to give us the zImage. Compiled zImage+ramdisk=custom kernel
As custom zImage cannot be installed on locked bootloader, this method won't work. There must be some other workaround to this problem..
abcdjdj said:
According to Arakmar, the CWM formatting issue was fixed by updating the MMC storage driver in the kernel. As far as I know, drivers are a part of the kernel source which is then compiled to give us the zImage. Compiled zImage+ramdisk=custom kernel
As custom zImage cannot be installed on locked bootloader, this method won't work. There must be some other workaround to this problem..
Click to expand...
Click to collapse
that's this workaround we're trying to find. i've been told that a recent install of busybox should fix the problem but AFAIK it does'nt work on my phone.
Edit : problem is still here. I've tried to change the rom i'm using today, first, by flashing CWM v2, but get the same errors.
Had to flash .45 firmware, upgrade to .55 by sony upgrade, root, flash CWM and then wipe and install rom.
help
I'm also having the same issue
B4 my phone was fine
But after my phone had microphone issue.and Sony service center said,they
Had 2 change the motherboard
Now with new board,I had that 'cant mount' cwm issue
So please help me fix this
I cant use nandroid backup.cant flash...
Tried different Rom except. 45
Plz help...this is a serious issue 4 me...seen different thread,,, but no sol.
Locked downloader here
I had those formatting errors sometimes, too. For me, it was solved by formatting /sdcard (first backing it up), after that, I could format other areas, too.
Anime13 said:
I'm also having the same issue
B4 my phone was fine
But after my phone had microphone issue.and Sony service center said,they
Had 2 change the motherboard
Now with new board,I had that 'cant mount' cwm issue
So please help me fix this
I cant use nandroid backup.cant flash...
Tried different Rom except. 45
Plz help...this is a serious issue 4 me...seen different thread,,, but no sol.
Locked downloader here
Click to expand...
Click to collapse
Same for me too. My XS also needed a motherboard replacement. For everyone, if possible then just unlock your boot loader and flash a kernel in which this bug has been fixed. Hopefully in the JB update Sony will update the mmc driver.
Sent from my LT26i using xda app-developers app
Sliverer said:
I had those formatting errors sometimes, too. For me, it was solved by formatting /sdcard (first backing it up), after that, I could format other areas, too.
Click to expand...
Click to collapse
Deleting 20 giga and restoring it is certainly not my idea of a quick backup and restore .
For the time it would take to copy 20 giga back and forth i could have installed everything again by hand..
Good info though.
I have noticed that formatting /data also lets us use it without the block errors

[Q] Messed up somewhere along the line...

Tried to flash my AT&T Samsung Galaxy SIII to CM10.1.3-RC2-d2att.zip
(along with gapps-jb-20130813-signed.zip) using TWRP v2.6.1.0
Messed up when I... deleted everything of my phone while wiping.
No more restore points, no rom to load, no gapps. Nothing.
Used a friends SD card and moved the files over to try on the TWRP left on my phone & end up with
set_perm: some changes failed
E: Error executing updater binary in zip '/extern
Error flashing zip '/external_sd/New folder/cm1
Updating partition details
Failed
tl;dr had everything ready to flash my rom, ended up wiping everything. Left with a useless hunk of a phone doing nothing but TWRP :crying:
I would suggest you install stock ROM through Odin.
Here is the link with everything needed
http://forum.xda-developers.com/showthread.php?p=39152518
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Corrupted /data partition? TWRP 2.6.3

So I wanted to install a new ROM to my SM-P600. I had a CryogenMod ROM installed and wanted to go to Hyperdrive. I reboot to recovery and do the Factory Reset in TWRP. Afterward I go install the Hyperdrive ROM. However I notice that i'm getting the message that TWRP is "unable to mount /data" in the logs. The installation of Hyperdrive seems fine but I never boots.
How do I go about repairing the /data partition? I have adb and odin installed and working.
One thing I tried was going in to adb shell but I get this error when I try "could not load library "libc.so" needed by /sbin/sh". :crying:
Thank you for your help.
Gasaraki- said:
So I wanted to install a new ROM to my SM-P600. I had a CryogenMod ROM installed and wanted to go to Hyperdrive. I reboot to recovery and do the Factory Reset in TWRP. Afterward I go install the Hyperdrive ROM. However I notice that i'm getting the message that TWRP is "unable to mount /data" in the logs. The installation of Hyperdrive seems fine but I never boots.
How do I go about repairing the /data partition? I have adb and odin installed and working.
One thing I tried was going in to adb shell but I get this error when I try "could not load library "libc.so" needed by /sbin/sh". :crying:
Thank you for your help.
Click to expand...
Click to collapse
have you had any luck with your corrupt /data partition? i spent a couple weeks it seemed on my /efs corruption & it just needed to be remounted. i had to use CWM/PHILZ for adb commands. i know TWRP can do it but i had better luck with cwm + i was able to backup my /efs with cwm. if you are still stuck give me a shout
good luck
mikmock said:
have you had any luck with your corrupt /data partition? i spent a couple weeks it seemed on my /efs corruption & it just needed to be remounted. i had to use CWM/PHILZ for adb commands. i know TWRP can do it but i had better luck with cwm + i was able to backup my /efs with cwm. if you are still stuck give me a shout
good luck
Click to expand...
Click to collapse
What is your process?

Twrp bootloop

Hello,
i just unlocked bootloader and installed twrp and it all went fine..
until i wanted to fully wipe my device, i did this via twrp.
after 20Minuts, nothing happend, the bar was still white and gray (not even a little bit blue)
and it kept stuck on ''twrp formatting data using make_ext4fs function''.
i knew this wasn't a good idea, but i decided to turn off my phone,
and now, everytime when i turn it on on the normal way it just redirrects me to TeamWin in a bootloop.
even if i want to go to recovery mode i keep stuck in that bootloop, so there is nothing i can do right now, i only can stick at Fastboot Mode but nothing else,
Is there any way to fix this problem?
Using ASUS ZENFONE 2 551ML
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
TheSSJ said:
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
Click to expand...
Click to collapse
How to he flash stock rom by twrp?
Download and flash this via twrp http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Make sure you flash Supersu before you flash the rom.
mr_gourav2000 said:
How to he flash stock rom by twrp?
Click to expand...
Click to collapse
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
TheSSJ said:
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
Click to expand...
Click to collapse
but i cant use twrp on my phone because its stuck in bootloop, or what do you mean? (english not my main language)
please give me some proper step by step instructions, i would really apreciate that!
thanks anyway your awesome!
Man, I misread your post, sorry...I thought you could boot only into twrp
If you still have fastboot, why not flashing twrp 2.8.x.x?
Code:
Fastboot flash recovery nameofrecovery.img
Fastboot reboot recovery
Otherwise you could flash stock system with this guide: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
It's a lot to read
wow, that is something really helpfull, there is still hope to revive my phone
i'll let you know how it turnt out xd
thanks alot!!
i fixed recovery mode, so thats already one step further. Oefff @TheSSJ thanks for the help.
But now i get some other problems, when i try to wipe my phone i get the error like ''unable to mount /data'' and ''unable to wipe dalvik''
and all other kinds of these errors, i get the same problem when i was installing rom. isn't there anything or a way to fully wipe all this **** so i can install a fresh rom.
i flashed custom rom and this is error log i get. its all full written down.
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
Seems you don't have a WW image installed, do you have a CN Software? Then you need another Software of course
what do you mean with ww & cn software?
sorry but im new in this.. but im really interested so can you please explain a little bit?
how can i get this other software! thanks!!!
Where did you buy your Phone? what does the packaging state? WW, CN, TW, etc? These 2 letters must be written in uppercase somewhere, then we will know which software to flash, there is a check where your phone's software is compared to the zip you are trying to flash:
assert failed: getprop ("ro.build.asus.sku") == ''WW''
Which TWRP did you flash?
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
colldor200 said:
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
Click to expand...
Click to collapse
There you go: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-CN-2.20.40.159-user.zip
I think flashing will still fail though...but pls try first,maybe it'll work
i tryed it, i get the same error :/
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there ?
colldor200 said:
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there
Click to expand...
Click to collapse
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
Click to expand...
Click to collapse
sorry for the kinda late answer, but yes i followed your instructions, and it works completely, after cm13 i also immediately installed gapps.
i skipped xaosp im fine with cm13
Thanks alot @TheSSJ for all the help my phone is fully fixed now and even working faster then before its like super fast.
thanks again your great!

Cannot Install Any Custom Rom

I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?
I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data
prospektus said:
I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data
Click to expand...
Click to collapse
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?
thrustaxehandle said:
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?
Click to expand...
Click to collapse
yes.. delete internal memory. rom board. format data.
thrustaxehandle said:
I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?
Click to expand...
Click to collapse
You need to upgrade to a higher version for twrp. 3.2.2
prospektus said:
yes.. delete internal memory. rom board. format data.
Click to expand...
Click to collapse
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
esiv129 said:
You need to upgrade to a higher version for twrp. 3.2.2
Click to expand...
Click to collapse
I'm already using TWRP version 3.2.3
thrustaxehandle said:
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
I'm already using TWRP version 3.2.3
Click to expand...
Click to collapse
try again unlock
prospektus said:
try again unlock
Click to expand...
Click to collapse
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.
thrustaxehandle said:
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.
Click to expand...
Click to collapse
When you get the mount error, come to the home page and get to the mount. speak enable all options enable all options. speak restart recovery restart recovery. make format data
Not sure if the link is forbidden? I can't tell you sorry. https://www.youtube.com/watch?v=dzrWkjOfndA&t=501s
I have read replies and everyone is sharing his bit of suggestions, here are mine
1. boot redwolf as FASTBOOT BOOT recovery.img - (if you arent already)
2. change file type of /data partition to-from (xFat to ext4) and wipe all partitions (internal storage can be skipped)
3. instead of linage15.1 same package, try downloading some other custom rom, i recomend DotOS2.5 or Crdroid4.6.2
4. uncheck enforce md5 bla bla while flashing zip.
i hope you will succeed

Categories

Resources