I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
modman21 said:
I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
Click to expand...
Click to collapse
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that
Click to expand...
Click to collapse
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Fain11 said:
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Click to expand...
Click to collapse
Thanks for the link. I tried to find similar threads, but couldn't. They are having the same problem but with a different rom (I was trying to flash Sky Dragon android L). The solution on that thread was to use TWRP 2.6.3.3, but some people reported having no problems with 2.8.3. The install instructions for Sky Dragon say use the latest twrp but doesn't specify a version. I guess I could try TWRP 2.6.3.3 but I'm not sure if it will work since CM requires 2.7.1.
The other solution was to mount the partition manually before flashing using the terminal in recovery. This command was suggested:
Code:
run_program("/sbin/umount", "/system");
Haven't tried any of these solution myself. After 3 hours and wiping my entire data partition by accident, I USB-OTG copied my nandroid backup to my phone and did a complete recovery. Luckily the restore process didn't care about mounting /system. I may try this again with manual mounting, but likely I will wait for a twrp update. I'm not sure if twrp 2.6 supports usb-otg so it will be a pain in the ass if I wipe /data again by accident.
Random side note for anyone googling this, if you accidently wipe all the data from your sdcard and have to copy the nandroid backup for twrp, the the restore function won't recognize the files unless they are in exactly the right directory. The best way to get this is to copy the entire TWRP directory when saving your backup in the first place so you can just copy it back. If you didn't do that then just run a nandroid backup of the blank sdcard and it will recreate the folder structure for you. Then you copy the files into the correct folder.
alray said:
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
Click to expand...
Click to collapse
Exactly this. I do not know the exact reason CM needs 2.7.1 so therefore I don't know if Sky Dragon needs it as well. The instructions just say use the latest twrp.
http://forum.xda-developers.com/showthread.php?t=2400161
Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Click to expand...
Click to collapse
I did wipe my entire data partition (by accident), but I did not try to format it as ext4. I did format /system to ext4 (so now the partition was displaying correctly as ~1.8gb). The used the twrp repair, then wipe It seemed to work, but if I restarted right then, without even trying to flash the rom, the /system would not mount on reboot to recovery and would show as 0mb. I used all reasonable combinations and permutations of the wipe, repair and format functions on system, nothing worked.
I finally copied my nandroid backup via usb-otg and recovered back to cm11.
Hi Guys, I'm having a big issue with my Android.
Since I've installed the Xposed alpha for Lollipop (xposed-sdk22-arm-20150514.zip; I have a rooted CM 12.1) I started to have some issues at boot (every time I was booting I had to clean the cache and the dalvik cache in CWM and I had to boot 2 times before seeing Android re-optimizing the apps).
Yesterday I've flashed an update of Xposed alpha for Lollipop (xposed-sdk22-arm-20150609.zip ) and it was working fine, then I've had the wonderful idea of updating CM with a newly nightly built:
- I've made a Nandroid backup in CWM
- I've made a dirty flash (wipe of cache/dalvik cache)
- I've flashed the new nightly
All this caused my Android to enter into bootloop.
This gave start to 2 painful days of trial-and-error to recover my nandroid backup with no success at all.
What I've done (IN SEQUENCE) to try restore my nandroid backup:
[TEST 1]
Full Nandroid Restore via CWM
wipe cache/dalvik cache
OUTCOME: bootloop
[TEST 2]
dirty flashed via CWM:
cm-12.1-20150518-NIGHTLY-jfltexx.zip [same ROM installed at the time of the Nandroid backup]
gapps-lpmr1-20150403-signed.zip [same GApps installed at the time of the Nandroid backup]
xposed-sdk22-arm-20150609.zip [same Xposed zip installed at the time of the Nandroid backup]
OUTCOME: bootloop
[TEST 3]
From CWM -> Mounts and Storage
format /system
format /cache
[NO FORMAT /DATA GIVEN THAT IT IS WHAT I WANNA KEEP]
wipe cache
wipe dalvik cache
install from zip:
cm-12.1-20150518-NIGHTLY-jfltexx.zip
gapps-lpmr1-20150403-signed.zip
OUTCOME: bootloop
[TEST 4]
flashed from recovery:
xposed-sdk22-arm-20150609.zip
reboot system
OUTCOME: bootloop
[TEST 5-...]
Tried to disable Xposed in all the different ways suggested in the post http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
(with adb commands or flashing zip files)
In the end I've decided to give up the full nandroid restore so I've made a full wipe:
CWM -> Mounts and Storage -> Format /system; Format /cache; Format /data
wipe cache
wipe dalvik cache
and then I've flashed:
cm-12.1-20150518-NIGHTLY-jfltexx.zip
gapps-lpmr1-20150403-signed.zip
Now everything works and at this time I'm recovering the User Apps (apps+data) from the Nandroid backup using Nandroid Manager under CyanogenMod but the problem is that I fear some apps will not work properly (I've already tried Nova Launcher and it crashes every time I try to use it) even tough I'm using the very same ROM. So I will probably need to uninstall many apps manually and reinstall them, which is kind of painful.
Meanwhile I'm working on this I still hope to be able to recover my Nandroid backup so I'm here to ask you for help.
From my tests (and others I haven't listed above) I've realized that the issue is in the /data partition and it is probably linked to Xposed and/or the modules I've installed (XMultiWindow and XHaloFloatingWindow). As I said earlier I started to have issues connected to Xposed alpha for Lollipop since I have installed it and probably the ROM update made Xposed "extremely upset" and gave me this issue with a corrupt (?!) Nandroid backup.
Any idea is very much appreciated!
Same with me. TWRP system and data backup won't be restored after boot loop. Haven't tried your method of recovering the rom.
Hello,
Can you pls tell how the TWRP backup and restore works?
I went to TWRP and backed up all the partitions to my internal storage.
I went to restore and could see the backed up image.
After that i wiped data, cache, dalvik and system...didn't wipe internal storage.
Flashed the AEX Oreo ROM, gapps, wiped cache/dalvik and rebooted system to boot into new ROM.
Then when I went to TWRP and clicked on restore, it was empty...the backed up image was gone!
I am confused as I didn't wipe my internal storage...so where does the backed up image go??
After formatting data partition, I am unable to restore backed-up data directly as I get an error (255?). I have to always let the phone boot to the welcome setup screen before going back into TWRP to restore my backup.
Is there something I can do to avoid this lengthy step?
I found the same. It's almost as if twrp doesn't format correctly.
I typically use fastboot -w, flash, then boot into the ROM, then restore from backup.
Hi every1
Like in title - I have TWRP 3.3.1.0. Flashed Revenge OS, installed & setuped everything what I need. Done the TWRP backup. Tried other ROMs but want to go back to Revenge. When I try to restore that backup in the end of a process TWRP informs me that "Failed to mount '/system/ (invalid argument)" and ofcoz phone didn't boot. Tried to go back to TWRP 3.2.3.0, change the system partition to ext2 and back to ext4 - no luck. Any suggestions?