Database Info

Can't install .zip file from CWM

I am relatively new to the world of rooting and ROMs, but I have successfully installed CM10 on a previous Samsung phone, so I am decently literate.
I am currently attempting to install CM10.1 on my Verizon Galaxy S III (following the instructions on the Install CM for d2vzw page on the CM wiki), but I have reached an impasse at step 7. I was not aware that I had to put the VRALE6.bootloader.zip file on the SD card before starting this process, so I am now attempting to get that file onto my SD card either by sideloading through CWM or by pushing it to the SD card through adb. The issue is that CWM gives me an error (can't mount SD card) and adb doesn't recognize my device (I have tried installing and reinstalling various drivers for the past few hours). I enabled USB Debugging mode before starting the process, but I am only able to get into Download and CWM modes right now (if I don't do the Download Mode or Recovery Mode key combination, I am stuck on the Galaxy S III screen). Am I bricked at this point, or is there a way to get VRALE6.bootloader.zip onto my phone and continue with the ROM process?

It is important to note that I formatted the SD card before starting this process because I wanted enough space to put the Cyanogenmod file on it. However, I think I may have formatted it generically rather than into FAT-32. Could this be the issue?
I am going to pick up a microSD card reader today in order to flash the SD card to FAT-32 and put the CyanogenMod file on it.
I am getting 5 errors upon startup of CWM (E: Can't mount /cache/recovery/command, can't mount /cache/recovery/log, etc.). When I try to mount the SD card or external SD card, I get E: Can't mount /sdcard/

Same issue with sd card not mounting.
I'm having somewhat of the same issue. I've tried both Clockwork recovery and TWRP and have the same issue.
Should have mentioned that i still have access to the stock rom and can use my phone just fine.
I some how got Clockwork mod recovery to work using the Rom Manager pro App.
I wish i had been paying better attention to what i was doing but i know i updated CWMrecovery from in rom manager and chose to install my chosen rom with that.

My suggestion is to start over completely. There is a much easier way to do this.
My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. If it bootloops wipe data. Then use Ez-Unlock 1.2 app to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
My suggestion is to start over completely. There is a much easier way to do this.
My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. If it bootloops wipe data. Then use Ez-Unlock 1.2 app to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I am not familiar with TWRP, so is the process the same for flashing CM (putting CM zip file on sd card and going to install from SD card in TWRP)? Are there any additional steps beyond this?

I am following the directions in the thread linked above to root and install TWRP. So far, I have the rooted stock ROM running fine, but I can't get TWRP to work. I downloaded Goomanager and attempted to get TWRP using the Install Openrecovery Script option. However, it said that it couldn't find a recovery for my device. I also tried to use the adb method, but nothing happened after I put in the commands. I even tried to flash the latest TWRP .tar file from their website using Odin, but it keeps failing. Is there any way to get TWRP on my phone?
EDIT:Whoops, I skipped over the EZ-Unlock step. Now everything works. Thanks for the help, Sandman!

mikestrong19 said:
I am following the directions in the thread linked above to root and install TWRP. So far, I have the rooted stock ROM running fine, but I can't get TWRP to work. I downloaded Goomanager and attempted to get TWRP using the Install Openrecovery Script option. However, it said that it couldn't find a recovery for my device. I also tried to use the adb method, but nothing happened after I put in the commands. I even tried to flash the latest TWRP .tar file from their website using Odin, but it keeps failing. Is there any way to get TWRP on my phone?
EDIT:Whoops, I skipped over the EZ-Unlock step. Now everything works. Thanks for the help, Sandman!
Click to expand...
Click to collapse
No problem bro. Glad you are all fixed up
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
No problem bro. Glad you are all fixed up
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Alright, maybe I'm not quite fixed up yet. I have TWRP installed and I can go between TWRP, download mode, and the normal stock rooted ROM fine. However, I cannot get to the SD Card in TWRP in order to install CM. TWRP gives me the following errors upon booting into recovery:
E: Unable to find parition size for '/boot'
E: Unable to find parition size for '/data'
E: Unable to find parition size for '/recovery'
Updating partition details:
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: TWFunc: :Copy_Log - - Can't open destination log
E: Unable to mount '/cache'
Upon trying to go to Install, I am unable to select the external SD card, and an additional error appears when I attempt to touch Micro SD Card (E: Unable to mount '/external_sd').
I guess I could try to sideload the CM zip file through adb, but I would rather fix the SD card for future use. I have been researching and working on the SD card for the better part of today, to no avail. I am pretty sure the issue is in the formatting of the SD card (it appears to be RAW rather than the required FAT32 for CM), but I cannot format the SD card into FAT-32 no matter what I try (both Windows and 3rd party formatting tools). They all say that the SD card is either write-protected (I have already checked the read/write switch on the side of the SD card adapter) and/or the format cannot be completed. I have tried both my old SD card that I have kept for a few phones (an 8GB Samsung microSD card) and a brand new Sandisk 8GB microSD card, both of which will not work.
I am able to transfer files to the SD card with no issue (with both ADB and through dragging/dropping in Windows), but I cannot install from SD in recovery.
Does anyone have a solution to allow me to install CM on my phone?

Download root checker from the play store. Make sure you are rooted
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
Download root checker from the play store. Make sure you are rooted
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yes, I do have root access. I think the problem lies somewhere in my SD card.

mikestrong19 said:
Yes, I do have root access. I think the problem lies somewhere in my SD card.
Click to expand...
Click to collapse
Do you have another computer to try formatting the sdcard with? And you said that you receive the same errors when trying to reformat the new 8 GB sdcard as with your other sdcard which is formatted to RAW?

SlimSnoopOS said:
Do you have another computer to try formatting the sdcard with? And you said that you receive the same errors when trying to reformat the new 8 GB sdcard as with your other sdcard which is formatted to RAW?
Click to expand...
Click to collapse
I do have access to another computer, but I ran out of time and patience yesterday. I will try it when I get home later today. And yes, both cards are RAW (even the new one) and I can't get either one to format or work in TWRP.

So it appears the the issue with formatting was due to my computer's drivers (even though I installed the latest Samsung USB drivers) and not the SD card. I was able to format the SD card to FAT32 on another computer and put CM and GAPPS onto it. When booted normally into TouchWiz, the phone sees the SD card fine. However, I still get the same "Can't mount external SD card" error as well as the others previously listed when I attempt to install a zip from recovery. I even tried to sideload the ROM from ADB, but it still didn't work.

mikestrong19 said:
So it appears the the issue with formatting was due to my computer's drivers (even though I installed the latest Samsung USB drivers) and not the SD card. I was able to format the SD card to FAT32 on another computer and put CM and GAPPS onto it. When booted normally into TouchWiz, the phone sees the SD card fine. However, I still get the same "Can't mount external SD card" error as well as the others previously listed when I attempt to install a zip from recovery. I even tried to sideload the ROM from ADB, but it still didn't work.
Click to expand...
Click to collapse
Which version of CWM and also TWRP are you using?

And the problems keep rolling in. I was able to mount my SD card and get rid of the TWRP errors by installing a modded TWRP 2.6.0.0 from this thread (http://forum.xda-developers.com/showthread.php?p=44277901). However, when I go to install CM (cm-10.1.3-d2vzw.zip), I get the following error:
assert failed: getprop("ro.product.device") ==
E: Error executing updater binary in zip '/external_sd/cm-10.1.3-d2vzw.zip'
Error flashing zip '/external_sd/cm-10.1.3-d2vzw.zip'
Updating partition details
I did a factory reset before attempting to install this, but I did not format data or do anything else.

mikestrong19 said:
And the problems keep rolling in. I was able to mount my SD card and get rid of the TWRP errors by installing a modded TWRP 2.6.0.0 from this thread (http://forum.xda-developers.com/showthread.php?p=44277901). However, when I go to install CM (cm-10.1.3-d2vzw.zip), I get the following error:
assert failed: getprop("ro.product.device") ==
E: Error executing updater binary in zip '/external_sd/cm-10.1.3-d2vzw.zip'
Error flashing zip '/external_sd/cm-10.1.3-d2vzw.zip'
Updating partition details
I did a factory reset before attempting to install this, but I did not format data or do anything else.
Click to expand...
Click to collapse
Well, that is for the Sprint S3 my friend. We can't interchange recoveries between the different S3 models to flash roms. You may want to ask Kennyglass123 or any of those other guys if they can make a change for the VZW S3 for you to test it out.

SlimSnoopOS said:
Well, that is for the Sprint S3 my friend. We can't interchange recoveries between the different S3 models to flash roms. You may want to ask Kennyglass123 or any of those other guys if they can make a change for the VZW S3 for you to test it out.
Click to expand...
Click to collapse
Sounds good. I think the problem has been isolated to being something with needing a modded TWRP. I tried using an older, non-modded TWRP (2.5.0.0), which didn't work.

mikestrong19 said:
Sounds good. I think the problem has been isolated to being something with needing a modded TWRP. I tried using an older, non-modded TWRP (2.5.0.0), which didn't work.
Click to expand...
Click to collapse
Would you mind trying this soft brick fix? If I'm not mistaken, I believe you're experiencing this same issue--excluding the Sprint TWRP issue you just mentioned. You will need to flash your VZW custom recovery either through GooManager, Rom Manager, or Odin btw.

SlimSnoopOS said:
Would you mind trying this soft brick fix? If I'm not mistaken, I believe you're experiencing this same issue--excluding the Sprint TWRP issue you just mentioned. You will need to flash your VZW custom recovery either through GooManager, Rom Manager, or Odin btw.
Click to expand...
Click to collapse
I can still get between the stock rooted ROM, download mode, and recovery mode fine, so does that mean I am still soft-bricked and should try this?

mikestrong19 said:
I can still get between the stock rooted ROM, download mode, and recovery mode fine, so does that mean I am still soft-bricked and should try this?
Click to expand...
Click to collapse
Yea, because you are still receiving these errors right?
E: Unable to find parition size for '/boot'
E: Unable to find parition size for '/data'
E: Unable to find parition size for '/recovery'
Updating partition details:
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: TWFunc: :Copy_Log - - Can't open destination log
E: Unable to mount '/cache'
Click to expand...
Click to collapse
This soft brick fix is an attempt to correct the /system and /data errors.
Edit: Oh great, none of the links work. I'll see about finding alternate links.

[Q] How do I successfully Convert /data to F2FS from Ext4

Ok guys, just as the title states; I am having no luck in converting my /data filesystem to F2FS using TWRP versions 2.7.0.0 - 2.8.7.0 and its f***ing killing me as every other aspect of the tablet works flawlessly. I have modified many tablets/phones and I most definitely know what I am doing so hit me with whatever you've got and I will understand perfectly.
I am on the latest version of the bootloader and its unlocked
TWRP .2.8.7.0 recovery
flashed omni 5.1 and changed /data from ext3 to ext4
All diagnostic access points (Fastboot etc) work perfect and I've also enabled NVFLASH and have brickproofed myself using flatline.
Anytime I go to Repair/Change and choose F2FS for /data it simply fails and says the following
"Unable to wipe /data"
"Unknown MTP message Type 1"
"Error changing filesystem"
This has been for "EVERY" version of TWRP from 2.7 to Current 2.8.7.0 every time I try and I am about to break this thing over my leg.
I do not ever post unless I have done due diligence and combed/searched through the the forum using any string and phrase I can think of relating to the topic. All instructions which involve changing to F2FS within every post related to the topic have failed me. Absolutely ANY help on this would be GREATLY appreciated!!

i will share with you my experience with flashing the tf300t and formatting. everithing went smooth... just a lot of preparation...
firstly i flashed twrp 2.8.x.x from kang
http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479
than i copyed all needed files to my external SD card:
image file katkiss 5.1 #25
superSu
gapps image file
and K.A.T tool apk
device buttery must be full..
After being sure that i have everything on my sd card i entered twrp recovery and went to wipe everything exept of external sd card.
second i went to format /data to f2fs file system
third i flashed Katkiss image
fourth SuperSU for root access
fifth gapps
sixth wipe delvick/cache
Everyything went smooth as silk... hope that this helps you..

Error updating CM13, and others.

Hi, i have the next versions:
CyanogenMod: 13.0-20161004-NIGHTLY-osprey
Kernel: 3.10.49-MPI24.107-56-g09ff0d1
And when trying to install the 1009-NIGHTLY update i get an error without a log in the cianogenmod recovery. When I try to "Apply update" and then "Choose from emulated", it shows the next message:
"E:failed to mount /data (Invalid argument)
Installation aborted"
Then, i go to see the recovery logs, but it blanks and shows the main menu again.
Why do I want to update to the latest version, having 5 days of difference with the installed version?
Because I'm having repeatedly bugs with the Firefox browser, can't update Telegram, can't connect via Bluetooth to the most of the devices, can't update the binaries of SuperSU, and other minor errors.
Which could be the cause of some of this problems?
Sorry for my poor english, Saludos!

Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.

Henriquefeira said:
Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.
Click to expand...
Click to collapse
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?

Gonzon said:
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?
Click to expand...
Click to collapse
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you

Just as a side question, did anyone got AICP nightlies .zip stuck at extracting image to /system? I tried clean install (wipe /system, /data, /cache and dalvik) but its just stuck there. Tried multiple nightlies. Tried deleting Android and .android_secure folders in both external and internal storage. I haven't tried wiping internal storage yet (I will do it ASAP). Any tips will be great. Thanks
Broadcasted from Zeta Reticuli

Henriquefeira said:
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you
Click to expand...
Click to collapse
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Code:
[email protected]:~$ fastboot -p xxxxxxxxxx flash /data/media /home/imperial/Android2/cmupdater/cm-13.0-20161009-NIGHTLY-osprey.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 91972855 is not a multiple of the block size 4096
fastboot: /build/android-tools-hIu7Bj/android-tools-4.2.2+git20130529/core/libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Abortado
Do you know what it means?

Gonzon said:
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Do you know what it means?
Click to expand...
Click to collapse
You can't flash the zip of a ROM via fastboot, follow this tutorial >goo.gl/JfRzZu and on the next time avoid installing the CM bundled recovery

Solved.
I flashed vía fastboot a stable twrp, then after a lot of errors and strange things i was able to flash the ROM.
Thanks a lot for your help.
I was seeing a bricked phone already jajaja.

[Nook HD/HD+] REPIT: enlarge /system and /data partitions without wiping your data

you can now use REPIT to increase the size of the /system partition on the Nook HD/HD+ to 1 GiB to support the newest roms with gapps. while you do this, you can optionally also add 0.5 GiB of free space to /data. the extra space is repurposed from partitions that go unused in custom roms.
see the details here:
https://github.com/Lanchon/REPIT/issues/59
full doc for REPIT is here, please read it:
https://github.com/Lanchon/REPIT
additionally, this note can be interesting for users and rom developers alike:
https://github.com/Lanchon/REPIT/issues/56
this is for Nook HD+ only, but HD owners can request a port of REPIT by following the instruction in the doc page.
UPDATE: a port request was submitted by BultoPaco and now REPIT supports the Nook HD too.
thanks!

Lanchon said:
you can now use REPIT to increase the size of the /system partition on the Nook HD+ to 1 GiB to support the newest roms with gapps. while you do this, you can optionally also add 0.5 GiB of free space to /data. the extra space is repurposed from partitions that go unused in custom roms.
see the details here:
https://github.com/Lanchon/REPIT/issues/59
full doc for REPIT is here, please read it:
https://github.com/Lanchon/REPIT
additionally, this note can be interesting for users and rom developers alike:
https://github.com/Lanchon/REPIT/issues/56
this is for Nook HD+ only, but HD owners can request a port of REPIT by following the instruction in the doc page.
thanks!
Click to expand...
Click to collapse
This is great. Would also be helpful if you included information on how to go to stock partition layout, but big thanks indeed.

ajislav said:
This is great. Would also be helpful if you included information on how to go to stock partition layout, but big thanks indeed.
Click to expand...
Click to collapse
added to the github note.

Following the guide \https://github.com/Lanchon/REPIT/issues/59 to increase /data,
"you can also add approximately 0.5 GiB to /data"
Does it make difference if the Ovation is 16gb or 32gb model

king200 said:
Following the guide \https://github.com/Lanchon/REPIT/issues/59 to increase /data,
"you can also add approximately 0.5 GiB to /data"
Does it make difference if the Ovation is 16gb or 32gb model
Click to expand...
Click to collapse
this was made and tested with the 16GB version. in all other devices REPIT has been smart enough to adapt to these differences automatically. it should work with the 32GB version. but if there's anything strange or too different, REPIT will bail instead of messing up your device.

Ext4 only?
Mine returns an error not able to read superblock on data even if I am only trying to expand system. my data and cache are f2fs. Is that the problem? I'll cut/paste the log here when I'm back on my ovation.
This with the 3.0.2 twrp currently in experimental folder
Update: OK, went back and reread the general instructions. Looks like doesn't work for f2fs. I did convert cache to ext4 and set data=same, but still returned error.

Using Android 7 and latest TWRP on Nook HD+. Downloaded repit file zip, renamed as per instructions & downloaded delete stock rom zip. Flashed delete stock rom in twrp w/o problems. Flashed renamed repit file and Got error 1 after flashing. Told to reboot and flash from tmp folder and also got error 1. The error related to unable to reload partition table and unable to mount all partitions. Info from file manager shows using 5.11 GB out of 27.01 GB of internal storage
Any ideas???.

I just did this today.
I tried to flash lanchon-repit-XXXXXXXX-factory=same-system=1G-cache=112M+wipe-data=same-ovation.zip using twrp, but it gave me errors. I tried to follow the instructions to flash the file from the /tmp folder that it has copied, but it still gave me errors about /emmc partition not able to be umounted. I tried this a few times according to instructions posted on github but still no-go.
This is how I got around the issue:
I went into TWRP's Advanced menu and open up Terminal. Then I did
umount -a
There will be some errors that some partition cannot be umounted (eg. /tmp). I ignored that.
Now, I flashed the REPIT script again from /tmp folder. This will now run the script, but at the end, it will fail with the error about not being able to write /etc/fstab file. I ignored that (Android's file is /fstab.ovation).
Then I went ahead and flashed a cm13 build as usual. After rebooting into cm13, I opened up terminal and then did a df. I could see that /system partition had then expanded to 1034136 1-K blocks, which was roughly 1GB. Hoping that the partition will stay, I then flashed a gapps package, and it went through. On rebooting, I found that about 73% of the /system partition was used (it was around 55% without gapps). So, everything seems to look good.
Hope that helps.

tsoheq said:
I just did this today.
I tried to flash lanchon-repit-XXXXXXXX-factory=same-system=1G-cache=112M+wipe-data=same-ovation.zip using twrp, but it gave me errors. I tried to follow the instructions to flash the file from the /tmp folder that it has copied, but it still gave me errors about /emmc partition not able to be umounted. I tried this a few times according to instructions posted on github but still no-go.
This is how I got around the issue:
I went into TWRP's Advanced menu and open up Terminal. Then I did
umount -a
There will be some errors that some partition cannot be umounted (eg. /tmp). I ignored that.
Now, I flashed the REPIT script again from /tmp folder. This will now run the script, but at the end, it will fail with the error about not being able to write /etc/fstab file. I ignored that (Android's file is /fstab.ovation).
Then I went ahead and flashed a cm13 build as usual. After rebooting into cm13, I opened up terminal and then did a df. I could see that /system partition had then expanded to 1034136 1-K blocks, which was roughly 1GB. Hoping that the partition will stay, I then flashed a gapps package, and it went through. On rebooting, I found that about 73% of the /system partition was used (it was around 55% without gapps). So, everything seems to look good.
Hope that helps.
Click to expand...
Click to collapse
I tried following this unsuccessfully - any chance of an idiot's walkthrough?
I got as far as running the report file from tmp with no errors but when trying to flash Pico gapps I'm told it runs out of space. so close and yet I'm too thick to know what I'm doing wrong

gascomm said:
I tried following this unsuccessfully - any chance of an idiot's walkthrough?
I got as far as running the report file from tmp with no errors but when trying to flash Pico gapps I'm told it runs out of space. so close and yet I'm too thick to know what I'm doing wrong
Click to expand...
Click to collapse
What was the partition size when you do a "df" in a terminal? If it did expand, then the df command should show you the expanded /system partition size.

prsa01 said:
Mine returns an error not able to read superblock on data even if I am only trying to expand system. my data and cache are f2fs. Is that the problem? I'll cut/paste the log here when I'm back on my ovation.
This with the 3.0.2 twrp currently in experimental folder
Update: OK, went back and reread the general instructions. Looks like doesn't work for f2fs. I did convert cache to ext4 and set data=same, but still returned error.
Click to expand...
Click to collapse
f2fs partitions cannot be resized without wiping on planet earth. if there exists an f2fs resize tool, only aliens have it.
you can can wipe data (not recommended) or you can flash the standard repit to simply grow /system with /cache if you want. /data will not be enlarged of course.
f2fs on /cache is stupid, don't ever do it!!! only /data should be f2fs.

acr123 said:
Using Android 7 and latest TWRP on Nook HD+. Downloaded repit file zip, renamed as per instructions & downloaded delete stock rom zip. Flashed delete stock rom in twrp w/o problems. Flashed renamed repit file and Got error 1 after flashing. Told to reboot and flash from tmp folder and also got error 1. The error related to unable to reload partition table and unable to mount all partitions. Info from file manager shows using 5.11 GB out of 27.01 GB of internal storage
Any ideas???.
Click to expand...
Click to collapse
this has been explained to death now, read the REPIT docs for the solution. create a github issue WITH THE REQUIRED INFO (as detailed in the docs) if you need official support.

tsoheq said:
I just did this today.
I tried to flash lanchon-repit-XXXXXXXX-factory=same-system=1G-cache=112M+wipe-data=same-ovation.zip using twrp, but it gave me errors. I tried to follow the instructions to flash the file from the /tmp folder that it has copied, but it still gave me errors about /emmc partition not able to be umounted. I tried this a few times according to instructions posted on github but still no-go.
This is how I got around the issue:
I went into TWRP's Advanced menu and open up Terminal. Then I did
umount -a
There will be some errors that some partition cannot be umounted (eg. /tmp). I ignored that.
Now, I flashed the REPIT script again from /tmp folder. This will now run the script, but at the end, it will fail with the error about not being able to write /etc/fstab file. I ignored that (Android's file is /fstab.ovation).
Then I went ahead and flashed a cm13 build as usual. After rebooting into cm13, I opened up terminal and then did a df. I could see that /system partition had then expanded to 1034136 1-K blocks, which was roughly 1GB. Hoping that the partition will stay, I then flashed a gapps package, and it went through. On rebooting, I found that about 73% of the /system partition was used (it was around 55% without gapps). So, everything seems to look good.
Hope that helps.
Click to expand...
Click to collapse
you didn't need to reflash system of course, REPIT keeps the data as explained in the docs. glad it worked.
btw, it is enough to follow the docs about unmounting partitions using the TWRP UI.

gascomm said:
I tried following this unsuccessfully - any chance of an idiot's walkthrough?
I got as far as running the report file from tmp with no errors but when trying to flash Pico gapps I'm told it runs out of space. so close and yet I'm too thick to know what I'm doing wrong
Click to expand...
Click to collapse
read the docs, everything is there. you can't be helped if you don't provide the REPIT log. (that is also stated in the docs, btw.)

Can confirm this works on 32gb ovation. Just finished after a bit of fighting. As always, YMMV but this was the process I followed:
Ran the delete file. Success.
Ran the resize file, errors.
Ran the resize file from tmp, errors.
Ran "umount -a" from terminal then reran resize from tmp, errors.
I found both my data and cache partitions were f2fs. Formatted both back to ext4 since f2fs cannot be resized. This was easy for me as I had all the important stuff backed up but be sure to back your data up before doing this, it will wipe the partition.
After the wipe I loaded one file on to the data drive, the renamed resize file.
Tried running the resize file. Unmount errors and the run from tmp message.
Went into terminal, ran "umount -a" 3 times. The first I got several errors, the second and third only one.
Went into tmp and ran the file. After realizing the process was working and was going to take a while, I plugged up the charger (wall, not pc) and let it set overnight.
Came back this morning to one error, the fstab error. No unmount errors though.
Remounted the drives in twrp and ran "df" in terminal. 1gb system.
Rebooted and ran through the setup
Reloaded my roms/gapps folder manually via USB
Rebooted to TWRP and ran opengapps pico. Completed succesfully.
Rebooted and had play store in apps. Logged into gapps.
Thank you Lanchon, this helps bring life back to an old love.

asksmity said:
Can confirm this works on 32gb ovation. Just finished after a bit of fighting. As always, YMMV but this was the process I followed:
Ran the delete file. Success.
Ran the resize file, errors.
Ran the resize file from tmp, errors.
Ran "umount -a" from terminal then reran resize from tmp, errors.
I found both my data and cache partitions were f2fs. Formatted both back to ext4 since f2fs cannot be resized. This was easy for me as I had all the important stuff backed up but be sure to back your data up before doing this, it will wipe the partition.
After the wipe I loaded one file on to the data drive, the renamed resize file.
Tried running the resize file. Unmount errors and the run from tmp message.
Went into terminal, ran "umount -a" 3 times. The first I got several errors, the second and third only one.
Went into tmp and ran the file. After realizing the process was working and was going to take a while, I plugged up the charger (wall, not pc) and let it set overnight.
Came back this morning to one error, the fstab error. No unmount errors though.
Remounted the drives in twrp and ran "df" in terminal. 1gb system.
Rebooted and ran through the setup
Reloaded my roms/gapps folder manually via USB
Rebooted to TWRP and ran opengapps pico. Completed succesfully.
Rebooted and had play store in apps. Logged into gapps.
Thank you Lanchon, this helps bring life back to an old love.
Click to expand...
Click to collapse
you are welcome!
lol! why not read the docs???
if you wanted to change the file system in /data to ext4 all you needed was to change:
-cache=32M+wipe-data=max
to:
-cache=32M+wipe-data=max+wipe
which is the same as:
-cache=32M+wipe+ext4-data=max+wipe+ext4
given that ext4 is the default fs for /data and /cache.
using -data=max+wipe would have been so much faster than moving a huge empty partition around!!! it would have finished the operation in around a minute. not to mention adding less wear and tear to the emmc of your aging device.
the file system in /cache was never a problem, you did not need to change it back to ext4. you were using -cache=32M+wipe which means that REPIT would resize/move the partition without keeping its contents (wiping) and without regard for the previous file system type and state (ie, whether it had errors, etc).
if you wanted to enlarge /data AND ALSO KEEP /DATA AS F2FS, all you needed was to change:
-cache=32M+wipe-data=max
to:
-cache=32M+wipe-data=max+wipe+f2fs
f2fs cannot be resized, but it can be moved/resized while wiping. (ie, the partition can be recreated from scratch with the new size, if data retention is not required.) this is all explained in the docs, seriously lol...
https://github.com/Lanchon/REPIT#partition-types
using an f2fs /cache partition is dumb and completely useless. all who have f2fs /cache are adviced to change /cache back to ext4 and leave it that way.
regarding the umount stuff, maybe your TWRP has an issue, but i'm willing to bet that if you followed instructions to the letter, you wouldn't have needed all that. the guy that requested the ovation port of repit (look for the github issue (closed now)) and first ran the test version did not have any of this issues. the TWRP he used is documented in the port request.
anyway, thank you very much for documenting what worked for you!

Lanchon said:
you are welcome!
lol! why not read the docs???
if you wanted to change the file system in /data to ext4 all you needed was to change:
-cache=32M+wipe-data=max
to:
-cache=32M+wipe-data=max+wipe
which is the same as:
-cache=32M+wipe+ext4-data=max+wipe+ext4
given that ext4 is the default fs for /data and /cache.
using -data=max+wipe would have been so much faster than moving a huge empty partition around!!! it would have finished the operation in around a minute. not to mention adding less wear and tear you the emmc of your aging device.
the file system in /cache was never a problem, you did not need to change it back to ext4. you were using -cache=32M+wipe which means that REPIT would resize/move the partition without keeping its contents (wiping) and without regard for the previous file system type and state (ie, whether it had errors, etc).
if you wanted to enlarge /data AND ALSO KEEP /DATA AS F2FS, all you needed was to change:
-cache=32M+wipe-data=max
to:
-cache=32M+wipe-data=max+wipe+f2fs
f2fs cannot be resized, but it can be moved/resized while wiping. (ie, the partition can be recreated from scratch with the new size, if data retention is not required.) this is all explained in the docs, seriously lol...
https://github.com/Lanchon/REPIT#partition-types
using an f2fs /cache partition is dumb and completely useless. all who have f2fs /cache are adviced to change /cache back to ext4 and leave it that way.
regarding the umount stuff, maybe your TWRP has an issue, but i'm willing to bet that if you followed instructions to the letter, you wouldn't have needed all that. the guy that requested the ovation port of repit (look for the github issue (closed now)) and first ran the test version did not have any of this issues. the TWRP he used is documented in the port request.
anyway, thank you very much for documenting what worked for you!
Click to expand...
Click to collapse
Very good info above!
I could have done that as well, and probably should have. But there was conformation in the thread that the options I renamed to worked. So for me being a "part timer" I wanted to make sure that I was not the reason for the issue (ie: fat fingering an extra letter in one of the options or misplacing an option). I have a bad habit of screwing things up.
As a recommendation, it might be a good idea to include some of these sample options in you main thread and explain what they do. I know I know, docs docs docs but it helps us roughians and would probably keep the issue posts down.
Thanks again for the tool and the feedback!

I read all the docs and used Lanchon's tip above to wipe /data and retain f2fs file structure. Got an error running it from my SD card but, when I ran it from the internal tmp folder (as instructed), it worked perfectly. Thank you @Lanchon! I'm going to request a Hummingbird version so I can have both of my Nooks optimized?
Sent from my Nook HD using Tapatalk

Is this supposed to provide more space for Gapps? I ran this and it worked with no errors, but I can't install any different sized gapps than nano.
EDIT: nano is still too big too.

Jazviper said:
Is this supposed to provide more space for Gapps? I ran this and it worked with no errors, but I can't install any different sized gapps than nano.
EDIT: nano is still too big too.
Click to expand...
Click to collapse
read:
https://github.com/Lanchon/REPIT/issues/56
tl;dr: you can fix this by pressing the resize partition button on twrp.

TWRP Backup

Howdy folks! New to android/honor 8 and I've been fiddling with it some. So far I've rooted, installed TWRP, SU and Xposed successfully. I've been trying to make a nandroid before completely ****ing up my device, but each time I try I get errors before completion...mainly at the end of the backup I get an error 255 or an error opening the backup directory (internal).
Anyone successfully back up their honor 8 with TWRP?
Appreciate any advice!

I have a copy of my stock rooted ROM with Xposed. What error are you getting? I'm backing mine up to the External SDcard.

Ascertion said:
I have a copy of my stock rooted ROM with Xposed. What error are you getting? I'm backing mine up to the External SDcard.
Click to expand...
Click to collapse
Most recently I'm getting this -
Backing up System...
createTarFork() process ended with ERROR: 255
Been trying to backup 3 partitions - data, system & boot using compression.
Here's some of the recovery.log file too -
Backing up System...
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000'
I:Using compression...
Error opening: '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' (No such file or directory)
I:Error creating tar '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' for thread 0
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.

fauxfive55 said:
Most recently I'm getting this -
Backing up System...
createTarFork() process ended with ERROR: 255
Been trying to backup 3 partitions - data, system & boot using compression.
Here's some of the recovery.log file too -
Backing up System...
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000'
I:Using compression...
Error opening: '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' (No such file or directory)
I:Error creating tar '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' for thread 0
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
Click to expand...
Click to collapse
Try backing up to external SD.
Sent from my Galaxy Tab 3 using XDA Labs

I have the same issue. I can't do a backup with TWRP. System, data and boot. It always ends with an error.
I have tried every storage, internal, SD, and OTG drive. Reflashed TWRP. Nothing seems to do any difference. Drives me crazy. Any solution?

just flash stock recovery then flash again TWRP . format SD throw recovery only then try backup should work . happened with me before ! .

Romiui said:
just flash stock recovery then flash again TWRP . format SD throw recovery only then try backup should work . happened with me before ! .
Click to expand...
Click to collapse
Unfortunately that didn't work. Tried flashing stock recovery and back, same thing. Then I flashed latest firmware (total reset), unlocked bl, flashed official TWRP and latest SuperSU. No success. ?
The issue is (or seem to be) data partition fail to mount, or does unmount during backup.
Can't be just me and OP struggling with this.

its really rare issue . i got that problem but honestly it get fixed after that solution !

Backup all other partitions except for the one that fails for now then as that is all you need to fix a bootloop etc and use Ti backup to get the apps etc

Hello,
I'm experiencing the same error when trying to backup to internal memory. I haven't yet tried to flash stock recovery back and after flash TWRP again to check if it solves the problem though.
RM

fauxfive55 said:
Most recently I'm getting this -
Backing up System...
createTarFork() process ended with ERROR: 255
Been trying to backup 3 partitions - data, system & boot using compression.
Here's some of the recovery.log file too -
Backing up System...
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000'
I:Using compression...
Error opening: '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' (No such file or directory)
I:Error creating tar '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' for thread 0
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
Click to expand...
Click to collapse
I think this has been suggested already but I'm not certain:
Since the only error you're showing us (and maybe getting) is on /system partition Target (backup target), then how about trying unchecking that and doing the backup and seeing if you can get the same error (or not) on the other two (/data and /boot). ? Another thing maybe worth a shot is a completely benign partition like /cache and it's small for a quick test, maybe just give that a try. It'd be good to know that anything at all can be backed up in your version of TWRP.
Just want to see if it's something special about /system [target]. Also have you told us here which version from which thread you got TWRP from? Just curious. For Honor8 there seems to be so many TWRP authors that aren't too sure of their versions of TWRP (yet). Good luck.

hachamacha said:
I think this has been suggested already but I'm not certain:
Since the only error you're showing us (and maybe getting) is on /system partition Target (backup target), then how about trying unchecking that and doing the backup and seeing if you can get the same error (or not) on the other two (/data and /boot). ? Another thing maybe worth a shot is a completely benign partition like /cache and it's small for a quick test, maybe just give that a try. It'd be good to know that anything at all can be backed up in your version of TWRP.
Just want to see if it's something special about /system [target]. Also have you told us here which version from which thread you got TWRP from? Just curious. For Honor8 there seems to be so many TWRP authors that aren't too sure of their versions of TWRP (yet). Good luck.
Click to expand...
Click to collapse
This is interesting, because I have the same problem as well. I've tried backing up to internal as well as SD. I've also tried doing a full reset, flashing back to TWRP and same issue. No matter what partition I try, it always fails with the same error 255. I followed this thread exactly: http://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946.
Doesn't seem as rare of an issue as initially thought. Any ideas?

joesee said:
This is interesting, because I have the same problem as well. I've tried backing up to internal as well as SD. I've also tried doing a full reset, flashing back to TWRP and same issue. No matter what partition I try, it always fails with the same error 255. I followed this thread exactly: http://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946.
Doesn't seem as rare of an issue as initially thought. Any ideas?
Click to expand...
Click to collapse
It looks like only 2 of the replies in this thread show any hint of success, and even they didn't specifically say they'd done a backup and recovery. I'd kind of like to see a log from a successful backup & recovery before spending much time on this version of TWRP. If it just doesn't work and from every TWRP thread I've read, lots of people are having problems on this phone, so it might not work. I still don't know which version of recovery you all are using and am wondering if it's the official one from twrp.me site? Also, I suppose you'd have to be on android 6 for that to work.
Anyway, I just got mine today (H8), and am seeing if I can live with the size (I really like the 4.6" form factor better), but I really like how things function so far. If I get to the point where I've got Nougat installed without rooting it and still haven't decided to get a refund, then I'll go ahead and do all this stuff and see if I can help. I worked on a bunch of variants of Philz recovery long ago (and it could be completely irrelevant) so I need to look at the TWRP code and try another take on it. For me, one of the best things about rooting is the custom backup and recovery where it actually does those two things perfectly. I guess with the different CPU that there's still a lot of flailing in development land.
One of the few things I really recall being possibly relevant from Philz was how often people who were writing for various devices screwed up the only path to the root of the target by picking one that was either a) a soft link with bad permissions or b) not exactly the right spot. Just because TWRP says "external SD" (or whatever it says) doesn't mean much it's not pointing to something you can write to. I was using a Synology app named DS files today to get some stuff on the H8 and it wouldn't let me put them on the sdcard because it thought I hadn't given permissions to the DS File app. Does that make any sense? I just navigated around until I found a better path to the sdcard that had permissions because there was no way to give sdcard permissions to that app.

Has anyone pointed this out to @LastStandingDroid ?
those were all the same problems I had.

clsA said:
Has anyone pointed this out to @LastStandingDroid ?
those were all the same problems I had.
Click to expand...
Click to collapse
I found LSD seem to be aware about this in his nougat 3.0.2.0 recovery.
He wrote something about data partition unmounting being fixed.
Not sure if this is a known Marshmallow issue though.

Hello!
I've followed the suggestion of flashing stock recovery and after that TWRP but it did not made any difference, same error while backing up DATA.
But, after that I tried disabling compression and it worked OK. I've made a second try and it worked again. After this second successful run, I've tried a third time, but this time with compression enabled again, result.. Error...
Not a very scientific test, but it suggests the error has something to do with the compression.
RM

omartins said:
Hello,
I'm experiencing the same error when trying to backup to internal memory. I haven't yet tried to flash stock recovery back and after flash TWRP again to check if it solves the problem though.
RM
Click to expand...
Click to collapse
Currently there is no data partition backup support
Sent from my KIW-L22 using Tapatalk

I've not tried to restore the backup I've made supposedly successfully with compression disabled, but, I didn't get any error during the backup operation...
RM

Thanks
Thanks Boss love u

Hi there!
Today I've used TWRP Data backup to restore app settings, using TiBu. I can confirm the backup was useful, hence well successfully made.
RM