Hello. I have ported TWRP from Redmi Note 3 for Xperia M5. But it's some issues in it.
1. I can't wipe cache, because I can't umount it. It writes that device or resource busy.
2. I can't mount usb-otg. It nothink happens when I trying check it.
Mb somebody faced with this problem and can give me advice how to fix it.
May be I forgot to put some files from boot.img to recovery.img when ported? Can somebody say which files I have to change?
Hi dude, Facing the same problem here. Also, after I installed TWRP, I got stuck in the logo screen so I have to flash my entire system and data partitions again.
Why are you trying to port, we already ported it.
Related
hey everyone I'm new to xda.
so forgive me if i went wrong somewhere.
I rooted my canvas a1 (sprout 4) couple of months ago. i then had cyanogen mod on it. between these two months i had 2-3 crashes but i successfully wiped and flashed the same rom again via twrp. recently i wanted to upgrade to resurrection remix so as i wipe the data,system,cache.but none of that happened.log said unable to mount storage. unable to mount data. unable to mount cache.(invalid argument). unable to find crypto footer etc.etc.I tried every i could. accidentally i also erased recovery. and also unfortunately i kept usb debugging off. but i can bout into recovery via fastboot boot command. fastboot flash command not working. can anyone help me?plz need urgent help....
Edit: I've tried using spflashtools but everything went wrong. I used format+download. but it only formatted no download. do i lost everything oem+bootloader+recovery+os. nothing happens whatever i do to my phone. only it is recognized by pc as mediatek device. That's it.
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.
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
Hi everyone, I was usually providing help on this forum, now i'm the one desperate for help after some unforeseen consequences.
Bear in mind I'm kind of a noob anyway.
I have seen the message on the telegram groups for our device regarding solving the los 17 problems with the ril and camera. So i have followed the steps. I flashed the last twrp 3.4 by jarl using the official twrp app and then rebooted to recovery, wiped everything beside the internal storage and tried flashing the last los 16 zip.
And then the disaster happened. firstly the log returned error 7 so i've rebooted to recovery again and attempted to flash the same zip again without wiping anything. well the flashing worked apparently but i couldnt boot into it as it showed me an infinite boot animation.
Then i rebooted to recovery and it prompted me with a decryption key request which i didn't set before. I cancelled the prompt and I moved forward and proceeded wiping everything including the internal storage thinking that was the problem. Maybe it was maybe it wasnt, now I'm no longer prompted by any decryption key, but I was hoping i could connect to my pc through mtp, transfer some zips and flash some functional rom. Even though I enable mtp and my pc detects the phone I can't access any storage nor the internal, nor the sd card.
I tried going through multiple versions of twrp as i can still access my bootloader and i can still flash recoveries through fastboot but i feel that i'm stuck and I dont know what i should try anymore.
Before trying all this I was on an older build of los16 with the oreo firmware.
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
JarlPenguin said:
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
Click to expand...
Click to collapse
I wasnt using the twrp sar, i was using the exact version you linked. And I can't flash any rom because i cant get the zip inside my internal memory.
You can try using adb sideload. adb sideload path/to/zip
worked like a charm. thanks a lot, Jarl.
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Some random said:
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Click to expand...
Click to collapse
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Aythriel said:
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Click to expand...
Click to collapse
Yes, I'll make sure to note that