Database Users

[RESOLVED] How do I restore factory Rom (from Revolution HD 3.0.1 on TF101)?

I am running the Revolution HD rom, this is how I purchased my TF101 from a friend, and I want to restore the factory rom so I can get ICS and the update for the battery issue until mike gets it implemented into Revolution.
How can I do this?
Thanks!

-edit- nevermind, I didn't notice you were running revolution.

If you want to flash back to stock, go to the ASUS Support site and download the 9.2.1.11 firmware for your device.
Unzip it 1 time (there is a zip file within the zip) so it will still have a zip.
Put the file on a microSD or the internal /sdcard/ directory depending on your version of CWM and where it can read.
Boot to CWM.
Install zip.
Choose the zip you downloaded.
Now you will be back to stock unrooted with stock recovery.
Then you will need to check for updates and grab the latest update from ASUS OTA.
If you want to root again you will need to vipermod option 1 to get root access.

Ah, thank you Fred! I did exactly that and it failed but it was the zip within a zip that killed me!

The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?

gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
Here's exactly what I did to go from Revolution HD 3.0.1 back to stock Asus ICS 9.2.1.11
1. Download the firmware from Asus website. The file name was US_epaduser9_2_1_11UpdateLauncher.zip. You unzip this. You get US_epad-user-9.2.1.11.zip. You put US_epad-user-9.2.1.11.zip on your microSD card.
2. Boot into CWM
3. Factory reset
4. Clear Cache
5. Clear dalvik cache
6. Mount & Storage - format /system
7. Mount & Storage - format /cache
8. Power off(from CWM menu, might be under advanced, I forgot)
9. Boot into CWM.
10. Install zip from sdcard. Choose US_epad-user-9.2.1.11.zip on your microSD.
11. Reboot after flashing is complete.
12. You should now be on Asus stock ICS with stock recovery.
13. I didn't add any of my google accounts during the initial setup because I wanted to do it after I do the 9.2.1.17 update.
14. Shut off and do a cold boot.
Worked perfectly fine for me.
What didn't work was, I was not getting the 9.2.1.17 update afterwards.
So I rooted using Vipermod, installed CWM, and manually flashed the update through CWM. I had to re-root after the update. Simply ran Vipermod again.
Been 2+ days, and it's super stable with great battery life. Not a single random reboot or crash.

gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision

gee one said:
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod

gbatt said:
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod
Click to expand...
Click to collapse
I am pretty sure my CWM Recovery was 3.1.0.1 too.
Try replacing your CWM with Rogue XM Recovery http://forum.xda-developers.com/showthread.php?t=1446019

Awesome! That worked great. Thanks Horndroid!

TWRP symlink:some symlinks failed

Hi guys, I'm trying to flash a kit kat ROM coming from purity 4.3, but when in recovery and trying to flash the zip it says
Symlink:some symlinks failed
E: error executing updater binary in zip,,,,
What's going on?
Sent from my Nexus 10 using xda app-developers app

filthygoat223996 said:
Hi guys, I'm trying to flash a kit kat ROM coming from purity 4.3, but when in recovery and trying to flash the zip it says
Symlink:some symlinks failed
E: error executing updater binary in zip,,,,
What's going on?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
What TWRP Version are u using? make sure u are on latest I thinks it's 2.6.3.1... here's linkg for the latest .img file http://techerrata.com/browse/twrp2/manta
or try the goomanager app.
if that fails u might have to use CWM.
Good Luck

Reboot recovery and unmount /cache partition. That worked for me

I could really use help with this as well. so many different issues. Sometimes its status 7 some symlinks failed, sometimes its just some symlinks failed, and sometimes its error in updater. I need help! Tried so many different things. My TWRP is up to date, ive downloaded the rom and gapps several times with all the same results, and High on Android said to open up the rom and change some of the script with a text editor and ive done that and rezipped the rom and flashed and still gotten errors. OMG please help

