I'm using great AOKP SGT7 Milestone #6 on GT-P1000. I have one problem for backup ROM to SD card.
While I use ROM Manager v5.5.2.3, I set "Use External Storage" to "ON" in setting as screenshot1. It shows "Backup Current ROM" to "/mnt/emmc/clockworkmod/backup" in screenshot2. After reboot into recovery mode to do the job. It gets error "E:unknown volume for path [/external_sd/clockworkmod/backup/2013-02-25-13.17.49]". I have no idea to fix it. Is there any simple way to fix this bug?
xgamer123 said:
I'm using great AOKP SGT7 Milestone #6 on GT-P1000. I have one problem for backup ROM to SD card.
While I use ROM Manager v5.5.2.3, I set "Use External Storage" to "ON" in setting as screenshot1. It shows "Backup Current ROM" to "/mnt/emmc/clockworkmod/backup" in screenshot2. After reboot into recovery mode to do the job. It gets error "E:unknown volume for path [/external_sd/clockworkmod/backup/2013-02-25-13.17.49]". I have no idea to fix it. Is there any simple way to fix this bug?
Click to expand...
Click to collapse
Any answer to this? I have the same error. Thanks!
raymond26170 said:
Any answer to this? I have the same error. Thanks!
Click to expand...
Click to collapse
Same issue here. It used to work, but all the sudden stopped. I just recently upgraded to cwm 6.0.4.3 but I'm not sure if I've done a backup since upgrading cwm.
Samsung GS3 on vzw
CM 10.2 android 4.31
FYI - I went downflashed back a couple versions of CWM Recovery and I got the same error until I went back to CWM Recovery 6.0.3.6 and that version WORKED!!!
Backup to external SD card for CWM versions 6.0.3.7 through 6.0.4.3 seem to be borked on my D2VZW (Gallaxy S3)
Within ROM Manager v5.5.3.2, it says it will be backing up to: "/storage/sdcard1/clockworkmod/backup" however when it reboots into recovery, versions 6.0.3.7 and beyond attempt to use the "/external_sd/clockworkmod/backup/" path, which doesn't exist. When I check the mounts, /external_sd/ isn't listed as an option in recovery.
This would appear to be an issue with CWM Recovery, now the real question is: how to get this fixed?......
Still broken in CWM version 6.0.4.5
Still broken.
I upgraded to CyanogenMod v11, running ROM Manager 5.5.3.7 still throws this error with CWM Recovery versions including & after v6.0.3.7
Still broken in CWM 6.0.4.5
Seriously, has anyone gotten this working?
Related
Sorry but I need some help. When upgrading roms a few times, no problems ever occurred. CWM always worked smoothly. Now, I have the Resurrection Remix 1.0 Pro installed and was attempting to upgrade to Resurrection Remix 1.2 AOKP. I see that when running CWM I only had to choice to access the "download" folder on the scard. When attempting to install the Remix 1.2 rom, I always end up with an e signature fail. I tried several times but had the same results. I had to reboot and stay with Remix 1.0 until someone can help me get the upgraded rom installed. I wiped all the data and reset, and don't know what else to do.
Please help!!
OK, not sure the procedure you made... but might also be that some files you got were corrupted. Check to see they all are fine before going ahead with this way to install:
Do a full wipe(factory reset+cache+dalvik cache)
Install the Main ROM
Install Siyah-v3.0.1-CWM.zip
Reboot
Do the initial setup of things
Go back to CWM and install navigation button fix
Reboot
Then go back to CWM and install app themes (there are some bugs, but if you want the black themes, then install classic first, then black)
Reboot
Some people have other issues after, but see how this goes.
I would change the DPI settings to 184 or 210 for everything to work fine from market apps.
*if have more problems, just reply here.
Is the file on an external SD?
It's wherever you put it, though some files will only flash properly from external SD.
I think it's the internal sd
felixg123 said:
Is the file on an external SD?
Click to expand...
Click to collapse
At first I thought I had the files on the external sd card, but when rebooting in recovery with CWM it looked like it was only allowing me to access the download folder on the internal sd card.
Thanks for any suggestions.
cyberboob said:
It's wherever you put it, though some files will only flash properly from external SD.
Click to expand...
Click to collapse
The CWM that came with the remix 1.0 pro rom is that weird one that seems to have to boot from the other little app. Do you recall this is the CWM zip file that was added to the files to download for the remix 1.0 pro rom. It doesn't appear to have the same flexibility that the CWM had that came with my previously used rom...remix 9.4
Any comments??
With 1.0 its 3e (stock recovery) so you have to put cwm.zip in your external SD or your cache then flash it through 3e. Now you have cwm. If its the one from westcrip its touch so don't use the volume buttons.. actually touch the screen.
Hopefully that helps.
Sent from my GT-I9100 using XDA
Does the same thing... but it's a touch version.
There is a newer 1.3 version out now for Resurrection Remix with far simpler installing procedure... and people have reported most bugs fixed now (maybe a couple remain to be found).
cyberboob said:
Does the same thing... but it's a touch version.
There is a newer 1.3 version out now for Resurrection Remix with far simpler installing procedure... and people have reported most bugs fixed now (maybe a couple remain to be found).
Click to expand...
Click to collapse
Now, I'm really scratching my head. When I try installing the 1.3 rom it begins ....but returns this message and then aborts.
E: failed to verify whole-life signature
E: signature verification failed
I re downloaded the rom 1.3 to make sure it wasn't corrupt, and it did the same thing. Then I downloaded remix 1.2 just to see if this would install properly. I got the same result with the failed signature coming up in red and then it aborts. So something is not allowing me to change roms?? At present I have remix 1.0 installed.
Please I need some assistance figuring this out. I don't know what to do now?
Thanks in advance
Check if your current rom is having any beta releases of siyah 3.0, if so then it would be the cause, download cf root, or any latest version of custom kernel in tar format and flash it via Odin, now enter cwm and flash the new rom, you would be good to go
#*posted on the move *#
Works fine ....but is there a GPS problem?
I got the darn thing installed. Thanks. I was able to install the CWM......one that worked properly and the remix 1.3 got installed without a hitch. One problem I'm noticing the the GPS taking a whole bunch of time trying to locate sats. Is there is gps fix ??
Thanks
go to the Emergency FAQ for 1.3 (in my sig)
Samsung galaxy note i717. I rooted my phone yesterday as I also updated from 4.0.4 to 4.1.2. I have learned a few things about roms, kernels, backing up, restoring, etc.
I have SUPER SU, titanium backup, and ROM manager.
I understand that all rooted phones must have a SU to grant apps access to the software.
As for titanium backup, I have deleted bloatware and backed up and verified all of my information. I also bought the pro version of titanium backup. But for the Rom manager, I'm not too sure how to use that yet. I guess Titanium is for backing up and restoring, and ROM manager is for downloading the new rom?
To get a new rom (someone please recommend one to me? Specifically for good battery life and a customizable UI)
So you have to download it from the computer, then move to your SD card. Afterwards, the computer part is done right? How do you get the phone in the mode to put in the new rom? And do you have to wipe the stock rom first?
Someone please please recommend me a rom and tell me step by step how to do it without bricking my phone... And to restore everything back.
Thank you thank you
ROM Manager installs the CWM recovery on your device, it's a little tool that we use for installing zips with ROMs, kernels and stuff like that.
You have to get the ROM on the internal or external SD, and then go to the recovery mode. You can do this by pressing a button combo when the device is booting or you can also get to it with ROM Manager. Select "apply update from sdcard", and after this select "install zip from sdcard" (or "install zip from external sdcard" if you have your flashable zip in the external sd). Browse for your zip and select it to apply it.
To restore everything back, you have to make a nandroid backup before installing a new ROM. After you entered the recovery, select "backup and restore" and then select "backup". Just wait a little and it's finished.
A custom ROM I highly recommend is CyanogenMod, and you can also try AOKP.
Big post, but hope I helped
g.carvalho97 said:
ROM Manager installs the CWM recovery on your device, it's a little tool that we use for installing zips with ROMs, kernels and stuff like that.
You have to get the ROM on the internal or external SD, and then go to the recovery mode. You can do this by pressing a button combo when the device is booting or you can also get to it with ROM Manager. Select "apply update from sdcard", and after this select "install zip from sdcard" (or "install zip from external sdcard" if you have your flashable zip in the external sd). Browse for your zip and select it to apply it.
To restore everything back, you have to make a nandroid backup before installing a new ROM. After you entered the recovery, select "backup and restore" and then select "backup". Just wait a little and it's finished.
A custom ROM I highly recommend is CyanogenMod, and you can also try AOKP, it's CyanogenMod based (I think).
Big post, but hope I helped
Click to expand...
Click to collapse
It isnt't very Important but: I think Cyanogenmod is based on AOKP
icebeanpie said:
It isnt't very Important but: I think Cyanogenmod is based on AOKP
Click to expand...
Click to collapse
LOL, didn't knew that, thanks ;D
Requeriments:
Locked bootloader (Unlocked bootloader can flash a custom kernel with this included).
You must be root, if you not be root do this --> http://forum.xda-developers.com/showthread.php?t=2783885 NEW
You need enable USB Debuging Options (go settings->about phone->compilation number and hit seven times, then go settings->developer options and Enable USB debugging..
Installation:
1.) down CWM_SP_#.#.#.zip file.
2.) unzip it on your desktop.
3.) go to the CWM_SP_#.#.# folder
4.) run the install.bat file in windows (use others for linux or mac)
5.) select option number 1 to install.
6.) stay tuned on the phone as it calls super user permissions.
7.) Read the directions to see that everything went well.
8.) If all went well you press a key to continue and after press 3 for reboot phone or 4 to finish.
Click to expand...
Click to collapse
If something goes wrong, reboot your computer and phone and try again.
For new installs in recovery, i add the flashable zip in downloads section.
Operation:
Turning on the phone will see four lights advancing (GREEN-WHITE-RED/BLUE) when the blue light show press:
Volume up -> Philz
Volume Down -> TWRP
Camera button -> CWM Touch
Click to expand...
Click to collapse
If you have a problem you can put your questions once they have exhausted all options and read the comments of others.
In CWM Touch the backups are stored in /data/media/clockworkmod or /storage/removable/sdcard1/clockworkmod
If you only need ClockworkMod (without philz and TWRP ) you can use a MOD made by @Dark Passenger (any doubt about this release or updates, please ask him), just go to this post <<---- clic here (credits for MOD to @Dark Passenger)
Bugs:
For now, restoring backups in 4.3 with CWM touch have troubles. Fixed!
The date in recoverys are wrong, please rename the backups. Fixed!
Click to expand...
Click to collapse
Changes:
2014.07.09 ver. 4.4.1
- Improvements in product number and version number detection.
2014.07.04 ver. 4.4
- added support to CM 11 KitKat by bagyusz.
- all version are supported (4.1, 4.3 ) in same installer.
2014.06.27 ver. 4.3.8
- added sd-ext suport to backup
second partition of sdcard to all
recoverys(if exists). Needed if you
use link2sd or similar.
- CWM is default recovery (when you
do "reboot in recovery" system enter
in CWM automatically. The buttons keep
same function.
2014.06.16 ver. 4.3.7
- added linux and mac installers
- fix autocreate init.d directory
if not exist.
2014.06.09 ver. 4.3.6
- reverted enhanced ramdisk.
- fixed some bugs.
2014.05.21 ver. 4.3.5
- Updated CWM Touch to 6.0.4.7
- Updated TWRP to 2.7.0.0
- Added enhanced ramdisk.
- Added init.d support.
- Added compression to ramdisk's.
- Fixed "reboot in recovery" feature.
2014.05.16 ver. 4.3.4
- Loaded stock exfat driver.
- Added improvements.
- Fixed wipedata permissions.
2014.05.15 ver. 4.3.3
- Philz updated to 6.41.6.
- Disabled Glove mode in TWRP.
- Fixed DateTime in recoverys.
- Changed script to wipedata.
- some bugs fixed.
- support only for 4.3 Roms. (Sorry )
2014.04.04 ver. 4.3.2
- philz updated to 6.25.0.0
- CWM Touch updated.
- some bugs fixed.
2014.03.18 ver. 4.3.1
- added ZIP recovery flashable.
2014.03.11 ver. 4.3.0
- added Philz touch (thanks to @Phil3759).
- Some fixes to TWRP
2014.02.17 initial version
- added external sdcard for backup / install
- Fixed problems mounting/unmounting system partition
Click to expand...
Click to collapse
Credits:
@Phil3759 for PhilZ touch.
@FXP for CWM
@teamwin for TWRP
@DooMLoRD for ramdisk´s and scripts
@bagyusz for hijack ramdisk.
@KeiranFTW for hijack ramdisk.
Cheers and enjoy :good:
Download:
Installer:
CWM_SP_4.4.1.zip - 11.81 MB NEW!
Flashable:
recoveries_SP_4.4.1_signed.zip - 10.62 MB NEW!
Click to expand...
Click to collapse
anyone tried this already?
Im gonna try right now... Risking flashing on a Sunday... God protect me
Works.... Tested CWM Touch.
Nice Job Man, now we dont have to reflash 4.1.2 and root and flash 4.3 again n again n again n again
Life saver.
---------- Post added at 10:53 AM ---------- Previous post was at 10:25 AM ----------
Tested All recoveries:
1. CWM works fine
2. TWRP fine
3. CWM-touch (some difficulty in navigation, but works ok)
is there any way .. with out installing purerome.. .for rooting ?
i dont wanna change my stock rom....
I tested it, but only TWRP make backup. CWM says "can't mount system". CWM touch says "backup completed", but there is no backup files on any of storages.I tested two others CWM mods and they also says "can't mount system".
Ohh, I found CWM Touch backup files. After I read log file, I saw this row -> "I:using /data/media for /sdcard/0/clockworkmod". Backup folder is in /data/media/clockworkmod/backup/..
There is something wrong with filesystem table. I saw several lines that say Unable to get recovery.fstab info for: /datadata, /emmc, /sdcard, /ed-ext and /external_sd.
yep. this works. haven't tried backing up yet though. thanks.
thanks, its work.... but, why i cant mount system, its always "mount system Eror"....????
can any body help...
Can cwm mount sdcard0/1 and system?
Sent from my C5303 using xda premium
CWM shows "error in mounting system" when I try to mount system. As a result, can't take nandroid backup.
CWM Touch shows "error in unmounting system" when I try to unmount system. Though it can take backup, when I try restore, it shows error in unmounting system.
TWRP though not showing error, and seeming to backup correctly, when I try restore, it shows error in unmounting system.
In other words,
not working for me.
I'm on CE 4.3 stock, rooted, LB.
Deepam7325 said:
CWM shows "error in mounting system" when I try to mount system. As a result, can't take nandroid backup.
CWM Touch shows "error in unmounting system" when I try to unmount system. Though it can take backup, when I try restore, it shows error in unmounting system.
TWRP though not showing error, and seeming to backup correctly, when I try restore, it shows error in unmounting system.
In other words,
not working for me.
Click to expand...
Click to collapse
Same for me, i use existenz v2
Sent from my C5303 using xda premium
kuriboo said:
Same for me, i use existenz v2
Sent from my C5303 using xda premium
Click to expand...
Click to collapse
For 4.1.2 backups use CWM or TWRP, for 4.3 backups use CWM Touch.
Remember, if you restore an 4.1.2 backup you need change kernel to 4.1.2.
Enviado desde mi C5303 mediante Tapatalk
dssmex said:
For 4.1.2 backups use CWM or TWRP, for 4.3 backups use CWM Touch.
Remember, if you restore an 4.1.2 backup you need change kernel to 4.1.2.
Enviado desde mi C5303 mediante Tapatalk
Click to expand...
Click to collapse
I tried to restore 4.3 backup in cwm touch & twrp. it showed error "unable to unmount system" after md5 verification.
I tried to restore 4.3 backup in cwm. It verified md5 and erased boot image. after that it showed error "error, can't mount system" . As a result, I got soft brick on booting.
Its as if, CWM has its "mount system" freezed. CWM & TWRP have their "unmount system" freezed
Same for me, can't mount /system, so it's basicaly unusable ;/
Deepam7325 said:
I tried to restore 4.3 backup in cwm touch & twrp. it showed error "unable to unmount system" after md5 verification.
I tried to restore 4.3 backup in cwm. It verified md5 and erased boot image. after that it showed error "error, can't mount system" . As a result, I got soft brick on booting.
Its as if, CWM has its "mount system" freezed. CWM & TWRP have their "unmount system" freezed
Click to expand...
Click to collapse
in cwm touch you need mount system and data first, if you have trouble try use advanced restore.
i test full backup and all are ok,
---update --
Restoring backup in 4.3 don´t work, i´m working for fix that.
dssmex said:
in cwm touch you need mount system and data first, if you have trouble try use advanced restore.
i test full backup and all are ok,
---update --
Restoring backup in 4.3 don´t work, i´m working for fix that.
Click to expand...
Click to collapse
Pray for that
I decide UBL again after Relock
Sent from my C5303 using xda premium
flashed the rom n its working great but now if i want to enter cwm m nt able to plz help
saurabh808 said:
flashed the rom n its working great but now if i want to enter cwm m nt able to plz help
Click to expand...
Click to collapse
once you flash the custom rom yo need flash root too, once reboot need install CWM again because the recovery image are in system partition.
@ OP
Suppose i am on a 4.3 ROM, and i want to flash a MOD or add-on, which recovery will be compatible with 4.3?
I am on LB, so if the recovery formats system, i have a very long process to get back to where i was.
Currently no compatible custom recovery for LB, but there are people working on it!
We all wait!
Hi,
I loaded CM 11 and was working fine. I tapped on the CMD update APP and it checked for updates and tablet rebooted and touch screen failed to work. I tried reinstall, wiped everything etc. I tried cm10 again and no luck. Not sure what to do at this point.
You might consider trying the Unbrick method posted at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ to see if you can get your NT back to stock ROM and operational.
will try that thanks. Will I have to root again?
I loaded factory with success. However the touch screen still dead.
It's a long shot, but perhaps you can try to burn of Succulent's CM10 or CM11 SD-based ROM images from https://iamafanof.wordpress.com/category/nook-tablet-2/ (e.g., cm_acclaim_11.0_29SEP2014_HD_SDC_IMG from https://iamafanof.wordpress.com/201...droid-4-4-4-for-nook-tablet-sdcimg-xxsep2014/) and see if your NT would run CM ROM on SD.
Also, while the device was still running CM, did you by any chance change the Touch Screen mode using the Touch Screen FW Flasher app?
digixmax said:
It's a long shot, but perhaps you can try to burn of Succulent's CM10 or CM11 SD-based ROM images from https://iamafanof.wordpress.com/category/nook-tablet-2/ (e.g., cm_acclaim_11.0_29SEP2014_HD_SDC_IMG from https://iamafanof.wordpress.com/201...droid-4-4-4-for-nook-tablet-sdcimg-xxsep2014/) and see if your NT would run CM ROM on SD.
Also, while the device was still running CM, did you by any chance change the Touch Screen mode using the Touch Screen FW Flasher app?
Click to expand...
Click to collapse
I did hit a flasher app but I think it was for the ROM update. Anyway I did what you said, everything loads fine but touch screen is dead. So weird was working after cm10 update to CM11 and then I hit rom update in the apps and everything turned to garbage after that.
fw flasher app many fixes no solution no touchscreen
On my nook tablet I had lolipop set up and running well. Then after many years of not pushing the screen flasher app something came over me and I pushed it. Bad mistake. I have tried every fix I could find. I have flashed most cm roms that work with 10 touch. Tried the sd card boot rom, als cm9 ,10. 10.1 10.2, 11 and b&n stock .img.
With every new flash everything sets up perfectly except no touch screen response, the first page is perfect otherwise.
Any other ideas would be greatly appreciated.
chainsawchef said:
On my nook tablet I had lolipop set up and running well. Then after many years of not pushing the screen flasher app something came over me and I pushed it. Bad mistake. I have tried every fix I could find. I have flashed most cm roms that work with 10 touch. Tried the sd card boot rom, als cm9 ,10. 10.1 10.2, 11 and b&n stock .img.
With every new flash everything sets up perfectly except no touch screen response, the first page is perfect otherwise.
Any other ideas would be greatly appreciated.
Click to expand...
Click to collapse
Yea super annoying, I never had software screw up hardware like this. Everything loads fine just cant use touch screen
How I restored touch to my Nook tablet touch screen.
bigdog100 said:
Yea super annoying, I never had software screw up hardware like this. Everything loads fine just cant use touch screen
Click to expand...
Click to collapse
How I restored touch to my Nook tablet touch screen.
(can't post links since I am a new user)
Google and Download:
cm 10.201212NookTabletAcclaim-HDSDC.img
9-20120815 acclaim-restorefw .zip
emcc cm10.0 zip with correct gapps
Format sd card w/ sd formater
burn to card cm 10.201212 Nook Tablet Acclaim - HD SDC .img
boot nook with new card
after boot to non responsive screen, power off nook
connect nook to pc
and place on an internal folder(I used My Files/Documets) an emcc cm10.0 zip with correct gapps
also cm 9-20120815 acclaim - restore fw zip (restore to two touch)
power off (with no sd card in nook)
make sure to boot nook into INTERNALrecovery flash:
cm10.0 zip with correct gapps
also cm 9-20120815 acclaim - restore fw zip
wipe and factory reset
wipe cache and Dalvick
advaced fix pemissions
Reboot nook
My recovery is cmw v6.0.3.0
chainsawchef24 said:
How I restored touch to my Nook tablet touch screen.
(can't post links since I am a new user)
Google and Download:
cm 10.201212NookTabletAcclaim-HDSDC.img
9-20120815 acclaim-restorefw .zip
emcc cm10.0 zip with correct gapps
Format sd card w/ sd formater
burn to card cm 10.201212 Nook Tablet Acclaim - HD SDC .img
boot nook with new card
after boot to non responsive screen, power off nook
connect nook to pc
and place on an internal folder(I used My Files/Documets) an emcc cm10.0 zip with correct gapps
also cm 9-20120815 acclaim - restore fw zip (restore to two touch)
power off (with no sd card in nook)
make sure to boot nook into INTERNALrecovery flash:
cm10.0 zip with correct gapps
also cm 9-20120815 acclaim - restore fw zip
wipe and factory reset
wipe cache and Dalvick
advaced fix pemissions
Reboot nook
My recovery is cmw v6.0.3.0
Click to expand...
Click to collapse
ok gonna give it a shot but google will not pull up cm 10.201212NookTabletAcclaim-HDSDC.img i even broke it down, must be old version and cycmogen site doesnt show
bigdog100 said:
ok gonna give it a shot but google will not pull up cm 10.201212NookTabletAcclaim-HDSDC.img i even broke it down, must be old version and cycmogen site doesnt show
Click to expand...
Click to collapse
It is an old version when I was done I was running cm9 and my touchscreen is working. Just have to upgrade to cm12 . Add this to your search iamafanof.wordpress should help.
Good Luck
chainsawchef24 said:
It is an old version when I was done I was running cm9 and my touchscreen is working. Just have to upgrade to cm12 . Add this to your search iamafanof.wordpress should help.
Good Luck
Click to expand...
Click to collapse
still cant find it
bigdog100 said:
still cant find it
Click to expand...
Click to collapse
add https://
iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
9-20120815 acclaim-restorefw .zip look for this near the bottom of the page.
add https://
iamafanof.wordpress.com/?s=cm+10.0cm
cm 10.201212NookTabletAcclaim-HDSDC.img
cm-9-20120815-acclaim-restorefw.zip got the zip file but cannot find the .IMG
bigdog100 said:
cm-9-20120815-acclaim-restorefw.zip got the zip file but cannot find the .IMG
Click to expand...
Click to collapse
here is the download link sorry I left off 31 from the end earlier.
add- https
://docs.google.com/file/d/0B0pqBNpVw4UUZ3VRLXVWN0VDWHc/edit
I also have a nook tablet with non responsive touch screen. Occasionally it will activate the power off button but nothing else. I always thought it was a hardware failure of the FT5406ee8 touch chip. I have also tried booting CM roms that should have 10 touch capability and no go.
Don't know what to do other than trash it.
I'm trying to do a full wipe, or factory reset on my Moto E 2015 with TWRP 3.0.2 to get a clean install of a previous Cyanogenmod nightly that didn't cause problems with Google Apps (but that's another story). When I enter TWRP recovery and choose Wipe, it says "Factory Reset Complete - Successful" on the top, but when it gives information about what is happening on the bottom in red letters it says "Unable to mount storage". I did take out my external SD card before this because it has my ROM and Gapps zips on it.
When I go into "Advanced Wipe" and select all the partitions except Micro SD card, it says "Wipe Complete - Failed", and in red letters "failed to unmount /system (device or resource busy) , unable to wipe /system, unable to mount storage".
Before all of this I uninstalled Google Play Services and my Google App because of the "google play services stopped" error, then tried to restore using Titanium backup but it was saying "ten elements failed." That's my reason for trying to wipe everything and start fresh.
So having said all that, I can easily flash my ROM and Gapps again, but I'm concerned about these errors. I'm new at this and am very interested in finding out if I did something wrong.
DaveMacD said:
I'm trying to do a full wipe, or factory reset on my Moto E 2015 with TWRP 3.0.2 to get a clean install of a previous Cyanogenmod nightly that didn't cause problems with Google Apps (but that's another story). When I enter TWRP recovery and choose Wipe, it says "Factory Reset Complete - Successful" on the top, but when it gives information about what is happening on the bottom in red letters it says "Unable to mount storage". I did take out my external SD card before this because it has my ROM and Gapps zips on it.
When I go into "Advanced Wipe" and select all the partitions except Micro SD card, it says "Wipe Complete - Failed", and in red letters "failed to unmount /system (device or resource busy) , unable to wipe /system, unable to mount storage".
Before all of this I uninstalled Google Play Services and my Google App because of the "google play services stopped" error, then tried to restore using Titanium backup but it was saying "ten elements failed." That's my reason for trying to wipe everything and start fresh.
So having said all that, I can easily flash my ROM and Gapps again, but I'm concerned about these errors. I'm new at this and am very interested in finding out if I did something wrong.
Click to expand...
Click to collapse
How did you install twrp? Try using fastboot method and make sure to use twrp 3.0
Change with v 3.0.2-1....that problem fixed....
Sent from my Redmi Note 2 using XDA Free mobile app
alv09012013 said:
How did you install twrp? Try using fastboot method and make sure to use twrp 3.0
Click to expand...
Click to collapse
I installed TWRP by fastboot.
But now I've just been told to use two different versions of TWRP. First 3.0 and second 3.0.2-1
My current version is 3.0.2 which according to TWRP's website is the most recently supported version for my surnia (Moto E 2015)
I know 3.0.0 is supported because it's older but I don't see any downloads for 3.0.2-1
Should I revert back to the old 3.0 or risk using a version that says it's not supported yet?
Thanks for advice.
Hey man, this should be a good link http://forum.xda-developers.com/showthread.php?p=61406133 to Squids TWRP latest are there. I'm running the latest 3.02 and found when I upgraded my modem as well (to 6.0) I've had great success with TWRP.
Sent from my XT1527 using XDA-Developers mobile app
I had that same problem, usually after a dirty flash or making kernel tweaks, but a clean flash of the recovery.img (plus modem for me) usually does it. Then I do wipe just to be sure! ?
DaveMacD said:
I installed TWRP by fastboot.
But now I've just been told to use two different versions of TWRP. First 3.0 and second 3.0.2-1
My current version is 3.0.2 which according to TWRP's website is the most recently supported version for my surnia (Moto E 2015)
I know 3.0.0 is supported because it's older but I don't see any downloads for 3.0.2-1
Should I revert back to the old 3.0 or risk using a version that says it's not supported yet?
Thanks for advice.
Click to expand...
Click to collapse
I used 3.0 and I had no problems with it. The only trouble I had was updating stock ROM when boost released an update last week but I went in and edited the script and fixed that issue. But I just updated to 3.0.2-r1 and can confirm it does indeed work. Here is the direct download link http://forum.xda-developers.com/devdb/project/dl/?id=17768&task=get
izzen42 said:
Change with v 3.0.2-1....that problem fixed....
Sent from my Redmi Note 2 using XDA Free mobile app
Click to expand...
Click to collapse
alv09012013 said:
I used 3.0 and I had no problems with it. The only trouble I had was updating stock ROM when boost released an update last week but I went in and edited the script and fixed that issue. But I just updated to 3.0.2-r1 and can confirm it does indeed work. Here is the direct download link http://forum.xda-developers.com/devdb/project/dl/?id=17768&task=get
Click to expand...
Click to collapse
Thanks a lot you guys. After updating to 3.0.2-r1 all my partitions finally got wiped, and all the errors went away. I'll try that kernel from Squid too after my poor head stops spinning after two days of battling through this haha but it's fun to learn. I really appreciate everyone's help.