Honorable forum members,
i can't explain my problem more detailed than this and attached logs and screenshots
I am having a problem with my redmi 1s since 4 days (reporting daily to everybody and every thread i know, Now i came to some conclusion *from my point of view*) i.e., System partition size reduced ( due to "My fault" of trying to expand system storage). Now i can't flash any custom rom on my phone. (Except CM11). I'm getting an error, i.e.,
1. strucks at - "Patching system image unconditionally"
2. and some times it gives me an error "E/system unable mount" and breaks operation here.
I was using CM14.1 official rom till 12th of this month ( So no need to doubt about proper installing of custom rom). As i'm unable to install any custom rom on my phone (tried CM12,13,14,14.1, RR, AICP). Then i tried MIUI. Surprisingly I can install MIUI from recovery (works well) but not from fastboot (by fastboot, after installation strucks at Mi Logo, wiping cache and dalvik cache doesn't work too). ***Another big wonder is that i'm able to install CM11 (works well but not used gapps)***. I think my phone no longer upgrades from Kitkat. Is it true?
Then after several research and several suggestions from some honorable forum members i found that (may be) the problem is with system partition. i.e., My system partition size decreased. It was my fault. I tried to increase my system partition to install aroma gapps (in the need of OK Google voice recognition from any screen and due to some google apps were creating a lot of cache) using a thread on increasing system partition size from our forum (not to specify). Then i realized that i'm not the one who can modify anything on somebody Else's rom- as after receiving a update, it took one after another all the google apps from me.
Then i used revert back flash file from the same thread, but it took something extra along with my some of my phones original system partition size. Tried restoring backup but not worked.
While installing custom rom it strucks at " patching system image unconditionally" (waited every time at least an hour), as i'm not being able to do anything, so i restart my phone. Then when i try again it gives me an error "E/System unable to mount". Then if i try to wipe or resize or repair nothing works gives same error. But if i format using f2fs and then again using ext4, then i can mount system partition in MOUNT in twrp (also tried Philz recovery and CM recovery- same issue). After Mounting when i try to install again it strucks at " patching system image unconditionally". So same cycle continues. But when i try to insatll MIUI or CM11 it works fine -after mounting system partiton ( not even takes command i.e., " patching system image unconditionally" in terminal).
Also i tried to flash the rom using adb sideload strucks at 45%, checked the rom file whether corrupted by extracting and for exact rom redownloaded. But there is no improvement.
Maybe Because of this I'm not being able to flash any custom rom on my device anymore. I've took some recovery log files and some screenshots from recovery of my phone. Here below i'm attaching them.
Finally i would like to inform you that
i) i'm using latest recovery- twrp 3.0.2-1,
ii)and latest firmware- v8.1.2.0. (used whichever firmware required for every rom).
iii) Now i'm using global stable MIUI v8.1.2.0
So now i request you all to please help me in installing a custom rom on my Redmi 1s.
I have updated the tutorial with the solution for your problem follow this link
http://forum.xda-developers.com/redmi-1s/general/tut-repartition-redmi-1s-to-increase-t3506904
Related
Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
SinusStudios said:
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
Click to expand...
Click to collapse
I don't know much, but I am surprised that flashing twrp 3 causes that problem. What method are you using? Try using Rashr to flash twrp 3 img, then try to boot to recovery. If vol up doesn't work, try vol down, (that's what works for me). Somehow I don't think you'll be able to just remove those things from the ROM and have it flash fine. Your better chance is to get twrp flashed, then figure out the F2FS, etc. Also, there are custom kernels for stock-based roms, and don't forget that twrp 3 is not official on Z1compact, so read threads thoroughly to make sure what you're trying to do is supported. I know many of us have twrp 3 on our phones, so I would look more into that.
Hi,
I had the same issues and maybe this helps.
- install your rom and go into dual recovery and choose twrp
- in twrp go to install and choose "IMG" and not "ZIP"
- you can now install the new twrp version via install !
Maybe you should not flash that ROM because it seems to contain malware. Have a look into the thread.
[Solved] I flashed Redwolf recovery and could wipe/format data.
Hello,
TL/DR : stuck in recovery due to filesystem issue, cannot format data. How can I solve this ? should I follow this thread [LENOVO P2] Fastboot Files Of Every Stock Firmware (fastboot flash system systemchunk0.img bla bla bla ??)
Maybe it is a hardware issue due to a fall of my phone.
How can I test the storage from adb or recovery ?
Thanks a lot.
Here is the story :
My phone fell and broke screen (LCD broken too - screen was black), it was on stock.
I changed the screen tonight.
Everything seems to work good, but I found that my phone had some little freezes : irresponsive for 1 or 2 seconds when trying to show notifications for eg.
(It is not the digitizer/multitouch which I tested)
I already applied a year ago to OEM unlock.
I followed Lineage OS guide closely to flash TWRP.
(No issue except one or two reboot with stock rom that reinstalled lenovo recovery right after flashing twrp recovery)
When flashing a rom and gapps I saw errors where /data would not mount.
When rebooting I get a message about encryption.
I did not encrypt my phone... (well I think) - I did indicate that my Pin code was needed to boot when on stock though.
Using Wipe Repair option, I changed file system of /data to ext4 - it worked, now I can mount /data ... but I can't wipe :
mkfs.f2fs -t0 -r blabla
gives this "ERROR : 1
unable to wipe Data.
unable to format to remove encryption"
what should I do next ?
thanks
Check my reply: https://forum.xda-developers.com/showpost.php?p=78892562&postcount=7
hey ho
so i have been reading several guides here and i recently posted in some of the threads but i think maybe it'll be clearer for you if i go through the steps i've taken. My goal is a non MIUI - rom without all the garbage, plus i want the option of expanded display or whatever it's called to hide the statusbar and i also want a rom with built in dark theme for the menus (settings for example)
what i did
redid EVERTYING, from scratch, I.E. (TWRP was erased)Downloaded: nitrogen_global_images_V10.0.1.0.OEDMIFH_20181012.0000.00_8.1_global_159a03b105
i then flashed it with MiFlashSetup.msi (previously before this whole entire debacle i had miui_MIMAX3Global_V10.2.1.0.PEDMIXM_a9972483fb_9.0.zip)
i installed TWRP with TOOL_ALL_IN_ONE_1.0.9.4-NO-INSTALLER
i booted into TWRP
Chose to flash DotOS-v3.0-arm64_aonly-vanilla-20190310.img and it then proceeded to ask what partition to flash, i chose system.
i then tried installing open_gapps-arm64-9.0-pico-20190327.zip and it said something about insufficient space and or / failed to mount partitions so i mounted vendor and system partitions and tried again, didn't help. so i just rebooted and it is now in the boot animation for DotOS and just.... spinning it's wheels so to speak...
p.s. before i did step 1 as extreme as that was when i tried going into twrp it asked me to decrypt using a password, the password should be the one i chose at setup, in my case i chose PIN and that password was never accepted as the correct password in TWRP so i could never show the system partition, it was listed as 0mb.
premier69 said:
hey ho
so i have been reading several guides here and i recently posted in some of the threads but i think maybe it'll be clearer for you if i go through the steps i've taken. My goal is a non MIUI - rom without all the garbage, plus i want the option of expanded display or whatever it's called to hide the statusbar and i also want a rom with built in dark theme for the menus (settings for example)
what i did
redid EVERTYING, from scratch, I.E. (TWRP was erased)Downloaded: nitrogen_global_images_V10.0.1.0.OEDMIFH_20181012.0000.00_8.1_global_159a03b105
i then flashed it with MiFlashSetup.msi (previously before this whole entire debacle i had miui_MIMAX3Global_V10.2.1.0.PEDMIXM_a9972483fb_9.0.zip)
i installed TWRP with TOOL_ALL_IN_ONE_1.0.9.4-NO-INSTALLER
i booted into TWRP
Chose to flash DotOS-v3.0-arm64_aonly-vanilla-20190310.img and it then proceeded to ask what partition to flash, i chose system.
i then tried installing open_gapps-arm64-9.0-pico-20190327.zip and it said something about insufficient space and or / failed to mount partitions so i mounted vendor and system partitions and tried again, didn't help. so i just rebooted and it is now in the boot animation for DotOS and just.... spinning it's wheels so to speak...
p.s. before i did step 1 as extreme as that was when i tried going into twrp it asked me to decrypt using a password, the password should be the one i chose at setup, in my case i chose PIN and that password was never accepted as the correct password in TWRP so i could never show the system partition, it was listed as 0mb.
Click to expand...
Click to collapse
To avoid this gapless error when installing gapps, first boot the GSI that you have installed, then go back to twrp and install the gapps. In my opinion, xiaomi.eu roms are better as a basis for GSI's, even because I've never been able to start a GSI using an official xiaomi rom.
The main thing is that your data partition is encrypted and you will need to format the data partition.
This may help you - https://forum.xda-developers.com/mi-max-3/how-to/b-guide-to-fake-rom-unlocked-bootloader-t3846891 (where appears china rom, china dev ... can be replaced by global rom - this process has to be done before installing the GSI of your choice and take care of the ARB.).
Germano1980 said:
To avoid this gapless error when installing gapps, first boot the GSI that you have installed, then go back to twrp and install the gapps. In my opinion, xiaomi.eu roms are better as a basis for GSI's, even because I've never been able to start a GSI using an official xiaomi rom.
The main thing is that your data partition is encrypted and you will need to format the data partition.
This may help you - https://forum.xda-developers.com/mi-max-3/how-to/b-guide-to-fake-rom-unlocked-bootloader-t3846891 (where appears china rom, china dev ... can be replaced by global rom - this process has to be done before installing the GSI of your choice and take care of the ARB.).
Click to expand...
Click to collapse
what do the acronyms GSI and ARB stand for?
premier69 said:
what do the acronyms GSI and ARB stand for?
Click to expand...
Click to collapse
GSI - generic system image (in this case, the rom you download in .img format for installation via twrp - for example, DotOS)
ARB - anti roll back - which is a mechanism to prevent the version rollback of Android.
Always read the topics carefully and follow the step by step without changing anything, not to generate problems.
Hello I have a problem with the files on my device and it is that when trying to install a ROM using TWRP I get that it has failed and a lot of messages saying:
"Error opening: ยด/data/user_de/0/" (Here it puts rare names of symbols and letters) operation not permitted
I already tried to mount the data folder from the recovery and I also tried to install the ROM from ADB commands but it is not possible, this is not the first time that I installed a ROM since I had Pixel Experence and when installing it it did not show me any error and now the Device does not start as it has no ROM and when it turns on it opens the TWRP.
someone could help me with that please.
I'm having problems with TWRP and OrangeFox, permission errors all the time
I'm facing some permissions problems and thus being unable to install Paranoid Android Q5. I was using MIUI 12 (Xiaomi.EU). The steps I took to change the ROM: Formated data (errors started right away) then I did the usual wipes (cache, dalvik...
forum.xda-developers.com