Worked for me
bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
Thank you. This helped me install the 4.4 liquidsmooth beta.

bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
Thanks a lot, that worked for me as well

I believe that the latest TWRP versions have resolved this.

bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
Thanks it worked for me tooo.

dint work for mee
i cant install aospextended rom :crying:
eternityhacker said:
Thank you. This helped me install the 4.4 liquidsmooth beta.
Click to expand...
Click to collapse

bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
thanks, that worked for me in moto xt1058 , rom stock mod debloated

how to
bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
how to unmount /cache partition?

dickydicky77 said:
how to unmount /cache partition?
Click to expand...
Click to collapse
veirdly that worked for me too.

bidzapfc said:
Reboot recovery and unmount /cache partition. That worked for me
Click to expand...
Click to collapse
done, great job it helped me thanks

[PARTITION] BlePart [v2.x]

BlePart is a customization for Huawei IDEOS X5's partition list. By default, U8800 has /system size of 220MiB, which is too small for new ROMs. To work around this problem, I have developed BlePart.
BlePart comes in multiple variations to have an optimized balance between /data (apps) and /emmc (internal SD - media, files). As a bonus, Huawei has left unused space between partitions. BlePart makes use of the space between those partitions.
Warning: If not done properly, you may brick your device. Look through the installation tutorial before applying this.
Strongly recommended
Have unlocked bootloader (pink screen accessible).
Have a full disk backup done from your device.
Installation
Reboot to recovery (by using volume up + power or by Android's power menu).
Flash BlePart recovery.
Reboot recovery (advanced->reboot recovery).
Flash any BlePart version (2.1, 2.2 or 2.3).
Warning: Your phone is without any ROMs installed at this stage. Normal boot won't work.
Replace the BlePart recovery by flashing a new one (by pink screen or recovery).
Note: BlePart does not require any special recovery. Install back your previous recovery or choose a new one.
Flash a BlePart-2 compatible ROM (in theory, every ROM for U8800 is compatible).
Warning: Installing ROM with BlePart INSTALLER is not possible.
BlePart-21
/system 550MiB
/data 1450MiB
/emmc 1002MiB
BlePart-22
/system 550MiB
/data 1953MiB
/emmc 499MiB
BlePart-23
/system 550MiB
/data 2403MiB
/emmc 49MiB
BlePart-stock
/system 220MiB
/data 600MiB
/emmc 2048MiB
Any questions you might have, kindly ask here. I have tested all of these on my device, but it won't mean there can't be any sideeffects.

MANY thanks for this yuupi!

Great work！

Do I need to be on stock partition layout before blepart flash? Can I flash any other 404020 rom e.g. dzo's aurora using any blepart scheme or do I need to revert to stock/forumber layout.
Sent from my IDEOS X5 using xda app-developers app

needed for cm11?
is this partition necessary for your cm11 @Blefish , or is the forumber partition good enough/usable too?

yay!
flashing right now . i am going to use blepart2.2
---------- Post added at 07:21 PM ---------- Previous post was at 07:16 PM ----------
Blefish said:
BlePart is a customization for Huawei IDEOS X5's partition list. ....
....
Any questions you might have, kindly ask here. I have tested all of these on my device, but it won't mean there can't be any sideeffects.
Click to expand...
Click to collapse
Hi blefish, i am sorry about flood msg , i couldnt edit. If i make a backup with my current partition, will it be usable with the new one? I have many apps and installing a new rom scares me thank you very much.

great work! now we wait cm11 for testing

I have a question on installation post it said to flash blepart recovery on recovery so with witch recovery we needed first? I am with twrp

Which version of Clockworkmode recovery I need for the flash partition?
Sent from my U8800

Stupid question.
What does 'replace the Blepart recovery by flashing the new one'? It means flash another recovery, doesn't it?

I have flashed it. Let me explain let's say currently you are on cwm 5.5.0.4 the first you have to flash blepart recovery using cwm 5.5.0.4 that you already have. Then go to advanced and choose reboot recovery. You will now boot into blepart recovery. Press volume up down buttons to select install zip and choose the blepart version you downloaded and flash it using power button. Now you have blepart partition scheme. Using the same recovery or pink screen flash again the recovery cwm 5.5.0.4. Now reboot to recovery you will boot into cwm 5.5.0.4. Now using recovery 5.5.0.4 flash any 404020 ROM u want.
Sent from my IDEOS X5 using xda app-developers app

One question left, from who have forumber's partition it's necessary revert to stock partition?
Using Tapatalk 2

nayneshdev said:
Do I need to be on stock partition layout before blepart flash? Can I flash any other 404020 rom e.g. dzo's aurora using any blepart scheme or do I need to revert to stock/forumber layout.
Sent from my IDEOS X5 using xda app-developers app
Click to expand...
Click to collapse
You don't need to necessarily be on stock layout. The great thing about BlePart is, it rewrite the partition layout using sfdisk utility. And since BlePart-2.x is using the standard layout (but with different sizes), it is compatible with Aurora, no need to go back to stock.
bdgraue said:
is this partition necessary for your cm11 @Blefish , or is the forumber partition good enough/usable too?
Click to expand...
Click to collapse
The ROM uses nearly 450MB with gapps installed. I don't know if forumber's /system partition is that big. If it is, then it will work. Otherwise it may happen that ROM can be installed successfully, but gapps can't (as they are pretty big in size).
cizkek_ said:
Hi blefish, i am sorry about flood msg , i couldnt edit. If i make a backup with my current partition, will it be usable with the new one? I have many apps and installing a new rom scares me thank you very much.
Click to expand...
Click to collapse
You are talking about CWM/TWRP backup, right? In theory, it should work. However, I don't know if CWM/TWRP do any size checking on the partition, if the backup /data partition is larger than with BlePart, it may fail restoring.
pl4t!n said:
I have a question on installation post it said to flash blepart recovery on recovery so with witch recovery we needed first? I am with twrp
Click to expand...
Click to collapse
Yes, any recovery will do as the starting step.
Oto_Shan said:
Which version of Clockworkmode recovery I need for the flash partition?
Sent from my U8800
Click to expand...
Click to collapse
season 8 said:
Stupid question.
What does 'replace the Blepart recovery by flashing the new one'? It means flash another recovery, doesn't it?
Click to expand...
Click to collapse
The last step means you will flash your favourite recovery back again. It doesn't need anything special unlike BlePart 1. I'll update the first post a bit to make it more sensible.

i try and it failed. it said:
assert failed_ getprop ("ro.blepart")=="1"
E:Error in /storage/sdcard0/blepart-22-signed.zip
(status7)
i tried with 2 different cards and with 3 blepart and failed 3 times
i even tried flash blefish recovery with recovery 5.0.4.0 failed again

pl4t!n said:
i try and it failed. it said:
assert failed_ getprop ("ro.blepart")=="1"
E:Error in /storage/sdcard0/blepart-22-signed.zip
(status7)
i tried with 2 different cards and with 3 blepart and failed 3 times
i even tried flash blefish recovery with recovery 5.0.4.0 failed again
Click to expand...
Click to collapse
This error comes up when BlePart recovery is not started. Can you make sure the recovery version says BlePart INSTALLER (v2.0) v6.0.4.6? After installing BlePart recovery, did you reboot the phone?

Blefish said:
This error comes up when BlePart recovery is not started. Can you make sure the recovery version says BlePart INSTALLER (v2.0) v6.0.4.6? After installing BlePart recovery, did you reboot the phone?
Click to expand...
Click to collapse
recovery said CM-based Recovery v6.0.4.6
maybe i have the wrong version wait a moment...
ps: yes, now says BlePart INSTALLER (v2.0) v6.0.4.6 lets try again
its working, now we just wait for cm11 thank you

Hi, I have a problem.
I flashed Blepart recovery, flashed blepart 21 partiton and flashed CWM recovery v 6.0.4.6
Everything was ok. No errors
Now I am trying install AuroraSP+ ROM and I got error :
Format ( ) excepts 5 args, got 4
E:Error in /storage/sdcard 0/aurorasp+.zip
(Status 7)
Installation aborted.
.

Did you install blefish recovery blepart installer (v2.0)? And then switch this recovery to your favorite recovery? You cannot install roms with blefish installer recovery

pl4t!n said:
Did you install blefish recovery blepart installer (v2.0)? And then switch this recovery to your favorite recovery? You cannot install roms with blefish installer recovery
Click to expand...
Click to collapse
Now I am using this recovery
http://forum.xda-developers.com/showthread.php?t=1377390
ClockworkMod Recovery [v6.0.4.6]
---
Edit:I installed old cwm 5.5.0.4 and rom is successfully installed. Without errors.
Everything works fine.

Ax1qwer said:
Hi, I have a problem.
I flashed Blepart recovery, flashed blepart 21 partiton and flashed CWM recovery v 6.0.4.6
Everything was ok. No errors
Now I am trying install AuroraSP+ ROM and I got error :
Format ( ) excepts 5 args, got 4
E:Error in /storage/sdcard 0/aurorasp+.zop
(Status 7)
Installation aborted.
.
Click to expand...
Click to collapse
Apparently the v6.0.4.6 (the standard, not blepart) recovery is not backward compatible with old ROMs. I can't do anything other about it than hope it will be fixed upstream. I'm glad though that the BlePart installation went smoothly .

[Rec][TWRP][exFat][F2FS] TWRP 2.8.6.0 for Z1 Honami

Hey guys, it's me again In the last few months I dont active much on this anymore, now I'm back
Here is the latest rec for our beloved device:
https://drive.google.com/file/d/0B5ePoKNP9UFtM1R5MW1vdjFGOGc/view?usp=sharing
How to use:
Code:
fastboot flash recovery twrp-z1-2860.img
Changelog:
v2.8.6.0:
Nothing much, just add support for Z1 and F2FS
Bugs: The image/icon may look weird because I have to compress all icon to make room for new update....Limited space for us to "hack" it...
You tell me
This thread will be main support for TWRP to use with CM/CM-based rom or maybe stock rom too by me...Stay update
I will update it ASAP when new TWRP version come out....
P/S: "TekCafe" is just the name of my support group...If you guys not like it, I will make another without that name....
Tested on AICP 9.0
Click "Thanks" if you find it useful...

Thanks. Everything is working perfectly we just seem to have 2 home buttons now. The 1 home button functions like the back button so it's just cosmetic

LSD DREAMER said:
Thanks. Everything is working perfectly we just seem to have 2 home buttons now. The 1 home button functions like the back button so it's just cosmetic
Click to expand...
Click to collapse
I compress and reuse all the icon so you may find broken artifact icon, duplicated,...It's just cosmetic, every function work just as fine....

BlackSoulxxx said:
I compress and reuse all the icon so you may find broken artifact icon, duplicated,...It's just cosmetic, every function work just as fine....
Click to expand...
Click to collapse
It all works fine it even looks the same just the 2 home buttons. Not complaining just thought I'll share

Hi!
Will this TWRP work with stock 4.4.4?
I´m on UB.
Best regards

C_Karhu said:
Hi!
Will this TWRP work with stock 4.4.4?
I´m on UB.
Best regards
Click to expand...
Click to collapse
You should install NUT XZDR...:fingers-crossed::fingers-crossed::fingers-crossed:

Sorry, I didn't make myself clear. I'm interested in the F2FS. My kernel has support, but I can't format system to it. Will this TWRP format stock 4.4.4 to full F2FS?
Best regards

Is it compiled from source or repacked from Sirius?

o-l-a-v said:
Is it compiled from source or repacked from Sirius?
Click to expand...
Click to collapse
You already answer that question.....

Does the latest CM12 nightly support F2FS already?

Hi,
I've changed /system and /cache successfully, but I cannot convert /data to f2fs. Formats to ext4 correctly, but even after I formatted ext4, rebooting to recovery and formatting it to f2fs fails.
Code:
Formatting Data using mkfs.f2fs...
E:Unable to wipe '/data'.
E:Unknown MTP message type: 1
E:Error changing file system.
Updating partition details...
I have unlocked bootloader, Xperia Z1 (c6903 honami) running 5.1 with Resurrection Remix 5.4.1 kernel and ROM. I have not encrypted device.
Thoughts?
FIXED! I was able to format it by using terminal from TWRP and typing
Code:
mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
then I rebooted device into recovery to update partition table, then Wipe > Repair/Change Filesystem > Data
Code:
current file system: f2fs
Yay!

kentexcitebot said:
Hi,
I've changed /system and /cache successfully, but I cannot convert /data to f2fs. Formats to ext4 correctly, but even after I formatted ext4, rebooting to recovery and formatting it to f2fs fails.
Code:
Formatting Data using mkfs.f2fs...
E:Unable to wipe '/data'.
E:Unknown MTP message type: 1
E:Error changing file system.
Updating partition details...
I have unlocked bootloader, Xperia Z1 (c6903 honami) running 5.1 with Resurrection Remix 5.4.1 kernel and ROM. I have not encrypted device.
Thoughts?
FIXED! I was able to format it by using terminal from TWRP and typing
Code:
mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
then I rebooted device into recovery to update partition table, then Wipe > Repair/Change Filesystem > Data
Code:
current file system: f2fs
Yay!
Click to expand...
Click to collapse
Tks!:fingers-crossed::fingers-crossed::fingers-crossed:

Up...............

guys help me pls. i flash the recovery by fastboot but when press volume - not enter in recovery why is? obviously i have unlocked the boot

axelgrox said:
guys help me pls. i flash the recovery by fastboot but when press volume - not enter in recovery why is? obviously i have unlocked the boot
Click to expand...
Click to collapse
+1... same problem!

axelgrox said:
guys help me pls. i flash the recovery by fastboot but when press volume - not enter in recovery why is? obviously i have unlocked the boot
Click to expand...
Click to collapse
There could be 2 reasons: one, you are not properly flashing, as you need to do
fastboot flash recovery "name of file": second, if you have kernel with TWRP integrated, the two will collide resulting in no recovery at all...

Hi
Does it work for stock android 5.0.2 build .270 ?!
Thank you

Does this work 14.6.A.0.368

I have been trying to reflash this, however when I try to boot in to TWRP all I get is the fastboot mode on my phone which doesn't allow me to do anything. I recently just uninstalled MultiRom for the same reasons, but now since I have removed MultiRom I cannot get into TWRP at all. Does anyone have any ideas?

File doesn't exist anymore

Cant mount R/W

Ok, I'm running Resurrection Remix on the Qualcomm Chipset. I have 3.2.0 R1 version of TWRP. I tried to install Xposed when it said it couldn't install because the /system was Read Only. I had tried everything... Any help would be appreciated, Thanks

codyalan said:
Ok, I'm running Resurrection Remix on the Qualcomm Chipset. I have 3.2.0 R1 version of TWRP. I tried to install Xposed when it said it couldn't install because the /system was Read Only. I had tried everything... Any help would be appreciated, Thanks
Click to expand...
Click to collapse
in the mount section unselect read only and tick mount system and flash .zip framework again

like so ..then you can flash it

Did that, like 2000 times...

do this
mount -o rw,remount /system
within the twrp terminal mode.

Francesco Franz said:
do this
mount -o rw,remount /system
within the twrp terminal mode.
Click to expand...
Click to collapse
Tried this twice, got two different responses...

codyalan said:
Tried this twice, got two different responses...
Click to expand...
Click to collapse
you need to correct mount flags in recovery.fstab within the recovery ramdisk.
---------- Post added at 08:54 AM ---------- Previous post was at 08:53 AM ----------
codyalan said:
Tried this twice, got two different responses...
Click to expand...
Click to collapse
or use another twrp recovery.
from Ressurection rom zip file works fine.

Francesco Franz said:
you need to correct mount flags in recovery.fstab within the recovery ramdisk.
Click to expand...
Click to collapse
How would one go about doing this?

codyalan said:
How would one go about doing this?
Click to expand...
Click to collapse
you could try installing systemless xposed from within magisk .....
if not your other option under advanced tab select terminal and run this command
“mount -t ext4 /dev/block/bootdevice/by-name/system /system”
* if that doesn't work get another recovery *

KevMetal said:
you could try installing systemless xposed from within magisk .....
if not your other option under advanced tab select terminal and run this command
“mount -t ext4 /dev/block/bootdevice/by-name/system /system”
* if that doesn't work get another recovery *
Click to expand...
Click to collapse
Yeah have Xposed systemless already, but command doesn't work either, not sure if any other recovery for our phones... Would formatting data fix this?

codyalan said:
Yeah have Xposed systemless already, but command doesn't work either, not sure if any other recovery for our phones... Would formatting data fix this?
Click to expand...
Click to collapse
well if your problem is mounting system formatting data wouldn't necessarily fix it ..what kind of error do you get when trying to mount system from terminal ? try posting a screenshot of recovery output and terminal output error when you try mounting system ..i don't know if there are any other recoveries for your variant
try flashing it via flash fire apk instead ..it might work

*out of interest *
i noticed you have twrp 3.2. ...the first recovery for moto e4 was 3.1...
i got this exact same error ..if you really MUST have latest recovery flash back to recovery version 3.1..
flash xposed zip ..flash back to recovery 3.2...
i went back to using recovery 3.1.... for mediatek due to a few errors in 3.2.... including error 1 above. didn't notice that before but there is definitely both a mtk and Qcom recovery version 3.1... ( old or first version ) available floating around the threads

codyalan said:
Yeah have Xposed systemless already, but command doesn't work either, not sure if any other recovery for our phones... Would formatting data fix this?
Click to expand...
Click to collapse
Instead of formatting /data, you can try going to /data/media/0/TWRP and delete the .twrps file and then boot to twrp and make sure you allow it to modify /system when it asks and try to flash Xposed again. Check for /data/media/TWRP also because sometimes you'll have both. Does this happen with other ROMs, or only RR? I don't think it has anything to do with wrong recovery mount flags.
Sent from my Moto E (4) Plus using XDA Labs

volatile1 said:
Instead of formatting /data, you can try going to /data/media/0/TWRP and delete the .twrps file and then boot to twrp and make sure you allow it to modify /system when it asks and try to flash Xposed again. Check for /data/media/TWRP also because sometimes you'll have both. Does this happen with other ROMs, or only RR? I don't think it has anything to do with wrong recovery mount flags.
Click to expand...
Click to collapse
Not sure if it happens with other ROMs, I'll try what you said and if that doesn't work I'll try another ROM

codyalan said:
Not sure if it happens with other ROMs, I'll try what you said and if that doesn't work I'll try another ROM
Click to expand...
Click to collapse
I forgot to ask if you were using the 3.2 TWRP and if it happened with 3.1 versions?
Sent from my Moto E (4) Plus using XDA Labs

volatile1 said:
I forgot to ask if you were using the 3.2 TWRP and if it happened with 3.1 versions?
Click to expand...
Click to collapse
Yeah.. should I install 3.1 and see if mounts as r/w?

codyalan said:
Yeah.. should I install 3.1 and see if mounts as r/w?
Click to expand...
Click to collapse
It can't hurt to try. It also can't hurt to get a recovery log after the failed flash with 3.2 and post it and mention your problem in the recovery thread if it doesn't happen with 3.1.
Sent from my Moto E (4) Plus using XDA Labs

Edit : Deleted