Hello
While trying to restore my backup data from advanced restore in CWM after doing an update to the latest FXP139, I get an error message saying this:
Code:
e: format_volume make_extf4fs failed on /dev/block/mmcblk0p14
I have gotten this message before but last time I updated it worked fine. Seems to happen pretty randomly.
I'm following these steps while updating:
> First make a nandroid! IMPORTANT
> Flash Bin4ry's recovery image <here> (Instructions in thread)
> Reboot phone and it will automatically boot into recovery
> Format /system
> Wipe data/factory reset
> Wipe Dalvik Cache
> Flash ROM
> Flash GApps
> Reboot and let the initial setup take place (Not sure whether this is necessary but just do it to be safe)
> Reboot into recovery
> Go into backup and restore, choose advanced restore, select your backup and select restore /data
> Finally reboot and you should be upgraded with all your data preserved
Does anyone have a clue why this is happening?
Thanks!
Did anyone ever address this. I am having the same issue and in my case i cannot use the restore process at all
http://forum.xda-developers.com/showthread.php?t=2163141
Related
Guys, I am trying to install a new ROM, using this site:
forum.xda-developers com/showthread.php?t=645253
(can't post links yet)
I can't see this:
-> Select Backup/Restore > Nand backup > confirm with Home > Wait
(or Nand + Ext if you have A2SD setup)
The only options I have is :
reboot system now
apply sdcard:update.zip (which doesn't work)
wipe data/factory reset
Can someone please tell me how to do this Nand backup?
Also, my phone isn't picked up by the computer or vice versa when its in recovery mode. Thanks so much guys!
Kr1tikalMas said:
Guys, I am trying to install a new ROM, using this site:
forum.xda-developers com/showthread.php?t=645253
(can't post links yet)
I can't see this:
-> Select Backup/Restore > Nand backup > confirm with Home > Wait
(or Nand + Ext if you have A2SD setup)
The only options I have is :
reboot system now
apply sdcard:update.zip (which doesn't work)
wipe data/factory reset
Can someone please tell me how to do this Nand backup?
Also, my phone isn't picked up by the computer or vice versa when its in recovery mode. Thanks so much guys!
Click to expand...
Click to collapse
You need to root your phone first and install the Clockworkmod recovery, for rooting try to use this tutorial http://forum.xda-developers.com/showthread.php?p=8258942 rooting will void your warranty so be careful!
After that go to the android market and look for Rom Manager, open the app and select "Flash Clockworkmod Recovery", after that turn off your phone, load Hboot (by pressing the volume down button and the power button) and you should be able to find the options that you're looking for!
I'm going to be ROM-ing for the first time (well, other than Safestrapping the Bionic for a day or two) and want to make sure I have the right thought in terms of running and upgrading a ROM over the long term. If I'm moving to AndroWook as my daily driver, I want to make sure I have a good procedure in place for quickly and easily upgrading to the latest version of the ROM.
The following is my understanding of this whole process. Is this procedure correct? My main concern is making sure I am doing everything right to be able to quickly update to the latest version of the ROM when it comes out, not spend a day re-configuring. Is there anything I am missing?
BACKGROUND: Partitions
Main Partitions Involved With Wiping
/system = Where the OS lives, along with the apps that are preinstalled
/data = Where user installed programs & their associated data/settings live. This data/settings is the part that gets deleted when you go Settings -> Applications -> pick an application and click "Clear Data". This is what Titanium Backup backs up for user apps (both the "apps" and "data" backed up live here). Also has SMS, contacts, settings, etc... the "system data" in TiBu
/cache = Cache files that help programs to load quickly. Harmless to wipe, as it will regenerate.
/sdcard = Internal sd card area where you keep files and use file manager. some programs also put files here. Not usually wiped.
external sdcard = Physical external sd card, if applicable. Not usually wiped.
Other partitions
/boot = Kernel and ramdisk. Don't wipe unless you fix it before rebooting.
/recovery = Where the recovery (stock or custom) lives.
/misc = Other settings not normally touched.
BACKGROUND: Types of Wiping
Cache = harmless. Cache regenerates itself over time to speed up phone.
Dalvik = harmless. This is simply another cache, this one having to do with Java.
Factory Reset = wipe /data and /cache. internal and external sdcard is NOT wiped
Wipe system = wipes /system (where the os and its preinstalled apps live)
Format data = wipes /sdcard (the internal sdcard)
Format external sd = wipes external sd card
ASSUMPTIONS & NOTES
You are rooted
You have Titanium Backup (TiBu)
For multi-user environment, modify the instructions to account for the need to backup/restore with TiBu for each user. Backup for each user, flash, then restore for each user.
BACKING UP
1. TiBu: Batch Backup all user apps & data (everything) in current ROM
2. TiBu: Batch verify the backup
3. Make a sketch of how your widgets/homescreen is supposed to look
4. If you are doing a total deep clean that wipes sdcard (generally not), here is where we want to back up anything else (sdcard files, etc)
5. File Manager: Backup apk for both TiBu & TiBu Pro to SD card
Alternate: Do nothing now, and we use market in new ROM later​6. Download ROM & put on SD
WIPING & FLASHING
This part subject to change based on ROM maker's recommendations
1. Boot into recovery
2. Wipe and flash:
Option A: Clean flash (typically done, does NOT wipe sdcard):
1. Factory reset
2. Wipe cache
3. Wipe dalvik
4. For a total deep clean (not usually done, DOES wipe sdcard): Wipe system; Format data
5. Flash zip
Option B: Dirty Flash (usually only OK for minor updates):
1. Wipe cache
2. Wipe dalvik
3. Flash zip
4. There is no need to set up the ROM again in this case.
SETTING UP NEW ROM
1. Boot into new ROM
It will take 30-60 minutes to get up to full speed. After that time, it will be full speed after a reboot.
You can tell it to keep backed up to Google (backups up TO Google), but tell it NOT to restore from Google right now (restores FROM Google right now).
2. System > Applications > Unknown Sources
Restore TiBu & TiBu Pro from apk backup
Alternate: get from market
3. TiBu: Batch Restore system data - ONLY THE GREEN ITEMS
Do not restore red items
Do not restore user stuff yet. We are doing system stuff first.
Note that icons will not show correctly yet... nothing to be concerned about.
If the new ROM is vastly different, take care to restore only what is necessary.
4. Reboot
5. TiBu: Batch Restore missing apps with data - ONLY THE WHITE ITEMS
6. Click Market Doctor to verify that everything is hooked back up to the Market OK
7. Fix up homescreen - widgets & wallpaper
One by one, delete empty Widget then add new one.
Also choose the wallpaper you want
8. Check:
Date & time, alarms, ringtone, voicemail number, other settings
Anti-theft is operating properly
9. Market Place > My apps > Update any other apps
10. If over the course of time you find any apps giving problems, use the market to uninstall them and reinstall them to clear out any problems it may have had in restoring from TiBu
I just glanced thru that and this is what I saw quickly.
Option A: clean flash..... I always wipe system as well. This is not a big deal if you don't do it because I format the system in the installer in case people have forgotten.
I also delete cache and dalvik in the installer also in case people forget but I still end up doing them on the wipe page.
The only one really you need to use for a major version update is factory reset. This is just on my rom tho.. I can't speak for how others do it so always best to do the manual wipes also.
Tibu : It is never advised to restore system apps. Even between minor updates in case I have changed a system app.
If there is one that you really need restored then try restoring just the data for that one app and test it properly.
In the installer I do not write all apps to system anyway. There is very little in there that would take more than a few seconds to set back up.
Hi, i'm new on this thread, today i get this from my brother with Android 2.1 and he ask me for and update to 4.3 or 4.4.
Using this tutorial i install success 4.0,
https://www.youtube.com/watch?v=rqxearzXrVY
and using this rom update to 4.4
http://forum.xda-developers.com/showthread.php?t=2535547
to this point all well...but i get the error about Invalid IMEI....i back to 2.1, backup efs, update againt to 4.0.
Now when i try install 4.4, the CWM can't install 4.4. I try many roms but it's the same problem...
When try install 4.4:
----------------------------Try 1----------------------------
1.Clean chache partition......OK
2.Clean dalvik-cache............OK
3.Istall ROM...........................Error Status 0....or Error Status 7
----------------------------Try 2----------------------------
1.Clean chache partition......OK
2.Clean dalvik-cache............OK
3.Format /system..................OK
4.Install ROM.........................Reboot -> CWM -> reboot -> CWM (BOOTLOOP)
----------------------------Try 3----------------------------
1.Clean chache partition......OK
2.Clean dalvik-cache............OK
3.Format /system..................OK
4.Restore CWM backup......Reboot -> CWM -> reboot -> CWM (BOOTLOOP)
when i get a BOOTLOOP whit this kernel
http://forum.xda-developers.com/showthread.php?t=2330998
and the option "AROMA", check the /SYSTEM and this is empty (0 files)
I never had a similar problem. Help me please :crying:. Any idea
Solved
solved, only format all directories including boot.
ZeroDrako said:
solved, only format all directories including boot.
Click to expand...
Click to collapse
I'm having similiar problems. How do you 'format' all directories?
Jut Flash this kernel GearKernel - Universal
-Factory Reset
-Wipe Cache
-Wipe Dalvik Cache
Then go to mounts and storage and format all directories....except the sdcard
that's all....
I wiped my my system by choosing "Clean to Install a New ROM" in Philz Touch Recovery. Does anyone have the stock firmware for Virgin Mobile HTC Desire 601? I've tried OTA_ZARA_CL_K44_SENSE55_MR_Sprint_WWE_VM_2.15.652.3-1.10.652.9_R3_release_378339 and I keep getting errors.
http://forum.xda-developers.com/showthread.php?t=2804427
Child's Play said:
http://forum.xda-developers.com/showthread.php?t=2804427
Click to expand...
Click to collapse
Thanks Childs-Play. I tried the OTA that I got from a member's google drive and I got the status 7 error, so I removed the "assert" lines in the updater-script file and I get the "....Updating Package....Installing Package...failed".
Is there a particular file under the Zara CL list that I should be using?
I've also tried to do an "adb push systembackupfolder /system/" by using a system dump i found, and after rebooting from the recovery, the files are gone.
Theres a file called system backup under the zara-cl list. Download it and unzip then drag the folder to sd card/cwm/backup or internal storage/cwm/backup then get into recovery and go to backup and restore and select restore then choose the folder that u downloaded and u r ready to flash a rom
Child's Play said:
Theres a file called system backup under the zara-cl list. Download it and unzip then drag the folder to sd card/cwm/backup or internal storage/cwm/back then get into recovery and go to backup and restore and select restore then choose the folder that u downloaded and u r ready to flash a rom
Click to expand...
Click to collapse
This is what happens when i follow your steps :
- Backup And Restore > Restore from /sdcard (I get "no files found")
- Backup And Restore > Custom restore job from /sdcard > Start Custom Restore Job (I get "nothing to restore in /sdcard/clockworkmod/backup")
- Backup And Restore > Restore from /storage/sdcard1 > kk_stock_dump/ > "Yes - Restore" (I get "Checking MD5 sums... MD5 mismatch!")
- Backup And Restore > Custom Restore from /storage/sdcard1 > Start Custom Restore Job > kk_stock_dump/ > (I select build.prop) > Yes Restore kk_stock_dump (I get "/storage/sdcard1/clockworkmod/backup/kk_stock_dump will be restored to a selected partitions! Checking MD5 sums... MD5 mismatch!")
Any idea what I'm doing wrong?
_____________________________________________________________________________________________
UPDATE
So I turned off MD5 check in the recovery settings, and did Restore from /storage/sdcard1
Now I get
>>Restoring /boot...
Using raw mode
boot.image not found. Skipping restore of /boot
>> Restoring /system
No system backup found(img, tar, dup). Skipping restore of /system
>> Restoring /data...
No data backup found(img, tar, dup) Skipping restore of /data
>> Restoring /cache...
No cache backup found(img, tar, dup) Skipping restore of /cache. Volume not found! Skipping restore of /sd-ext...
Finalizing, please wait...
Restore complete!
Restore time: 00:00 mn
press any key to continue.
R u on jellybean or kitkat? I assume u r on kk. We dont have cwm recovery for kk. U need to flash twrp
I had TWRP on it before and I was trying to adb push the system dump directly to the /system folder and the files wouldn't persist. I'll try again in TWRP using both methods, TWRP's restore function and adb push of the dump to the /system folder. Am I correct to still use the KK dump, or should I use JB instead in this case?
n_r said:
I had TWRP on it before and I was trying to adb push the system dump directly to the /system folder and the files wouldn't persist. I'll try again in TWRP using both methods, TWRP's restore function and adb push of the dump to the /system folder. Am I correct to still use the KK dump, or should I use JB instead in this case?
Click to expand...
Click to collapse
if u r on kk, u need to download the kk system backup from xXminiWHOOPERxX's link then follow my instructions. forget abt using adb
Child's Play said:
if u r on kk, u need to download the kk system backup from xXminiWHOOPERxX's link then follow my instructions. forget abt using adb
Click to expand...
Click to collapse
Followed your instructions and made some progress but now this is what I get:
[RESTORE STARTED]
Restore folder: '/external_sdcard/TWRP/BACKUPS/HT3ABSD01726/KK_stock_system_dump'
Skipping MD5 check based on user setting.
E:No partitionss selected for restore.
Any ideas on what I'm doing wrong?
No not the system dump file. I meant a diff 1. Its the system backup file
n_r said:
Followed your instructions and made some progress but now this is what I get:
[RESTORE STARTED]
Restore folder: '/external_sdcard/TWRP/BACKUPS/HT3ABSD01726/KK_stock_system_dump'
Skipping MD5 check based on user setting.
E:No partitionss selected for restore.
Any ideas on what I'm doing wrong?
Click to expand...
Click to collapse
This is not a flashable zip file.
What is your bootloader 2.20 or 2.22?
Probably kk
So good news I found this https://docs.google.com/file/d/0B8-7I2_Vt73ldUNPd2c4X0xoQXc/edit zara_cl442.zip on the same thread, I unarchived the files and put them in my twrp/backups/phoneserialnumber/ folder and did a successful restore!
Thanks guys!!:victory:
Now I'm getting strange behaviour.......my phone reboots at random. It seems to reboot every 2-5mins ....Well at least now I know how to do a restore with TWRP....:highfive:
Not sure why it happens
After the last maybe....20 random reboots.......it seems that the random rebooting has stopped.
n_r said:
After the last maybe....20 random reboots.......it seems that the random rebooting has stopped.
Click to expand...
Click to collapse
I create for you flashable zip. Uploading to google drive. Wait cca one hour.
Edit. Here is flashable zip Stock Virgin mobile rom for you Zara CL. In recovery wipe cache, dalvik cache and format system before flash.
https://drive.google.com/file/d/0B6bGr-ir8saMSG5jN0dFN1o5YWs/edit?usp=sharing
standak14 said:
I create for you flashable zip. Uploading to google drive. Wait cca one hour.
Edit. Here is flashable zip Stock Virgin mobile rom for you Zara CL. In recovery wipe cache, dalvik cache and format system before flash.
https://drive.google.com/file/d/0B6bGr-ir8saMSG5jN0dFN1o5YWs/edit?usp=sharing
Click to expand...
Click to collapse
Thanks a lot standak14 . I flashed zara UL to my phone and got the same random reboot issue, turns out its SuperSU(force closed it and everything became fine). I wish it was possible to disable the simlock on this phone though. I'm Never buying a Virgin Mobile again.
standak14 said:
I create for you flashable zip. Uploading to google drive. Wait cca one hour.
Edit. Here is flashable zip Stock Virgin mobile rom for you Zara CL. In recovery wipe cache, dalvik cache and format system before flash.
https://drive.google.com/file/d/0B6bGr-ir8saMSG5jN0dFN1o5YWs/edit?usp=sharing
Click to expand...
Click to collapse
When I flashed this zip I thought it was stock kitkat for zara_cl. However it would not make my phone boot.
Edit: I'm now realizing this is likely because of hcheck or custom boot.
My phone is basically unbootable after a shutdown due to low battery. Things I tried:
1. Wipe System+Cache -> Flash ROM
(Result: Stuck at boot animation)
2. Wipe System+Data+Cache -> Flash ROM
(Result: Bootable)
3. Wipe System+Data+Cache -> Flash ROM -> Restore Data
(Result: Stuck at boot animation)
4. Wipe System+Data+Cache -> Flash ROM -> Restore Data -> Delete /data/system
(experiment)
(Result: Bootable system but Android warns system unstable till factory reset, Apps can launch but behave as if no previous state)
Can I conclude that there is something wrong with my data partition?
Strategy 1
What are the files I could try to minimally delete/modify to get it bookable and have my existing data intact? Or please guide me know how to trace to the problematic files/folders.
Strategy 2
I do have a TWRP Data partition backup before I did the various (dumb) experiments. If I were to start from scratch, how to I copy over /data/data (which I am guessing where all app's data is at) to restore the previous state?
I have tried to:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash and replace the /data/data folder, does not boot
Also tried:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash, boot.
4. Download a single app.
5. Went to TWRP and copy only the app's backup data folder to /data/data
6. Boot to system and launch app. Apps crashes.
7. I understand it has something to do with permissions and I have out of frustration, used an app to allow all actions (I believe a 777 chmod equivalent?) and set the owner and group to the app itself. App launches with previous data, but seems to have problems saving (writing) changes.
Extra info: Phone: Xiaomi Redmi Note 3 (SD)
ROM: Resurrection Remix v5.7.4, Android 6.x.x
As you can tell, I don't know much about how Android works. Please pardon me for the long post and thank you in advance.
ic2e said:
My phone is basically unbootable after a shutdown due to low battery. Things I tried:
1. Wipe System+Cache -> Flash ROM
(Result: Stuck at boot animation)
2. Wipe System+Data+Cache -> Flash ROM
(Result: Bootable)
3. Wipe System+Data+Cache -> Flash ROM -> Restore Data
(Result: Stuck at boot animation)
4. Wipe System+Data+Cache -> Flash ROM -> Restore Data -> Delete /data/system
(experiment)
(Result: Bootable system but Android warns system unstable till factory reset, Apps can launch but behave as if no previous state)
Can I conclude that there is something wrong with my data partition?
Strategy 1
What are the files I could try to minimally delete/modify to get it bookable and have my existing data intact? Or please guide me know how to trace to the problematic files/folders.
Strategy 2
I do have a TWRP Data partition backup before I did the various (dumb) experiments. If I were to start from scratch, how to I copy over /data/data (which I am guessing where all app's data is at) to restore the previous state?
I have tried to:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash and replace the /data/data folder, does not boot
Also tried:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash, boot.
4. Download a single app.
5. Went to TWRP and copy only the app's backup data folder to /data/data
6. Boot to system and launch app. Apps crashes.
7. I understand it has something to do with permissions and I have out of frustration, used an app to allow all actions (I believe a 777 chmod equivalent?) and set the owner and group to the app itself. App launches with previous data, but seems to have problems saving (writing) changes.
Extra info: Phone: Xiaomi Redmi Note 3 (SD)
ROM: Resurrection Remix v5.7.4, Android 6.x.x
As you can tell, I don't know much about how Android works. Please pardon me for the long post and thank you in advance.
Click to expand...
Click to collapse
use miflash to start fresh with miui, use miflashunlock to check if bootloader is unlocked properly, flash twrp, redownload the rom and gapps, start flashing through twrp
If you're flashing ROM, do not restore data.
Wipe system+data+cache+dalvik ,then flash ROM+gapps then reboot.
Don't restore anything from other backup